On 01/21/16 12:10, Martin Simmons wrote:

>>> , got 2800 End Job TermCode=69 JobFiles=147756 ReadBytes=17353960553 
>>> JobBytes=17353960553 Errors=1 VSS=0 Encrypt=0 CommBytes=0 
>>> CompressCommBytes=0
>
> It is probably caused by this error on the fd:
>
>> 21-Jan 00:07 xxxxxx-fd JobId 1199: Error: bsock.c:221 Socket open error. 
>> proto=28 port=9103. ERR=Protocol not supported
>
> It looks like your configuration is specifying IPv6, but the client doesn't
> support it.

This is indeed true: bacula on FreeBSD is always compiled with IPv6 
support, but my kernel has IPv6 disabled.

However I feel a bit confused why the two would be related...
The "status" command gives this warning, but works.
Backups work too (again with this warning).
Why would it matter only on restores?



I also asked about this in the past and I was told it was harmless.
Is it a bug then?



In any case, I recompiled everything without IPv6 (by adding 
"--disable-ipv6" to the port's Makefile) and nothing changed:
I still get "Error: bsock.c:221 Socket open error. proto=28 port=9103. 
ERR=Protocol not supported" on status, backup and restore; the former 
two work properly anyway, while the third fails.




  bye & Thanks
        av.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users