Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 5 of 5

Thread: cron jobs not running

  1. #1
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,062
    Thanks
    751
    Thanked 403 Times in 303 Posts

    cron jobs not running

    ViX 6.0.003

    I'm having a problem with a couple of cron timers that I've set not running. I can run them from the ViX script runner with no problems.
    Permissions for the scripts in /usr/script/ & /usr/scripts/ and the scripts in cron.hourly/daily are set at 755 and the crontabs root file is also 755.
    I've checked /var/log/messages and seeing a lot of errors:

    Code:
    Dec  4 18:53:25 sf8008 authpriv.notice passwd[3317]: pam_unix(passwd:chauthtok): password changed for root
    Dec  4 18:53:25 sf8008 authpriv.notice passwd[3317]: pam_smbpass(passwd:chauthtok): password for (root/0) changed by (root/0)
    Dec  4 18:53:29 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 18:53:30 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 18:53:44 sf8008 authpriv.info smbd[3412]: pam_unix(samba:session): session opened for user root(uid=0) by (uid=0)
    Dec  4 18:54:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 18:54:24 sf8008 authpriv.info smbd[3412]: pam_unix(samba:session): session closed for user root
    Dec  4 18:55:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 18:56:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 18:57:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 18:58:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 18:59:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:00:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:01:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:02:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:03:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:04:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:05:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:06:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:07:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:08:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:09:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:10:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:11:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:12:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:13:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:14:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:15:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:16:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:17:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:17:01 sf8008 cron.info CROND[10615]: (root) CMD (cd / && run-parts /etc/cron.hourly)
    Dec  4 19:17:01 sf8008 cron.info CROND[10614]: (root) CMDEND (cd / && run-parts /etc/cron.hourly)
    Dec  4 19:18:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:18:43 sf8008 authpriv.info smbd[11141]: pam_unix(samba:session): session opened for user root(uid=0) by (uid=0)
    Dec  4 19:19:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:20:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:20:16 sf8008 kern.info kernel: sh (11628): drop_caches: 3
    Dec  4 19:20:25 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 19:20:28 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 19:20:31 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 19:20:35 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 19:20:37 sf8008 kern.info kernel: sh (11746): drop_caches: 1
    Dec  4 19:20:37 sf8008 kern.info kernel: sh (11746): drop_caches: 2
    Dec  4 19:20:37 sf8008 kern.info kernel: sh (11746): drop_caches: 3
    Dec  4 19:20:37 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 19:20:42 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 19:20:43 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 19:20:43 sf8008 kern.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
    Dec  4 19:21:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:22:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:23:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:24:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:25:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:26:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:27:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:27:18 sf8008 authpriv.info smbd[11141]: pam_unix(samba:session): session closed for user root
    Dec  4 19:27:29 sf8008 authpriv.info smbd[13864]: pam_unix(samba:session): session opened for user root(uid=0) by (uid=0)
    Dec  4 19:28:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:29:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:30:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Dec  4 19:31:01 sf8008 cron.info crond[2127]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Does anyone have any ideas?

    messages.log


    EDIT: It seems to be something to do with my /etc/cron/crontabs/root file. I've deleted it and set my jobs up manually in the cron timer plugin and seems to be running.
    Maybe the one in my settings backup is corrupted in some way but it looks okay?

    Code:
    @reboot /usr/script/skyscraper.sh
    @reboot /usr/script/skypicker.sh
    0 */3 * * * /usr/script/skyscraper.sh
    7,22,37,52 * * * * /usr/script/skypicker.sh
    Last edited by Willo3092; 04-12-21 at 20:58.

  2. #2
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    The file permissions were probably too high, cron is very security conscious.

    See what they're set to now.

    https://www.world-of-satellite.com/s...bs-not-running
    Last edited by ccs; 04-12-21 at 22:45.

  3. The Following User Says Thank You to ccs For This Useful Post:

    Willo3092 (05-12-21)

  4. #3
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,062
    Thanks
    751
    Thanked 403 Times in 303 Posts
    I had them set at 644 before. Will try changing them back.

  5. #4
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,775
    Thanks
    236
    Thanked 1,656 Times in 1,305 Posts
    This is the code that produces the message:

    Code:
                   if ((statbuf.st_mode & 07533) != 0400) { 
                            log_it(uname, pid, "BAD FILE MODE", tabname, 0); 
                            close(crontab_fd); 
                            return (-1);
    So the file:
    • must have no special bits set (setuid/setgid/sticky)
    • must not be executable by anyone
    • must only be readable by the owner.

    600 would be normal.
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  6. The Following User Says Thank You to birdman For This Useful Post:

    Willo3092 (05-12-21)

  7. #5
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,062
    Thanks
    751
    Thanked 403 Times in 303 Posts
    I think my original problem was a corrupt crontabs/root file. If I tried to open the cron manager it was crashing the box.
    I've set my cron jobs up manually in cron manager and set permissions to 600 and all is working again.
    Thanks for the advice guys

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.