I have been running  bacula Version: 1.38.8 (compiled from source) for a
few months now.  I am running CentOS 4.3 on an x86_64 platform.

I am backing up to disk (external USB storage).

This has been running fine for the past few months.

This week the system has crashed hard (no kernel panic) 2 times.  I can
not find anything of value in any of the system logs.  It is a complete
hang of the system.

I am running VMware Workstation on this server.  The reason I mention this
is because the only significant change to the system this week is that
more VM instances have been running on the server this week.  All day long
the Virtual Machines and the physical system plays nicely with one
another.  Then, within 2 minutes of seeing this bacula message Volume
"INCR-0003" previously written, moving to end of data, the system hangs. 
The above message is seen write after the script defined in the
RunBeforeJob (for the physical system) directive is run (and completed
successfully).

It is a presumed 2 minutes because that is the time from the above message
to the last message written to the /var/log/messages file.

I can not find any other jobs running at that time then would be any
different then the jobs running throughout the day.

Anyone have any suggestions on things I could tune that would prevent the
system from crashing?  My bacula configurations are not all that complex
or strange.  Anyone else seen this type of behavior?

Thanks.
-- 
Scott



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to