Admin

I once installed Checkmk into an existing Nagios installation, back then by using a plain source package. This also meant I had to take care of installing and configuring all dependencies like Apache, Nagios and PNP4Nagios. Keeping this setup working was quite tedious over the last two upgrades (1.2.4 to 1.2.6 and finally 1.2.6p16) so I decided to switch to the official Checkmk CRE packages instead. For now I switched to the rather outdated 1.2.6p16 packages to concentrate on migrating my configuration first.

After upgrading to Seafile 5 I observed that my client was not syncing libraries anymore.

It turns out that this happens for libraries that were created long ago (before Seafile 3). According to Seafile issue #975 syncing of Seafile libraries may fail over HTTP(S) if they are stored in an older format on the server.

This is just a small update of an earlier post about Seafile on Nginx with uWSGI.

The upgrade to Seafile 5.x needed a few changes to the uWSGI configuration because the Seafile directory layout hanged a bit in Seafile 5.0.0.

After a self-inflicted downtime of my server that also happens to handle my email I decided that it’s time to have monitoring notifications delivered out-of-band instead of foolishly trying to send them via the most important resource I monitor. Since I recently started using Telegram I decided to give it a try for monitoring notifications. Please note that normal Telegram message contents are unencrypted so they can possibly be read on the Telegram server side!

I’ve been using Seafile as my personal cloud storage for quite some time now and it’s working really really well. Since I’ve departed quite a bit from the standard setup instructions for the web frontend (Seahub) I’m going to document the setup a tiny little bit.

This is a sort of follow-up post to Running Trac on Nginx with Phusion Passenger.

As my hosting needs have slightly changed lately I now have no immediate need for running Ruby, Rails or Rack applications. I’m lately using more and more web applications but they are based on different technologies.

So far I’ve been using Nullmailer only to relay mail from LAN machines to SMTP servers that accept anything from the internal network, a very easy method to forward system messages from various internal boxes without the need to administrate a full-blown MTA.

I’m currently investigating ways to replace Apache httpd with nginx on srcbox.net.

After about two years of complete TV absence both due to technical reasons (TV socket in wrong room on the other side of my flat) as well as the quality of the programme (ads, fake reality shows, lack of real movies), I nevertheless decided to get myself a network-enabled TV-tuner. Being network-enabled was both an easy way to get around the need for new cabling as well as making TV available to all the machines scattered throughout the flat.