• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Plesk Obsidian - 18.0.36 and nginx worker connection issues

GregFowler

New Pleskian
Hi Guys,

I recently took a server from Plesk Obsidian 18.0.35 to .36, everything appeared to be fine but on a daily basis the sites go offline for 10/15 minutes at a time and return a 500 internal nginx error.

Looking at the nginx logs I can see the below entry continually in the error_log

2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough
2021/06/16 06:23:26 [alert] 54492#0: 1024 worker_connections are not enough

Looking through old logs the first occurence happened at:

2021/06/14 08:17:03 [alert] 37837#0: 1024 worker_connections are not enough

The only change that was made was updating Plesk to 18.0.36 which completed at 08:11 the same day so I can only conclude its related to this somehow.

Any pointers?
 
It is set to the default of 1024. I tried to double it but the same problem, still getting worked connections are not enough.

No errors in the log to this effect until the update, not sure if this this just a coincidence?
 
Hi,

I also face problems since upgrade to latest version this morning. Some PHP now take 5-15 minutes to "run" instead of 10 seconds (PDF generation on the fly), and also have the BUG of not fetching local SERVER side images.

Issue might be related to a change of some memory configuration on latest Plesk version, not known to users.

I have contacted the Plesk Support about 2 hours ago, however still haven't received response.

Currently, Plesk support do not see a connection between my issue, to the latest Plesk version upgrade, however did not identify my root cause.
 
Last edited:
Sorry I meant error.log as opposed to error_log.

This is definitely nginx. I have no further outages but the error remains and still no further forward regarding root cause.
 
Back
Top