I think the email issue was the problem. The jobs ran last night. More as I
figure this out. Everyone, thanks VERY much for the help.
-- D
On 20 Jan, 2010, at 13:46 , Phil Stracchino wrote:
> On 01/20/10 14:36, Daniel wrote:
>> The priority of all jobs is 10, but I would assume that if conc
As someone sad,
this problem was discussed few time ago, in other tread
Otherwise, I have got the same problem, my sendmail work fine, but
something where wrong with bacula.
Try disabling 'mailcommand' and 'operatorcommand' of your messages. In
this way you can check if the problem is there. If th
On 01/20/10 14:36, Daniel wrote:
> The priority of all jobs is 10, but I would assume that if concurrency were
> an issue that the messages would indicate such?
Concurrency, not priority. But yes, if there was a problem of that kind
I would expect it to result in only one job runnable at a time,
On 01/20/10 13:33, Daniel wrote:
> 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
Sendmail for outgoing mail on the server is running just fine and tested at the
commandline. Interesting that you mention this, though. If I accidentally put
more than one email in the mail= line and forgot to replace the %r, will that
cause this effect as well?
-- D
On 20 Jan, 2010, at 12:
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
>>
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
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
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
==
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
10 matches
Mail list logo
