Yes i think that is most likely the reason. The IP in question is a machine that runs a network monitor. I wasn't aware that it was sending packets to the Bacula ports and see no reason why it should since it isn't a port scanner. It just pings and checks a webserver on port 80 is up.
However, I'll turn it off and see if the errors stop. Thanks to all for those pointers. Regards Chris Wilkinson On Wed, 25 Sep 2019, 10:22 p.m. David Brodbeck, <brodb...@math.ucsb.edu> wrote: > > > On Wed, Sep 25, 2019 at 1:37 AM Radosław Korzeniewski < > rados...@korzeniewski.net> wrote: > >> Hello, >> >> pon., 23 wrz 2019 o 12:26 Chris Wilkinson <winstonia...@gmail.com> >> napisał(a): >> >>> >>> Sep 22 10:11:12 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got bad >>> command from 192.168.1.30. Len=0. >>> >>> Something/someone at 192.168.1.30 is connecting to your (I see all your >> Bacula Components) server and is trying to chat with Bacula but is not >> using a bacula network protocol. So the errors. >> >> You have to verify what/who it is and disable it. >> > > If you're using a network monitoring system, like Observium or Big > Brother, that's a likely culprit. > > -- > David Brodbeck > System Administrator, Department of Mathematics > University of California, Santa Barbara > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
