[7.450][QUESTION][ANSWERED] Cron Task Scheduler not running - restarted

This night I received the following notification:

Cron Task Scheduler not running - restarted

--
System Uptime      : 4 days 15 hours 14 minutes
System Load        : 0.41
System Version     : Astaro Security Gateway Software 7.450

This was just at the time at which I configured the PPPoE automatic reconnect (0400h).

The system log only noted:

2009:06:04-04:00:19 astaro1 /usr/sbin/cron[1836]: (CRON) STARTUP (V5.0)
2009:06:04-04:00:22 astaro1 /usr/sbin/cron[1936]: (CRON) STARTUP (V5.0)

This was the first time I ever got this notification.

Regards,
Bastian

0 nitehawk over 16 years ago

Is this regularly? Sometimes it can happen that a service is restart - you know this :-).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Monarch over 16 years ago in reply to nitehawk

I'd say it happened three or four times during the last 16 days (where the beta has not been rebooted).

I created the thread, as this did never occur for months in the past with earlier versions.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Astaro Beta Bot over 16 years ago in reply to Monarch

Astaro Beta Report
--------------------------------
Version: 7.450
Type: QUESTION
State: ANSWERED
Reporter: Monarch
Contributor: 
MantisID: 
--------------------------------

0 [Thorsten] over 16 years ago in reply to Astaro Beta Bot

Monarch,

since update to V7.460 I didn't get the message "/usr/sbin/cron[3018]: (CRON) STARTUP (V5.0)" anymore.

Can you confirm, that is it also stopped on your ASG using V7.460+?

BR,
Thorsten
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Monarch over 16 years ago in reply to [Thorsten]

Yes, didn't occur with 7.460 anymore until now.

Regards,
Bastian
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BuBU over 16 years ago in reply to Monarch

Hi

I can also confirm.. got that in 7.450 but have no more cron restart for 7.460

thx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 andyk007 over 16 years ago

due to middleware and confdaemon changes this seems to be fixed in 7.460

greetings
andreas
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 stevenhemelaere over 16 years ago

I just got the same error with 7.470, should this be made a new thread then?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Monarch over 16 years ago in reply to stevenhemelaere

I don't know. And I don't know why this has been re-labled as question, too [;)]
I'll monitor my installation for further occurrences of this event (but I did a fresh install for safety reasons...).

Regards,
Bastian
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 stevenhemelaere over 16 years ago in reply to Monarch

bump

Not solved.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel