• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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