Jump to content


Photo

cron does not run on develop

Started by doglover, 06 Jun 2021 09:35

  • Please log in to reply
11 replies to this topic

#1 doglover

  • Rytec EPG Team
  • 17,013 posts

+639
Excellent

Posted 6 June 2021 - 09:35

Although I have installed busybox-cron, I cannot see cron running on develop on the Mutant HD2400.

It does not show up at the ps command either.

S   UID   PID  PPID   VSZ   RSS TTY   STIME TIME     CMD
S     0     1     0  1884   508 0:0   Jun03 00:00:00 init [3]
S     0     2     0     0     0 0:0   Jun03 00:00:00 [kthreadd]
S     0     4     2     0     0 0:0   Jun03 00:00:00 [kworker/0:0H]
S     0     5     2     0     0 0:0   Jun03 00:00:01 [kworker/u4:0]
S     0     6     2     0     0 0:0   Jun03 00:00:16 [ksoftirqd/0]
S     0     7     2     0     0 0:0   Jun03 00:00:00 [rcu_sched]
S     0     8     2     0     0 0:0   Jun03 00:00:00 [rcu_bh]
S     0     9     2     0     0 0:0   Jun03 00:00:00 [migration/0]
S     0    10     2     0     0 0:0   Jun03 00:00:00 [lru-add-drain]
S     0    11     2     0     0 0:0   Jun03 00:00:00 [cpuhp/0]
S     0    12     2     0     0 0:0   Jun03 00:00:00 [cpuhp/1]
S     0    13     2     0     0 0:0   Jun03 00:00:00 [migration/1]
S     0    14     2     0     0 0:0   Jun03 00:00:00 [ksoftirqd/1]
S     0    16     2     0     0 0:0   Jun03 00:00:00 [kworker/1:0H]
S     0    17     2     0     0 0:0   Jun03 00:00:00 [kdevtmpfs]
S     0    18     2     0     0 0:0   Jun03 00:00:00 [oom_reaper]
S     0    19     2     0     0 0:0   Jun03 00:00:00 [writeback]
S     0    20     2     0     0 0:0   Jun03 00:00:00 [crypto]
S     0    22     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    23     2     0     0 0:0   Jun03 00:00:00 [kblockd]
S     0    24     2     0     0 0:0   Jun03 00:00:00 [ata_sff]
S     0    25     2     0     0 0:0   Jun03 00:00:00 [cfg80211]
S     0    26     2     0     0 0:0   Jun03 00:00:00 [rpciod]
S     0    27     2     0     0 0:0   Jun03 00:00:00 [xprtiod]
S     0    28     2     0     0 0:0   Jun03 00:00:16 [kswapd0]
S     0    29     2     0     0 0:0   Jun03 00:00:00 [vmstat]
S     0    30     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    31     2     0     0 0:0   Jun03 00:00:00 [nfsiod]
S     0    32     2     0     0 0:0   Jun03 00:00:00 [cifsiod]
S     0    60     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    61     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    62     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    63     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    64     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    65     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    66     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    67     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    68     2     0     0 0:0   Jun03 00:00:00 [scsi_eh_0]
S     0    69     2     0     0 0:0   Jun03 00:00:00 [scsi_tmf_0]
S     0    70     2     0     0 0:0   Jun03 00:00:00 [scsi_eh_1]
S     0    71     2     0     0 0:0   Jun03 00:00:00 [scsi_tmf_1]
S     0    78     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    79     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    80     2     0     0 0:0   Jun03 00:00:00 [bioset]
S     0    82     2     0     0 0:0   Jun03 00:00:00 [ubi_bgt0d]
S     0    83     2     0     0 0:0   Jun03 00:00:00 [ubifs_bgt0_0]
S     0   135     2     0     0 0:0   Jun03 00:00:06 [lllllllllllllll]
S     0   136     2     0     0 0:0   Jun03 00:00:00 [fffffffffffffff]
S     0   137     2     0     0 0:0   Jun03 00:00:00 [nxsched]
S     0   138     2     0     0 0:0   Jun03 00:00:01 [nxsched]
S     0   139     2     0     0 0:0   Jun03 00:00:08 [nxsched]
S     0   140     2     0     0 0:0   Jun03 00:00:00 [nxsched]
S     0   141     2     0     0 0:0   Jun03 00:00:00 [nxsched]
S     0   142     2     0     0 0:0   Jun03 00:00:00 [nxsched]
S     0   143     2     0     0 0:0   Jun03 00:00:00 [nxsched]
S     0   144     2     0     0 0:0   Jun03 00:06:21 [nxsched]
S     0   145     2     0     0 0:0   Jun03 00:00:00 [pp_work]
S     0   146     2     0     0 0:0   Jun03 00:00:00 [rp_work]
S     0   147     2     0     0 0:0   Jun03 00:00:00 [reboot_work]
S     0   148     2     0     0 0:0   Jun03 00:00:00 [ci_work]
S     0   149     2     0     0 0:0   Jun03 00:00:00 [sci0]
S     0   150     2     0     0 0:0   Jun03 00:00:00 [sci1]
S     0   151     2     0     0 0:0   Jun03 00:00:00 [cec-hdmi_cec]
S     0   167     1 10876   848 0:0   Jun03 00:00:00 /sbin/udevd -d
S   999   411     1  2860   952 0:0   Jun03 00:00:00 /usr/bin/dbus-daemon --system
S     0   413     2     0     0 0:0   Jun03 00:00:00 [ipv6_addrconf]
S     0   415     1  2532   520 0:0   Jun03 00:00:00 /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22
S   998   420     1  2428   708 0:0   Jun03 00:00:00 /usr/sbin/rpcbind
S     0   425     2     0     0 0:0   Jun03 00:00:35 [cifsd]
S     0   434     2     0     0 0:0   Jun03 00:00:12 [kworker/1:1H]
S     0   435     2     0     0 0:0   Jun03 00:01:21 [kworker/0:1H]
S   997   444     1  3060  1124 0:0   Jun03 00:00:00 /usr/sbin/rpc.statd
S     0   457     1  3296   604 0:0   Jun03 00:00:00 /usr/sbin/inetd
S     0   463     2     0     0 0:0   Jun03 00:00:00 [lockd]
S     0   464     2     0     0 0:0   Jun03 00:00:00 [nfsd]
S     0   465     2     0     0 0:0   Jun03 00:00:00 [nfsd]
S     0   466     2     0     0 0:0   Jun03 00:00:00 [nfsd]
S     0   467     2     0     0 0:0   Jun03 00:00:00 [nfsd]
S     0   468     2     0     0 0:0   Jun03 00:00:00 [nfsd]
S     0   469     2     0     0 0:0   Jun03 00:00:00 [nfsd]
S     0   470     2     0     0 0:0   Jun03 00:00:00 [nfsd]
S     0   471     2     0     0 0:0   Jun03 00:00:00 [nfsd]
S     0   473     1  3244   940 0:0   Jun03 00:00:00 /usr/sbin/rpc.mountd
S     0   482     1 38960  2904 0:0   Jun03 00:00:01 /usr/sbin/smbd
S     0   485   482 37736  2720 0:0   Jun03 00:00:00 {smbd-notifyd} /usr/sbin/smbd
S     0   486   482 37740  2620 0:0   Jun03 00:00:00 {cleanupd} /usr/sbin/smbd
S     0   487     1 27052  2500 0:0   Jun03 00:00:07 /usr/sbin/nmbd
R     0   495     1  2000   592 0:0   Jun03 49:00:01 /usr/sbin/wsdd
S     0   499     1  3068   552 0:0   Jun03 00:00:00 /sbin/syslogd -n -O /var/log/messages
S     0   502     1  3068   556 0:0   Jun03 00:00:00 /sbin/klogd -n
S   997   509     1  3540  1256 0:0   Jun03 00:00:01 avahi-daemon: running [hd2400.local]
S   997   510   509  3412   616 0:0   Jun03 00:00:00 avahi-daemon: chroot helper
S     0   513     1  6748   688 0:0   Jun03 00:00:00 /usr/bin/oscam --wait 60 --config-dir /etc/tuxbox/config/oscam --da
S     0   514   513 18092  5232 0:0   Jun03 00:29:57 /usr/bin/oscam --wait 60 --config-dir /etc/tuxbox/config/oscam --da
S     0   518     1  3040   680 0:0   Jun03 00:00:00 {enigma2.sh} /bin/sh /usr/bin/enigma2.sh
S     0   544   518  303m  178m 0:0   Jun03 01:00:33 /usr/bin/enigma2
S     0 12599     2     0     0 0:0   09:39 00:00:00 [kworker/1:1]
S     0 17593     2     0     0 0:0   07:45 00:00:02 [kdvb-ad-0-fe-0]
S     0 20671     2     0     0 0:0   10:11 00:00:00 [kworker/u4:1]
S     0 23352     2     0     0 0:0   10:22 00:00:00 [kworker/1:2]
S     0 23937   457  3164  1400 0:0   10:25 00:00:00 telnetd
S     0 23938 23937 27132  5800 pts0  10:25 00:00:00 /bin/login
S     0 23957 23938  7852  2216 pts0  10:25 00:00:00 -sh
S     0 24633   482 47884  9392 0:0   08:13 00:00:02 /usr/sbin/smbd
S     0 24731     2     0     0 0:0   10:28 00:00:00 [kworker/1:0]
R     0 25387 23957  3068  1284 pts0  10:30 00:00:00 ps -l
S     0 29343     2     0     0 0:0   19:53 00:00:37 [kworker/0:1]
S     0 31708     2     0     0 0:0   21:51 00:00:00 [kworker/0:0]

