• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Random 502 Bad Gateway Again and Again

labulle

New Pleskian
Hi,

I'm the guy who is never posting a problem usually but I'm tired with Plesk I'm doing nothing instead using plesk web admin but I ofter get : 502 Bad Gateway

Code:
Starting psa...  * Starting Plesk engine pool manager sw-engine-fpm             Segmentation fault
                                                                         [fail]
                                                                     done
Starting xinetd service...                                           done
Starting sw-cp-server service...                                     done
Starting mysql service...                                            done
Starting bind9 service...                                            done
Starting postgresql service...                                       not installed
Starting spamassassin service...                                     not installed
Plesk: Starting Mail Server... already started
Starting psa...  * Starting Plesk engine pool manager sw-engine-fpm             Segmentation fault
                                                                         [fail]
                                                                     done
Starting drwebd service...                                           done


I checked log but I don't get any clue at psa restart :
2015/11/20 11:00:47 [crit] 4271#0: *21 connect() to unix:/var/run/sw-engine.sock failed (2: No such file or directory) while connecting to upstream, client: ::1, server: , request: "POST /check-plesk.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "localhost:8443"

Can someone help to check were does that seg fault error comes from ??

Regards,
 
Je précise que ce n'est que l'admin de Plesk qui renvoie cette erreur, les sites webs tournent eux..
 
Back
Top