10-22-2011 03:24 AM
Has anyone else seen the following log errors and experienced connectivity loss (both web access through and SSH to the SRX) with 11.2R3?
Oct 21 21:51:38 srx100h init: l2cpd-service (PID 1235) started Oct 21 21:51:44 srx100h init: l2cpd-service (PID 1235) exited with status=0 Normal Exit Oct 21 21:51:44 srx100h init: l2cpd-service is thrashing, not restarted Oct 21 21:51:46 srx100h init: l2cpd-service (PID 1239) started Oct 21 21:51:46 srx100h init: can not access /usr/sbin/hostname-cached: No such file or directory Oct 21 21:51:46 srx100h init: hostname-caching-process (PID 0) started Oct 21 21:51:46 srx100h init: can not access /usr/sbin/ipmid: No such file or directory Oct 21 21:51:46 srx100h init: ipmi (PID 0) started Oct 21 21:51:52 srx100h init: l2cpd-service (PID 1239) exited with status=0 Normal Exit Oct 21 21:51:52 srx100h init: l2cpd-service is thrashing, not restarted Oct 21 21:52:02 srx100h /kernel: RT_PFE: RT msg op 1 (PREFIX ADD) failed, err 5 (Invalid) Oct 21 21:52:02 srx100h /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown) Oct 21 21:52:02 srx100h /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown) Oct 21 21:52:02 srx100h /kernel: GENCFG: op 2 (USP Blob) failed; err 7 (Doesn't Exist) Oct 21 21:52:06 srx100h last message repeated 2 times Oct 21 21:52:18 srx100h /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown) Oct 21 21:52:19 srx100h last message repeated 7 times
Thanks.
11-04-2011 05:26 PM
Yes! I'm getting almost exactly the same messages without switching subsystem or STP running on my SRX100's (chassie cluster) Did you ever solve this?
11-04-2011 05:33 PM
Sorry, to add to this. the VPN drops packets as does any packets addressed to the router, or any routing (NATting in my case) through the router. It's as if the router goes down for a time when I see these messages (about once a day, lasts for about a minute)
11-04-2011 08:31 PM
I am seeing the same on a SRX210 11.2R2.4 non-clustered box. Mine just rebooted after 2 weeks of those messages.
12-16-2011 11:24 AM - edited 12-16-2011 11:25 AM
I am seeing something similar on 11.2R4, has anyone opened cases on this?
01-27-2012 06:42 AM
We are seeing this as well accompanied by lots of low_mem_signal_processes messages. Spontaneous reboots occur about every other week.
SRX240 11.2R3
01-27-2012 08:36 AM
We have hit the same issue as well. Only choice is to upgrade to 11.2R4 or watch the CPU spike and reboot.
01-27-2012 02:23 PM
On my SRX100's, I rolled back to 10.4R6.5 and it has been as solid as a rock for a few months now.
05-28-2012 11:04 PM
Unable to ssh via Radius to the srx110. Software running on the device is 11.2R3.3
May 29 15:19:17 AUBBAUBSR001 init: l2cpd-service is thrashing, not restarted
May 29 15:19:47 AUBBAUBSR001 init: l2cpd-service (PID 70309) started
May 29 15:19:47 AUBBAUBSR001 init: can not access /usr/sbin/hostname-cached: No such file or directory
May 29 15:19:47 AUBBAUBSR001 init: hostname-caching-process (PID 0) started
May 29 15:19:48 AUBBAUBSR001 init: can not access /usr/sbin/ipmid: No such file or directory
May 29 15:19:48 AUBBAUBSR001 init: ipmi (PID 0) started
May 29 15:19:50 AUBBAUBSR001 init: l2cpd-service (PID 70309) exited with status=0 Normal Exit
May 29 15:19:50 AUBBAUBSR001 init: l2cpd-service (PID 70311) started
May 29 15:19:52 AUBBAUBSR001 init: l2cpd-service (PID 70311) exited with status=0 Normal Exit
Is this issue resolved in the JTAC recommended ver (11.2R6.3)
09-28-2012 09:14 AM - edited 09-28-2012 09:17 AM
FYI - I'm seeing the same error on two (independant, non-clustered) SRX 100s both running 12.1R3.5. Error being:
Sep 28 08:56:17 firewall-a init: l2cpd-service (PID 45596) exited with status=0 Normal Exit
Sep 28 08:56:17 firewall-a init: l2cpd-service (PID 45597) started
Sep 28 08:56:22 firewall-a init: l2cpd-service (PID 45597) exited with status=0 Normal Exit
...(service started / exited mesages repeat about a dozen times)...
Sep 28 08:56:22 firewall-a init: l2cpd-service is thrashing, not restarted
However, I'm not seeing crashes or reboots; just the error in logs.