Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

random reboot - stale tasks

Status
Not open for further replies.

james1982

Technical User
Nov 14, 2003
441
GB
Hi,

Have a 3300 mxe rel 8 ur 5.
Today it randomly rebooted, ive checked the logs and found the below.
To me it basically looks like there was a critical alarm due to Stale Tasks, this caused a resource reboot. Can anyone confirm what stale tasks are, and how to prevent them - cant have this occur again!!!

Clearly feel free to correct me if ive got this completely wrong!!

All Maintenance/Software Logs

Log Type: Maintenance
Log Number: 1360
Severity: Warning
Date: 2009/Feb/25
Time: 14:43:53
Source: AppShutdown
Description: Maintenance: Category(General); msgFormatId(0) Progress Monitor->InitiateShutdown System Shutdown invoked by task: tTMonitor
Module: Main
File Name and Line Number: Maintenance;0


Log Type: Maintenance
Log Number: 1359
Severity: Warning
Date: 2009/Feb/25
Time: 14:43:53
Source: ResourceMonitor
Description: Maintenance: Category(General); msgFormatId(0) Progress Monitor->RaiseAlarm Raised Critical Alarm on Stale Tasks
Module: Main
File Name and Line Number: Maintenance;0



 
Stale tasks are tasks (think processing threads here) that have for whatever reason stopped running. Tasks are categorized by importance, and when this happens to less important or less critical tasks, they are considered 'stale'. Instead of immediately rebooting the system to recover the resources lost by that task stopping, it is delayed until a scheduled reboot time. If of course it is deemed a critical task, then the reboot is immediate.

For example, if the task that collects log messages stops, you can live without that until a schedule reboot time. On the other hand if it's one of the call processing tasks, then there's little point in keeping the system up if no one can make calls.

There should be another log in the system before those indicating what task actually suspended.
 
think this is the other log:

Log Number: 1361
Severity: Error
Date: 2009/Feb/25
Time: 14:43:53
Source: Task Monitor
Description: Maintenance: Category(General); msgFormatId(0) Critical Alarm being raised upon detecting the following task suspended: SacDataSrv 0x3971b40 at: WED FEB 25 14:42:52 2009


Any idea what SacDataSrv is?????

cheers
 
It's related to 5330/5340 phone applications, which is why it's not critical, people may not be able to run applications on their set but they could still make phone calls.

You'll need to talk to Mitel to find out why it suspended....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top