Greetings all,
Near the end of my day's run of backup jobs I noticed 3 still
scheduled... 1 was a job that apparently isn't working right, and two
others waiting on higher priority jobs.
I canceled the problem job (named dms48) and the one I changed priority
on (wnacs06) and the 3rd job wound up still waiting. I then was left
with the following...
*status storage
Automatically selected Storage: Dell-PV136T
Connecting to Storage daemon Dell-PV136T at gyrus:9103
gyrus-sd Version: 2.2.5 (09 October 2007) i686-pc-linux-gnu suse 10.2
Daemon started 16-Oct-07 11:30, 70 Jobs run since started.
Heap: heap=1,044,480 smbytes=624,104 max_bytes=826,119 bufs=142
max_bufs=203
Sizes: boffset_t=8 size_t=4 int32_t=4 int64_t=8
Running Jobs:
Writing: Incremental Backup job dms48 JobId=988 Volume="LTO235L2"
pool="Default" device="IBMLTO2-1" (/dev/nst0)
spooling=1 despooling=0 despool_wait=0
Files=0 Bytes=0 Bytes/sec=0
FDReadSeqNo=7 in_msg=6 out_msg=5 fd=14
====
Jobs waiting to reserve a drive:
====
Terminated Jobs:
JobId Level Files Bytes Status Finished Name
===================================================================
<snip no need to show these>
====
Device status:
Autochanger "Dell-PV136T" with devices:
"IBMLTO2-1" (/dev/nst0)
Device "FileStorage" (/home/baculastorage) is not open.
Device "IBMLTO2-1" (/dev/nst0) is mounted with:
Volume: LTO235L2
Pool: Default
Media type: LTO-2
Slot 26 is loaded in drive 0.
Total Bytes=212,202,482,688 Blocks=3,289,348 Bytes/block=64,512
Positioned at File=222 Block=8,328
====
In Use Volume status:
LTO235L2 on device "IBMLTO2-1" (/dev/nst0)
Reader=0 writers=1 reserved=0
====
Data spooling: 1 active jobs, 0 bytes; 63 total jobs, 46,425,349,172 max
bytes/job.
Attr spooling: 1 active jobs, 0 bytes; 63 total jobs, 60,886,386 max bytes.
====
*status director
gyrus-dir Version: 2.2.5 (09 October 2007) i686-pc-linux-gnu suse 10.2
Daemon started 16-Oct-07 11:30, 87 Jobs run since started.
Heap: heap=864,256 smbytes=357,966 max_bytes=566,007 bufs=2,378
max_bufs=3,910
Scheduled Jobs:
Level Type Pri Scheduled Name Volume
===================================================================================
====
Running Jobs:
JobId Level Name Status
======================================================================
988 Increme dms48.2007-10-17_11.35.06 has been canceled
1015 Increme wnacs06.2007-10-17_11.35.33 has been canceled
1016 Full BackupCatalog.2007-10-17_13.10.37 is waiting execution
====
*release
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
Automatically selected Storage: Dell-PV136T
Connecting to Storage daemon Dell-PV136T at gyrus:9103 ...
3937 Device "IBMLTO2-1" (/dev/nst0) is busy with 1 writer(s).
*estimate job=dms48
Using Catalog "MyCatalog"
Connecting to Client dms48 at dms48.case.edu:9102
Failed to connect to Client.
*
Looking at the spool directory... I find the following file...
-rw-r----- 1 root bacula 0 2007-10-17 11:43
gyrus-sd.data.988.dms48.2007-10-17_11.35.06.IBMLTO2-1.spool
which is the job that I tried to cancel.
I was able to stop and start the bacula services and continue so it's
clear I don't have a hardware failure at least...
Any thoughts? I've been able to cancel other jobs just fine in the past
but I just upgraded to bacula version 2.2.5.
Bob
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
