Hi,

"Device not configured" is the output, when there is no tape in drive. (As mentioned somewhere here: http://www.cyberdelix.net/tech/bsd-backups.htm)

bareos is running as root (for now, to avoid rights problems)
the changer devices has 0666 set as rights

Output of the mtx-changer log:

20140820-09:50:30 Parms: /dev/pass16 loaded 0 /dev/nsa11 0
20140820-09:50:30 Doing mtx -f /dev/pass16 on Drive 0 -- to find what is loaded
20140820-09:50:32 Parms: /dev/pass16 loaded 0 /dev/nsa11 0
20140820-09:50:32 Doing mtx -f /dev/pass16 on Drive 0 -- to find what is loaded
20140820-09:50:33 Parms: /dev/pass16 loaded 0 /dev/nsa22 1
20140820-09:50:33 Doing mtx -f /dev/pass16 on Drive 1 -- to find what is loaded
20140820-09:50:35 Parms: /dev/pass16 loaded 0 /dev/nsa22 1
20140820-09:50:35 Doing mtx -f /dev/pass16 on Drive 1 -- to find what is loaded
20140820-09:50:37 Parms: /dev/pass16 loaded 0 /dev/nsa13 2
20140820-09:50:37 Doing mtx -f /dev/pass16 on Drive 2 -- to find what is loaded
20140820-09:50:39 Parms: /dev/pass16 loaded 0 /dev/nsa13 2
20140820-09:50:39 Doing mtx -f /dev/pass16 on Drive 2 -- to find what is loaded
20140820-09:50:40 Parms: /dev/pass16 loaded 0 /dev/nsa24 3
20140820-09:50:40 Doing mtx -f /dev/pass16 on Drive 3 -- to find what is loaded
20140820-09:50:42 Parms: /dev/pass16 loaded 0 /dev/nsa24 3
20140820-09:50:42 Doing mtx -f /dev/pass16 on Drive 3 -- to find what is loaded
20140820-09:50:44 Parms: /dev/pass16 loaded 0 /dev/nsa25 4
20140820-09:50:44 Doing mtx -f /dev/pass16 on Drive 4 -- to find what is loaded
20140820-09:50:45 Parms: /dev/pass16 loaded 0 /dev/nsa25 4
20140820-09:50:45 Doing mtx -f /dev/pass16 on Drive 4 -- to find what is loaded
20140820-09:51:07 Parms: /dev/pass16 loaded 0 /dev/nsa11 0
20140820-09:51:07 Doing mtx -f /dev/pass16 on Drive 0 -- to find what is loaded
20140820-09:51:09 Parms: /dev/pass16 loaded 0 /dev/nsa11 0
20140820-09:51:09 Doing mtx -f /dev/pass16 on Drive 0 -- to find what is loaded
20140820-09:51:11 Parms: /dev/pass16 loaded 0 /dev/nsa22 1
20140820-09:51:11 Doing mtx -f /dev/pass16 on Drive 1 -- to find what is loaded
20140820-09:51:12 Parms: /dev/pass16 loaded 0 /dev/nsa22 1
20140820-09:51:12 Doing mtx -f /dev/pass16 on Drive 1 -- to find what is loaded
20140820-09:51:14 Parms: /dev/pass16 loaded 0 /dev/nsa13 2
20140820-09:51:14 Doing mtx -f /dev/pass16 on Drive 2 -- to find what is loaded
20140820-09:51:16 Parms: /dev/pass16 loaded 0 /dev/nsa13 2
20140820-09:51:16 Doing mtx -f /dev/pass16 on Drive 2 -- to find what is loaded
20140820-09:51:18 Parms: /dev/pass16 loaded 0 /dev/nsa24 3
20140820-09:51:18 Doing mtx -f /dev/pass16 on Drive 3 -- to find what is loaded
20140820-09:51:19 Parms: /dev/pass16 loaded 0 /dev/nsa24 3
20140820-09:51:19 Doing mtx -f /dev/pass16 on Drive 3 -- to find what is loaded
20140820-09:51:21 Parms: /dev/pass16 loaded 0 /dev/nsa25 4
20140820-09:51:21 Doing mtx -f /dev/pass16 on Drive 4 -- to find what is loaded
20140820-09:51:23 Parms: /dev/pass16 loaded 0 /dev/nsa25 4
20140820-09:51:23 Doing mtx -f /dev/pass16 on Drive 4 -- to find what is loaded

On 20.08.2014 10:13, Philipp Storz wrote:
Are you sure that the access rights on the changer device are ok for the user 
that the sd runs as?

I would try to enable the debug_log writing in mtx-changer.conf and see what is 
written there.

Also, something seems wrong with the tape devices, as "Device not configured" 
is returned there.


Am 20.08.2014 09:52, schrieb A. Podstawka:
Hi,

[root@gimli /opt/bareos/etc]# /opt/bareos/sbin/bareos-sd -d500 -v -c
/opt/bareos/etc/bareos-sd.conf -f
bareos-sd: lex.c:217-0 Open config file: /opt/bareos/etc/bareos-sd.conf
bareos-sd: stored_conf.c:859-0 Inserting director res: gimli-mon
bareos-sd: stored_conf.c:859-0 Inserting device res: Drive-2
bareos-sd: stored_conf.c:859-0 Inserting device res: Drive-3
bareos-sd: stored_conf.c:859-0 Inserting device res: Drive-4
bareos-sd: stored_conf.c:859-0 Inserting device res: Drive-5
bareos-sd: lex.c:217-0 Open config file: /opt/bareos/etc/bareos-sd.conf
bareos-sd: message.c:349-0 Copy message resource 802c1a268 to 802c1d188
gimli-sd: bsys.c:619-0 Could not open state file. sfd=-1 size=192: ERR=No such 
file or directory
gimli-sd: crypto_cache.c:55-0 Could not open crypto cache file.
/opt/bareos/var/bareos/working/bareos-sd.9103.cryptoc ERR=No such file or 
directory
gimli-sd: sd_plugins.c:308-0 Load sd plugins
gimli-sd: plugins.c:182-0 load_plugins
gimli-sd: plugins.c:276-0 Rejected plugin: want=-sd.so name=libbareos-13.2.3.so 
len=19





--
Adam Podstawka
Informatician - Bioinformatics
Leibniz Institute DSMZ-German Collection of Microorganisms and Cell Cultures

--
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to