Yup, autochanger passed the tests. Since it works when I manually start the daemon, it's not really permission issue no? I think I'll try changing group setting anyway.
BTW, great article! I've been following your page closely for my bacula project and it's been a great help. Thanks!
Joe
On 4/6/06, Dan Langille <[EMAIL PROTECTED]> wrote:
On 6 Apr 2006 at 14:52, Joe Park wrote:
> Hello,
>
> I've been testing bacula for awhile and could not figure out this problem.
> Following is my environment --
>
> bacula ver: 1.38.6
> OS: FreeBSD 6.0
> DB: postgresql 8.1.3
Same here.
> Changer/Tapedrive: Dell PowerVault 122T
>
> When I try something like "label" after boot up, autochanger throws error,
> as if it does not have correct permission for autochanger device --
>
>
> Connecting to Director localhost:9101 1000 OK: localhost-dir Version:
> 1.38.6(28 March 2006) Enter a period to cancel a command.
> *label
> Using default Catalog name=MyCatalog DB=bacula The defined Storage resources
> are:
> 1: File
> 2: DellPowervault_122T
> Select Storage resource (1-2): 2
> Connecting to Storage daemon DellPowervault_122T at 192.168.3.114:9103 ...
> Enter new Volume name: TestVol04
> Enter slot (0 or Enter for none): 1
> Automatically selected Pool: Default Connecting to Storage daemon
> DellPowervault_122T at 192.168.X.XXX:9103 ...
> Sending label command for Volume "TestVol04" Slot 1 ...
> 3301 Issuing autochanger "loaded drive 0" command.
> 3991 Bad autochanger "loaded drive 0" command: ERR=Child exited with code
> 127.
> 3301 Issuing autochanger "loaded drive 0" command.
> 3991 Bad autochanger "loaded drive 0" command: ERR=Child exited with code
> 127.
> 3304 Issuing autochanger "load slot 1, drive 0" command.
> 3992 Bad autochanger "load slot 1, drive 0": ERR=Child exited with code 127.
> Label command failed for Volume TestVol04.
> Do not forget to mount the drive!!!
> *q
>
>
> However, if I kill all three 3 daemons (either kill pid, or "
> z-bacula-dir.sh stop") and start the daemons manually
> (/usr/local/etc/rc.d/z-bacula-dir.sh start, etc), the problem goes away.
>
> I made sure correct permission / ownership ( 0660 root:bacula ) is set on
> the devices and I don't see any differences (same options) when I look at
> the process with ps -- same whether or not daemon was started during boot
> time or manually by me.
I generally keep the permissions on the devices unchanged. I then
alter the groups to suit. That is, my devices are root:operator. At
the URL below, you can see the permissions.
Did your autchanger pass the tests as described in the manual?
Shortcuts can be found here where I documented my testing:
http://www.freebsddiary.org/digital-tl891.php
--
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php
