We would like to receive notification the unexpected node restart.

Takayuki Anzai
ServiceNow Employee
ServiceNow Employee

Hi,

We are facing java.lang.OutOfMemoryError: Metaspace error(KB0960944) 2 or 3 times a week on an irregular basis on our production instance, and the node is restarted each time, it causes problems with some scheduled jobs and UIs.

We can't implement the workaround soon.

When this error occurs, we have to immediately check if there are impacts and recover.

We tried to configure the notification email as the event trigger against 'Node Start' event in the diagnostic_event table. However the diagnostic_event table does not support for using the notification email engine on an event trigger and it does not work.

Are there any ways to receive notification by email(,etc.) the unexpected node restart?

Thanks

7 REPLIES 7

Sulabh Garg
Mega Sage
Mega Sage

Hello,

we have the same issue on our Instance and HI recommend to apply the workaround mentioned in the below KB.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0960944&sysparm_rank=1&syspar...

 

you can also reach out to HI to resolve the concern.

 

 

find_real_file.png

Please Mark ✅ Correct/helpful, if applicable, Thanks!!
Regards
Sulabh Garg

Hi Sulabh,

Thank you very much for your reply. But as I mentioned, we can't apply the workaround soon for some reasons, so we would like to know how we can receive notification when node restarts unexpectedly.

Thanks

Hi Takayuki,

In that case, you can build the email notification with conditions as shown below when record is inserted into the diagnostic_event table, instead of the event.

Ideally it should work.

 

find_real_file.png

Please Mark ✅ Correct/helpful, if applicable, Thanks!!
Regards
Sulabh Garg

Hi Sulabh,

We tried to build the email notification with the conditions you provided against diagnostic_event table, but it didn't work.

ServiceNow technical support responded that the email notification engine does not support for diagnostic_event table, it supports only for the event that logged into the sysevent.LIST. Is it true??

Thanks,
Takayuki