How to investigate a PANIC

Forum|Forum|9 years ago
October 27, 2016
2 replies
20 views

+1

ScubaDrew
Participating Frequently

Hello,

I had a node go down today and am not able to find much info on why.

The vertica.log says:

2016-10-27 13:23:11.454 Init Session:0x7fc03401e080 [Main] <INFO> Handling signal: 11
2016-10-27 13:23:11.622 Init Session:0x7fc03401e080 [Main] <PANIC> Received fatal signal SIGSEGV.
2016-10-27 13:23:11.622 Init Session:0x7fc03401e080 [Main] <PANIC> Info: si_code: 1, si_pid: -335544320, si_uid: 32693, si_addr: 0x7fb5ec000000

And the next lines are from the restart...

How can I investigate what went wrong?

Thanks,

Drew

A

+2

Anonymous
Participating Frequently
Forum|Forum|9 years ago
November 9, 2016

with the PANIC vertica should write a ErrorReport.txt file with the vertica backtrace of what happened. At least there you should be able to see what session or transaciton PANIC the cluster. Vertica should not PANIC so I recommend to open a ticket with taht ErrorReport so we can investigate accordenly.

Hope this helps.

Eugenia