Problem recurring downtime second Backend

[Manuel Gutiérrez Molina]

Hi;

When program downtimes recur in the thruk interface for my second backend, I see that they are generated in Apache's cron, but I need to set the backend to which it applies.

This is what it generates:

58 11  *  *  3 cd /usr/share/thruk && /bin/bash -l -c '/usr/bin/thruk downtimetask "13"' >/dev/null 2>>/var/lib/thruk/cron.log
 

When should it be generated like this?

58 11  *  *  3 cd /usr/share/thruk && /bin/bash -l -c '/usr/bin/thruk -b SECONDBACKEND downtimetask "13"' >/dev/null 2>>/var/lib/thruk/cron.log  

Thruk 3.08.3

Is it a bug?

Thanks.

[Sven Nierlein]

Hi,

the backend information should be extracted from the actual downtime, not from the command parameter. So i'd say this is expected.
Or is the downtime applied to the wrong backend?

Regards,
Sven

On 26.03.25 16:30, Manuel Gutiérrez Molina wrote:
> Hi;
>
> When program downtimes recur in the thruk interface for my second backend, I see that they are generated in Apache's cron, but I need to set the backend to which it applies.
>

> *This is what it generates:*
> 58 11  *  *  3 cd /usr/share/thruk && /bin/bash -l -c '/usr/bin/thruk downtimetask "13"' >/dev/null 2>>/var/lib/thruk/cron.log*
> *
> *When should it be generated like this?*
> 58 11  *  *  3 cd /usr/share/thruk && /bin/bash -l -c '/usr/bin/thruk -b *SECONDBACKEND* downtimetask "13"' >/dev/null 2>>/var/lib/thruk/cron.log

>
> Thruk 3.08.3
>
> Is it a bug?
>
> Thanks.
>

> --
> You received this message because you are subscribed to the Google Groups "Thruk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to thruk+un...@googlegroups.com <mailto:thruk+un...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/thruk/998376a5-f374-4f84-9823-75eeeb8adc96n%40googlegroups.com <https://groups.google.com/d/msgid/thruk/998376a5-f374-4f84-9823-75eeeb8adc96n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Manuel Gutiérrez Molina]

It is not being applied to the correct backend, it should be applied to the backend SECONDBACKEND But the cron is generated without backend.

[Manuel Gutiérrez Molina]

Hi;

I've updated to thruk 3.20.2 and we're still having the same issue.

After creating a recurring downtime on the primary backend for the secondary backend, the downtime is created in the cron job, but it's not actually applied to the secondary backend; when it should be applied, it has no effect.

In another environment we've updated, the cron job is created with the -b SECOND_BACKEND flag.

Regards.