killed by SIGSEGV

[blueearth]

Hello, first post here. For the last few weeks, I am seeing many logs reporting: lsphp killed by SIGSEGV. All variants of PHP I.E 7.1/7.2/5.6

It started after either a WHM update or Litespeed update. Output below. Any help would be appreciated. I have xxxx out any sensitive info.

reason:         lsphp killed by SIGSEGV
cmdline:        lsphp:/home/xxxxxxx/public_html/mainsite/index.php
executable:     /opt/alt/php72/usr/bin/lsphp
package:        alt-php72-cli-7.2.13-1.el7
component:      alt-php72
pid:            10386
pwd:            /opt/cpanel/ea-php56/root/usr/bin
hostname:       xxxxxxxxxx
count:          50
abrt_version:   2.1.11
analyzer:       CCpp
architecture:   x86_64
event_log:     
global_pid:     10386
kernel:         3.10.0-714.10.2.lve1.5.19.9.el7.x86_64
last_occurrence: 1545029665
os_release:     CloudLinux release 7.6 (Vladimir Lyakhov)
pkg_arch:       x86_64
pkg_epoch:      0
pkg_fingerprint: 8C55 A662 8608 CB71
pkg_name:       alt-php72-cli
pkg_release:    1.el7
pkg_vendor:     CloudLinux
pkg_version:    7.2.13
runlevel:       N 3
time:           Sat 15 Dec 2018 03:23:58 PM GMT
type:           CCpp
uid:            1440
username:       xxxxxxx
uuid:           3af87ecd254b5a96a4818e5f2636a2b4d0974751

 

[cPanelMichael]

Hello @blueearth,

The issue you've reported looks similar to an issue addressed as part of a recent mod_lsapi update from CloudLinux:

https://cloudlinux.com/cloudlinux-os-blog/entry/mod-lsapi-updated-1-20

Are you using mod_lsapi on this system? If so, can you run the following command and let us know the output so we can confirm you're using the most recent version on the affected system?

rpm -qa|grep lsapi

Thank you.

 

[blueearth]

Thanks for your reply, no we are using CloudLinux.

 

[cPanelMichael]

Hi @blueeearth,

Can you open a support ticket with cPanel so we can take a closer look at the affected system?

Thank you.

 

[blueearth]

Hi, thanks for your reply. I have opened a ticket with cPanel.
best
Nick

 

[cPanelMichael]

Hi Nick,

It looks like our Technical Analysts advised increasing the PMEM limit for the account referenced in the log output. Let us know if this helps.

Thank you.