Switching

Saved one interface setting and goe the error below.

 

Message from syslogd@ at Jun 10 20:13:32 ...
fpc0 SCHED: Thread 34 (PFE Manager) ran for 1174 ms without yielding

Message from syslogd@ at Jun 10 20:13:31 ...
pfex: Scheduler Oinker

Message from syslogd@ at Jun 10 20:13:32 ...
fpc0 Scheduler Oinker

Message from syslogd@ at Jun 10 20:13:31 ...
pfex: Frame 00: sp = 0x05af13c0, pc = 0x0184da7c

Message from syslogd@ at Jun 10 20:13:31 ...
pfex: Frame 01: sp = 0x05af13d8, pc = 0x01810948

Message from syslogd@ at Jun 10 20:13:32 ...
fpc0 Frame 00: sp = 0x05af13c0, pc = 0x0184da7c

Message from syslogd@ at Jun 10 20:13:31 ...
pfex: Frame 02: sp = 0x05af1438, pc = 0x018129ec

Message from syslogd@ at Jun 10 20:13:32 ...
fpc0 Frame 01: sp = 0x05af13d8, pc = 0x01810948

Message from syslogd@ at Jun 10 20:13:31 ...
pfex: Frame 03: sp = 0x05af1460, pc = 0x018478dc

Message from syslogd@ at Jun 10 20:13:32 ...
fpc0 Frame 02: sp = 0x05af1438, pc = 0x018129ec

Message from syslogd@ at Jun 10 20:13:31 ...
pfex: Frame 04: sp = 0x05af1518, pc = 0x018122f0

Message from syslogd@ at Jun 10 20:13:32 ...
fpc0 Frame 03: sp = 0x05af1460, pc = 0x018478dc

Message from syslogd@ at Jun 10 20:13:32 ...
fpc0 Frame 04: sp = 0x05af1518, pc = 0x018122f0

 

can this be ignored or there is some fix for it?

Thanks

Hi aspx9

 

it is safely to ignore the log message , please refer to the following KB link it contains all the details.

 

https://supportportal.juniper.net/s/article/Syslog-Message-Scheduler-Oinker 

(*this link has been updated to reflect the latest KB article)

------------------------------------------

 

If this solves your problem, please mark this post as "Accepted Solution.

Hi,

 That is always bad (exept boot up) to see stack trace in log files.

I don't recomended to ignore these messages. Do you see any core-dump files in "show system core" output command?

If so, that is the time to ask JTAC about of reason of the proccess crash.

Hi,

 

The below KB says that  the Scheduler Oinker  messages indicate that a thread is not releasing itself from memory and CPU resources. I think you should note the frequency of the messages and if are frequent, please check with JTAC if they are safe to ignore and why a threat is not releasing itself from the  CPU and memory. May be it is a minor trigger but ideally a small change to interface shouldn't trigger any trace. 

https://supportportal.juniper.net/s/article/Syslog-Message-Scheduler-Oinker   (*this link has been updated to reflect the latest KB Article )

Regards,

Rahul Gautam

Please mark my solution as accepted if it helped.

What is this box and version running? Was there any service impacting event in and around the logs were seen. There are occasions this need not be the actual root cause or trigger, this could be just an outcome of some other event seen with the box.

I think,

that is the reason of the messages:

PR1398398

---

@python wrote:
What is this box and version running? Was there any service impacting event in and around the logs were seen. There are occasions this need not be the actual root cause or trigger, this could be just an outcome of some other event seen with the box.

---

 

Please check if there was a fpc restart following these logs. If so a coredump analysis would be required (jtac case). Usually the Scheduler Oinker messages are generated on the system console when a single thread of execution does not release itself from memory and CPU resources. Do you see these messages every time you make a config change on a specific interface?

Good day,

 

Please don't ignore this messages due to It's most likely the result of the PR1398398.

Please check this PR and try the workaround or use Junos with the fix of the problem.

Hello, 

 

What is the platform and what Junos version is it running? Can you also paste the output of "show system processes extensive | except 0.00"? 

 

Thanks,

Puneet