Hi,

I'm running Bacula 5.2.12 (RPMs distributed by Simone Caronni on
repos.fedorapeople.org) on CentOS 6 (x86_64) with a sqlite catalog.

I defined a base backup job and a regular backup job. The base job worked fine
after the subsequent full backup the bacula director "hangs": It consumes all
CPU (for at least 4 hours) and I can't start new jobs through bconsole.

Some observations/background info:
- The client/sd tell me that the backup was successful, however the director
  lists the job as still running (with status 'terminated').
- With a new bconsole connection I can issue some queries on the director so
  it's at least partially alive.
- My setup is a pretty simple one currently: disk based backup, about
  60-100 GB data, all communication encrypted with TLS certificates (though
  no the backups themself).

I attached the status output as well as a short snippet of an strace on the
bacula-director.

My questions:
- Is that a known bug? (or a bug at all?)
- Which additional information should I provide you?

fs

bacula-job-status.txt
Description: Text document

strace.txt
Description: Text document

------------------------------------------------------------------------------
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