>Hello, > >Please always copy the list. > >Unfortunately, you didn't supply any of the basic info requested on the Bugs >page of the web site, so I cannot give you much help. See attached files, sorry they must have gotten stripped off by the work filters from where I sent this. :(
>My two suggestsions: >1. Read in detail the ReleaseNotes -- most likely you will find the key there I couldn't locate anything that appears to apply to this problem unfortunately, I'm already using the Autochanger statement with 1.36.3 successfully. >2. From the little info I have, it appears to me that you might be running on >a 64 bit machine, and thus running into what appears to be a compiler >problem. If this is the case, the ReleaseNotes supply the solution -- turn >off all optimization. No, 32 bit Linux, config.out is attached. 1.36.3 compiles and runs just fine with the same default config setup. I've got kernel version 2.6.12.2 on a Pentium-III 933MHz CPU. Hopefully this will help out with any ideas on a solution. George >On Monday 02 January 2006 14:37, [EMAIL PROTECTED] wrote: >> Kern: >> >> Sorry to bother you with this directly, but I've posted both to the >> list with no response since 12/29, though Wolfgang did give me a patch >> for mtx-changer, it is not functioning at this time from within >> bconsole. The system worked normally and well under 1.36.3 however >> there are major issues with 1.38.3 BETA. Config files are the same for >> both versions - copied them from a backup directory so there is no >> question on typos. >> >> First Issue: >> ============ >> >> Command line tests pass fine. When I attempt to do an update slots >> command I get the following error: >> >> *update >> Update choice: >> 1: Volume parameters >> 2: Pool from resource >> 3: Slots from autochanger >> Choose catalog item to update (1-3): 3 >> >> The defined Storage resources are: >> 1: File >> 2: DDS-3-Drive0 >> 3: DDS-3-Drive1 >> 4: Exabyte-Drive >> Select Storage resource (1-4): 2 >> >> Connecting to Storage daemon DDS-3-Drive0 at 192.168.1.1:9103 ... >> 3908 Error scanning autocharger list command: autochanger slots >> DDS-3-Drive0 >> >> Device "DDS-3-Drive0" has 0 slots. >> No slots in changer to scan. >> >> Second Issue: >> ============= >> I simply CANNOT get any type of backup to run, be it backup to file or >> tape from either the "local" linux box that is running bacula to a >> pair of Windows boxes that are clients (using the 1.38.3 BETA Windows >> Client) one is XPSP2 and other is Windows Server 2003 SP1 both with >> all the latest patches applied. Here are the errors I'm seeing: >> >> 02-Jan 00:05 eagle-dir: No prior Full backup Job record found. >> 02-Jan 00:05 eagle-dir: No prior or suitable Full backup found. Doing >> FULL backup. >> 02-Jan 00:05 eagle-dir: Start Backup JobId 12, >> Job=Client1.2006-01-02_00.05.09 >> 02-Jan 00:05 eagle-dir: Client1.2006-01-02_00.05.09 Fatal error: >> Storage daemon didn't accept Device "FileStorage" because: >> 02-Jan 00:05 eagle-dir: Client1.2006-01-02_00.05.09 Error: >> bnet.c:257 Read error from Storage daemon:192.168.1.1:9103: >> ERR=Connection reset by peer >> 02-Jan 00:05 eagle-dir: Client1.2006-01-02_00.05.09 Error: Bacula >> 1.38.3 (22Dec05): 02-Jan-2006 00:05:19 >> JobId: 12 >> Job: Client1.2006-01-02_00.05.09 >> Backup Level: Full (upgraded from Incremental) >> Client: "eagle-fd" i686-pc-linux-gnu,unknown,unknown >> FileSet: "Full Set" 2005-12-29 00:05:07 >> Pool: "Default" >> Storage: "File" >> Scheduled time: 02-Jan-2006 00:05:00 >> Start time: 02-Jan-2006 00:05:12 >> End time: 02-Jan-2006 00:05:19 >> Priority: 10 >> FD Files Written: 0 >> SD Files Written: 0 >> FD Bytes Written: 0 >> SD Bytes Written: 0 >> Rate: 0.0 KB/s >> Software Compression: None >> Volume name(s): >> Volume Session Id: 4 >> Volume Session Time: 1136039809 >> Last Volume Bytes: 0 >> Non-fatal FD errors: 1 >> SD Errors: 0 >> FD termination status: >> SD termination status: >> Termination: *** Backup Error *** >> >> >> 02-Jan 00:10 eagle-dir: Start Backup JobId 13, >> Job=BackupCatalog.2006-01-02_00.10.06 >> 02-Jan 00:10 eagle-dir: BackupCatalog.2006-01-02_00.10.06 Fatal error: >> Storage daemon didn't accept Device "FileStorage" because: >> 02-Jan 00:10 eagle-dir: BackupCatalog.2006-01-02_00.10.06 Error: >> bnet.c:426 Write error sending 23 bytes to Storage >> daemon:192.168.1.1:9103: ERR=Broken pipe >> 02-Jan 00:10 eagle-dir: BackupCatalog.2006-01-02_00.10.06 Error: >> Bacula 1.38.3 (22Dec05): 02-Jan-2006 00:10:30 >> JobId: 13 >> Job: BackupCatalog.2006-01-02_00.10.06 >> Backup Level: Full >> Client: "eagle-fd" i686-pc-linux-gnu,unknown,unknown >> FileSet: "Catalog" 2005-12-29 00:10:07 >> Pool: "Default" >> Storage: "File" >> Scheduled time: 02-Jan-2006 00:10:01 >> Start time: 02-Jan-2006 00:10:09 >> End time: 02-Jan-2006 00:10:30 >> Priority: 11 >> FD Files Written: 0 >> SD Files Written: 0 >> FD Bytes Written: 0 >> SD Bytes Written: 0 >> Rate: 0.0 KB/s >> Software Compression: None >> Volume name(s): >> Volume Session Id: 5 >> Volume Session Time: 1136039809 >> Last Volume Bytes: 0 >> Non-fatal FD errors: 1 >> SD Errors: 0 >> FD termination status: >> SD termination status: >> Termination: *** Backup Error *** >> >> >> >> 02-Jan 01:00 eagle-dir: Start Backup JobId 15, >> Job=Apollo-Set-A.2006-01-02_01.00.24 >> 02-Jan 01:00 eagle-dir: Apollo-Set-A.2006-01-02_01.00.24 Fatal error: >> Storage daemon didn't accept Device "Exabyte-Drive" because: >> 02-Jan 01:00 eagle-dir: Apollo-Set-A.2006-01-02_01.00.24 Error: >> bnet.c:257 Read error from Storage daemon:192.168.1.1:9103: >> ERR=Connection reset by peer >> 02-Jan 01:00 eagle-dir: Apollo-Set-A.2006-01-02_01.00.24 Error: Bacula >> 1.38.3 (22Dec05): 02-Jan-2006 01:00:29 >> JobId: 15 >> Job: Apollo-Set-A.2006-01-02_01.00.24 >> Backup Level: Full >> Client: "apollo-fd" Windows Server 2003,MVS,NT >> 5.2.3790 >> FileSet: "Apollo-Full" 2006-01-02 01:00:26 >> Pool: "Exabyte-Drive-Set-A" >> Storage: "Exabyte-Drive" >> Scheduled time: 02-Jan-2006 01:00:24 >> Start time: 02-Jan-2006 01:00:26 >> End time: 02-Jan-2006 01:00:29 >> Priority: 12 >> FD Files Written: 0 >> SD Files Written: 0 >> FD Bytes Written: 0 >> SD Bytes Written: 0 >> Rate: 0.0 KB/s >> Software Compression: None >> Volume name(s): >> Volume Session Id: 6 >> Volume Session Time: 1136039809 >> Last Volume Bytes: 0 >> Non-fatal FD errors: 1 >> SD Errors: 0 >> FD termination status: >> SD termination status: >> Termination: *** Backup Error *** >> >> >> DO you have any suggestions on how to fix these problems and get >> backups running again or should I go back to 1.36.3 for now? >> >> Thank you very much, >> >> ===[George R. Kasica]=== +1 262 677 0766 >> President +1 206 374 6482 FAX >> Netwrx Consulting Inc. Jackson, WI USA >> http://www.netwrx1.com >> [EMAIL PROTECTED] >> ICQ #12862186 ===[George R. Kasica]=== +1 262 677 0766 President +1 206 374 6482 FAX Netwrx Consulting Inc. Jackson, WI USA http://www.netwrx1.com [EMAIL PROTECTED] ICQ #12862186
bacula-dir.conf
Description: Binary data
bacula-fd.conf
Description: Binary data
bacula-sd.conf
Description: Binary data
bconsole.conf
Description: Binary data
config.out
Description: Binary data
