11/17 web8 httpd issues

[Jeff]

Hi,

Please stand by while we troubleshoot httpd issues on web8. We were terminating a reseller's account via WHM when our server monitor reported httpd was not functioning properly. I believe this to be attributed to how cPanel/WHM is trying to terminate the account. This thread will be updated as soon as possible, thanks for your patience in the meantime.

[Jeff]

Further investigation shows this to be largely a non issue. httpd performance on web8 may be less than optimal while the reseller's account is being terminated. The reason for this is that the way cPanel's account terminating script ( /scripts/killacct ) works is that after terminating each of the resellers' accounts, it sends a SIGUSR1 to httpd for a graceful restart. As a result, there are a lot of defunct httpd processes, as connections are being made then torn down due to the restart.

However, our server monitoring utility has reported no further issues, and I have verified that I can successfully browse to many sites on web8. Performance is expected to fully return back to normal once this account has been deleted. I will check things out again after this has been completed and update the thread accordingly.

As an aside, I wonder if it wouldn't make more sense for /scripts/killacct to gracefully restart the webserver only after all accounts have been terminated, vice after each individual one. I will bring this to cPanel's attention for their thoughts.

[Jeff]

As expected, now that the resellers' account has been terminated, httpd performance on web8 has improved back to normal.

A bug report has been filed with cPanel regarding this, specifically requesting that the webserver not be restarted until all accounts have been terminated (vice restarting the webserver after each individual account termination).

If you have any questions, please feel free to let us know, thanks.