Jump to content
Welcome to our new Citrix community!

Citrix ADC - Unexpected Crash & Reboot


Recommended Posts

Hello there,

 

We are on Citrix ADC version 12.1 55.18. We have had recurring occurrences of Citrix ADC crashing due to EDT being on on several virtual servers and that was causing some core processes to crash in a previous build and had overcome this issue by upgrading to this version. Turned EDT back on and working okay for 7-8 months now. However, today the VPX crashed and rebooted today with the following log;

 

May 14 09:15:58 <local0.alert> ns nsppe: PE 2 (pid 91269) got signal 11; signal  mask is 0x0 0x0 0x0 0x0
May 14 09:15:58 <local0.alert> ns nsppe: PE 2 (pid 91269) got signal 11; signal  mask is 0x0 0x0 0x0 0x0
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 NSPPE-0  2 (91269) unexpectedly died due to receiving signal
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 NSPPE-0  2 (91269) unexpectedly died due to receiving signal
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 There may be a delay restarting process while collecting core dump on NSPPE-02 (91269)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 There may be a delay restarting process while collecting core dump on NSPPE-02 (91269)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 proc NSPPE-02 (91269) failure. Therefore initiating nCore NetScaler restart according to policy setting (0x29b4)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 proc NSPPE-02 (91269) failure. Therefore initiating nCore NetScaler restart according to policy setting (0x29b4)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 NetScaler restart may be delayed if collecting core dump for NSPPE-02 (91269)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 NetScaler restart may be delayed if collecting core dump for NSPPE-02 (91269)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 Pitboss declaring system failure: NSPPE-02 (91269) exited
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 Pitboss declaring system failure: NSPPE-02 (91269) exited
May 14 09:16:00 <kern.info> ns kernel: pid 91401 (nscac64p), uid 0: exited on signal 6 (core dumped)
May 14 09:16:00 <kern.info> ns kernel: pid 91401 (nscac64p), uid 0: exited on signal 6 (core dumped)
May 14 09:16:04 <kern.info> ns kernel: pid 91269 (NSPPE-02), uid 0: exited on signal 11 (core dumped)
May 14 09:16:04 <kern.info> ns kernel: pid 91269 (NSPPE-02), uid 0: exited on signal 11 (core dumped)
May 14 09:16:04 <local0.alert> ns restart[25070]:   Nsshutdown lock released !                                                                                                                                                               
May 14 09:16:04 <local0.alert> ns restart[25070]:   Nsshutdown lock released !

 

Any ideas? Just submitted a ticket to Citrix as well. This is a production environment issue affecting approximately 2000 people including call center users. Failover was successful and the standby node picked up all of the existing sessions.

Link to comment
Share on other sites

  • 3 years later...

hello, I have the same problem. can anyone tell us how to fix it? someone solved it?

On 5/14/2020 at 9:00 AM, Bertug Demir1709155795 said:

Hello there,

 

We are on Citrix ADC version 12.1 55.18. We have had recurring occurrences of Citrix ADC crashing due to EDT being on on several virtual servers and that was causing some core processes to crash in a previous build and had overcome this issue by upgrading to this version. Turned EDT back on and working okay for 7-8 months now. However, today the VPX crashed and rebooted today with the following log;

 

May 14 09:15:58 <local0.alert> ns nsppe: PE 2 (pid 91269) got signal 11; signal  mask is 0x0 0x0 0x0 0x0
May 14 09:15:58 <local0.alert> ns nsppe: PE 2 (pid 91269) got signal 11; signal  mask is 0x0 0x0 0x0 0x0
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 NSPPE-0  2 (91269) unexpectedly died due to receiving signal
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 NSPPE-0  2 (91269) unexpectedly died due to receiving signal
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 There may be a delay restarting process while collecting core dump on NSPPE-02 (91269)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 There may be a delay restarting process while collecting core dump on NSPPE-02 (91269)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 proc NSPPE-02 (91269) failure. Therefore initiating nCore NetScaler restart according to policy setting (0x29b4)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 proc NSPPE-02 (91269) failure. Therefore initiating nCore NetScaler restart according to policy setting (0x29b4)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 NetScaler restart may be delayed if collecting core dump for NSPPE-02 (91269)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 NetScaler restart may be delayed if collecting core dump for NSPPE-02 (91269)
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 Pitboss declaring system failure: NSPPE-02 (91269) exited
May 14 09:15:58 <local0.alert> ns [25]: pitboss Thu May 14 09:15:58 2020 Pitboss declaring system failure: NSPPE-02 (91269) exited
May 14 09:16:00 <kern.info> ns kernel: pid 91401 (nscac64p), uid 0: exited on signal 6 (core dumped)
May 14 09:16:00 <kern.info> ns kernel: pid 91401 (nscac64p), uid 0: exited on signal 6 (core dumped)
May 14 09:16:04 <kern.info> ns kernel: pid 91269 (NSPPE-02), uid 0: exited on signal 11 (core dumped)
May 14 09:16:04 <kern.info> ns kernel: pid 91269 (NSPPE-02), uid 0: exited on signal 11 (core dumped)
May 14 09:16:04 <local0.alert> ns restart[25070]:   Nsshutdown lock released !                                                                                                                                                               
May 14 09:16:04 <local0.alert> ns restart[25070]:   Nsshutdown lock released !

 

Any ideas? Just submitted a ticket to Citrix as well. This is a production environment issue affecting approximately 2000 people including call center users. Failover was successful and the standby node picked up all of the existing sessions.

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...