• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Phusion Passenger on CentOS 8 causes nginx and apache stop commands to hang until timeout

websavers

Regular Pleskian
This is a weird one. The commands systemctl stop httpd and systemctl stop nginx hang until timeout (90s) on CentOS 8.

I narrowed it down to Phusion Passenger -- once removed (via Plesk Installer), nginx and httpd stop normally. When I reinstall Passenger (which I kinda need for nodejs and ruby support), the issue returns.

When I check nginx and apache logs, Phusion Passenger reports as stopping within seconds of the stop command, but for some reason systemctl doesn't seem to realize it. The logs don't indicate any actual problems with Phusion Passenger.

passenger-6.0.6-2.centos.8+p18.0.31.0+t201020.1804.x86_6
CentOS Linux release 8.2.2004 (Core)
Plesk Obsidian Version 18.0.31
 
For unknown reasons this doesn't appear to be a problem with apache restarts anymore. I reinstalled Phusion and the apache service appears to be able to stop fine. However nginx is still an issue. If I edit /usr/share/passenger/phusion_passenger/locations.ini and comment out nginx_module_source_dir=/usr/share/passenger/ngx_http_passenger_module nginx then restarts fine again without the 1.5 minute delay.

From what I can tell Plesk integrates with Phusion through apache such that requests are proxied with nginx like this:

Incoming request -> nginx -> apache -> phusion

If this is accurate, then the changes I made above should be fine. Does anyone know if any of the Phusion services are launched direct through nginx like the following?

Incoming request -> nginx -> phusion

As I'm assuming that the changes I made will break that, if so.
 
Back
Top