What can I do to revive cron?

 

Box info:

 

Systeem OE:  PLi-OE
Firmware versie:  OpenPLi develop (2021-05-27-develop)
Kernel versie / stuurprogramma datum:  4.10.12 / 20180424
 


Edited by doglover, 6 June 2021 - 09:46.

~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: cron does not run on develop #2 rantanplan

  • PLi® Contributor
  • 1,806 posts

+83
Good

Posted 6 June 2021 - 09:58

https://github.com/O...247572fa8191679

 

rework cron


Re: cron does not run on develop #3 doglover

  • Rytec EPG Team
  • 17,013 posts

+639
Excellent

Posted 6 June 2021 - 10:19

And now....  what?

 

This also means that this:

30 * * * *    /usr/bin/ntpdate-sync silent

 

 

does not runs anymore.


Edited by doglover, 6 June 2021 - 10:31.

~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: cron does not run on develop #4 rantanplan

  • PLi® Contributor
  • 1,806 posts

+83
Good

Posted 6 June 2021 - 12:14

As I understand it, you have to start Cron first

case "$1" in
    start)
        echo -n "starting $DESC: $NAME... "
	start-stop-daemon -S -b -n $NAME -a $DAEMON -- $ARGS
	echo "done."
	;;

 


Re: cron does not run on develop #5 doglover

  • Rytec EPG Team
  • 17,013 posts

