I'm seeing a series of errors in the syslog.

Debian 9, Bacula v9.2.2


Dir/sd/fd are all on the same server with storage on a local NAS.


A recent syslog sample is below though they go way back and I hadn't noticed.


Backups are running normally without errors.


What would some things be to check the origin of these errors?

....

Sep 22 10:11:12 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=0.
Sep 22 10:21:04 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=0.
Sep 22 10:21:12 HOMESERVER bacula-fd: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:34012". Maximum
permitted 1000000. Terminating connection.
Sep 22 10:21:12 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=-4.
Sep 22 11:50:48 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=0.
Sep 22 11:50:48 HOMESERVER bacula-sd: dircmd.c:172 Connection request
from client failed.
Sep 22 11:50:53 HOMESERVER bacula-dir: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:41558". Maximum
permitted 1000000. Terminating connection.
Sep 22 11:50:53 HOMESERVER bacula-fd: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:46718". Maximum
permitted 1000000. Terminating connection.
Sep 22 11:50:53 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=-4.
Sep 22 11:50:53 HOMESERVER bacula-sd: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:46789". Maximum
permitted 1000000. Terminating connection.
Sep 22 11:50:53 HOMESERVER bacula-sd: dircmd.c:172 Connection request
from client failed.
Sep 22 22:38:36 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=0.
Sep 22 22:38:36 HOMESERVER bacula-sd: dircmd.c:172 Connection request
from client failed.
Sep 22 22:38:41 HOMESERVER bacula-sd: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:49352". Maximum
permitted 1000000. Terminating connection.
Sep 22 22:38:41 HOMESERVER bacula-sd: dircmd.c:172 Connection request
from client failed.
Sep 22 22:38:41 HOMESERVER bacula-dir: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:49433". Maximum
permitted 1000000. Terminating connection.
Sep 22 22:38:41 HOMESERVER bacula-fd: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:60241". Maximum
permitted 1000000. Terminating connection.
Sep 22 22:38:41 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=-4.
Sep 23 09:44:47 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=0.
Sep 23 09:44:47 HOMESERVER bacula-sd: dircmd.c:172 Connection request
from client failed.
Sep 23 09:44:53 HOMESERVER bacula-fd: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:38352". Maximum
permitted 1000000. Terminating connection.
Sep 23 09:44:53 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=-4.
Sep 23 09:44:53 HOMESERVER bacula-sd: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:60854". Maximum
permitted 1000000. Terminating connection.
Sep 23 09:44:53 HOMESERVER bacula-sd: dircmd.c:172 Connection request
from client failed.
Sep 23 10:37:37 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=0.
Sep 23 10:37:37 HOMESERVER bacula-sd: dircmd.c:172 Connection request
from client failed.
Sep 23 10:37:45 HOMESERVER bacula-fd: bsock.c:517 Packet
size=121984032 too big from "client:192.168.1.30:36351". Maximum
permitted 1000000. Terminating connection.
Sep 23 10:37:45 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got
bad command from 192.168.1.30. Len=-4.
Sep 23 10:37:45 HOMESERVER bacula-sd: bsock.c:517 Packet
size=121984032 too big from

...

Thanks
Chris Wilkinson
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to