Hi All,
I"m evaluating Bacula for a client. So far I like what I see, but I'm
having trouble adding a second (remote) client.
I am following the Brief Tutorial to become familar with Bacula and have
successfully set up the local machine backup and restores. However,
setting up a second client is giving me troubles.
I've followed the section in the Brief Tutorial entitled "Adding a
Second Client" which entails simply copying the bacula-fd binary and
bacula-fd.conf file from the bacula director machine to the client that
I want to back up. I've changed the name of the machine from the
director to my client in the bacula-fd.conf file as instructed in that
section.
However, when I try attempt to get the status of that client from the
director machine's bconsole, it cannot connect (mi01.fusion is the
remote machine that is giving me problems):
*status
Status available for:
1: Director
2: Storage
3: Client
4: All
Select daemon type for status (1-4): 3
The defined Client resources are:
1: mi01-fd
2: mi01.fusion
Select Client (File daemon) resource (1-2): 2
Connecting to Client mi01.fusion at xx.xx.xx.xx:9102
Failed to connect to Client mi01.fusion.
====
You have messages.
*
29-Oct 10:20 mi01-dir JobId 0: Fatal error: Unable to authenticate with
File daemon at "mi01.fusion.xxxx.xxx: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.
I apologize for the domain mame and IP address obsfucation but I do not
have authorization to post any significant network information to the
Internet.
I have read the AuthorizationErrors page, but as near as I can tell most
of these types of errors are differing passwords between the director
and the fd.conf files. Since I just copied the bacula-fd.conf file from
the working director machine to the remote client, the password is the same.
I have also verified that the concurrent jobs is set to 10 and there is
only one running at any given time during testing.
I have verified the network connectivity. The director machine can
resolve the second client's name and can also route to its IP correctly.
The director machine can also telnet to the client on port 9102 and the
FD picks up.
I have also verified that the bacula-fd daemon is indeed running on the
client:
[EMAIL PROTECTED] /]# ps ax | grep fd
16358 ? Ssl 0:00 bacula-fd
17936 pts/3 S+ 0:00 grep fd
[EMAIL PROTECTED] /]# telnet localhost 9102
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
^]
I can't seem to find a log anywhere that has more meaningful information
in it than 'cannot connect'. I suspect that I've done something wrong
with the client machine, but I don't know how to trace that down.
All I did on the second client was to copy the bacula-fd binary from the
director machine and the bacula-fd.conf file to the client machine. I
then made the necessary change to the bacula-fd.conf file as I indicated
above.
Can someone help me troubleshoot this issue further?
Thanks,
Jon
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
