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.

 

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.

#

 

Paul E. Binkley

Objective Interface Systems, Inc.

220 Spring St., Suite 530

Herndon, VA 20170

Tel: 703.295.6528

Fax: 703.296.6501

paul.bink...@ois.com

http://www.ois.com

 

***************************************************************

This email contains information confidential and proprietary

to Objective Interface Systems, Inc. and should not be

disclosed to third parties without written permission from

Objective Interface Systems, Inc. If this was delivered to

someone other than the intended recipient by mistake please

notify  <mailto:le...@ois.com> le...@ois.com and remove any remaining copies
of this

email.

***************************************************************

 

------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to