SRX

Hi

I am using 2-node SRX 240 cluster. Today the primary node rebooted. After analyzing logs I have found this messages on rebooted node.

Jun  6 13:32:20 fwba01 /kernel: KERNEL_MEMORY_CRITICAL: System low on free memory, notifying init (#1264).
Jun  6 13:35:17 fwba01 /kernel: rt_pfe_veto: Severe low-free-pages, below threshold. Op 5, rtsm_id 0, msg type 1
Jun  6 13:35:17 fwba01 /kernel: rt_pfe_veto: Severe low-free-pages, below threshold. Op 4, rtsm_id 0, msg type 1
Jun  6 13:35:17 fwba01 /kernel: rt_pfe_veto: Possible slowest client is rmopd. States processed - 301105176. States to be processed - 174
Jun  6 13:36:17 fwba01 /kernel: rt_pfe_veto: Severe low-free-pages, below threshold. Op 4, rtsm_id 0, msg type 1
Jun  6 13:36:17 fwba01 /kernel: rt_pfe_veto: Possible slowest client is mcsnoopd. States processed - 301105262. States to be processed - 362
Jun  6 13:36:17 fwba01 /kernel: rt_pfe_veto: Possible second slowest client is rmopd. States processed - 301105465. States to be processed - 159
Jun  6 13:36:17 fwba01 /kernel: KERNEL_MEMORY_CRITICAL: System low on free memory, notifying init (#1406).

and

Last reboot reason             0x1000:reboot due to panic

After reboot I also lost configuration on rebooted node. Is this normal behaviour of SRXthat in case of low memory the system is rebooted ? thanks

Probably a memory leak bug, what version are you running?

Is there a core dump available?

show system core-dumps

Regards, Wojtek

Hi thansk

 

version is JUNOS Software Release [12.1X44-D60.2]

and core-dumps are not probably available

{secondary:node0}
root> show system core-dumps
node0:
--------------------------------------------------------------------------
/var/crash/*core*: No such file or directory
/var/tmp/*core*: No such file or directory
/var/tmp/pics/*core*: No such file or directory
/var/crash/kernel.*: No such file or directory
/tftpboot/corefiles/*core*: No such file or directory

Could be related to an older software issue.

 

12.1X44 release is End of Life

http://www.juniper.net/support/eol/junos.html

 

I would recommend upgrading the cluster to current recommended software release. You can check the details here:

https://kb.juniper.net/InfoCenter/index?page=content&id=KB21476&actp=METADATA

Thanks I will upgrade junos on the cluster.

I just wanted to know if it's some built-in mechanism to reboot node with low memory or just sw issue.