On Mon, 2007-12-03 at 20:17 +0000, Martin Simmons wrote: > >>>>> On Mon, 03 Dec 2007 10:51:00 -0800, Ross Boylan said: > > > > Clarifying: > > On Mon, 2007-12-03 at 09:18 -0800, Ross Boylan wrote: > > > I have a BACULA job that runs a SHELL script; the script does an sudo and > > > it appears > > > to be waiting for a password. Cancelling the BACULA job doesn't kill it. > > That is, after the cancel, bconsole status dir shows > > Running Jobs: > > JobId Level Name Status > > ====================================================================== > > 407 Increme Cyrus.2007-12-03_01.05.04 has been canceled > > This is over an hour since I used bconsole to issue a cancel command. > > > > > > How can I kill the BACULA job? Is it safe to kill the UNIX job with the > > > invoked > > > shell script? > > That is, the bacula job invoked a script cryus-prep, which I see running > > as a Unix job. What if I kill cyrus-prep using Unix kill? > > Should be safe from the Bacula side. At worst, it will continue doing the > backup without the useful effects of the script. Killing the Unix job left the bacula job in the same state as reported above, even after waiting a minute or two. I restarted the director, and all was well. > > > > I'm running on Linux. > > > > > > I tested the sudo on the command line and it did not ask for a password; > > > that was in a terminal in which I did an su. In contrast, the job is > > > configured with > > > Run Before Job = "super cyrus-prep" > > > So I think it runs as bacula, does a "super" to root, and the offending > > > line in the script is trying to sudo to cyrus. I guess the environment > > > created by su is sufficiently "root" that sudo doesn't ask for a > > > password, but the one created by super is not "root" enough. > > > > > > I used super because I had problems with su and sudo asking for > > > passwords; I notice a lot of advice on this list to use sudo. > > > > > > Can anyone recommend how I can make this work properly in the future? > > > The big picture is that before the job runs I need to run as root, > > > mostly, but one of the items needs to be done as user cyrus. > > Try configuring sudo to not prompt for a password when invoked by the username > that runs the Bacula Director (probably called "bacula"). I switched the scripts to run on the client. Although the director and client are the same machine in this case, logically the jobs run on the client. Since client jobs run from the fd, which runs as root, this eliminated the need to super/su/sudo the main script, and allowed sudo to operate without prompts within the invoked scripts.
Thanks for the help. Ross ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
