Priority column in Jobs->Jobs not updating

Plural

Hi Marcin,

To reproduce do the following:

Create a config with some priority values, e.g. 5
Apply the config to some jobs

Only the first row change the priority, but the directive change in the resource.

Best regards,
Rui

gani

Hi Rui,

Thanks for your report. I tried to reproduce it on my side but I was not able to reproduce it.

Is it possible that before applying the config in the first job/row resource configuration you did not have the Priority directive defined and in rest you already had the Priority defined?

If it is this case, then to apply this Priority from config to all selected jobs you will need to use Overwrite policy in the apply config window. I mean this policy:

https://bacularis.app/doc/patterns/policies.html#policy-overwrite

Please let us know if it is this case or not.

Best regards,
Marcin Haba (gani)

Plural

HI Marcin,

Let me guide you through. Forget about the Config/Pattern, it's not relevant

This is the state of the list:

Now, I open the "PPA_TONY" through the "Quick Edit" button. As you can see the priority is 5, not 10.

Now I change the priority to 6 and I save the de resource.

When I back to the list I refresh the page. The row for the resource reports 10 in the priority column instead of 6.

I go to the edit again and it shows 6 in the priority directive.

I hope this help you.

Best regards,
Rui

gani

Hi Rui,

Many thanks for describing this case. Excellent report.

The first thing that comes to my head about this problem is that the Bacula configuration has not been refreshed correctly in Bacula Director after saving the config.

This priority value is taken from the Bconsole show jobs command. You can see it for example here (example for single PPA-TONY job):

show job="PPA-TONY"

In the first line of this output there is Priority=XXXX value. Could you tell me what is this XXXX? If this X is 5 it can mean that the Bacula Director configuration has not been reloaded correctly.

Are you using Console ACL for this user or not? Maybe the reload command is not allowed in the Console ACL? I would propose to run in the bconsole available on the web interface ([Main menu] => [Page: Console] the reload command anyway and see if it reloads this configuration:

reload

There are also some rare cases when the Director cannot be reloaded because it exhausted allowed connections limit at the moment, but you will see it if it will be this case.

Please let us know what you found.

Thanks.

Best regards,
Marcin Haba (gani)

Plural

Hi Marcin,

The Job configuration in the bacula-dir.conf

Job {
  Name = "PPA-TONY"
  Storage = "Scalar-i3-2"
  Pool = "Prod_TONY_PPA_Motion"
  Client = "PPADMIN"
  Fileset = "PPA-TONY"
  Schedule = "DailyCycle_2hInterval"
  JobDefs = "DefaultJob"
  SpoolData = yes
  Priority = 6
  Accurate = no
}

Running from bconsole in the server (using the Bacularis console feature returns the same):

*show job=PPA-TONY
Job: name=PPA-TONY JobType=66 level=Incremental Priority=10 Enabled=1
...

After the reload command the result is the same.

Using bdirjson command:

bdirjson -r job -n PPA-TONY
{

    "Name": "PPA-TONY",
    "Type": "Backup",
    "Level": "Incremental",
    "Messages": "Standard",
    "Storage": ["Scalar-i3-2"],
    "Pool": "Prod_TONY_PPA_Motion",
    "Client": "PPADMIN",
    "Fileset": "PPA-TONY",
    "Schedule": "DailyCycle_2hInterval",
    "JobDefs": "DefaultJob",
    "WriteBootstrap": "/var/lib/bacula/%c.bsr",
    "SpoolAttributes": true,
    "SpoolData": true,
    "Priority": 6,
    "AllowMixedPriority": true,
    "Accurate": false,
    "CancelQueuedDuplicates": true
}

Query to the API:

{
  "output": [
    "show job=\"PPA-TONY\"",
    "Job: name=PPA-TONY JobType=66 level=Incremental Priority=10 Enabled=1",
...

Best regards,
Rui

gani

Hi Rui,

Thanks. It means that your Director configuration has a problem with reloading configuration.

In the status director command there is information about date and time of latest config reload.

*status dir
darkstar-dir Version: 15.0.3 (25 March 2025) x86_64-pc-linux-gnu redhat 
Daemon started 23-maj-25 00:07, conf reloaded 23-maj-2025 10:51:42
...
...etc.

I guess that on your side there can be an old date (not current). Could you confirm it?

In the Bacula Director configuration there is MaximumReloadRequests directive:

https://www.bacula.org/15.0.x-manuals/en/main/Configuring_Director.html#10710

Maybe something caused that this limit is reached... 🤔

If the configuration is still not reloaded I would propose to try reload this configuration in Bconsole once again when no job is running. If it will not help, then the restart the Bacula Director service can be necessary, I think.

Best regards,
Marcin Haba (gani)

Plural

Hi Marcin,

gani I guess that on your side there can be an old date (not current). Could you confirm it?

You are right, the date it is from yesterday.

gani Maybe something caused that this limit is reached... 🤔

I don't have the directive but the default it's 32. Yes, it may was reached. I have a large Virtual Full backup with priotity 7 running. Althroug I have 3 tape devices, the other jobs are waiting for that high priotity job to end. Thats why I need to change the priorities.

gani If the configuration is still not reloaded I would propose to try reload this configuration in Bconsole once again when no job is running. If it will not help, then the restart the Bacula Director service can be necessary, I think.

Can't do that now, I need to wait for the Virtual Full to end. 😥

Thanks Marcin.

Best resgards,
Rui

Plural

Hi Marcin,

The Virtual Full terminate and the director reload ok. No need for restart the service.

Thank you Marcin.

Best regards,
Rui

gani

Hi Rui,

Super 🙂 Thanks.