Hi,

19.11.2009 21:34, Paul Binkley wrote:
> 
> 
> Greetings,
> 
>  
> 
> I am having an issue in that the director cannot communicate with a 
> particular file daemon. The file daemon in question is running on the 
> same machine as the storage daemon.
> 
>  
> 
> If the file daemon is not running, the director has no problem with any 
> other file daemons, but if the fd in question is running, the director 
> can communicate with other clients only until a failed try with the 
> problem fd.

Looks interesting :-)

Can you check the versions of the programs involved?

The ones running on the same machine need to be the exact same version 
in particular.

Cheers,

Arno

>  
> 
> The included console output shows this anomaly. Notice that the estimate 
> works fine for 2 different clients, then fails when trying to access the 
> “bad” client, then can no longer access the previously good clients.
> 
>  
> 
> Also possibly of note is the fact that the Fatal Error line shows that 
> the director seems to be stuck on the bad fd ( xxx.xxx.0.70:9102) after 
> the original failure…
> 
>  
> 
> Thanks for any suggestions.
> 
>  
> 
> # estimate
> 
> …
> 
> Using Catalog "MyCatalog"
> 
> Connecting to Client bacula-fd at xxx.xxx.0.71:9102
> 
> 2000 OK estimate files=197593 bytes=20,445,781,245
> 
> # estimate
> 
> …
> 
> Using Catalog "MyCatalog"
> 
> Connecting to Client MISD620-fd at xxx.xxx.61.7:9102
> 
> 2000 OK estimate files=100996 bytes=40,012,706,471
> 
> # estimate
> 
> …
> 
> Using Catalog "MyCatalog"
> 
> Connecting to Client remotefs-fd at xxx.xxx.0.70:9102
> 
> Failed to connect to Client.
> 
> 19-Nov 15:24 bacula-dir JobId 0: Fatal error: File daemon at " 
> xxx.xxx.0.70:9102" rejected Hello command
> 
> # estimate
> 
> …
> 
> Using Catalog "MyCatalog"
> 
> Connecting to Client bacula-fd at xxx.xxx.0.71:9102
> 
> Failed to connect to Client.
> 
> 19-Nov 15:25 bacula-dir JobId 0: Fatal error: Unable to authenticate 
> with File daemon at " xxx.xxx.0.70:9102". Possible causes:
> 
> Passwords or names not the same or
> 
> Maximum Concurrent Jobs exceeded on the FD or
> 
> FD networking messed up (restart daemon).
> 
> Please see http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors 
> for help.
> 
> # estimate
> 
> …
> 
> Using Catalog "MyCatalog"
> 
> Connecting to Client MISD620-fd at xxx.xxx.61.7:9102
> 
> Failed to connect to Client.
> 
> 19-Nov 15:25 bacula-dir JobId 0: Fatal error: Unable to authenticate 
> with File daemon at " xxx.xxx.0.70:9102". Possible causes:
> 
> Passwords or names not the same or
> 
> Maximum Concurrent Jobs exceeded on the FD or
> 
> FD networking messed up (restart daemon).
> 
> Please see http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors 
> for help.
> 

-- 
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users