Skip to Content

ezsh segfault or kicked of ezsh ssh session or ssh session crash

How to resolve ezsh segfault error or ezsh shell crashes without error messages, causing you to be logged out of the Ezeelogin backend?


Overview: The article outlines troubleshooting steps to resolve EZSH shell crashes and segfault errors, focusing on checking resource limits, whitelisting the binary in security software, and reviewing specific log files for error details.


The normal skm abrt[25575]: Saved core dump of pid 25575 (/usr/local/bin/ezsh) to /var/spool/abrt/ccpp-2017-04-18-11:58:28-25575 (2420736 bytes)

Apr 18 11:58:28 skm abrtd: Executable '/usr/local/bin/ezsh' doesn't belong to any package and ProcessUnpackaged is set to 'no'

Step 1: This is most likely occurring because of resource shortages.Ensure that there is enough memory on the server. Raise the memory limits on the server and reboot. 

Step 2: Also, make sure that security software like CloudLinux is not blocking the /usr/local/bin/ezsh binary, if yes, ensure to whitelist it.

Step 3: Check for the logs for any errors messages

root@gateway:~# /home/username/ezsh.log

root@gateway:~# /var/log/message

root@gateway:~# /var/log/dmesg 


Related Articles:

Unable to login to Ezeelogin Backend - CageFS-Cloudlinux