IP500v2 Monitor Alarm log dump

[gmacdonald78]

Can anyone detail the meaning of this alarm and a fix other than swapping out the IPO CCU, its got the dreaded "i will reboot randomly when I want affliction" In the past we have always just swapped out the CCU but this seems really wasteful?

09:39:37 1463173907mS PRN: +++ START OF ALARM LOG DUMP +++
09:39:37 1463173907mS PRN: ALARM: 27/09/2018 21:34:01 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 752 Rem: 199904 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f149a488 f149a130 f0743d70 f070ef7c
09:39:37 1463173907mS PRN: ALARM: 29/09/2018 10:43:24 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 752 Rem: 199336 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f149a488 f149a130 f0743d70 f070ef7c
09:39:37 1463173907mS PRN: ALARM: 29/09/2018 14:46:31 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 752 Rem: 199776 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f149a488 f149a130 f0743d70 f070ef7c
09:39:37 1463173908mS PRN: ALARM: 29/09/2018 19:25:56 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 752 Rem: 199816 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f149a488 f149a130 f0743d70 f070ef7c
09:39:37 1463173908mS PRN: ALARM: 30/09/2018 01:37:12 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 752 Rem: 199360 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f149a488 f149a130 f0743d70 f070ef7c
09:39:37 1463173908mS PRN: ALARM: 30/09/2018 07:07:48 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 752 Rem: 199648 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f149a488 f149a130 f0743d70 f070ef7c
09:39:37 1463173908mS PRN: ALARM: 01/10/2018 15:44:35 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 752 Rem: 199608 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f149a488 f149a130 f0743d70 f070ef7c
09:39:37 1463173908mS PRN: ALARM: 01/10/2018 21:37:01 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 752 Rem: 199992 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f149a488 f149a130 f0743d70 f070ef7c
09:39:37 1463173908mS PRN: ALARM: 02/10/2018 16:15:53 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 4096 Rem: 199792 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f0337128 f113fa14 f113fe9c f0740890 f07414b8
09:39:37 1463173909mS PRN: ALARM: 04/10/2018 11:10:00 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 4096 Rem: 199976 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f0337128 f113fa14 f113fe9c f0740890 f07414b8
09:39:37 1463173909mS PRN: ALARM: 07/10/2018 14:41:08 IP 500 V2 9.0.12.0 build 1006 <No Pools! Req: 1216 Rem: 199920 > CRIT RAISED addr=f0380f48 d=5 pc=f03346d0 f03370e4 f09def7c f09df814 f04d0b18 f15a7d30
09:39:37 1463173909mS PRN: +++ END OF ALARM LOG DUMP +++

 

[sizbut]

Those a distinctly not random reboots - so what happens in the business at 9:39 each day? No pools make me think a memory leak but that wouldn't be so absolutely regular.

Stuck in a never ending cycle of file copying.

 

[janni78]

The reboot time isn't 9:39, it's when it's shown in SysMon.

Since you're on a unsupported software level you might consider upgrading to see if the issue remains, in that case you can raise a ticket.

"Trying is the first step to failure..." - Homer

 

[janni78]

Otherwise you need to leave monitor running and try to figure out what is happening before the reboot.

"Trying is the first step to failure..." - Homer

 

[sizbut]

I'd delete myself if I could...

Stuck in a never ending cycle of file copying.