[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#611607: marked as done (bacula: "setip" command in bconsole fails)

Your message dated Thu, 3 Mar 2011 11:53:27 +1100
with message-id <20110303005327.GA7996@master.debian.org>
and subject line Re: Bug#611607: Resolved
has caused the Debian Bug report #611607,
regarding bacula: "setip" command in bconsole fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

611607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611607
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: bacula
Version: 5.0.2-2.2
Severity: minor

I have a configured bconsole on a remote client and all seems to work,
however I cannot execute the setip command from the remote bconsole
despite having explicitly followed the instrction in the manual.

It seems someone else had this issue a year ago.

I won't cut and paste but my setup would be almost identical.

It doesn't show below, but I am using the sqlite versions of bacula,
although I can't see that could be relevant.

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bacula depends on:
ii  bacula-client               5.0.2-2.2    network backup, recovery and verif
ii  bacula-common               5.0.2-2.2+b1 network backup, recovery and verif
ii  bacula-server               5.0.2-2.2    network backup, recovery and verif

bacula recommends no packages.

Versions of packages bacula suggests:
pn  bacula-doc                    <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 5.0.2-2.2

On Thu, Mar 03, 2011 at 10:46:50AM +1100, David Maslen wrote:
>This was not a bug, and should be closed.
>For the benefit of others here is where I went wrong.
>In the Director conf and bconsole conf, you reference a name & password.
>If these match, then you can connect the bconsole to the director.
>I had been using the "name = bigmac-con" in both the director and
>bconsole configs, and couldn't use the 'setip' command, as I got
>permission denied. I could however connect and run other commands.
>If you read the manual,
>It specifically states "if the console name, provided on the Name =
>directive, is the same as a Client name, the user of that console is
>permitted to use the SetIP command"
>The Client name in my case was bigmac-fd, not bigmac-con.
>My confusion came as a connection can still be made as long as the
>Name directive matches at both ends, but can only use the SetIP
>command is it matches AND is the sames as the Client name.
>So changing the name in both the bconsole and director config files,
>made it work.

Thank you for your message.

--- End Message ---

Reply to: