Disabled scheduled jobs still executing

  • Hi all.


    I'm facing a weird problem with scheduled job that never happened before.

    I have several jobs running without any problem, but I need to disable one of them for convenience, doing it through Scheduled Jobs menu.

    If I select the one I need to disable and I edit it according, the GUI show it as disabled, but it keeps executing every night.


    I don't know why the userdefined cron jobs keeps untouched when I change enable/disable flag in GUI, I see it changing the executing hour for example, but didn't see any # commenting out or deleting the entire line.


    Here is my openmediavault-userdefined file, where you can see the last one as the disabled job in GUI:




    Does anybody knows whats going on here?

    I have deleted and created from scratch this particular job, and still executes no matter what I do.


    Thanks in advance for your time.

    Greetings.

  • No error messages at all.

    Here's the output:


    Code
    root@ariennas:~# ls -al /etc/cron.d/openmediavault-userdefined
    -rw-r--r-- 1 root root 812 dic 26 11:14 /etc/cron.d/openmediavault-userdefined
  • Came here to say "Me to". Only noticed this recently because I added a cron job this week that I would normally keep disabled and will only manually run it. I originally thought that maybe me enabling it, then disabling it caused some odd issue so I deleted it entirely, then recreated it but left it disabled when I saved it. It's still running.


    Running OMV 5.5.19-1


    the output I'm getting for ls -al /etc/cron.d/openmediavault-userdefined

    -rw-r--r-- 1 root root 558 Dec 25 07:22 /etc/cron.d/openmediavault-userdefined

  • For me I have two jobs scheduled in the GUI. One enabled, one disabled.

    Both jobs exist in openmediavault-userdefined, both are executing as if they're both set to enabled even though one is disabled.


    The GUI doesn't get the enabled or disabled status from openmediavault-userdefined, that's just where it stores the job. It gets the info for the gui from config.xml.


    Looking at config.xml the for the disabled job, the enable flag is <enable>0</enable>...which says it should be disabled.

    In config.xml, the enabled job is <enable>1</enable>


    So somewhere in OMV's scripts when it's updating the cron jobs, it appears to be ignoring whether or not the job is supposed to be enabled.

  • Looks fine.


    When you open the GUI in private mode, do you see the same in scheduled jobs: first two entries disabled?

    As @ParadingLunatic says, we can see disabled jobs being marked without the green light, and <enable>0</enable> in config.xml

    So it seems to be a problem with any config script not making it's job.


    I see allways disabled both first entries.

  • Arien

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!