Re: [Bacula-users] Problems with tape drive showing busy.

[Bill M. <wm...@co...>]

On Wed, 26 Apr 2006 14:17:26 -0600
Chuck Bunn <chu...@ne...> wrote:

> Hi,
> 
> I have done a './bacula stop' and a 'killall bconsole'is there something 
> else I have to do before running './bconsole'. Also I am using putty to 
> control bconsole through an SSH connection. I have tried mapping a port 
> to 9101 via Putty but that did not help. Does bconsole only work on the 
> local machine. If I issue a './bconsole' via putty will this fail since 
> putty is running on a remote machine? Is there another way to add tape 
> jobs besides bconsole? (I will be using bacula-web for management since 
> the local user refuses to use a command line, I have have bacula-web 
> running through a SSH tunnel but it does not show anything since I have 
> not set any jobs up. 'test.php' works fine). How do people manage bacula 
> remotely???

You would do well to more carefully word your questions.  That previous
paragraph made me dizzy.

Here's the scoop:
bacula-dir is the master Bacula process.  This is what bconsole talks
to.  bconsole can be running anywhere you like as long as 2 criteria
are met:
1) bacula-dir and bconsole have the correct shared secret so they
   can communicated
2) There are no network issues between the two (such as firewalls)
   that would prevent the communications.
bconsole needs to connect to bacula-dir on port 9101, so you can use
that to program your firewalls, if needed.

I recommend the following testing procedure:
1) Ensure that bacula-dir is actually running.  Using top(1) or ps(1)
   on POSIX systems will show this.
2) Ensure that the bacula-dir.conf and the bconsole.conf files have
   the same shared secret for console access - check to ensure that
   names, ports, and IP addresses match as well.
3) On the machine that's running bacula-dir, attempt to connect with
   bconsole.  If this fails, use "bconsole -d100".  If the problem
   isn't obvious from the debugging output, cut/paste the output to
   an email to this list.

> I have tried telneting through a SSH tunnel but nothing happens it just 
> sits there - just like bconsole... I am going to head over to the client 
> and try it locally... but there has to be a way to do this remotely - 
> gas is just too expensive!

Take a step back and walk forward one step at a time, unless you want
to go insane.  Before you add all sorts of tunnels and port-forwards
into the mix, make sure the basics are correct.

-- 
Bill Moran
Collaborative Fusion Inc.