Warning: Missing argument 2 for wpdb::prepare(), called in /home/content/s/u/l/sullego/html/cachengo/website/wp-content/plugins/wp-post-thumbnail/wppt.php on line 375 and defined in /home/content/s/u/l/sullego/html/cachengo/website/wp-includes/wp-db.php on line 992
Troubleshooting the connection between the client and director

Troubleshooting the connection between the client and director

On October 27, 2009, in FAQs, by admin

After installing the agent onto your client, regardless of the operating system, it’s generally a good idea to test the connection. This can be done both ways, the first being from the client to the director. The second test is from the director back to the client. Just because the first test passes, doesn’t mean […]

After installing the agent onto your client, regardless of the operating system, it’s generally a good idea to test the connection. This can be done both ways, the first being from the client to the director. The second test is from the director back to the client. Just because the first test passes, doesn’t mean the second should work. Here are some things to try.

  1. Once you’ve installed your agent software, launch the bwc-console, which can be found in Start=>All Programs=>Bacula.
  2. When the console initializes, it will automatically try to connect to the Director and should display some information such as status. If you wish, you can run status dir to get the status again. The output should look as follows:

    Cachengo-104C-dir Version: 3.0.3 (18 October 2009) x86_64-unknown-linux-gnu suse 11
    Daemon started 27-Oct-09 15:36, 0 Jobs run since started.
    Heap: heap=282,624 smbytes=68,749 max_bytes=69,634 bufs=230 max_bufs=238

  3. If the console is not connecting to the Director, then chances are good that the bwx-console.conf file is improperly configured. Most of the time the issue is the password is improperly set. But the IP address of the Director could be wrong. Or the Director name may be missing the -dir suffix too. Double check these values.
  4. To check whether the client is properly configured, type status client. You may have several clients configured. Be sure to select the right one from the menu option. If all is working well, you will see something as follows:
    Connecting to Client windemo3-fd at windemo3:9102

    windemo3-fd Version: 3.0.2 (18 July 2009) VSS Linux Cross-compile Win32
    Daemon started 27-Oct-09 16:29, 0 Jobs run since started.
    Heap: heap=0 smbytes=12,906 max_bytes=13,028 bufs=53 max_bufs=54
    Sizeof: boffset_t=8 size_t=4 debug=0 trace=1

    If the client is not configured properly, then you will very likely see the following:

    Connecting to Client windemo3-fd at windemo3:9102
    Failed to connect to Client windemo3-fd.
    ====
    27-Oct 20:19 Cachengo-104C-dir JobId 0: Fatal error: Unable to authenticate with File daemon at “windemo3: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/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION003760000000000000000 for help.

    If you’re receiving this message, then chances are very good you’ve mis-configured the bacula-fd.conf file on the client. In this case, the file is configured with the following Director entry:

    Director {
    Name = cachengo-104C-dir
    Password = “demo411″
    }

    On the surface, everything looks fine with this file. However, the Director name is actually Cachengo-104C. Notice the name has a lower case letter as opposed to the upper case one.

  5. Assuming these are all set properly, you may have a firewall problem, which is blocking ports 9101 and 9102. You can always try to test this by opening up a telnet program and type telnet [ip address of client] 9102. You should receive some login confirmation such as:

    Trying 10.0.1.16…
    Connected to 10.0.1.16.
    Escape character is ‘^]’.

    If you don’t, then there’s a good chance your problem is actually firewall related.

 

Comments are closed.

Copyright © 2010 Cachengo, Inc. All rights reserved.