admin-how-to: Difference between revisions
(→server transition testing: editing your local hosts file) |
(update ps command to see root/apache proc ownership, use of killall command) |
||
Line 21: | Line 21: | ||
** <code>(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80</code> | ** <code>(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80</code> | ||
* then see if there are any existing stalled restart processes by doing: | * then see if there are any existing stalled restart processes by doing: | ||
** <code>ps - | ** <code>ps -eaf | grep http</code> | ||
* if you see any processes like: | * if you see any processes like: | ||
** <code> 1337 ? S 0:44 httpd -k restart</code> | ** <code> 1337 ? S 0:44 httpd -k restart</code> | ||
Line 27: | Line 27: | ||
* then kill them using their id (that first number) like: | * then kill them using their id (that first number) like: | ||
** <code>sudo kill -9 1337</code> | ** <code>sudo kill -9 1337</code> | ||
* if there are too many to do individually, you can also use: | |||
** <code>sudo killall httpd</code> | |||
* re-run the ps command: | * re-run the ps command: | ||
** <code>ps - | ** <code>ps -eaf | grep http</code> | ||
* it should be the only thing running with "http" in the name, e.g. | * it should be the only thing running with "http" in the name, e.g. | ||
** <code>25252 pts/0 S+ 0:00 grep http</code> | ** <code>25252 pts/0 S+ 0:00 grep http</code> |
Revision as of 00:58, 9 August 2011
<entry-title>admin how-to</entry-title>
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:
- "if any of the microformats.org website admins are on, the site is down."
Then:
- ssh into the server
- check for web server errors (sometimes this can reveal the source of a problem)
tail /var/log/httpd/error_log
- find the apache install (it might not be where you expect it or it might have moved)
locate apache
- then using the full path to "apachectl" (rather than just "apachectl" in the command)
sudo apachectl -k restart
- if you get an error like:
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
- then see if there are any existing stalled restart processes by doing:
ps -eaf | grep http
- if you see any processes like:
1337 ? S 0:44 httpd -k restart
31337 ? S 0:44 httpd -k restart
- then kill them using their id (that first number) like:
sudo kill -9 1337
- if there are too many to do individually, you can also use:
sudo killall httpd
- re-run the ps command:
ps -eaf | grep http
- it should be the only thing running with "http" in the name, e.g.
25252 pts/0 S+ 0:00 grep http
- at this point, try restarting the apache server again:
sudo apachectl -k restart
- and you should see:
httpd not running, trying to start
- now try browsing to http://microformats.org/ and make sure it loads
- report back on IRC or Twitter to whoever pointed out that the server was down.
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:
http://www.howtogeek.com/howto/27350/beginner-geek-how-to-edit-your-hosts-file/
- Add the line: to the hosts file on your local machine.
64.207.154.205 www.microformats.org microformats.org
- Do the flush cache tip as described below.
- Restart your browser
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
- home page: http://microformats.org/
- blog permalink: ...
- logging into WordPress: ...
wiki
- wiki home: http://microformats.org/wiki/
- logging in: http://microformats.org/wiki/Special:UserLogin
- logged in wiki home (should just take you there automatically)
- ...
irc bots
- does editing a wiki page result in the bot noticing and outputting the diff to irc://irc.freenode.net/microformats ?
profiles
media
- audio / video recordings of talks
- ... need URLs ...
mailing list archives
- ...
shorteners
- http://microformats.org/w/hcard should go to http://microformats.org/wiki/hcard
- http://microformats.org/x/hcard#fn should go to http://microformats.org/profile/hcard#fn
other
- ...