[Eisfair] Update Base 2.7.3 online

[Jürgen Witt]

Hallo Marcus,

Am 31.05.2016 um 09:16 schrieb Marcus Roeckrath:
> Hallo Jürgen,
> 
> 
>> Ich sehe auch in /var/spool/fcron, das die Datein verändert wurden.
>>
>> server # ls -la /var/spool/fcron
>> total 20
>> drwxrwx---  2 fcron fcron 4096 May 29 00:37 .
>> drwxr-xr-x 11 root  root  4096 Aug 27  2012 ..
>> -rw-------  1 root  fcron 1949 May 29 00:37 new.root
>> -rw-------  1 root  root  1954 May 29 00:37 root
>> -rw-------  1 root  fcron 3672 May 29 00:37 root.orig
> 
> Wann hast Du das Update genau durchgeführt?
> 
> xx.05.16 7:31?

nein, am 29.5. um 0:37 Uhr

hier noch einmal der vorher/nachher Effekt

Vor dem Update (installiert am 29.5. 0:37 Uhr) sieht es am 28.5. kurz
vor 2:00 Uhr so aus:

May 28 01:14:04 server fcron[5541]: Job 'chmod 544
/var/www/htdocs/roundcube/bin/cleandb.sh;
/var/www/htdocs/roundcube/bin/cleandb.sh >/dev/null' completed
May 28 02:00:00 server fcron[5797]: Job '/usr/bin/snapshot > /dev/null'
started for user root (pid 5806)
May 28 02:00:00 server fcron[5807]: Job '/var/install/config.d/eisfax.sh
make_faxqclean' started for user root (pid 5817)
May 28 02:00:02 server fcron[5807]: Job '/var/install/config.d/eisfax.sh
make_faxqclean' completed
May 28 02:05:00 server fcron[5894]: Job '/var/install/bin/smartmon-plot'
started for user root (pid 5903)
May 28 02:05:54 server fcron[5894]: Job '/var/install/bin/smartmon-plot'
completed
May 28 02:08:00 server fcron[7673]: Job '/sbin/setdate -quiet' started
for user root (pid 7682)
May 28 02:08:05 server fcron[7673]: Job '/sbin/setdate -quiet' completed
May 28 03:00:00 server fcron[8006]: Job '/var/install/config.d/eisfax.sh
make_faxqclean' started for user root (pid 8015)
May 28 03:00:02 server fcron[8006]: Job '/var/install/config.d/eisfax.sh
make_faxqclean' completed
May 28 03:05:00 server fcron[8069]: Job '/var/install/bin/smartmon-plot'
started for user root (pid 8078)
May 28 03:05:35 server fcron[8069]: Job '/var/install/bin/smartmon-plot'
completed
May 28 03:07:00 server fcron[9893]: Job
'/var/webmail/bin/remove_forgotten_attachments' started for user root
(pid 9902)
May 28 03:07:02 server fcron[9893]: Job
'/var/webmail/bin/remove_forgotten_attachments' completed
May 28 03:08:00 server fcron[9930]: Job '/sbin/setdate -quiet' started
for user root (pid 9939)
May 28 03:08:06 server fcron[9930]: Job '/sbin/setdate -quiet' completed
May 28 04:00:00 server fcron[10508]: Job '/usr/bin/test-plattenplatz'
started for user root (pid 10517)
May 28 04:00:00 server fcron[10518]: Job
'/var/install/config.d/eisfax.sh make_faxqclean' started for user root
(pid 10527)
May 28 04:00:02 server fcron[10508]: Job '/usr/bin/test-plattenplatz'
completed

Und jetzt am 29.5. ab 0:0 Uhr

