[EP-tech] Sysadmin Best Practices
drn at ecs.soton.ac.uk
Mon Apr 1 17:53:27 BST 2019
Here are some things I do:
* I use Ansible to manage OS (YUM) package upgrades to systems on a
fortnightly cycle. (I have a number of systems to update and don't want
more regular or internally automated updates, where if there was
problematic upgrade, I would either have a lot of broken systems all at
once or systems randomly breaking at unexpected times).
* I make sure I reboot systems after any kernel upgrade to ensure a
vulnerable kernel is not left in place indefinitely.
* I monitor (using Icinga) packages available for upgrade, so I can
make sure security updates are applied more urgently.
* I have written a systemd service file to ensure the indexer starts
after a reboot.
* I have a root @reboot cron job for making sure OpenOffice starts for
coversheeting after a reboot. I tried to write a systemd service file
for this but is was unreliable.
* I have an @reboot tidy_pids cron job to ensure there are no stale pid
(or tick) files in /opt/eprints3/var/ after a reboot that may stop the
indexer or OpenOffice from restarting automatically.
* I have a script that regenerates the sitemap on a daily basis. the
default sitemap seems to not be compatible when I tried to register
this on Google Webmaster portal, so I wrote a modified version that
just lists all the abstract pages and sets the changefreq to weekly.
* I have lots of monitoring of the server itself. This is the standard
stuff like ping, load, disk space, number of processes, packages to
upgrade, reboot required, etc. as well as some more EPrints specific
stuff like the size like response on http, checking MySQL tables are
not corrupted, checking if there are config files not committed to
version control, any mail generated for the eprints user (e.g. by cron
jobs), is the indexer/OpenOffice running, what is the size of the
I am sure there are other things I do that do not spring to mind on
On Mon, 2019-04-01 at 16:46 +0100, Adam Field via Eprints-tech wrote:
> Can anyone share what they do on the systems side
> (e.g. cron jobs, regular restarts, monitoring) that they have set up
> on EPrints? I’m interested in finding out what the best-practice is
> for making an EPrints installation as reliable as possible.
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-
> *** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=01%7C01%7C%7C44575e2fd03549812ceb08d6b6c28fc9%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=U0CESml1hVYn0oZcAkGhd2esj1wxXBBNHuMAKoDKalA%3D&reserved=0
> *** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&data=01%7C01%7C%7C44575e2fd03549812ceb08d6b6c28fc9%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=ByfmaZyHAN5WnqOlY5fwYDB8CeZBXc%2FoZzI7Q%2FOV%2BZw%3D&reserved=0
> *** EPrints developers Forum: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fforum.eprints.org%2F&data=01%7C01%7C%7C44575e2fd03549812ceb08d6b6c28fc9%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=WS1RQo9yyBzZS3UOe%2FCMwafNQuFSytryCSDwXFGDqLU%3D&reserved=0
More information about the Eprints-tech