User login
Navigation
Recent blog posts
- Ubuntu mirrors up and improved!
- Google-jstemplate: Iterate object with unknown properties
- nginx https proxypass for php apps
- sugarcrm & memcache: Doing it Wrong
- subversion and https in Ubuntu Karmic
- Drupal: Views block delta converted to md5 hash
- Ubuntu Server install requires PAE
- Installing Drupal from command line
- Drupal: Handling form field weight through CCK
- minify javascript using Google Closure Compiler
angch's location
angch twitter
sysadmin
Among other mundane checks:
Check Zone-H.org to see if your site have been defaced.
Check Sender Base to see if your server have been blacklisted for whatever reason you missed.
I've to stress that the above is the additional checks you should do. Because you should be able to detect patterns of abuse even before you get listed in any of the above.

Monitoring
angch — Tue, 12/08/2008 - 23:17
Don't have anything that fancy like last.fm:
http://blog.last.fm/2008/08/01/quality-control
but we use zabbix a lot for our monitoring. It's not as efficient (mysql over rrdtool) as cacti or nagios, but definitely more flexible if you have a mix of different operating systems and ad hoc stats on very different things.

Patch your nameservers!
angch — Thu, 24/07/2008 - 23:18
This bears repeating:
Just patched a number of our nameservers. ( http://www.doxpara.com/ ). Be careful that it's not your content nameservers that matters here, but your own resolver and upstream's nameservers that matters. Check with the tool in www.doxpara.com. Ingenius way to check for vulnerablity, btw.
If you don't trust your upstream's dns, run your own patched nameserver, but don't forward queries upstream, but straight to the root servers.
