Hi folks, 

sometimes we have a weird problem with bacula 5.2.12 (compiled from
source on CentOS 6) getting stuck trying to recycle an on-disk
volume. 

The clients where this problem crops up have their own storages,
devices, pools and volumes (disk-based). We see a lot of messages in
the logs like this (please excuse the long lines): 
######################################################################
23-Okt 23:10 deniol186-dir JobId 46356: Purging oldest volume
"deniol2146.2012-10-16_10.25.19_03-Full"
23-Okt 23:10 deniol186-dir JobId 46356: 0 File on Volume
"deniol2146.2012-10-16_10.25.19_03-Full" purged from ca\
talog.
23-Okt 23:15 deniol186-dir JobId 46356: Purging oldest volume
"deniol2146.2012-10-16_10.25.19_03-Full"
23-Okt 23:15 deniol186-dir JobId 46356: 0 File on Volume
"deniol2146.2012-10-16_10.25.19_03-Full" purged from ca\
talog.

<snip snip>

24-Okt 08:25 server-186-dir JobId 46356: Purging oldest volume
"server-2146.201\
2-10-16_10.25.19_03-Full"
24-Okt 08:25 server-186-dir JobId 46356: 0 File on Volume
"server-2146.2012-10-\
16_10.25.19_03-Full" purged from catalog.
24-Okt 08:30 server-186-dir JobId 46356: Purging oldest volume
"server-2146.201\
2-10-16_10.25.19_03-Full"
24-Okt 08:30 server-186-dir JobId 46356: 0 File on Volume
"server-2146.2012-10-\
16_10.25.19_03-Full" purged from catalog.
24-Okt 08:35 server-186-dir JobId 46356: Purging oldest volume
"server-2146.201\
2-10-16_10.25.19_03-Full"
24-Okt 08:35 server-186-dir JobId 46356: 0 File on Volume
"server-2146.2012-10-\
16_10.25.19_03-Full" purged from catalog.
24-Okt 08:40 server-186-dir JobId 46356: Purging oldest volume
"server-2146.201\
2-10-16_10.25.19_03-Full"
24-Okt 08:40 server-186-dir JobId 46356: 0 File on Volume
"server-2146.2012-10-\
16_10.25.19_03-Full" purged from catalog.
24-Okt 08:45 server-186-dir JobId 46356: Purging oldest volume
"server-2146.201\
2-10-16_10.25.19_03-Full"
24-Okt 08:45 server-186-dir JobId 46356: 0 File on Volume
"server-2146.2012-10-\
16_10.25.19_03-Full" purged from catalog.
24-Okt 08:50 server-186-dir JobId 46356: Purging oldest volume
"server-2146.201\
2-10-16_10.25.19_03-Full"
24-Okt 08:50 server-186-dir JobId 46356: 0 File on Volume
"server-2146.2012-10-\
16_10.25.19_03-Full" purged from catalog.
24-Okt 08:55 server-186-dir JobId 46356: Purging oldest volume
"server-2146.201\
2-10-16_10.25.19_03-Full"
24-Okt 08:55 server-186-dir JobId 46356: 0 File on Volume
"server-2146.2012-10-\
16_10.25.19_03-Full" purged from catalog.
24-Okt 09:00 server-186-dir JobId 46356: Purging oldest volume
"server-2146.201\
2-10-16_10.25.19_03-Full"
######################################################################

and apparently, the recycling / purging never finishes successfully
until I manually cancel the copy job in bconsole or until I restart
the bacula process. After a restart, the remaining copy jobs will
proceed without any problems. As you can see, in this case bacula was
stuck from around 23:00 to about 9 am the next morning when I took
"manual action" to resolve the problem. 

I'd be most grateful for any suggestions where to look to solve this
problem; please let me know if you require more information or there's
anything I've forgotten to mention. 

All the best, 

Uwe 

-- 
NIONEX --- Ein Unternehmen der Bertelsmann SE & Co. KGaA



------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users