For the longest time, I’ve had a random image sitting in the right sidebar. It happily picks random images from my local gallery. Last night, I figured it was about time to play catch up on the Gallery2 install we had been using. After all, we were on 2.2.3, and they were up to 2.3.something. All was working well, gallery loaded, images were all showing, everybody was happy. Until I checked the front page of my blog.
For a while, I’d been using an offline reader, then Google did some upgrades, so I swapped. I’ve been using Google Reader since late 2006, diligently serving my news to me, in its simple, and easy to use interface.
Recently I decided to tinker with a new offline reader, RSSOwl. Simple interface, easy to use, customizable searches, article flagging, and sharing features. Well worth a peek…
After today’s little hiccup, I noticed the random image in the top right of my page throwing an error message, something about ERROR_STORAGE_FAILURE. A little digging about, I stumbled across an error in the daemon.log file…
Fortunately, most of the times, this is relatively easy to resolve.
As you can see from the Msg_text column, the command completed OK. A quick refresh of the blog page, and the error is now gone, and the random picture is back…
Running on from today’s outage, I’ve put a few more safety measures in place. I’ve always had old faithful Nagios watching over my servers, however sometimes a little more is needed. Introducing Monit into the picture…
I’ve been meaning to get some proper stats setup for my mail server, but until then, I’ve been mostly content with reading the LogWatch reports from my server. It has been dutifully analyzing my log files, and giving me all kinds of useful data, such as the mail stats from Saturday, 18th July…
One of my more popular posts, oddly, is about CapitalOne and Fraud, which is going on nearly 2 years old now. There are a number of comments on the thread, but I noticed something that just started bugging me. When replying, I had no way of creating a nicely formatted reply (threading).
So I went in search of plugins, and discovered that WordPress 2.7.1 actually supports it natively, you just have to update your themes. I found a great reference here which detailed how to do it, but it seemed to not work, so I went in search of more details. I found that the old comment handling used to be performed using an array, and you’d have to setup the formatting yourself. They now provide a nifty function wplistcomments that outputs the entire array of comments for you, including all the settings for the reply information.
You can see the new modifications at work here on this post, see the second comment down is indented to reflect a comment to Bill.
I’ve been on the SquirrelMail project for quite some time now, and an administrator on the project for several years. One of the things that has always been an issue has donations. As there are multiple people that contribute to the project at varying levels at different times, we’ve never figured out a good way to handle donations. Other projects, such as MySQL, setup a foundation, and generate enough donations that they’re capable of supporting full time working developers. Whilst it’d definitely be cool to do that, we’re not there project wise. So recently Paul sent out a rather interesting option, and it hit the lists.
He gave the users the ability to donate to individual people on the project, as well as sign up for bounties. The copy of the announcement can be found here. The other option was bounties. This has been used on several open source projects before, and the idea is that people “sponsor” a project, bug, or target. There are already several listed, but we’re always looking for more ideas. So if you have some, submit an idea.
One of the LinkedIn groups, Nagios related, I am on recently had a discussion about monitoring WHOIS servers, and checking for a certain response. This is just a small exercise in some simple bash scripting, reading input, output, and passing exit results.
Read more…I’ve recently moved my primary domain over to a dynamic zone. I did this to allow for me to do some tweaking remotely, and auto-updating (using keys) for certain DNS records so I can connect to my network at home if I want to access resources here. This led to an interesting issue with updating the zone files…
