Arno Lehmann wrote:
Hello,
Thomas Simmons wrote:
Looks like I found another problem with 1.37.37. It seems I can't
cancel jobs.
status dir shows:
Running Jobs:
JobId Level Name Status
======================================================================
122 Full cap1build.2005-08-31_20.00.05 is waiting on Storage
Dell-PowerVault-132T
130 Full ibm-8af0a5d734d.2005-08-31_20.00.13 is waiting on
Storage Dell-PowerVault-132T
132 Full pegasus.2005-08-31_20.00.15 is waiting on Storage
Dell-PowerVault-132T
137 Full ws-hq-r210-1.2005-08-31_20.00.20 is running
138 Increme volans.2005-08-31_20.00.21 is waiting on Storage
Dell-PowerVault-132T
139 Increme aquariuslt.2005-08-31_20.00.22 is waiting on max
Storage jobs
cancel gives me:
Select Job:
1: JobId=122 Job=cap1build.2005-08-31_20.00.05
2: JobId=125 Job=socrates.2005-08-31_20.00.08
... 22: JobId=154 Job=catalog.2005-08-31_20.01.00
Choose Job to cancel (1-22): 2
3902 Job socrates.2005-08-31_20.00.08 not found.
Now this is hard to say anything about, because that socrates job didn't
show up in the status report...
Depending on what has happened, the above message *might* be normal.
The behaviour on job cancel did change, I think. But the jobs I tried
this with have all been correctly cancelled, only they show up in the
status output for some time - I guess they are removed from the queue in
a different manner now.
Arno,
Actually it was listed in status dir, I guess I missed it. DOH! In any
event, the job "socrates" finally failed (couldn't contact FD), and the
rest of the jobs went on to finish successfully. The previous errors I
mentioned didn't show up.
I guess for now I'm gonna have to roll back to 1.37.30, as it seems to
be the last stable (enough) version. Am I really the only one with all
these issues in 1.37.37? Just my luck :)
No, Beta version.
:-)
After all, the 1.37 versions exist to find problems and are not
considered stable.
Arno
The only problem I had with 1.37.30 was the fact that it used the wrong
pool for upgraded jobs, otherwise it seemed to work great. 1.36 didn't
have VSS support, and backing up clients is the only reason for bacula
here. Servers were, and still are backed up nightly with tar+ssh, until
I get bacula working right.
I'm not complaining about bacula, to be honest I'm very happy with it.
It's the only open source backup solution that can compete with CA,
Bakbone, Veritas, and EMC in terms of features, and in my opinion it
takes the gold for ease of use (once you figure out the conf files). It
currently has a few bugs to be worked out, but like you said, it's still
beta. I'm just trying to help find some them.
Thomas
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
