planetubuntu

Zabbix has a log of built-in support to monitor diskspace on servers.  But I'm not always interested in triggers that fire on a certain amount or percentage of free space defined in  a template.  For some filesystems, it may be perfectly normal to be at 90% usage and remain stable there.

What does interest me more is the amount by which disk usage increases in a short timespan, and Zabbix does have the functionality to cater for this.  For example:

The Zabbix server at my customer failed badly today with a flood of 'unreachable' alerts across multiple locations.  It became clear pretty quickly that the hosts where up and Zabbix was at fault.

With the proxies reported up, I turned to the Zabbix server itself and saw MySQL errors rolling by in the log:

 Just a small heads up for those using OwnCloud and upgraded to precise, version 1.0.1 of their client is broken (exits with csync.vio.main - loading ownclouds plugin failed - /usr/src/packages/BUILD/obj-x86_64-linux-gnu/modules/csync_ownclouds.so: cannot open shared object file: No such file or directory) on 12.04.

OwnCloud will release 1.0.2 soon that fixes this.

I set up owncloud yesterday, and it seems to be very nice.

But when I wanted to open it outside my network over SSL, it got stuck in a redirect loop.

Now, I use pound as a reverse proxy to balance requests over several servers and to do SSL termination.  This proved to be the problem, owncloud did not detect that the connection was SSL enabled despite the "X-Forwarded-Proto: https" header added by pound (which fixed similar problems in other webapps).

But luckily, just adding "SetEnv HTTPS on" in the Apache vhost fixed that!

I recently installed a DNS sever using Ubuntu 12.04.  The server should serve only my exernal domain, but should use an internal server for it's own name resolution.

Setting dns-nameservers to the correct ip in /etc/network/interfaces did not work on this host (but does on all my non-dns hosts).

After some digging, I found the cause: resolvconf always reverts to nameserver 127.0.0.1 which in turn queries the hosts in dns-nameservers.  Because my host is already a nameserver, 127.0.0.1 points to my bind instance instead of a caching daemon.

 Last week, I released a new version of eLAS, a PHP based web application.  This version included a combination of changes in 2 branches., trunk and an experimental branch that introduced the Mootools javascript framework.  Both branches received significant testing and worked and behaved well.

The merge with the Mootools branch happened very late in the 2.2 cycle because version 3 (which would have gotten this) will not happen for at least another year.

My latest article titled 'Ubuntu and Gnome 3, from unity to divergence' will be published in the upcoming editon off Linux Identity.

If I find the time. I'm going to put an updated list of my articles up on this site (with links when allowed).

After upgrading to Precise, I noticed that Skype was uninstalled.  But it was easily fixed by downloading the deb from Skype's site.

But now, at each update via-update manager, it says the skype package should have been removed and I need to remove it before proceeding?

Is this a bug?  Any workaround?

I'm looking for an integrated distribution/VM appliance to do virus and SPAM filtering, much in the way that spamtitan does it.  Having a GUI for users would be a huge plus.

So far, I only found proprietary solutions, so if anyone knows a community project that does the same, please recommend it to me!

Thanks

PS.  Yes, I know mailscanner and amavis, been running them for years :-)

 The number of (Ubuntu) servers I have is growing steadily, and with it approaching 10 (including VM's), I'm starting to look for a solution to manage security upgrades beyond the apt-get update && apt-get upgrade mantra.

What are other people using for this?  I know RH Satellite/Spacewalk is nice but it's only for RHEL-derivates.

Already looked at unattended upgrades, but I'd like something with a little more options and centrally managed (I have redundant web frontends so they should be upgraded sequentially).