Facebook
Twitter-
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.
Apache dies every night since upgrading to Debian 8
- Thread starter H9k
- Start date
Hello,
I remember same problems with server graceful reload in short time, i.e */etc/init.d/apache2 reload && /etc/init.d/apache2 reload && /etc/init.d/apache2 reload* leads to segmentation fault.
You can try to replace reload to restart in /etc/logrotate.d/apache2 to make sure that this problem caused by logrotation
I remember same problems with server graceful reload in short time, i.e */etc/init.d/apache2 reload && /etc/init.d/apache2 reload && /etc/init.d/apache2 reload* leads to segmentation fault.
You can try to replace reload to restart in /etc/logrotate.d/apache2 to make sure that this problem caused by logrotation
Yeah I did that and it at least is a workaround, apache does not crash anymore on logrotate.
I have a feeling that Apache 2.4 is less reliable than 2.2, maybe that has something to do with the fact that it runs in a OpenVZ container which still has the 2.6 kernel. I will upgrade to kernel 4.2 and LXC container sometime over the next weeks/months, until then I hope I won't get any other major problems...
I have a feeling that Apache 2.4 is less reliable than 2.2, maybe that has something to do with the fact that it runs in a OpenVZ container which still has the 2.6 kernel. I will upgrade to kernel 4.2 and LXC container sometime over the next weeks/months, until then I hope I won't get any other major problems...
