• 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.

Okay, what just happened?

michaellunsford

Regular Pleskian
I have occasional trouble with my server where it just stops working. I ssh into it (it can take 10 minutes to login), and "reboot".

So, how do I find out what it's doing, or what it was doing before it ground to a hault?
 
Check those log files:
/var/log/boot.log
/var/log/boot.log.*

And also this one:
/var/log/messages

Then try to figure out at what time your server stopped working, then check the logs for strange entries.

Hope this helps, note that the path to the logs are "as seen" on a Fedora Core 2 install.
 
Funny, I got about 25 domains, but 512mb of ram and it's working fine...
Check for a new plan.
 
Back
Top