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.
Page 1 of 2 12 LastLast
Results 1 to 15 of 20

Thread: cron jobs not running

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

    cron jobs not running

    I've noticed that my cron jobs aren't running but will work via ScriptRunner.
    Can't find anything in debug logs but /var/log/messages has the following entries:

    Oct 24 19:45:01 zgemmah7 cron.info crond[2195]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 19:45:01 zgemmah7 cron.info crond[2195]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Oct 24 19:46:01 zgemmah7 cron.info crond[2195]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 19:46:01 zgemmah7 cron.info crond[2195]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Oct 24 19:47:01 zgemmah7 cron.info crond[2195]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 19:47:01 zgemmah7 cron.info crond[2195]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Oct 24 19:48:01 zgemmah7 cron.info crond[2195]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 19:48:01 zgemmah7 cron.info crond[2195]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)

    I'd set it to run every minute to test it.

  2. #2
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,067
    Thanks
    752
    Thanked 403 Times in 303 Posts
    Sorry, it's 5.4.001, not 5.3.039

  3. #3
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    I see the same, but the cronjob setup for ntp is working ok......

    Code:
    Oct 24 21:14:01 et10000 cron.info crond[646]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 21:15:01 et10000 cron.info crond[646]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 21:16:01 et10000 cron.info crond[646]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 21:16:36 et10000 cron.info crontab[21093]: (root) LIST (root)
    Oct 24 21:17:01 et10000 cron.info crond[646]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 21:17:01 et10000 cron.info CROND[21141]: (root) CMD ( cd / && run-parts /etc/cron.hourly)
    Oct 24 21:18:01 et10000 cron.info crond[646]: (readme.txt) ORPHAN (no passwd entry)
    Oct 24 21:19:01 et10000 cron.info crond[646]: (readme.txt) ORPHAN (no passwd entry)
    root@et10000:~#
    Code:
    Oct 24 18:30:01 et10000 cron.info CROND[4218]: (root) CMD (/usr/bin/ntpdate-sync silent)
    Oct 24 18:30:07 et10000 daemon.notice ntpdate[4222]: adjust time server 178.62.18.76 offset -0.002628 sec
    Oct 24 18:42:33 et10000 daemon.notice ntpdate[4605]: adjust time server 129.250.35.251 offset -0.003887 sec
    Oct 24 19:12:42 et10000 daemon.notice ntpdate[7761]: adjust time server 213.251.52.107 offset -0.010235 sec
    Oct 24 19:30:01 et10000 cron.info CROND[10187]: (root) CMD (/usr/bin/ntpdate-sync silent)
    Oct 24 19:30:07 et10000 daemon.notice ntpdate[10191]: adjust time server 85.199.214.99 offset 0.003329 sec
    Oct 24 20:30:01 et10000 cron.info CROND[17979]: (root) CMD (/usr/bin/ntpdate-sync silent)
    Oct 24 20:33:53 et10000 daemon.notice ntpdate[18335]: adjust time server 85.199.214.99 offset -0.018937 sec
    root@et10000:~#
    Google suggests checking file permissions.
    Last edited by ccs; 24-10-20 at 21:24.

  4. #4
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,067
    Thanks
    752
    Thanked 403 Times in 303 Posts
    Quote Originally Posted by ccs View Post
    Google suggests checking file permissions.
    Google was actually my first port of call and I checked but the script permissions are set at 755 which should be okay I think

  5. #5
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,790
    Thanks
    237
    Thanked 1,658 Times in 1,306 Posts
    Quote Originally Posted by Willo3092 View Post
    Google was actually my first port of call and I checked but the script permissions are set at 755 which should be okay I think
    Try 700. I have a sneaking suspicion that they are meant to be usable only by the owner.
    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 (25-10-20)

  7. #6
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,067
    Thanks
    752
    Thanked 403 Times in 303 Posts
    No, still not working. Is it right that there is no mention of cron timers in the debug logs? /var/log/messages is the only place I can see any reference to them.
    These are my root entries in /etc/cron/crontabs/, nothing seems to work apart from ntpdate-sync.
    I've tried changing the script permissions but doesn't seem to have any effect.

    30 * * * * /usr/bin/ntpdate-sync silent
    02 00 * * * /usr/script/skyscraper.sh
    */15 * * * * /usr/script/skypicker.sh
    * * * * * /usr/script/willo.sh

    Oct 25 09:31:01 zgemmah7 cron.info crond[2133]: (readme.txt) ORPHAN (no passwd entry)
    Oct 25 09:31:01 zgemmah7 cron.info crond[2133]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)

  8. #7
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    ... a post elsewhere suggests setting permissions to 600.

    What's /usr/script set to?
    Last edited by ccs; 25-10-20 at 10:53.

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

    Willo3092 (25-10-20)

  10. #8
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,764
    Thanks
    473
    Thanked 607 Times in 433 Posts
    Quote Originally Posted by ccs View Post
    ... a post elsewhere suggests setting permissions to 600.

    What's /usr/script set to?
    0755 https://github.com/OpenViX/vix-core/...tRunner.py#L35

  11. The Following User Says Thank You to dsayers For This Useful Post:

    ccs (25-10-20)

  12. #9
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,067
    Thanks
    752
    Thanked 403 Times in 303 Posts
    I've put the script in /usr/script/ and /usr/scripts/ but still doesn't work with permissions set as 755

  13. #10
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,764
    Thanks
    473
    Thanked 607 Times in 433 Posts
    Trying to test this but I haven't setup top picks yet.

    I've ran scripts manually but when trying to add Cron timer via gui I get an error.

    Code:
    67758.2006> Traceback (most recent call last):
    < 67758.2007>   File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
    < 67758.2009>   File "/usr/lib/enigma2/python/Screens/CronTimer.py", line 147, in addtocron
    < 67758.2010>   File "/usr/lib/enigma2/python/mytest.py", line 324, in openWithCallback
    < 67758.2012>     dlg = self.open(screen, *arguments, **kwargs)
    < 67758.2012>   File "/usr/lib/enigma2/python/mytest.py", line 334, in open
    < 67758.2014>     dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
    < 67758.2015>   File "/usr/lib/enigma2/python/mytest.py", line 271, in instantiateDialog
    < 67758.2016>     return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
    < 67758.2016>   File "/usr/lib/enigma2/python/mytest.py", line 294, in doInstantiateDialog
    < 67758.2023>     dlg = screen(self, *arguments, **kwargs)
    < 67758.2023>   File "/usr/lib/enigma2/python/Screens/CronTimer.py", line 318, in __init__
    < 67758.2025> AttributeError: 'CronTimersConfig' object has no attribute 'KeyText'
    < 67758.2025> [ePyObject] (CallObject(<bound method ActionMap.action of <Components.ActionMap.ActionMap instance at 0xaf16ab98>>,('ColorActions', 'green')) failed
    Using vix 5.4.001


    Steps to reproduce error

    Menu, timers, Cron Timers and press green to add
    Attached Files Attached Files
    Last edited by dsayers; 25-10-20 at 11:49.

  14. #11
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,764
    Thanks
    473
    Thanked 607 Times in 433 Posts
    Quote Originally Posted by Willo3092 View Post
    No, still not working. Is it right that there is no mention of cron timers in the debug logs? /var/log/messages is the only place I can see any reference to them.
    These are my root entries in /etc/cron/crontabs/, nothing seems to work apart from ntpdate-sync.
    I've tried changing the script permissions but doesn't seem to have any effect.

    30 * * * * /usr/bin/ntpdate-sync silent
    02 00 * * * /usr/script/skyscraper.sh
    */15 * * * * /usr/script/skypicker.sh
    * * * * * /usr/script/willo.sh

    Oct 25 09:31:01 zgemmah7 cron.info crond[2133]: (readme.txt) ORPHAN (no passwd entry)
    Oct 25 09:31:01 zgemmah7 cron.info crond[2133]: (root) BAD FILE MODE (/var/spool/cron/crontabs/root)
    Manually added toppicks and it worked on the half hour for me

    Code:
    0 9 * * * /usr/script/skyscraper.sh
    */30 * * * * /usr/script/skypicker.sh

  15. #12
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,067
    Thanks
    752
    Thanked 403 Times in 303 Posts
    I just went into the cron timers screen and also got a crash:

    < 4273.9163> 11:04:45.1634 [Screen] Showing screen 'CronTimers'.
    < 4273.9640> 11:04:45.2110 [Console] finished: /usr/bin/opkg list_installed cronie
    [MAIN] executing main
    TuxTxt cache cleared
    < 4273.9879> 11:04:45.2349 Traceback (most recent call last):
    < 4273.9880> 11:04:45.2350 File "/usr/lib/enigma2/python/Components/Console.py", line 45, in finishedCB
    < 4273.9883> 11:04:45.2354 File "/usr/lib/enigma2/python/Screens/CronTimer.py", line 65, in checkNetworkState
    < 4273.9885> 11:04:45.2355 File "/usr/lib/enigma2/python/Screens/CronTimer.py", line 198, in updateList
    < 4273.9887> 11:04:45.2357 IndexError: list index out of range
    < 4273.9888> 11:04:45.2358 [ePyObject] (CallObject(<bound method EnigmaLogFatal.write of <bound method Process.__init__ of <bound method EnigmaLogDebug.write of <bound method ActionMap.action of <bound method boundFunction.__call__ of <bound method List.doSuspend of <bound method VolumeText.changed of <bound method CList.__call__ of <bound method Label.changed of <bound method Label.changed of <bound method Label.changed of <bound method Label.changed of <bound method Label.changed of <bound method CList.__call__ of <unbound method eLabel.eLabel_setText>>>>>>>>>>>>>>>,(0,)) failed)
    < 4277.9593> 11:04:49.2063 [gRC] main thread is non-idle! display spinner!

  16. #13
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,764
    Thanks
    473
    Thanked 607 Times in 433 Posts
    Quote Originally Posted by Willo3092 View Post
    I just went into the cron timers screen and also got a crash:

    < 4273.9163> 11:04:45.1634 [Screen] Showing screen 'CronTimers'.
    < 4273.9640> 11:04:45.2110 [Console] finished: /usr/bin/opkg list_installed cronie
    [MAIN] executing main
    TuxTxt cache cleared
    < 4273.9879> 11:04:45.2349 Traceback (most recent call last):
    < 4273.9880> 11:04:45.2350 File "/usr/lib/enigma2/python/Components/Console.py", line 45, in finishedCB
    < 4273.9883> 11:04:45.2354 File "/usr/lib/enigma2/python/Screens/CronTimer.py", line 65, in checkNetworkState
    < 4273.9885> 11:04:45.2355 File "/usr/lib/enigma2/python/Screens/CronTimer.py", line 198, in updateList
    < 4273.9887> 11:04:45.2357 IndexError: list index out of range
    < 4273.9888> 11:04:45.2358 [ePyObject] (CallObject(<bound method EnigmaLogFatal.write of <bound method Process.__init__ of <bound method EnigmaLogDebug.write of <bound method ActionMap.action of <bound method boundFunction.__call__ of <bound method List.doSuspend of <bound method VolumeText.changed of <bound method CList.__call__ of <bound method Label.changed of <bound method Label.changed of <bound method Label.changed of <bound method Label.changed of <bound method Label.changed of <bound method CList.__call__ of <unbound method eLabel.eLabel_setText>>>>>>>>>>>>>>>,(0,)) failed)
    < 4277.9593> 11:04:49.2063 [gRC] main thread is non-idle! display spinner!
    Is yours crashing when going into Cron Timers screen or trying to add Cron timer? Mine crashes when pressing green to add in Cron timer screen

  17. #14
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,067
    Thanks
    752
    Thanked 403 Times in 303 Posts
    I'd already gone into the Cron Timers screen and manually added the script after first deleting it from /etc/cron/crontabs/root.
    I'd set the script to run every minute (because I have no patience!).
    It didn't run so I went back into Cron Timers screen and no cron jobs showing at all and then it crashed.

  18. #15
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,764
    Thanks
    473
    Thanked 607 Times in 433 Posts
    For my crash it looks like it's been fixed here https://github.com/OpenViX/enigma2/c...87ab5a72ecec4a maybe fixed in next update.


    For the Cron timer it's working for me */30 * * * * /usr/script/skypicker.sh is running every 30 minutes

Page 1 of 2 12 LastLast

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.