Segfaulting service scripts causing you a headache? It’s time to resolve those segmentation faults with help from our skilled Support Engineers.

If you have been at the receiving end of segfaulting Service scripts, our talented Support Techs have an easy solution for you. This trick will have your services up and running in no time.

What are segfaulting service scripts?

Segmentation faults are a common occurrence that often arises as a result of disk corruption or server crashes.

Before we dive into the solution, let’s take a closer look at the issue on hand. Segmentation faults are caused by a server crash or when the server is restored using a bad image. This leads to data corruption which ultimately causes segmentation faults. This is why you wind up facing segfaults.

How to resolve segfaulting service scripts?

First, let’s take a look at /var/log/message for signs of hard drive corruption like the entries seen below:

EXT4-fs (dm-2): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (dm-2): initial error at time 1541392747: ext4_find_entry:1312: inode 3412729
EXT4-fs (dm-0): initial error at time 1584604048: ext4_lookup:1447: inode 1453424
EXT4-fs (dm-0): last error at time 1592986564: ext4_lookup:1447: inode 1453566
EXT4-fs (dm-2): last error at time 1592937124: ext4_mb_generate_buddy:758

According to our Support Techs, this is the reason behind the service issues when you attempt to restart services.

Fortunately, we can resolve the issue by first moving the following file:

# mv /usr/local/cpanel/bin/restartsrv_base{,.backup}

Then, we will run the upcp script as illustrated below:

# /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

We can confirm if this resolved the issue by calling the script:

#/usr/local/cpanel/bin/restartsrv_base
You cannot call the 'scripts/restartsrv_base' script directly.

You can also verify with a restart:

#  /scripts/restartsrv_clamd --status
clamd (/usr/local/cpanel/3rdparty/bin/clamd) is running as root with PID 10597 (systemd+/proc check method).

[Have a similar query? Contact us for further assistance.]

Conclusion

To sum up, we learned how to deal with Segfaulting service scripts and get those services up and running after server crashes or disk corruptions. The solution offered by the skilled Support Techs resolved the issue in a jiffy.