users@lists.sourceforge.net
Objet : Re: [Bacula-users] Broken Pipe messages
Hi,
well I don't know wich Job is the culprit. JobId 0 can't be - I have
already 48k jobs and this problem appeared just a few days ago.
However the director is configured with this:
FDConnectTimeout = 3 min
SDCon
t;
> Max wait time
>
> I have maybe an idea..
>
> François
>
> -Message d'origine-
> De : Stefan Sorin Nicolin [mailto:bac...@nicolinux.org]
> Envoyé : lundi 30 mars 2009 13:14
> À : Bacula-users@lists.sourceforge.net
> Objet : [Bacula-users] Broken Pipe
Objet : [Bacula-users] Broken Pipe messages
Hi,
I am getting more and more messages like this although the Bacula jobs
do finish fine:
29-Mär 03:16 db-backup-dir JobId 0: Error: bsock.c:306 Write error
sending 79 bytes to client:192.168.1..236:36131: ERR=Broken pipe
The IP mentioned in the messag
Hi,
I am getting more and more messages like this although the Bacula jobs
do finish fine:
29-Mär 03:16 db-backup-dir JobId 0: Error: bsock.c:306 Write error
sending 79 bytes to client:192.168.1..236:36131: ERR=Broken pipe
The IP mentioned in the message ist the one from the vServer where the
