Hi. I had a similar situation (1.38.10 on sd/dir, 1.38.11 on the client with problems, 1.38.9 on the rest of the clients). I have a job to back up an Oracle DB with a "client run before job" to shut down the DB and a "client run after job" to start it again. My problem is that everyting works fine, the "run before job", the backup and the "run after job", but the job never finishes. On the "stat dir" I see that the job "has terminated". The way to stop it is by restarting the FD. (or Dir/SD) I have a similar scenario (same scripts) on another server, but with 1.38.9 and works as expected. I've downgraded the FD to 1.38.9 and apparently it did work, but I'll confirm next monday.
Bye. El Miércoles, 20 de Septiembre de 2006 04:41, Silver Salonen escribió: > On Wednesday 20 September 2006 09:07, Silver Salonen wrote: > > On Tuesday 19 September 2006 23:44, pedro moreno wrote: > > > On 9/19/06, Silver Salonen <[EMAIL PROTECTED]> wrote: > > > > Hi. > > > > > > > > I use Bacula 1.38.11 on server (FreeBSD 6.1) as well as on client > > (FreeBSD > > > > > 5.3), server's database is MySQL 5.0.24a. > > > > > > > > I've got a job with "client run before job" creating a snapshot with > > > > a shellscript. When this job runs, I see client-machine creating > > > > snapshot successfully on /usr, but nothing is done further. So this > > > > job hangs > > there > > > > > until MySQL times out (after several days) and bacula-dir has to be > > > > restarted, or until I cancel the job. > > > > > > > > "status client" shows me: > > > > ==== > > > > Running Jobs: > > > > JobId 731 Job myserver-userdata.2006-09-19_12.36.20 is running. > > > > Backup Job started: 19-Sep-06 12:36 > > > > Files=0 Bytes=0 Bytes/sec=0 > > > > Files Examined=0 > > > > SDReadSeqNo=5 fd=5 > > > > Director connected at: 19-Sep-06 12:39 > > > > ==== > > > > > > > > What could cause it? I have the same script on another FreeBSD (6.1), > > > > creating > > > > the similar size snapshot and everything is OK there. > > > > > > > > Silver > > > > > > Have you run this script manually on that computer..? Is working..? > > > > Yes I have - the script runs just OK. When job starts, it creates > > snapshot, but nothing is done further. > > > > Now I tried running the job without the script (commented these lines out > > and > > > reloaded bacula-dir), still the same - job just sits there with the same > > status. > > > > Silver > > Looks like I found the problem: there were 20 (the maximum) jobs "running" > in bacula-sd. Actually these jobs were already cancelled ages ago, but it > seems that not in bacula-sd, and I hadn't restarted bacula-sd for a while. > > Why had these jobs stayed in bacula-sd when they were cancelled in > bacula-dir as well as in bacula-fd? > > Silver -- Cris. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
