How to get rid of Frame 0 and oinker on cli

Have you ever experienced the message

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:

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

5 thoughts on “How to get rid of Frame 0 and oinker on cli

  1. Timothy McGaha

    Console CLI stalls and I cannot type any input until after the message burps out. While ssh session it occurs as the ssh session stalls and disconnects. You cannot stay ssh sessioned without being kicked off trueing to figure this out.

    Reply
    1. christianscholz Post author

      Hi Timothy,
      I never had this issue – the messages are just “blocking my view” but never actually disconnect me.
      What Device and Version are you using?

      BR
      Chris

      Reply
  2. monsi

    This post has been a life saver so far in 2021.

    also did you ever keep pressing buttons on the console thinking you cannot connect….??

    then find out, it’s because you left a ping running……..

    after ctrl + z

    spoiler alert

    i did

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Captcha * Time limit is exhausted. Please reload CAPTCHA.