Symptoms
Services may throw segmentation faults when a server crashes and disk corruption occurs; this can cause service to report down and may be unable to start due to segmentation faults.
Description
When a server crashes or is restored from a bad image, it can lead to data corruption that causes segmentation faults for the services.
You can check for hard drive corrupt through /var/log/message and you will see entries similar to this:
EXT4-fs (dm-2): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (dm-2): initial error at time 1541392746: ext4_find_entry:1312: inode 3412729
EXT4-fs (dm-0): initial error at time 1584604049: ext4_lookup:1447: inode 1453424
EXT4-fs (dm-0): last error at time 1592986565: ext4_lookup:1447: inode 1453566
EXT4-fs (dm-2): last error at time 1592937125: ext4_mb_generate_buddy:758
This will likely be the culprit for any service issues when restarting the services.
Workaround
If the services are segfaulting, you will want to move the following file and run the upcp script.
# mv /usr/local/cpanel/bin/restartsrv_base{,.backup}
# /scripts/upcp --sync
[2020-06-30 19:16:15 -0400] Detected cron=0 (Terminal detected)
[2020-06-30 19:18:42 -0400] Completed all updates
=> Log closed Tue Jun 30 19:18:42 2020
To confirm this worked, simply call the script directly:
#/usr/local/cpanel/bin/restartsrv_base
You cannot call the 'scripts/restartsrv_base' script directly.
Or test a restart:
# /scripts/restartsrv_clamd --status
clamd (/usr/local/cpanel/3rdparty/bin/clamd) is running as root with PID 10597 (systemd+/proc check method).