Re: [Bacula-users] Bacula hangs "waiting for execution"...

On 20 Jan, 2010, at 12:41 , Dan Langille wrote:

Daniel wrote:
On 20 Jan, 2010, at 12:24 , Dan Langille wrote:
Daniel wrote:
Hello,
I am having a problem where all jobs but the first immediately after starting bacula-dir hang "waiting for execution.". I have no further information on why they are waiting, nor what they are waiting on. They have waited nearly a week. All jobs I queue after them even ones with the same or higher priority do not run either.
If I restart bacula-dir service, all of my running jobs disappear completely as though it forgot about them.
This is expected behaviour.

If I try to cancel a job, it stays in the running queue with the note "has been cancelled." Nothing else changes and the other jobs stay "waiting for execution".
This is expected.

What is the output of status dir?

Well I've restarted the director to get a critical job running, but as soon as that job finishes I'll run a few more and show you what happens. Essentially they show up as:
Running Jobs:
Console connected at 20-Jan-10 13:27
JobId Level   Name                       Status
======================================================================
  42         BackupServer1.2010-01-20_10.30.00_01 is waiting for execution
  43         BackupServer2.2010-01-20_10.30.00_01 is waiting for execution
  44         RestoreFiles.2010-01-20_12.20.31_03 is waiting for execution
That's a simulation of previous results.
When I cancel the jobs and they sit there and then I restart the director, I do NOT see the cancelled jobs show up in the "Terminated Job" list.

Ok, that's a good start. Now, for BackupServer1, what is the Schedule resource for it?

Does that job ever run?

Current Schedule resource is the default "WeeklyCycle". It runs every day, but hangs waiting for execution if its not the first job immediately after restarting bacula-dir. I can run it manually after restart and it succeeds every time.

The restores are manually queued to see if anything will run, but it seems that after that first job, regardless of the method of queuing the job to run, they all stick in this state.

-- D

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users