Thomas Simmons wrote:
> Last night five clients failed with the following error. These are
> clients that were successfully backed up Friday, with no change to any
> configs.
>
> 29-Aug 20:47 sioux-dir: auriga.2005-08-29_20.00.29 Fatal error:
> authenticate.c:99 Unable to authenticate with Storage daemon.
> Possible causes:
> Passwords or names not the same or
> Maximum Concurrent Jobs exceeded on the SD or
> SD networking messed up (restart daemon).
>
>
> Another Five clients failed with this error:
>
> 29-Aug 21:12 sioux-sd: sirius.2005-08-29_20.00.32 Fatal error:
> acquire.c:359 Wanted Volume "000002", but device "IBM-LTO2" (/
> dev/nst0) is busy writing on "000003" .
> 29-Aug 21:15 sirius-fd: sirius.2005-08-29_20.00.32 Fatal error:
> c:\cygwin\home\kern\bacula\k\src\win32\filed\../../filed/job.
> c:1597 Bad response to Append Data command. Wanted 3000 OK data
> , got 3903 Error append data
>
>
> Any ideas?
>
> Thanks,
> Thomas
Hello,
I have the same error "Unable to authenticate with Storage daemon"
randomly on our desktop computers. First of all I thought that the
source of the problem was that I use concurrent jobs.
But now I see that the problem occurs when three or more computers are
not online ( "Unable to connect to File Daemon" error) during the
backup, then the following (or the two following) jobs failed. Then, all
the remaining jobs succeed again if the computers are online.
Loïs
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
