The storage log shows no sign of any connection from the client (though it looks like you sent logs from two different jobs).
Does the problem affect all clients? Is 10.10.10.3 the correct IP address of distress? Is distress running some firewall (iptables etc)? You could try telnet distress 9103 on the client machine to see if that can connect (see https://technet.microsoft.com/en-us/library/cc771275(v=ws.10).aspx). __Martin >>>>> On Fri, 12 Jan 2018 10:32:10 -0800, Jerry Lowry said: > > Well, I recompiled the source for bacula 9.0.6 on the offending server but > it is still failing to work. I have started each of the processes with the > debug flag set at 100 and am attaching the output for each system ( > director, storage,client). It looks to me like the client gets started but > is not connecting to the storage daemon. Not sure why because I can ping > it from the client, it is not blocked by a firewall because it's on the > same subnet. The windows firewall is turned off as well. Hopefully, this > information will help figure out the problem. > centos 7.3 > mariadb 10.2.12 > bacula 9.0.6 > > thanks > > On Thu, Jan 11, 2018 at 2:08 PM, Jerry Lowry <michaiah2...@gmail.com> wrote: > > > Dan, > > Yes, bacula did not change at all. This bacula server is both director and > > storage. All of the clients are windows systems running the latest 64 bit > > release of community client ( 5.2.10). > > > > I am getting ready to rebuild bacula based on the new kernel and hoping > > this will fix the problem. I have already done a database check with the > > new version of MariaDB and the bacula database is fine for its point of > > view. > > > > jerry > > > > On Thu, Jan 11, 2018 at 11:51 AM, Dan Langille <d...@langille.org> wrote: > > > >> > On Jan 11, 2018, at 11:56 AM, Jerry Lowry <michaiah2...@gmail.com> > >> wrote: > >> > > >> > Hi, Last weekend I ran through a bunch of updates for my backup > >> server. Of the many updates it updated the kernel and MariaDB ( 10.2.8 -> > >> 10.2.12 ). I have recently upgraded bacula to 9.0.6. The problem is that > >> the following error: > >> > 10-Jan 20:36 distress-dir JobId 34724: Fatal error: Bad response to > >> Storage command: wanted 2000 OK storage > >> > , got 2902 Bad storage > >> > > >> > I also get errors saying that the client can not connect to the storage > >> server: > >> > > >> > 11-Jan 01:37 Denial-fd: BackupDenial.2018-01-11_00.05.01_44 Fatal > >> error: ../../lib/bnet.c:870 Unable to connect to Storage daemon on > >> distress.ACCOUNTING.EDT.LOCAL:9103. ERR=No error > >> > 11-Jan 01:38 distress-dir JobId 34726: Fatal error: Socket error on > >> Storage command: ERR=No data available > >> > 11-Jan 01:38 distress-dir JobId 34726: Fatal error: No Job status > >> returned from FD. > >> > > >> > nothing was changed in the config files, just the updates were > >> installed. I can ping the storage server from all of the clients. > >> > > >> > The jobs get to the point where they display "waiting for client" but > >> the jobs never complete. > >> > > >> > >> When you did those update, did you keep all bacula-dir and all bacula-sd > >> on the same exact version? > >> > >> The general rule for software versions is: > >> > >> bacula-dir = bacula-sd >= bacula-fd > >> > >> -- > >> Dan Langille - BSDCan / PGCon > >> d...@langille.org > >> > >> > >> > >> > >> > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
