I'm not sure if you care or not, but here's a patch for internal case EA-4938.
/scripts/upcp gets ran and eventually initiates the bash script /usr/local/cpanel/scripts/remdefssl. On line 26 of remdefssl, /usr/local/cpanel/scripts/initsslhttpd gets executed.
/usr/local/cpanel/scripts/initsslhttpd is a very simple bash script that executes another script based on what Apache version is installed. On line 16, you can see it sets a variable, $script, to /usr/local/cpanel/scripts/initsslhttpd2_4, which is just a symbolic link to /usr/local/cpanel/scripts/initsslhttpd2_2. On line 17 of the initsslhttpd script, initsslhttpd2_2 gets executed. Either directly, or by the symbolic link that initsslhttpd2_4 points to (initsslhttpd2_2).
If you look at /usr/local/cpanel/scripts/initsslhttpd2_2, on lines 15 through 17, you see where the script deletes the EasyApache 4 /etc/init.d/httpd script (plus a few others). On line 29 of /usr/local/cpanel/scripts/initsslhttpd2_2 (or 2_4), you see where the /etc/init.d/httpd script is recreated, using the older EasyApache 3 style /etc/init.d/httpd script.
Whether the initsslhttpd2_2 script should still be executed or not, I don't know. But I do know that the patch I've attached removes the older EasyApache 3 style /etc/init.d/httpd script and replaces it with the newer EasyApache 4 /etc/init.d/httpd script.
Perhaps the developers could use the patch if initsslhttpd2_2 is actually still supposed to be executed. If not, perhaps anyone who runs CentOS 6 (maybe all CentOS distro's are affected) can benefit from this patch. Although /scripts/restartsrv_apache can restart Apache, I feel there's probably a lot of scripts that simply restart it via service httpd restart
Or even use service httpd status. A big one might be people who use Let's Encrypt crontab entries. For people who use this patch, they're more than likely going to need to put an entry in /etc/cpanelsync.exclude so /usr/local/cpanel/scripts/initsslhttpd2_2 doesn't get replaced.
Hopefully this can help EA-4938 get fixed a bit quicker. I created a ticket about this issue, ticket # 7609925 in case any cPanel technicians want to read it.
/scripts/upcp gets ran and eventually initiates the bash script /usr/local/cpanel/scripts/remdefssl. On line 26 of remdefssl, /usr/local/cpanel/scripts/initsslhttpd gets executed.
/usr/local/cpanel/scripts/initsslhttpd is a very simple bash script that executes another script based on what Apache version is installed. On line 16, you can see it sets a variable, $script, to /usr/local/cpanel/scripts/initsslhttpd2_4, which is just a symbolic link to /usr/local/cpanel/scripts/initsslhttpd2_2. On line 17 of the initsslhttpd script, initsslhttpd2_2 gets executed. Either directly, or by the symbolic link that initsslhttpd2_4 points to (initsslhttpd2_2).
If you look at /usr/local/cpanel/scripts/initsslhttpd2_2, on lines 15 through 17, you see where the script deletes the EasyApache 4 /etc/init.d/httpd script (plus a few others). On line 29 of /usr/local/cpanel/scripts/initsslhttpd2_2 (or 2_4), you see where the /etc/init.d/httpd script is recreated, using the older EasyApache 3 style /etc/init.d/httpd script.
Whether the initsslhttpd2_2 script should still be executed or not, I don't know. But I do know that the patch I've attached removes the older EasyApache 3 style /etc/init.d/httpd script and replaces it with the newer EasyApache 4 /etc/init.d/httpd script.
Perhaps the developers could use the patch if initsslhttpd2_2 is actually still supposed to be executed. If not, perhaps anyone who runs CentOS 6 (maybe all CentOS distro's are affected) can benefit from this patch. Although /scripts/restartsrv_apache can restart Apache, I feel there's probably a lot of scripts that simply restart it via service httpd restart
Or even use service httpd status. A big one might be people who use Let's Encrypt crontab entries. For people who use this patch, they're more than likely going to need to put an entry in /etc/cpanelsync.exclude so /usr/local/cpanel/scripts/initsslhttpd2_2 doesn't get replaced.
Hopefully this can help EA-4938 get fixed a bit quicker. I created a ticket about this issue, ticket # 7609925 in case any cPanel technicians want to read it.
Last edited by a moderator: