On Thursday 01 November 2007 22:22:40 Dane Miller wrote:
Eric Bollengier wrote:
IHMO, i think that the script doesn't close stderr, stdout and stdin
properly.
Hey you're right! stderr is the culprit here. The following Client Run
After Job script works around the problem:
#!/bin/sh
#
Hi,
I added Client Run Before/After Job scripts to two backup jobs in
order to stop/start mysql. But the After script seems to hang the
bacula-fd. Using 'status dir', the bacula console shows a terminated
status for these jobs, and the command 'list jobs' shows their status as
'R'.
The
Eric Bollengier wrote:
IHMO, i think that the script doesn't close stderr, stdout and stdin
properly.
Hey you're right! stderr is the culprit here. The following Client Run
After Job script works around the problem:
#!/bin/sh
# AfterScript.sh
/usr/local/etc/rc.d/mysql-server start 2
Hi,
I added Client Run Before/After Job scripts to two backup jobs in
order to stop/start mysql. But the After script seems to hang the
bacula-fd. Using 'status dir', the bacula console shows a terminated
status for these jobs, and the command 'list jobs' shows their status as
'R'.
The script
Hi Dane,
Is bacula running as root or bacula user ? bacula user cannot restart mysql.
Michael
On 10/30/07, Dane Miller [EMAIL PROTECTED] wrote:
Hi,
I added Client Run Before/After Job scripts to two backup jobs in
order to stop/start mysql. But the After script seems to hang the
Michael Lewinger wrote:
Is bacula running as root or bacula user ? bacula user cannot restart
mysql.
Thanks Michael. bacula-fd is running as root. Also note that it *does*
stop and start mysql, but hangs after-wards (see the job output from my
o.p. below)
Dane
On 10/30/07, Dane Miller
Interesting... I've been testing this manually and have more info. When
bacula-fd is hung, I can fix it by stopping mysql. As soon as I stop
mysql, the bacula job completes successfully.
Also, it doesn't matter if my fileset includes mysql's data directory or
not. For example, if I set my
