Have you ever experienced the message
|
1 2 3 4 5 6 7 8 |
Message from syslogd@srx3 at Jul 20 10:45:39 2017 ... srx3 srx3 SCHED: Thread 2 (Idle) ran for 1734 ms without yielding Message from syslogd@srx3 at Jul 20 10:45:39 2017 ... srx3 srx3 Scheduler Oinker Message from syslogd@srx3 at Jul 20 10:45:39 2017 ... srx3 srx3 Frame 0: sp = 0x2010f280, pc = 0x200c9e40 |
when labbing with your vSRX / vQFX / vMX or even with hardware?
Calm down – this is nothing to worry about.
With the following code your device will “silently drop” the messages for you:
|
1 2 3 4 5 6 7 8 |
system { syslog { user * { any emergency; match "!(.*Scheduler Oinker*.|.*Frame 0*.|.*ms without yielding*.)"; } } } |
Finally my CLI is calm again 😉
Source: https://kb.juniper.net/InfoCenter/index?page=content&id=KB19723