[Eisfair] Fwd: fcron <wwwrun at eis2> /var/owncloud/owncloud-cron.sh

[Stefan Welte]

Hallo Marcus,

Am 07.10.2016 um 08:19 schrieb Marcus Roeckrath:
>>> Vielleicht kommt der etwas zu früh.
>> scheinbar direkt wenn cron oder apache2 oder was auch immer beim Booten
>> startet.
> 
> Wie steht der cronjob bei Dir?
> 
> Defaultmäßig startet der immer um x.14, x.28 ... auch nach einem Reboot.
jup, so auch bei mir.

> Komisch, wenn Du beim Boot immer genau diese Zeiten treffen solltest.
ja, vier Mal an vier Tagen. Die eposts kam 00, 14, 28 und 42.
Bei 00 und 42 war es dummer Zufall.

Bei 28 fing allerdings asterisk um 27:40 an zu protokollieren, daher sollte dort apache2, redis bereits am
Start gewesen sein.
Auszug der messages-logdatei:
> Oct  5 09:26:30 eis2 kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> Oct  5 09:26:38 eis2 fcrontab[7851]: installing file /tmp/fcr-fM1h1D for user root
> Oct  5 09:26:39 eis2 fcron[4672]: updating configuration from /var/spool/fcron
> Oct  5 09:26:39 eis2 fcron[4672]: adding new file root
> Oct  5 09:26:39 eis2 fcrontab[7869]: installing file /tmp/fcr-wU6uje for user wwwrun
> Oct  5 09:26:39 eis2 fcron[4672]: SIGTERM signal received
> Oct  5 09:26:39 eis2 fcron[4672]: Exiting with code 0
> Oct  5 09:26:42 eis2 fcron[7898]: fcron[7898] 3.2.0 started
> Oct  5 09:26:42 eis2 fcron[7898]: @reboot jobs will only be run at computer's startup.
> Oct  5 09:26:42 eis2 fcron[7898]: updating configuration from /var/spool/fcron
> Oct  5 09:26:42 eis2 fcron[7898]: adding file wwwrun
> Oct  5 09:26:42 eis2 fcron[7898]: adding file root
> Oct  5 09:26:42 eis2 fcron[7898]: adding new file wwwrun
> Oct  5 09:26:42 eis2 fcron[7898]: adding new file root
> Oct  5 09:26:57 eis2 squid: Processing Configuration File: /etc/squid.conf (depth 0) 
...
> Oct  5 09:27:57 eis2 kernel: dahdi_transcode: Loaded.
> Oct  5 09:28:00 eis2 fcron[11619]: Job '/var/owncloud/owncloud-cron.sh' started for user wwwrun (pid 11632)
> Oct  5 09:28:10 eis2 fcron[11619]: Job '/var/owncloud/owncloud-cron.sh' completed (mailing output)
> Oct  5 09:28:30 eis2 pure-ftpd: (?@172.21.5.49) [INFO] New connection from 172.21.5.49
...
> Oct  5 09:41:11 eis2 pure-ftpd: (wwwrun at 172.21.4.49) [INFO] Logout.
> Oct  5 09:42:00 eis2 fcron[5403]: Job '/var/owncloud/owncloud-cron.sh' started for user wwwrun (pid 5412)
> Oct  5 09:42:43 eis2 fcron[5403]: Job '/var/owncloud/owncloud-cron.sh' completed
...
> Oct  5 09:55:02 eis2 fcron[30115]: Job '/var/install/config.d/lm_sensors.sh make_cron' completed
> Oct  5 09:56:00 eis2 fcron[32197]: Job '/var/owncloud/owncloud-cron.sh' started for user wwwrun (pid 32206)
> Oct  5 09:56:21 eis2 fcron[32197]: Job '/var/owncloud/owncloud-cron.sh' completed
> Oct  5 09:58:31 eis2 pure-ftpd: (?@172.21.5.49) [INFO] New connection from 172.21.5.49


