Knowledge Search


×
 

[EX/QFX/SRX] Syslog Message: "Scheduler Oinker"

  [KB19723] Show Article Properties


Summary:

This article provides information about the Scheduler Oinker syslog message.

Symptoms:

The Scheduler Oinker syslog message below is sometimes encountered:

fpc0 SCHED: Thread "<id>" ("<reason >") ran for "<time>" ms without yielding
fpc0 Scheduler Oinker
Cause:

Scheduler Oinker messages are generated on the console when a single thread of execution does not release itself from memory and CPU resources.

Solution:

Scheduler Oinker messages, though undesirable, do not indicate a malfunction or problem with device functionality. They simply indicate that a thread is not releasing itself from memory and CPU resources.

Scheduler Oinker messages can be safely ignored.

In the example below, the Syslog message is related to the information obtained by the device about PFE statistics (such as when traceoption are enabled or frequent information is generated by any other service).

Dec 3 02:58:21 sny-js19 fpc0 SCHED: Thread 21 (PFE Statistics) ran for 18446744069414584331 ms without yielding
Dec 3 02:58:21 sny-js19 fpc0 Scheduler Oinker
To block these message from appearing on console or being logged by syslog output,  add the following configuration to the 'system syslog' configuration stanza:


    Console Ouptuts
user * {
any emergency;
match "!(.*Scheduler Oinker*.|.*Frame 0*.|.*ms without yielding*.)";
}

    Local Syslog Files
files messages {
any any ;
match "!(.*Scheduler Oinker*.|.*Frame 0*.|.*ms without yielding*.)";
}
   
    Remote syslog Outputs
host 1.1.1.1 {
any any ;
match "!(.*Scheduler Oinker*.|.*Frame 0*.|.*ms without yielding*.)";
}



Related Links: