• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

sw-cp-server does not maintain the pidfile /var/run/sw-cp-server.pid

Miguel_Tellería

Basic Pleskian
[Plesk 12.0.18 on CentOS 6 with the latest microupdates]

Hi there,

From time time we observe the following phenomenon. Am I the only one?

Plesk nginx front-end (sw-cp-server) is running perfectly and listening on port 8443 but the pidfile (/var/run/sw-cp-server.pid) is missing or corresponds to a non-existing process (probably a previous encarnation).

This creates false watchdog alarms and inhibits any changes in Plesk front-end config (e.g. changing TLS certificate) becase a service sw-cp-service stop doesn't kill the process and the socket is already taken.

The only way to come back from this situation is manually killing the actual sw-cp-server process (easy to find through ps or netstat), actually kill it for a second time (the listener is taken over by another process) and start the process with the service command.

The server has not gone through any high load scenario.

Is there a way to fix this?
 
Back
Top