May 29 00:00:00 server fcron[28754]: Job '/etc/cron.daily/logrotate'
started for user root (pid 28763)
May 29 00:00:00 server fcron[28764]: Job '/usr/bin/test-plattenplatz'
started for user root (pid 28773)
May 29 00:00:00 server fcron[28774]: Job
'/var/install/config.d/eisfax.sh make_faxqclean' started for user root
(pid 28784)
May 29 00:00:02 server fcron[28774]: Job
'/var/install/config.d/eisfax.sh make_faxqclean' completed
May 29 00:00:02 server fcron[28764]: Job '/usr/bin/test-plattenplatz'
completed
May 29 00:00:10 server fcron[28754]: Job '/etc/cron.daily/logrotate'
completed
May 29 00:05:00 server fcron[28993]: Job
'/var/install/bin/smartmon-plot' started for user root (pid 29002)
May 29 00:05:25 server fcron[28993]: Job
'/var/install/bin/smartmon-plot' completed
May 29 00:08:00 server fcron[30790]: Job '/sbin/setdate -quiet' started
for user root (pid 30799)
May 29 00:08:05 server fcron[30790]: Job '/sbin/setdate -quiet' completed
May 29 00:25:00 server fcron[30921]: Job '/usr/bin/updatedb 1>/dev/null'
started for user root (pid 30930)
May 29 00:37:26 server fcron[2036]: SIGTERM signal received
May 29 00:37:31 server fcrontab[752]: installing file /tmp/fcr-jvjXYm
for user root
May 29 02:39:05 server fcron[30921]: Job '/usr/bin/updatedb 1>/dev/null'
completed
May 31 08:08:42 server fcrontab[2939]: installing file /tmp/fcr-3daoRd
for user root
May 31 08:08:45 server fcron[2978]: fcron[2978] 3.2.0 started
May 31 08:08:45 server fcron[2978]: @reboot jobs will only be run at
computer's startup.
May 31 08:08:46 server fcron[2978]: updating configuration from
/var/spool/fcron
May 31 08:08:46 server fcron[2978]: adding file root
May 31 08:08:46 server fcron[2978]: job '/usr/bin/updatedb 1>/dev/null'
did not finish : running it again.
May 31 08:08:46 server fcron[2978]: adding new file root
May 31 08:10:00 server fcron[3020]: Job '/root/prfweg.sh &> /dev/null'
started for user root (pid 3029)
May 31 08:10:02 server fcron[3020]: Job '/root/prfweg.sh &> /dev/null'
completed
May 31 08:20:00 server fcron[3155]: Job '/root/prfweg.sh &> /dev/null'
started for user root (pid 3164)
May 31 08:20:02 server fcron[3155]: Job '/root/prfweg.sh &> /dev/null'
completed
May 31 08:30:00 server fcron[3371]: Job '/root/prfweg.sh &> /dev/null'
started for user root (pid 3380)
May 31 08:30:02 server fcron[3371]: Job '/root/prfweg.sh &> /dev/null'
completed
May 31 08:35:37 server fcron[2978]: SIGTERM signal received
May 31 08:35:38 server fcron[2978]: Exiting with code 0
May 31 08:35:40 server fcron[3551]: fcron[3551] 3.2.0 started
May 31 08:35:40 server fcron[3551]: @reboot jobs will only be run at
computer's startup.
May 31 08:35:40 server fcron[3551]: updating configuration from
/var/spool/fcron
May 31 08:35:40 server fcron[3551]: adding file root


> Die Dateien in /var/spool/fcron sind allerdings von 29.05.16 0:37.
> 
> Falsch wäre allerdings die new.root, die IMHO nur als temporäre Datei von
> fcron während der Neuerzeugung der Cron-Jobs - also z. B. bei Aufruf
> von /var/install/config.d/cron.sh - erzeugt wird.
> 
> Da ist also etwas am 29.5. 00:37 schief gelaufen.

aber nicht nur auf einem System, sondern auf (fast - ich prüfe noch)
allen meinen Servern

> 
>> Kann das jemand bestätigen?
> 
> Ich nicht.
> 
>> Reicht ein Reboot?
> 
> Mach mal ein
> 
> /var/install/config.d/cron.sh

OK, habe ich ausgeführt.

> und danach darf /var/spool/fcron/new.root NICHT existieren. Ich würde sie
> sogar vor dem cron.sh Aufruf löschen.

die Datei war schon weg. Wahrscheinlich, weil ich die cron-Konfiguration
mehrfach aufgerufen und abgespeichert habe. Ebenso haben ich über das
Menü cron mehrfach gestoppt und gestartet.

Danke
Jürgen