Received fatal signal SIGSEGV

Moderator: NorbertKrupa

Post Reply
ogreDnO
Newbie
Newbie
Posts: 1
Joined: Mon Mar 21, 2016 10:12 am

Received fatal signal SIGSEGV

Post by ogreDnO » Mon Mar 21, 2016 11:33 am

Hello,
One of my vertica cluster node down, and in log file a found :

Code: Select all

2016-03-19 20:01:55.263 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.263 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.266 nameless:0x7f325accb730 [Main] <INFO> Handling signal: 11
2016-03-19 20:01:55.291 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.291 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.292 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.292 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.292 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.292 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.293 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.293 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.294 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.294 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.294 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.294 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.295 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.295 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.296 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.296 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.297 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.297 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.297 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.297 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.298 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> SortManager found maxMerges 7 too small(38 MB Assigned).
2016-03-19 20:01:55.298 Init Session:0x7f3420013970-b00000000a70ab [EE] <INFO> After disabling optimization, maxMerges becomes 7.
2016-03-19 20:01:55.305 EEThread:0x7f307fab12c0-c0000000099401 [EE] <INFO> Running ROS from sort buffer. Merge chunks = 1, merges per batch = 36
2016-03-19 20:01:55.305 EEThread:0x7f3379799f10-c0000000099401 [EE] <INFO> Running ROS from sort buffer. Merge chunks = 1, merges per batch = 36
2016-03-19 20:01:55.305 EEThread:0x7f2fb3edbea0-c0000000099401 [EE] <INFO> Running ROS from sort buffer. Merge chunks = 1, merges per batch = 36
2016-03-19 20:01:55.306 EEThread:0x7f307fab12c0-c0000000099401 [EE] <INFO> Finished writing one ROS at 0.00 sec. Write cost 0.00 sec, including compress pipe wait 0.00 sec
2016-03-19 20:01:55.306 EEThread:0x7f3379799f10-c0000000099401 [EE] <INFO> Finished writing one ROS at 0.00 sec. Write cost 0.00 sec, including compress pipe wait 0.00 sec
2016-03-19 20:01:55.307 EEThread:0x7f2fb3edbea0-c0000000099401 [EE] <INFO> Finished writing one ROS at 0.00 sec. Write cost 0.00 sec, including compress pipe wait 0.00 sec
2016-03-19 20:01:55.308 EEThread:0x7f307fab12c0-c0000000099401 [EE] <INFO> Finished writing ROSes from sort buffer.
2016-03-19 20:01:55.309 EEThread:0x7f3379799f10-c0000000099401 [EE] <INFO> Finished writing ROSes from sort buffer.
2016-03-19 20:01:55.309 EEThread:0x7f2fb3edbea0-c0000000099401 [EE] <INFO> Finished writing ROSes from sort buffer.
2016-03-19 20:01:56.780 nameless:0x7f325accb730 [Main] <PANIC> Received fatal signal SIGSEGV.
2016-03-19 20:01:56.780 nameless:0x7f325accb730 [Main] <PANIC> Info: si_code: 128, si_pid: 0, si_uid: 0, si_addr: (nil)
Maybe someone now the reason of this crash ?

User avatar
JimKnicely
Site Admin
Site Admin
Posts: 1778
Joined: Sat Jan 21, 2012 4:58 am
Contact:

Re: Received fatal signal SIGSEGV

Post by JimKnicely » Wed Mar 23, 2016 2:58 am

Search this site for SIGSEGV. If you can't find an answer there, you really need to open a ticket with Vertica support.
Jim Knicely

Image

Note: I work for HPE. My views, opinions, and thoughts expressed here do not represent those of my employer.

Post Reply

Return to “Vertica Community Edition”