Re: [tsc-devel] On the server issues
Quintus |
Wed, 21 Jan 2015 21:03:08 UTC
Chris Jacobsen <…9@y…> writes:
> Making a program to monitor the sever and restart it if it goes down
> makes sense. This probably is the first thing we should do now.
I’ve resorted to the most easy and most hacky solution I had at hand
while I have no time to properly set things up. I have added an entry to
/etc/crontab that automatically restarts Apache httpd every hour. Thanks
to cron we should be able to defer the setup until I have more time.
> Long term we probably do need to resolve the root cause of the issues
> -- if the CPU goes to 100%, it might cause some intermittent issues
> for users even if a server restart is initiated. Whether a new
> version of Debian is better or whether we should do more work to just
> get the wiki software is up to date -- I'll probably have to leave
> that to you guys.
Debian Jessie has not yet been released, and I don’t think running an
unstable version of an operating system on a server is a good
idea. Also, the server is running on OpenVZ and not on KVM, so
installing another operating system will cause some trouble (with
OpenVZ, the virtualised system is forced to share the kernel with the
host system, while KVM allows you to use your own kernel). Running after
the new versions of a software manually rather than just doing $ apt-get
upgrade is a mess. It WILL be forgotten, I tell you.
I don’t think having 100% CPU usage on the server for a few seconds is
something we should fix by upgrading to an unstable OS or by manually
updating something without the package manager. Once monitoring is set
up, Apache httpd will only run for some few seconds on 100% CPU before
it is automatically restarted.
> -datahead
Valete,
Quintus
--
Blog: http://www.quintilianus.eu
I will reject HTML emails. | Ich akzeptiere keine HTML-Nachrichten.
|
Use GnuPG for mail encryption: | GnuPG für Mail-Verschlüsselung:
http://www.gnupg.org | http://gnupg.org/index.de.html