Bacula-users

Re: [Bacula-users] Fatal error: Bad response from stored to open command

2013-02-11 07:03:19
Subject: Re: [Bacula-users] Fatal error: Bad response from stored to open command
From: Antony Mayi <antonymayi AT yahoo DOT com>
To: Antony Mayi <antonymayi AT yahoo DOT com>, Bacula List <Bacula-users AT lists.sourceforge DOT net>
Date: Mon, 11 Feb 2013 11:59:56 +0000 (GMT)
just for case anyone runs into similar problem - the issue was the firewall between clients and storage daemon was timing out the inactive tcp session after certain period. what happens is when the job starts it establishes the tcp session with the storage daemon and then it starts the scripts on the client. only when the script is finished the data are sent over the tcp. if the script takes too long the tcp stays established but not active for the whole period so it can time out on the firewall and later when bacula attempts to use the tcp which it thinks is still established it fails.

I was trying to use "Heartbeat Interval" together with tweaking tcp keepalive time on system level but that doesn't seem to be enough for my firewall (that's another problem though)...

cheers,
Antony.


From: Antony Mayi <antonymayi AT yahoo DOT com>
To: Bacula List <Bacula-users AT lists.sourceforge DOT net>
Sent: Tuesday, 29 January 2013, 8:14
Subject: [Bacula-users] Fatal error: Bad response from stored to open command

Hi,

I started getting this error for some of the bacula jobs. This only happened after I redesigned our network moving the servers behind NAT - bacula storage daemon is remote so the traffic sent to storage daemon is now NATted. As I said it still works fine as before for most of the jobs but some of them strangely fail with the error in $subj. Interestingly the common thing for these jobs is they all have defined RunScripts so I would say only jobs with RunScripts are affected actually.

Running bacula 5.0.0.

This is an example job affected:

Job {
  Name = "MonitorBackup"
  JobDefs = "BasicTemplate"
  Client = monitor1
  FileSet = "MonitorData"
  RunScript {
    RunsWhen = Before
    RunsOnClient = Yes
    Command = "/usr/bin/mysqldump -u root -r /var/tmp/monitor.sql monitor"
  }
  RunScript {
    RunsWhen = After
    RunsOnClient = Yes
    Command = "/bin/rm /var/tmp/monitor.sql"
  }
}


This is the error message I get from the failing job:

27-Jan 23:26 bacula-dir JobId 634: Start Backup JobId 634, Job=MonitorBackup.2013-01-27_23.05.00_47
27-Jan 23:26 bacula-dir JobId 634: Using Device "FileStorage"
27-Jan 23:26 mgr1 JobId 634: DIR and FD clocks differ by -17 seconds, FD automatically compensating.
27-Jan 23:26 mgr1 JobId 634: ClientBeforeJob: run command "/usr/bin/mysqldump -u root -r /var/tmp/monitor.sql monitor"
27-Jan 23:53 mgr1 JobId 634: Fatal error: Bad response from stored to open command
27-Jan 23:54 bacula-dir JobId 634: Error: Bacula bacula-dir 5.0.0 (26Jan10): 27-Jan-2013 23:54:16
  Build OS:               x86_64-unknown-linux-gnu redhat (Final)
  JobId:                  634
  Job:                    MonitorBackup.2013-01-27_23.05.00_47
  Backup Level:           Differential, since=2013-01-21 23:26:49
  Client:                 "monitor1" 2.4.4 (28Dec08) x86_64-redhat-linux-gnu,redhat,Enterprise release
  FileSet:                "MonitorData" 2012-12-10 23:05:00
  Pool:                   "DiffBackups" (From Job DiffPool override)
  Catalog:                "BaculaDB" (From Client resource)
  Storage:                "Offsite" (From Job resource)
  Scheduled time:         27-Jan-2013 23:05:00
  Start time:             27-Jan-2013 23:38:13
  End time:               27-Jan-2013 23:54:16
  Elapsed time:           16 mins 3 secs
  Priority:               10
  FD Files Written:       0
  SD Files Written:       0
  FD Bytes Written:       0 (0 B)
  SD Bytes Written:       0 (0 B)
  Rate:                   0.0 KB/s
  Software Compression:   None
  VSS:                    no
  Encryption:             no
  Accurate:               no
  Volume name(s):         
  Volume Session Id:      113
  Volume Session Time:    1358767818
  Last Volume Bytes:      43,274,233 (43.27 MB)
  Non-fatal FD errors:    0
  SD Errors:              0
  FD termination status:  Error
  SD termination status:  Error
  Termination:            *** Backup Error ***

I found similar problems on the internet but without any clarification or hints towards a resolution. Any ideas where to look next?

thank you,
Antony.


------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, _javascript_ and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users


------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Bacula-users] Fatal error: Bad response from stored to open command, Antony Mayi <=