admin how-to

Revision as of 19:08, 6 February 2012 by Rohit (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)

Jump to: navigation, search

This is a reference for various tasks that admins may have to perform.


web server restart

If you're reading this then either the server is up, or the server is down and you're reading a Google Cache copy (thus it's still useful to post this here).

If the web server is down, e.g. someone notes on IRC or Twitter:


semaphore exhaustion

This is a much rarer error state: Apache error log stating: [emerg] (28)No space left on device: Couldn't create accept lock (/etc/httpd/run/accept.lock.NNNN) (5). Thanks to for the hint.

… and then proceed to restart as before.

server transition testing

Some things to check when transitioning to / setting up a new server.

editing your local hosts file

In order to test a new server from your local machine and still have hardcoded URL references work, you may need to manually edit your local machine's hosts file, per:

Your browser should now behave *exactly* as if you'd switched actual DNS.

This makes it a very good way to test.

DNS flush cache tips

If you're using OSX, you'll probably have to run this to flush the local dns cache:

dscacheutil -flushcache

current servers being tested

home and blog


irc bots



mailing list archives



attack logs

Note any logs / summaries of attacks. Anything more than a summary should be moved to its own page.

see also

admin how-to was last modified: Wednesday, December 31st, 1969