+639
Excellent

Posted 6 June 2021 - 12:41

Is it not the idea that cron is automatically started?


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: cron does not run on develop #6 rantanplan

  • PLi® Contributor
  • 1,806 posts

+83
Good

Posted 6 June 2021 - 12:54

You can have cron start automatically by putting this in the autostart.
Perhaps it is easier to install this Crondmanager-plgin.
 

via script make it believe most of those who use cron
 


Re: cron does not run on develop #7 doglover

  • Rytec EPG Team
  • 17,013 posts

+639
Excellent

Posted 6 June 2021 - 13:08

I never had to start cron on OpenPLi.  Install it and it runs.

BTW:  there is no crondmanager plugin in the OpenPli feed.


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: cron does not run on develop #8 doglover

  • Rytec EPG Team
  • 17,013 posts

+639
Excellent

Posted 6 June 2021 - 13:16

There is a busybox-cron in init.d.

 

It contains this:

 

ARGS="-c /var/sppol/cron"

 

but there is no folder with this name:

there is however a  /var/spool/cron/  folder.

 

A typo?

 

Changed the sppol in the init.d  script to spool.

Will report the result.


Edited by doglover, 6 June 2021 - 13:19.

~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: cron does not run on develop #9 doglover

  • Rytec EPG Team
  • 17,013 posts

+639
Excellent

Posted 6 June 2021 - 13:44

cron runs now.

 

So indeed a typo.

 

Request to Wanwizard:  Can you correct  the Typo pls.


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: cron does not run on develop #10 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 6 June 2021 - 14:51

Woops... Done.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: cron does not run on develop #11 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 22 July 2021 - 18:31

I am also have a problem with cron.I am add some command to /etc/cron/crontabs/root but the script not run.On openpli 8.0 the same script working fine.

If I put this command on telnet:  /etc/init.d/busybox-cron start & I got this message:

 

root@osmio4k:~# starting Busybox Periodic Command Scheduler: crond... /usr/sbin/crond is already running
root@osmio4k:~# starting Busybox Periodic Command Scheduler: crond... /usr/sbin/crond is already running
-sh: root@osmio4k:~#: command not found

What am I doing wrong because the command I enter in the root file does not work.


Edited by Rudi1, 22 July 2021 - 18:32.

VU+Zero

Osmio4K

Re: cron does not run on develop #12 Pr2

  • PLi® Contributor
  • 6,075 posts

+257
Excellent

Posted 22 July 2021 - 19:28

cron is now running by default in OpenPLi so you try to stard an already running process.

You need to use:

/etc/init.d/busybox-cron restart

 

Or if you only need to reload the change in the configuration file you can use:

 

/etc/init.d/busybox-cron reload


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 

Back to [EN] Test Feedback

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Forums
  2. → PLi® Development
  3. → [EN] Test Feedback