[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-server does not maintain the pidfile /var/run/sw-cp-server.pid
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-server does not maintain the pidfile /var/run/sw-cp-server.pid