Improve checkruntimejobs output

[martialblog]

• The query assumed a string and used LIKE, probably from an older iteration of the plugin. Now uses IN syntax to support multiple states

See #40

[martialblog]

@mowgli This should fix the issue with the runtimejobs query and improve the output. Can you verify that?

[mowgli]

Hi,

Am Mo den 23. Sep 2024 um 16:44 schrieb Markus Opolka:

@mowgli This should fix the issue with the runtimejobs query and improve the output. Can you verify that?

Not really.

git co fix/runtimequery ./check_bareos.py -U bareos --password-file /etc/bareos/db-password job --runTimeJobs -t 2 -w 1 -c 3 [UNKNOWN] - Error: column "c" does not exist LINE 4: ...now()::date-2 '1 day'::INTERVAL) AND Job.JobStatus in (C); ./check_bareos.py -U bareos --password-file /etc/bareos/db-password job --runTimeJobs -st R -t 2 -w 1 -c 3 [UNKNOWN] - Error: column "r" does not exist LINE 4: ...now()::date-2 '1 day'::INTERVAL) AND Job.JobStatus in (R);

Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen @.***> Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C

[martialblog]

Meh -.- guess I have to setup a Bareos Database to fix this. I'll keep you posted

[martialblog]

@mowgli Ok upon closer look the query looks alright and seems to work with Bareos 23.0.4.

I extended the output of the plugin so that it is clearer what is happening. As mentioned in the issue, I think the the -st parameter is what you need.