Re: [Bacula-users] Special Permissions to Stop and Start Services during backup

2017-04-28 Thread Jim Richardson
ir JobId 114: Volume used once. Marking Volume "MyService-fd-Daily-111-2017.4.28.bak" as Used. MyService-fd JobId 114: shell command: run ClientAfterJob "systemctl start MyService" bacula-sd JobId 114: Elapsed time=00:00:16, Transfer rate=3.883 M Bytes/second Jim Richardso

Re: [Bacula-users] Special Permissions to Stop and Start Services during backup

2017-04-28 Thread Roberts, Ben
Hi Jim, Note that sudo requires the command be executed from a TTY by default for security, which isn't compatible with how system services run. Do you have a defaults entry for bacula that disables the "requiretty" option? Not having this would manifest as a permission denied as if the sudo ru

Re: [Bacula-users] Special Permissions to Stop and Start Services during backup

2017-04-28 Thread Martin Simmons
> On Fri, 28 Apr 2017 00:46:09 +, Jim Richardson said: > > I am starting to get into a few special circumstances that I need to have a > service stopped before I can back it up I am receiving the errors below. I > have established a Bacula sudoers file that should allow for things, but >

Re: [Bacula-users] Special Permissions to Stop and Start Services during backup

2017-04-28 Thread andy
On Fri, Apr 28, 2017 at 12:46:09AM +, Jim Richardson wrote: > > # cat /etc/sudoers.d/bacula > > bacula ALL=NOPASSWD: /usr/bin/systemctl. > Is there really a trailing "." there? I don't think that will work... Check your system security log - usually /var/log/secure or /var/log/auth.log -

[Bacula-users] Special Permissions to Stop and Start Services during backup

2017-04-27 Thread Jim Richardson
I am starting to get into a few special circumstances that I need to have a service stopped before I can back it up I am receiving the errors below. I have established a Bacula sudoers file that should allow for things, but still run into the permission denied see information below. Thank yo