Solved the issue of the ghost-job by running dbcheck (which fixed thousands
of orphaned files/paths, probably from previous tests), then
stopping/restarting the involved storage and file daemons.
This list is really helpful ;) (well, I only read about 200 pages of the
manual so far and saw dbcheck mentioned)
Foo Bar <[EMAIL PROTECTED]> wrote:
> I stopped and restarted the bacula-director process. Now, using 'status
> dir' the job listing doesn't show any running jobs (all scheduled/waiting
> jobs are gone), but using 'status client' the job seems to be still
> running
> (showing the filename where it stopped due to the volume byte limit).
>
> When trying to use 'cancel' it says there are no jobs running. How do I
> fix this?
___________________________________________________________
Want ideas for reducing your carbon footprint? Visit Yahoo! For Good
http://uk.promotions.yahoo.com/forgood/environment.html
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