Bei 14 doch wohl auch dummer Zufall:
> Oct  4 09:13:47 eis2 kernel: pnp 00:03: [dma 4]
> Oct  4 09:13:47 eis2 fcron[2327]: fcron[2327] 3.2.0 started
> Oct  4 09:13:47 eis2 xinetd[2299]: Started working: 11 available services
> Oct  4 09:13:47 eis2 kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
> Oct  4 09:13:47 eis2 fcron[2327]: updating configuration from /var/spool/fcron
> Oct  4 09:13:47 eis2 kernel: pnp 00:04: [io  0x0070-0x0071]
> Oct  4 09:13:47 eis2 fcron[2327]: adding file wwwrun
> Oct  4 09:13:47 eis2 kernel: pnp 00:04: [irq 8]
> Oct  4 09:13:47 eis2 fcron[2327]: adding file root
> Oct  4 09:13:47 eis2 kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
> Oct  4 09:13:47 eis2 fcron[2327]: job '/usr/local/eisgraph/eisgraph.sh graph > /dev/null' did not finish : running it again.
> Oct  4 09:13:47 eis2 kernel: pnp 00:05: [io  0x00f0-0x00fe]
> Oct  4 09:13:47 eis2 fcron[2327]: job '/usr/local/eisgraph/eisgraph.sh collect > /dev/null' did not finish : running it again.
> Oct  4 09:13:47 eis2 kernel: pnp 00:05: [irq 13]
> Oct  4 09:13:48 eis2 kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
...
> Oct  4 09:14:09 eis2 kernel: EXT3-fs (sda6): using internal journal
> Oct  4 09:14:09 eis2 fcron[3231]: Job '/var/owncloud/owncloud-cron.sh' started for user wwwrun (pid 3390)
> Oct  4 09:14:09 eis2 fcron[2327]:     process already running: root's '/usr/local/eisgraph/eisgraph.sh collect > /dev/null'
> Oct  4 09:14:09 eis2 kernel: kjournald starting.  Commit interval 5 seconds
...
> Oct  4 09:14:11 eis2 kernel: eth0: no IPv6 routers present
> Oct  4 09:14:11 eis2 kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> Oct  4 09:14:15 eis2 fcrontab[4800]: installing file /tmp/fcr-ds0fgf for user root
> Oct  4 09:14:17 eis2 fcron[2327]: updating configuration from /var/spool/fcron
> Oct  4 09:14:17 eis2 fcron[2327]: adding new file root
> Oct  4 09:14:17 eis2 fcrontab[4818]: installing file /tmp/fcr-lUxkyD for user wwwrun
> Oct  4 09:14:18 eis2 fcron[2327]: SIGTERM signal received
> Oct  4 09:14:23 eis2 fcron[5106]: fcron[5106] 3.2.0 started
> Oct  4 09:14:23 eis2 fcron[5106]: @reboot jobs will only be run at computer's startup.
> Oct  4 09:14:23 eis2 fcron[5106]: updating configuration from /var/spool/fcron
> Oct  4 09:14:23 eis2 fcron[5106]: adding file wwwrun
> Oct  4 09:14:23 eis2 fcron[5106]: job '/var/owncloud/owncloud-cron.sh' did not finish : running it again.
> Oct  4 09:14:23 eis2 fcron[5106]: adding file root
> Oct  4 09:14:23 eis2 fcron[5106]: adding new file wwwrun
> Oct  4 09:14:23 eis2 fcron[5106]: adding new file root
> Oct  4 09:14:40 eis2 fcron[3231]: Job '/var/owncloud/owncloud-cron.sh' completed (mailing output)
> Oct  4 09:14:44 eis2 squid: Processing Configuration File: /etc/squid.conf (depth 0) 
...
> Oct  4 09:25:02 eis2 fcron[25451]: Job '/var/install/config.d/lm_sensors.sh make_cron' completed
> Oct  4 09:28:00 eis2 fcron[30977]: Job '/var/owncloud/owncloud-cron.sh' started for user wwwrun (pid 30986)
> Oct  4 09:28:34 eis2 fcron[30977]: Job '/var/owncloud/owncloud-cron.sh' completed
> Oct  4 09:28:43 eis2 pure-ftpd: (?@172.21.4.49) [INFO] New connection from 172.21.4.49

Die epost beim dummen Zufall
Oct  4 09:14:23 eis2 fcron[5106]: job '/var/owncloud/owncloud-cron.sh' did not finish : running it again.
Oct  4 09:14:40 eis2 fcron[3231]: Job '/var/owncloud/owncloud-cron.sh' completed (mailing output)
leuchtet mir ein, aber
Oct  5 09:28:00 eis2 fcron[11619]: Job '/var/owncloud/owncloud-cron.sh' started for user wwwrun (pid 11632)
Oct  5 09:28:10 eis2 fcron[11619]: Job '/var/owncloud/owncloud-cron.sh' completed (mailing output)
nicht, da alle Dienste zu dieser Zeit an sind.

Wenn ich dazu komme, mache ich einen Neustart direkt nach dem cronlauf, damit der Server bereits >5min oben
ist, bis der erste Cronlauf für owncloud kommt.
Wäre es sinnvoll das irgendwie abzufangen: Dass der Server > 10 Minuten oben sein muss, damit der cronjob
das erste Mal startet?

Stefan