On my server running Ubuntu 12.04, I have Apache2 listening on port 8008 (20 virtual hosts) and Varnish on port 80. I use munin and monit to keep tabs on the various services running on the machine and they use the mod_status output to keep tabs on Apache2 processes. As mod_status is compiled into Apache2 by default and the module is enabled this means that the detailed information about your secure webserver is exposed for all the world to see. The mod_status configuation file allows you to lock access down to localhost access only which is nice.
However, Varnish connects to the backend Apache2 server as localhost and so exposes the server-status page to the wild wild web. With the Varnish VCL I was using my server-status page was cached for an hour so it was still available but only provided a static status report that changed when the cache refreshed. Implementing a solution from serverfault.com made the live server-status available through Varnish as it passed it to the backend. This did not help. To secure my server-status I had to block access to the server-status URL but still keep it open for munin-node. Continue reading Varnish cache, munin-node and server-status
For Christmas Kevin gave me a WH1081 wireless USB weather station. It has a wind vane and anemometer, minimum and maximum thermometer, barometer, rain gauge and hygrometer mounted externally. It communicates wirelessly with a base station inside the house. The base station is connected to the server in the loft and there is much chatter between the two. The server runs pywws (Python Wireless Weather Station) software developed by Jim Easterbrook. This processes the data from the weather station at regular intervals and submits the information to a number of different sites. You can check the weather for IPERTHSH12 on Weather Underground (wunderground.com) and on the Met Office WOW site (wow.metoffice.gov.uk). You can also follow the current weather and 12 hourly forecasts on twitter (@newtyleweather). I also wrote up my own pages to display the weather information (cribbing from various other sites on the web) and give further details here: http://wx.mixedbredie.net/Continue reading New Weather Station
Printer plugged into Server in the loft via USB. Desktop and Server connected by wired ethernet through Netgear router. Macbook connects through wireless.
Server runs CUPS 1.4.3, Macbook runs CUPS 1.4.7 and Desktop has CUPS 1.5.0.
Server is set up to share the Printer over IPP on port 631. Some machines can connect to http://server:631/ (i.e. the remote print server) and print a test page. The Macbook just connects but cannot print. All machines can connect to http://localhost:631/ (i.e. their own CUPS print server) and can see the remote Printer on the Server. Continue reading In My CUPS*
I have been running Linux Mint 10 for ages and have hacked and patched and updated it with various repositories to make sure it was reasonably up-to-date. The application I use most often on the desktop is DigiKam. The development of DigiKam has accelerated recently to the point of a new release almost monthly. The repositories are all trying to play catch-up. Some dedicated individuals are rolling their own .debs/.rpms for different flavours of linux. All you have to do is connect to their repository and install. But it is never that simple as the newer versions of DigiKam required newer versions of all the dependencies and a simple install ends up pulling in loads of different packages. In the end I gave up and stuck with version 1.9 as newer versions required an updated version of KDE and it was getting to be a hassle patching everything together. Continue reading Farewell Kubuntu Mint, Hello Fedora 16
The Ubuntu Community Documentation recommends the following steps when upgrading the Long Term Support (LTS) version of its server operating system. My server has been running 8.04 since April 2008 and has been a good and faithful server. However, the time has come to upgrade it to new versions of the server software. It is also an opportunity to completely clean out the accumulated cruft that happens when your development, test and live servers are one and the same.