cPanel results in Segmentation faults

Spike1506

Registered
May 10, 2010
2
0
51
All of the sudden every script in /scripts results in a Segmentation fault.
Even upgrading or a force upgrade is not possible due the segmentation faults.
yum update results in: memory alloc (71900 bytes) returned NULL.
And running perl commands also results in segmentation faults.

How can I solve this?
My cPanel version: 11.25.0-CURRENT_45139
 

JaredR.

Well-Known Member
Feb 25, 2010
1,834
27
143
Houston, TX
cPanel Access Level
Root Administrator
Wide variety of possible causes

Segmentation faults can be caused by any number of things, and it sounds like this is affecting most operations on the server. The first thing to do is to check dmesg:

Code:
# dmesg
In the output, look specifically for any memory- or hardware-related error or failure messages. Next, check to see if the system has any free RAM:

Code:
# free -m
I would recommend that you submit a ticket so that we can look at the server directly. There really is a large number of things that can be wrong, and it is difficult to even speculate without logging into the server.
 

cPanelJamyn

Social Engineer
Staff member
Jan 29, 2009
105
2
143
All of the sudden <snip> yum update results in: memory alloc (71900 bytes) returned NULL.<snip>
This is likely an insufficient memory issue; I presume you're running on a VM (with associated dynamic memory allocation) so these issues can happen more often in those environments. If it exists, what does 'cat /proc/user_beancounters' return?
 

Spike1506

Registered
May 10, 2010
2
0
51
Segmentation faults can be caused by any number of things, and it sounds like this is affecting most operations on the server. The first thing to do is to check dmesg:

Code:
# dmesg
In the output, look specifically for any memory- or hardware-related error or failure messages. Next, check to see if the system has any free RAM:

Code:
# free -m
I would recommend that you submit a ticket so that we can look at the server directly. There really is a large number of things that can be wrong, and it is difficult to even speculate without logging into the server.
dmesg does not show any hardware related issues to me.
Only messages like: perl[19803]: segfault at 00007fffcb462ff0 rip 00002aeedfee2be4 rsp 00007fffcb462ff0 error 6
setupvirtfs[19942]: segfault at 00007fffa2331ff8 rip 00002b5208d514c0 rsp 00007fffa2332008 error 6
fixperl[20228]: segfault at 00007fff6834cff0 rip 00002b964303585a rsp 00007fff6834cfa0 error 6

free -m results in:
total used free shared buffers cached
Mem: 1024 818 205 0 15 137
-/+ buffers/cache: 664 359
Swap: 2047 172 1875

So the amount of memory is not a problem either.
If I have to support a ticket what is the best place to do so?

This is likely an insufficient memory issue; I presume you're running on a VM (with associated dynamic memory allocation) so these issues can happen more often in those environments. If it exists, what does 'cat /proc/user_beancounters' return?
That results in a "No such file or directory" error.