Thanks for your reply.
Well… I don’t want to experience situation when in case of disaster I cannot restore system because „something else in the job didn't go so well”.
I would like to know what exactly didn’t go so well to avoid this in future.
Unfortunately log file doesn’t show more than email report.
Also I doubt that ClientRunBeforeJob could cause it, because this error occures after ClientRunBeforeJob is done and shortly after Generate VSS snapshot is
done:
2011-04-05 03:35:56 server1-fd JobId 259: Generate VSS snapshots. Driver="VSS Vista", Drive(s)="C"
2011-04-05 03:53:44 server1-fd JobId 259: Error: /home/kern/bacula/k/bacula/src/lib/bsock.c:346 Socket is terminated=1 on call to client:10.2.2.2:36387
2011-04-05 03:53:52 server1-fd JobId 259: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
……
……
Thanks anyway..
Edgars
From: Tor Willy Austerslått [mailto:twa AT sesamdata DOT no]
Sent: Tuesday, April 05, 2011 1:54 PM
To: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] bsock.c:346 Socket is terminated=1 on call to client
On 5. apr. 2011, at 12.01, Edgars Mazurs wrote:
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK -- with warnings
So I am not sure whether backup went fine or not!? And what causes this error:
It means exactly what it says: the backup is OK, but something else in the job didn't go so well. In my (limited) experience this is usually caused by a RunBeforeJob or RunAfterJob script which throws an error but still exits with success.
Look for the job ID in the logfile (/var/log/bacula/log perhaps?) to find exactly what caused the warning.