• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Question Error 503

Nicola

Basic Pleskian
Hello,
since a couple of days there are many random 503 errors coming from only one software (in the domain there are other software that do not present problems).

When the error occurs in the logs I see that the request is interrupted because the process (in this case the 180208) is terminated

plesk-php72-fpm/error.log
[10-Apr-2019 09:07:38] WARNING: [pool example.com] child 180208 exited on signal 11 (SIGSEGV) after 53.208653 seconds from start

audit/audit.log
type=ANOM_ABEND msg=audit(1554880058.362:2627880): auid=4294967295 uid=10038 gid=1003 ses=4294967295 pid=180208 comm="php-fpm" reason="memory violation" sig=11

In addition there are several errors always from the same software

[Wed Apr 10 10:04:27.951187 2019] [proxy_fcgi:error] [pid 64197:tid 140410173179648] (104)Connection reset by peer: [client 87.26.38.204:60582] AH01075: Error dispatching request to :, referer: https://example.com/page/example/

Is there a way to better investigate the problem?

The domain is served by nginx and this application is the only one that uses the rewrite engine url


Regards
 
The script that is requested or an asynchronously running script (an AJAX call from the browser) has errors and is not responding with a proper output.
 
Back
Top