Bacula Error 3903
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central Forums Forum Index » Bacula » Bad response to Append Data command. The time now is Sat Oct 01, 2016 2:49 pm View previous topic | View next topic Page 1 of 2 Goto page 1, 2Next Bad response to Append Data command. Author Message Guest Bad response to Append Data command. Evening... I'm repeatedly seeing the following messages cancelling my backup jobs: ============================== 03-Nov 08:11 torf-dir: Start Backup JobId 206, Job=BackupCatalog.2005-11-03_08.10.00 03-Nov 08:13 torf-sd: BackupCatalog.2005-11-03_08.10.00 Fatal error: device.c:317 Unable to open device /dev/nst0. ERR=dev.c:289 stored: unable to open device /dev/nst0: ERR=Input/output error 03-Nov 08:13 torf-fd: BackupCatalog.2005-11-03_08.10.00 Fatal error: job.c:1665 Bad response to Append Data command. Wanted 3000 OK data , got 3903 Error append data 03-Nov 08:13 torf-dir: BackupCatalog.2005-11-03_08.10.00 Error: Bacula 1.36.2 (28Feb05): 03-Nov-2005 08:13:26 ============================== The storage daemon should be able to open /dev/nst0. "lsof" shows no other processes accessing it. So I don't see a reason why Bacula is unable to open that device. Once I saw that error message (from a status email telling me the backup has failed) all subsequent backups will fail with the same error. But when I restart both the director and the storage daemon I can suddenly run a successful backup. This is my Device configuration in the storage daemons config file: Device { Name = Streamer Media Type = DDS-3 Archive Device = /dev/nst0 AutomaticMount = yes; AlwaysOpen = no; RemovableMedia = yes; RandomAcce
from GoogleSign inHidden fieldsSearch for groups or messages
jobs that are run nightly, allowing Bacula to run multiple jobs at once (one https://www.mail-archive.com/bacula-users@lists.sourceforge.net/msg27976.html on each drive). Here are my configuration files & log: http://esweb.mcc.edu/~marc.smith/bacula/ http://bacula-users.narkive.com/g9NhVpZQ/bad-response-to-append-data-command This seems to happen somewhat randomly, usually happens to a few of my jobs each night. Other nights it doesn't happen to any. I can't really seem to reproduce the problem reliably, I happened to get lucky this time when I started 2 jobs. Here bacula error are the errors: 27-Nov 17:20 escabot-fd JobId 7784: Fatal error: job.c:1811 Bad response to Append Data command. Wanted 3 000 OK data , got 3903 Error append data 27-Nov 17:20 escabot-sd JobId 7784: Fatal error: 3992 Bad autochanger "load slot 10, drive 1": ERR=Child died from signal 15: Termination. Results=source Element Address 4105 is Empty Program killed bacula error 3903 by Bacula watchdog (timeout) 27-Nov 17:20 escabot-sd JobId 7783: 3301 Issuing autochanger "loaded? drive 0" command. 27-Nov 17:20 escabot-dir JobId 7784: Error: Bacula escabot-dir 2.2.6 (10Nov07): 27-Nov-2007 17:20:07 Build OS: i686-pc-linux-gnu gentoo JobId: 7784 Job: sun_squid_data.2007-11-27_17.12.04 Backup Level: Differential, since=2007-11-25 16:38:02 Client: "escabot-fd" 2.2.6 (10Nov07) i686-pc-linux-gnu,gentoo, FileSet: "sun_snap-squid_data" 2007-07-26 09:36:19 Pool: "Daily" (From Job resource) Storage: "SpectraLogicT50" (From Job resource) Scheduled time: 27-Nov-2007 17:12:20 Start time: 27-Nov-2007 17:14:47 End time: 27-Nov-2007 17:20:07 Elapsed time: 5 mins 20 secs Priority: 22 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 Volume name(s): Volume Session Id: 2 Volume Session Time: 1196201503 Last Volume Bytes: 692,129,636,352 (692.1 GB) Non-fatal FD errors: 0 SD Errors: 0 FD termination status: Error SD termination status: Error Termination: *** Backup Error *** 27-Nov 17:20 escabot-sd JobId 7783: 3302 Autochanger "loaded? drive 0", result is Slot 10. 27-Nov 17:20 escabot-sd JobId 7783: Error: Autoc
went through the manuals, and everything seems to workfine. I started backup job and it looked very good. After the testrun, I changed my bacula-dir.conf to add another client and changewhat has to be backed up. After i made those changes as soon I willrun a backup I get the following message. The same message appears ifI use my old files.I hope someone can help me. If you need more information let me know.RobertJob started. JobId=4409-Oct 11:48 server1-dir: Start Backup JobId 44, Job=Client1.2006-10-09_11.48.5609-Oct 11:49 server1-sd: 3301 Issuing autochanger "loaded drive 0" command.09-Oct 11:49 server1-sd: 3302 Autochanger "loaded drive 0", result:nothing loaded.09-Oct 11:49 server1-sd: 3304 Issuing autochanger "load slot 1, drive0" command.09-Oct 11:49 server1-fd: Client1.2006-10-09_11.48.56 Fatal error:job.c:1617 Bad response to Append Data command. Wanted 3000 OK data, got 3903 Error append data09-Oct 11:49 server1-sd: Client1.2006-10-09_11.48.56 Fatal error: 3992Bad autochanger "load slot 1, drive 0": ERR=Child exited with code 1.09-Oct 11:49 server1-dir: Client1.2006-10-09_11.48.56 Error: Bacula1.38.11 (28Jun06): 09-Oct-2006 11:49:00JobId: 44Job: Client1.2006-10-09_11.48.56Backup Level: Incremental, since=2006-10-06 08:35:44Client: "server1-fd" i686-redhat-linux-gnu,redhat,FileSet: "Full Set" 2006-10-05 09:49:48Pool: "Default"Storage: "VXA2"Scheduled time: 09-Oct-2006 11:48:55Start time: 09-Oct-2006 11:49:00End time: 09-Oct-2006 11:49:00Elapsed time: 0 secsPriority: 100FD Files Written: 0SD Files Written: 0FD Bytes Written: 0 (0 B)SD Bytes Written: 0 (0 B)Rate: 0.0 KB/sSoftware Compression: NoneVolume name(s):Volume Session Id: 3Volume Session Time: 1160414803Last Volume Bytes: 14,357,017,975 (14.35 GB)Non-fatal FD errors: 0SD Errors: 0FD termination status: ErrorSD termination status: ErrorTermination: *** Backup