Op 13/07/2011 18:57, Josh Fisher schreef: > On 7/13/2011 5:36 AM, Bill Damage wrote: >> Hi - the upgrade wasn't without trouble - we had to preserve the >> bacula config, do a clean installation and restore the config/cats >> etc. So its almost definitely not a "bacula doesn't work with Fed15 >> problem" ;-) >> >> What happens is if I restart the services I can see them running fine >> and the sd is running as the user "bacula". If I try anything with >> touches the sd, say in bconsole even a "status all", the display stops >> at the first "Connecting to Storage daemon..." message. However, if I >> kill the sd process and run it from root with "bacula-sd -f -v" in >> another console all is well. There's nothing in any logs I can see. >> Whats gives please? Thanks. > Does user bacula, (or the group bacula-sd runs as), have the needed > permissions to access the /dev devices? Do you have selinux enabled? I know for example that in RHEL6 (which is basically a stable version of fedora) the /dev/st and /dev/nst devices no longer belong to group disk like the used to, but now belong to group tape. In a default config the bacula user will only be member of the disk group and not tape.
I ran into the same weird problem, but adding the bacula user to the tape group solved it. Maybe it's the same in fedora 15? Regards, Jeremy **** DISCLAIMER **** http://www.schaubroeck.be/maildisclaimer.htm ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
