I updated my postgresql database, as it was version 8 and version 9 has been out for quite a while. That actually went painlessly. Backup the SQL, terminate the db server, build/install the new one, and restore the SQL. Then tewak configuration files to get everything back the way it was before. No problem.

Then realized I needed to rebuild a pg gem on the deployed host so that it’d talk to postgresql 9 now. Did that. Suddenly the app server no longer responds. it just sits there forever waiting on … something. No amount of debugging output from Passenger will help. It must be something else. So now I’m updating ruby and rebuilding a new Passsenger against it in the hopes that it’s a bug in ruby that I’ve encountered that evidences itself with postgresql 9 or something. Otherwise, I might be spending the day getting the newer revision of my application ready to go a bit earlier than I had planned.

Had I had an automated deployment script built in, I could’ve just clobbered the environment and redeployed within the new fresh environment. Instead I’m having to monkey around getting everything to behave well, and generally failing at it.

I kept having a horrible error building collectd 4.10.x on my Source Mage servers:

libiptc.c:85: error: redefinition of ‘struct xt_error_target’

The internets couldn’t really help me with the error, I think I was searching for the wrong words. There was also issues regarding warnings that gcc now treats as errors.

I ended up spending probably about an hour cloning their git repo, cherry-picking a few commits into the 4.10.3 tag, and then submitting the patches to the bug I created.

End result is that collectd-4.10.3 now builds on gcc 4.4.3 and 4.6.1. The fix is in the Grimoire on Source Mage, and should trickle out to stable eventually. I think I’m the only one who uses collectd, so it’s not all that important, heh.

Well, I was using an internal lighttpd to render the same thing internally, and I didn’t disable its directory listing at all. Whilst I was working on setting up collectd to monitor my Apache scoreboards, I noticed that it could also monitor the lighttpd scoreboard. So I was going about the config to set that up, and I noticed that the Apache wasn’t proxying it’s requests through to lighttpd, and was taking a lot of time and resources to do something simple.

Welp, having ADD like I do, I got sidetracked on doing that instead and started to rewrite my configs to not serve files directly, but proxy it to the lighttpd internally.

Originally, I had two aliases set up “/sourcemage” and “/sourcemage/fallback” which both pointed to the same spot on disk, This way you could reference things using “/sourcemage/file.tar.bz2″ or “/sourcemage/fallback/file.tar.bz2″. The reasoning behind this is simple: I set up my fallback mirror before Source Mage standardized on a fallback URL, and I wanted to keep both paths functional. Easy to do with aliases. Oh, and I also have an alias to “/sourcemage/codex” for all my local codex needs.

Switching to a proxied setup was a bit more complicated than I anticipated. The alias stuff doesn’t work the same way everything else does, in that what it finds first it goes with. I needed to have mod_rewrite rules wired in to properly redirect things and manipulate the URL sufficiently. But I have two special cases. I can’t simply redirect everything “/sourcemage/*” to “/sourcemage/fallback.” Also, I wanted to be able to continue to use “/sourcemage/file.tar.bz2″

My solution is relatively simple and follows:

#aliases
Alias /sourcemage/codex    "/srv/webMirrors/sourcemage.org/codex"
#rewrite /sourcemage/ to /sourcemage/fallback
#some very fancy rewrite rules to keep the old alias functionality
RewriteEngine On
RewriteRule ^/sourcemage/?$ /sourcemage/fallback/ [R]
RewriteRule ^/sourcemage/codex/?$ - [L]
RewriteRule ^/sourcemage/([a-zA-Z0-9.i_\-+]+)$ /sourcemage/fallback/$1 [R]
# do the actual passing through to the lighttpd (which handles huge
# directory listing much much better
ProxyPass /sourcemage/fallback http://fallback.shlrm.org/
ProxyPassReverse /sourcemage/fallback http://fallback.shlrm.org/

# old notes kept here for reference as to what the above rewrite
# rules are doing -- dkowis 2011-09-07
# going to proxy these to the lighttpd
#Alias /sourcemage/fallback "/var/spool/sorcery/"
#Alias /sourcemage          "/var/spool/sorcery/"
# directories!
#<Directory "/var/spool/sorcery/" >
#       Options none
#    AllowOverride None
#    Order allow,deny
#    Allow from all
#</Directory>

<Directory "/srv/webMirrors/sourcemage.org/codex/" >
        Options Indexes
        Order allow,deny
        Allow from all
</directory>

# vi: set ft=apache:

The rewriting rules are the most complicated part of this. The trick was getting it not to try to rewrite anything when the url matched “/sourcemage/codex” After that, the rest was really easy. Some matching logic to pick up on “/sourcemage/file.tar.bz2″ and redirect that to “/sourcemage/fallback/$1″ and everything worked as it did before, except way faster.

I’ve been working on building MaraDNS 2.0 RPMs for Fedora 13 and 14, but I don’t know the RPM SPEC structure very well. The 2.0 version of MaraDNS has separated the authoritative resolver from the recursive resolver, which is wise. But it means I need to build a spec file that produces two RPMs. I suppose I could build a separate spec file for each one, but that doesn’t seem like the right way to do things.

I updated it along with updating wordpress to 3.0.3 the other day. I fired off the Broken Links Checker, and as it usually takes a while, I ignored it and went on playing Eve and writing some ruby code (a simple little project to organize a whole lot of files into 4.7GB disks and include manifests and md5s of all the files for an archive. Still doesn’t work yet.) The next morning, I woke up to a large amount of email. I figured it was just spam or something that was significantly different than the normal spam. Unfortunately it was notifications from my Nagios telling me that the box doesn’t respond to ssh or http anymore. Uh oh.

Luckily, I’m running Xen, so it is trivial to get to the console over ssh. I connect to the console and try to log in. The box is totally wedged. OOM Killer had gone crazy with httpd, and anything else that was on that box. So xm destroy. Fire it back up again, wait for it to replay all the transactions, and it had decided to check the disks, since they haven’t been checked in 214 days. All came back up fine. Nagios was again satisfied. However, none of the sites worked. “Error: Cannot access database.” Oh noes. Started the normal debugging process, looking through logs and what not. Found a bunch of local requests from Broken Links Checker checking links. It appears that it caused a DOS to myself. Wonderful. Still no luck with MySQL, so I tried to connect to the mysql server via the command line, I had already determined that it was up, and it’s on a different box, so it didn’t get oom killed when apache killed the box. I get an error telling me that MySQL was denying connections from this host due to too many errors. So a flush-hosts later, and it all works again. Fun.

Guess I should set up some kind of resource limits for Apache on that box. Also, I’m removing that Broken Links Checker plugin, I don’t need to find my broken links that badly…

This blog post talks about how to do it, but it didn’t cooperate with Fedora 14 very well. A bit of googleing later and I found this mailing list post that did it for me. Now I have userspace cgroups for each terminal I open. Handy, I suppose. Might be more useful on an SSH server to guarantee that each person logging in can’t overwhelm the system for the others.

It was quite tricky to figure out, especially right after 14 came out, as I didn’t have an ethernet connection, and when I was able to get the connection up, and I asked on the IRC channel, no one had any insight. I let 14 stew a while, and the rest of the internet came up with similar problems. Turns out that the kernel driver included in 2.6.35 has issues. There’s some patches in the works, but I don’t know if they’ll get pulled down into 2.6.35. The fix is in 2.6.36.

Until then, you can get the latest driver directly from the e1000e’s SourceForge website here. Make, then make install it as root and you’ll be good to go. This driver version worked for me on a Intel Corporation 82566DC Gigabit Network Connection (rev 02).

It appears that someone['s botnet] was trying to hack my little server yesterday. I have a good portion of attempted logins as root from a slew of hosts. 194 separate hosts with multiple attempts from more than a few. This might explain the horrible internet connectivity problems I was having the other day.

Not really sure what I did to piss off some script kiddie. Perhaps I got someone’s attention? I haven’t blagged about anything controversial recently. Not even in politics. I did submit my resume to Monster.com, perhaps someone is determining if they can hire me as a Systems Administrator?

Logwatch entries follow after the break.

These are the relevant entries from the logwatch email I received today. I’ve sanitized them just a smidge.

Pam_unix’s logwatch section

sshd’s logwatch section

--------------------- pam_unix Begin ------------------------

 dovecot:
    Authentication Failures:
       <valid user>: 139 Time(s)
    Unknown Entries:
       session closed for user <valid user>: 139 Time(s)
       session opened for user <valid user> by (uid=0): 139 Time(s)

 sshd:
    Authentication Failures:
       root (189.22.10.3): 6 Time(s)
       root (189.8.88.10): 4 Time(s)
       root (222.173.107.103): 4 Time(s)
       root (112.215.7.123): 3 Time(s)
       root (122.116.133.14): 3 Time(s)
       root (190.68.61.66): 3 Time(s)
       root (212.116.138.149): 3 Time(s)
       root (220.232.206.71): 3 Time(s)
       root (91.142.242.165): 3 Time(s)
       <valid user> (<internal network address>): 2 Time(s)
       root (119.62.128.110): 2 Time(s)
       root (12.234.198.58): 2 Time(s)
       root (122.117.211.109): 2 Time(s)
       root (130.231.15.12): 2 Time(s)
       root (133.42.149.193): 2 Time(s)
       root (189.2.187.4): 2 Time(s)
       root (189.20.205.210): 2 Time(s)
       root (189.210.153.50): 2 Time(s)
       root (190.1.171.108): 2 Time(s)
       root (190.248.8.19): 2 Time(s)
       root (190.253.223.162): 2 Time(s)
       root (190.29.2.204): 2 Time(s)
       root (190.68.117.18): 2 Time(s)
       root (190.68.117.82): 2 Time(s)
       root (194.2.25.13): 2 Time(s)
       root (195.78.46.99): 2 Time(s)
       root (195.81.144.28): 2 Time(s)
       root (200.105.228.202): 2 Time(s)
       root (200.111.111.51): 2 Time(s)
       root (200.187.60.60): 2 Time(s)
       root (200.242.100.30): 2 Time(s)
       root (200.248.10.200): 2 Time(s)
       root (201.238.197.3): 2 Time(s)
       root (202.53.225.162): 2 Time(s)
       root (212.224.142.100): 2 Time(s)
       root (212.92.23.139): 2 Time(s)
       root (213.129.249.99): 2 Time(s)
       root (213.23.211.11): 2 Time(s)
       root (218.241.156.219): 2 Time(s)
       root (219.117.236.219): 2 Time(s)
       root (222.107.61.161): 2 Time(s)
       root (41.204.194.154): 2 Time(s)
       root (58.246.85.122): 2 Time(s)
       root (59.106.27.49): 2 Time(s)
       root (62.97.49.6): 2 Time(s)
       root (64.182.136.46): 2 Time(s)
       root (70.247.71.201): 2 Time(s)
       root (74.55.60.90): 2 Time(s)
       root (75.125.235.162): 2 Time(s)
       root (81.221.15.140): 2 Time(s)
       root (82.119.240.3): 2 Time(s)
       root (85.22.60.6): 2 Time(s)
       root (85.24.138.173): 2 Time(s)
       root (87.86.55.4): 2 Time(s)
       root (89.250.247.28): 2 Time(s)
       root (91.144.170.50): 2 Time(s)
       root (93.104.243.162): 2 Time(s)
       root (93.152.158.141): 2 Time(s)
       root (93.157.210.254): 2 Time(s)
       root (93.93.191.186): 2 Time(s)
       root (115.186.131.106): 1 Time(s)
       root (122.115.35.242): 1 Time(s)
       root (122.221.65.18): 1 Time(s)
       root (123.231.21.19): 1 Time(s)
       root (124.92.251.2): 1 Time(s)
       root (125.255.49.179): 1 Time(s)
       root (140.115.155.221): 1 Time(s)
       root (146.134.30.157): 1 Time(s)
       root (146.83.216.201): 1 Time(s)
       root (147.83.52.103): 1 Time(s)
       root (161.132.77.16): 1 Time(s)
       root (163.19.1.92): 1 Time(s)
       root (163.247.46.150): 1 Time(s)
       root (174.143.234.81): 1 Time(s)
       root (180.168.5.184): 1 Time(s)
       root (189.112.139.83): 1 Time(s)
       root (189.114.56.253): 1 Time(s)
       root (189.47.135.118): 1 Time(s)
       root (189.47.206.203): 1 Time(s)
       root (190.128.29.4): 1 Time(s)
       root (190.144.1.98): 1 Time(s)
       root (190.144.103.146): 1 Time(s)
       root (190.152.145.54): 1 Time(s)
       root (190.165.136.11): 1 Time(s)
       root (190.182.3.143): 1 Time(s)
       root (190.2.3.85): 1 Time(s)
       root (190.254.197.10): 1 Time(s)
       root (190.255.182.106): 1 Time(s)
       root (194.94.121.238): 1 Time(s)
       root (195.162.22.59): 1 Time(s)
       root (195.24.37.122): 1 Time(s)
       root (196.0.5.114): 1 Time(s)
       root (196.10.224.108): 1 Time(s)
       root (196.12.232.100): 1 Time(s)
       root (196.20.71.66): 1 Time(s)
       root (196.201.230.18): 1 Time(s)
       root (196.43.83.170): 1 Time(s)
       root (200.101.12.86): 1 Time(s)
       root (200.123.4.25): 1 Time(s)
       root (200.160.121.246): 1 Time(s)
       root (200.175.79.150): 1 Time(s)
       root (200.182.126.166): 1 Time(s)
       root (200.25.180.75): 1 Time(s)
       root (200.79.53.211): 1 Time(s)
       root (201.155.88.252): 1 Time(s)
       root (201.21.49.185): 1 Time(s)
       root (201.227.239.11): 1 Time(s)
       root (201.238.211.133): 1 Time(s)
       root (201.41.215.154): 1 Time(s)
       root (202.120.46.2): 1 Time(s)
       root (202.147.244.165): 1 Time(s)
       root (202.171.148.106): 1 Time(s)
       root (202.177.24.199): 1 Time(s)
       root (202.39.49.109): 1 Time(s)
       root (202.53.250.42): 1 Time(s)
       root (202.71.140.165): 1 Time(s)
       root (203.110.245.243): 1 Time(s)
       root (203.122.225.226): 1 Time(s)
       root (203.183.81.155): 1 Time(s)
       root (203.58.188.17): 1 Time(s)
       root (203.72.59.6): 1 Time(s)
       root (204.38.191.170): 1 Time(s)
       root (208.115.111.200): 1 Time(s)
       root (208.179.176.66): 1 Time(s)
       root (209.203.18.122): 1 Time(s)
       root (209.88.156.132): 1 Time(s)
       root (210.196.168.137): 1 Time(s)
       root (210.51.57.139): 1 Time(s)
       root (211.234.100.205): 1 Time(s)
       root (211.239.172.188): 1 Time(s)
       root (211.9.48.203): 1 Time(s)
       root (212.155.135.204): 1 Time(s)
       root (212.92.23.24): 1 Time(s)
       root (213.215.10.116): 1 Time(s)
       root (213.215.247.194): 1 Time(s)
       root (213.235.133.209): 1 Time(s)
       root (213.97.211.74): 1 Time(s)
       root (217.119.231.143): 1 Time(s)
       root (217.15.197.136): 1 Time(s)
       root (217.159.148.62): 1 Time(s)
       root (217.166.213.218): 1 Time(s)
       root (217.220.124.90): 1 Time(s)
       root (217.8.80.9): 1 Time(s)
       root (219.234.81.209): 1 Time(s)
       root (219.94.144.73): 1 Time(s)
       root (24.75.21.4): 1 Time(s)
       root (38.112.30.222): 1 Time(s)
       root (58.215.75.55): 1 Time(s)
       root (58.221.249.66): 1 Time(s)
       root (59.124.223.238): 1 Time(s)
       root (59.124.78.179): 1 Time(s)
       root (61.31.200.49): 1 Time(s)
       root (62.129.164.36): 1 Time(s)
       root (62.94.161.156): 1 Time(s)
       root (64.117.46.243): 1 Time(s)
       root (64.164.215.91): 1 Time(s)
       root (64.185.113.237): 1 Time(s)
       root (65.111.177.12): 1 Time(s)
       root (65.111.177.212): 1 Time(s)
       root (65.70.247.20): 1 Time(s)
       root (66.115.174.80): 1 Time(s)
       root (66.240.254.216): 1 Time(s)
       root (67.222.236.19): 1 Time(s)
       root (69.159.244.44): 1 Time(s)
       root (72.51.43.242): 1 Time(s)
       root (72.54.128.19): 1 Time(s)
       root (72.90.111.10): 1 Time(s)
       root (74.189.117.98): 1 Time(s)
       root (74.80.48.25): 1 Time(s)
       root (75.125.69.82): 1 Time(s)
       root (75.160.204.13): 1 Time(s)
       root (79.170.186.119): 1 Time(s)
       root (79.38.79.53): 1 Time(s)
       root (80.26.69.233): 1 Time(s)
       root (81.168.103.177): 1 Time(s)
       root (81.18.250.224): 1 Time(s)
       root (81.255.107.145): 1 Time(s)
       root (82.145.241.5): 1 Time(s)
       root (82.187.183.124): 1 Time(s)
       root (83.238.170.128): 1 Time(s)
       root (84.19.182.97): 1 Time(s)
       root (84.40.53.32): 1 Time(s)
       root (85.145.196.239): 1 Time(s)
       root (85.214.25.226): 1 Time(s)
       root (87.244.204.196): 1 Time(s)
       root (87.63.208.238): 1 Time(s)
       root (88.40.179.242): 1 Time(s)
       root (89.251.106.242): 1 Time(s)
       root (89.39.28.239): 1 Time(s)
       root (93.82.242.114): 1 Time(s)
       root (94.127.136.74): 1 Time(s)
       root (94.83.231.154): 1 Time(s)

 ---------------------- pam_unix End -------------------------

Here’s the section from sshd itself. It’s a bit more noisier than just reporting authentication failures.

 --------------------- SSHD Begin ------------------------

 Users logging in through sshd:
    <valid user>:
       <internal network ip> (raziel.shlrm.org): 2 times

 Refused incoming connections:
       110.8.75.19: 1 Time(s)
       165.Red-217-127-98.staticIP.rima-tde.net: 1 Time(s)
       190.144.1.98: 1 Time(s)
       221.232.155.6: 1 Time(s)
       222.237.78.139: 2 Time(s)
       60.191.47.54: 1 Time(s)
       60.195.250.54: 1 Time(s)
       74.203.204.99: 2 Time(s)
       78.97.93.150: 1 Time(s)
       ms.onpcs.com: 2 Time(s)
       nc-65-40-234-248.sta.embarqhsd.net: 1 Time(s)
       p23171-ipbffx02osakakita.osaka.ocn.ne.jp: 2 Time(s)
       sphinx.wbsconnect.com: 1 Time(s)

 Error in PAM authentication:
    User not known to the underlying authentication module for root from 112.215.7.123 : 3 Time(s)
    User not known to the underlying authentication module for root from 115.186.131.106 : 1 Time(s)
    User not known to the underlying authentication module for root from 119.62.128.110 : 2 Time(s)
    User not known to the underlying authentication module for root from 12.234.198.58 : 2 Time(s)
    User not known to the underlying authentication module for root from 122.115.35.242 : 1 Time(s)
    User not known to the underlying authentication module for root from 122.116.133.14 : 3 Time(s)
    User not known to the underlying authentication module for root from 122.117.211.109 : 2 Time(s)
    User not known to the underlying authentication module for root from 122.221.65.18 : 1 Time(s)
    User not known to the underlying authentication module for root from 123.231.21.19 : 1 Time(s)
    User not known to the underlying authentication module for root from 124.92.251.2 : 1 Time(s)
    User not known to the underlying authentication module for root from 125.255.49.179 : 1 Time(s)
    User not known to the underlying authentication module for root from 130.231.15.12 : 2 Time(s)
    User not known to the underlying authentication module for root from 133.42.149.193 : 2 Time(s)
    User not known to the underlying authentication module for root from 140.115.155.221 : 1 Time(s)
    User not known to the underlying authentication module for root from 146.134.30.157 : 1 Time(s)
    User not known to the underlying authentication module for root from 146.83.216.201 : 1 Time(s)
    User not known to the underlying authentication module for root from 147.83.52.103 : 1 Time(s)
    User not known to the underlying authentication module for root from 161.132.77.16 : 1 Time(s)
    User not known to the underlying authentication module for root from 163.19.1.92 : 1 Time(s)
    User not known to the underlying authentication module for root from 163.247.46.150 : 1 Time(s)
    User not known to the underlying authentication module for root from 174.143.234.81 : 1 Time(s)
    User not known to the underlying authentication module for root from 180.168.5.184 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.112.139.83 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.114.56.253 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.2.187.4 : 2 Time(s)
    User not known to the underlying authentication module for root from 189.20.205.210 : 2 Time(s)
    User not known to the underlying authentication module for root from 189.210.153.50 : 2 Time(s)
    User not known to the underlying authentication module for root from 189.22.10.3 : 6 Time(s)
    User not known to the underlying authentication module for root from 189.47.135.118 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.47.206.203 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.8.88.10 : 4 Time(s)
    User not known to the underlying authentication module for root from 190.1.171.108 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.128.29.4 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.144.1.98 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.144.103.146 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.152.145.54 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.165.136.11 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.182.3.143 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.2.3.85 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.248.8.19 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.253.223.162 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.254.197.10 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.255.182.106 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.29.2.204 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.68.117.18 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.68.117.82 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.68.61.66 : 3 Time(s)
    User not known to the underlying authentication module for root from 194.2.25.13 : 2 Time(s)
    User not known to the underlying authentication module for root from 194.94.121.238 : 1 Time(s)
    User not known to the underlying authentication module for root from 195.162.22.59 : 1 Time(s)
    User not known to the underlying authentication module for root from 195.24.37.122 : 1 Time(s)
    User not known to the underlying authentication module for root from 195.78.46.99 : 2 Time(s)
    User not known to the underlying authentication module for root from 195.81.144.28 : 2 Time(s)
    User not known to the underlying authentication module for root from 196.0.5.114 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.10.224.108 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.12.232.100 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.20.71.66 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.201.230.18 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.43.83.170 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.101.12.86 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.105.228.202 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.111.111.51 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.123.4.25 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.160.121.246 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.175.79.150 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.182.126.166 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.187.60.60 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.242.100.30 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.248.10.200 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.25.180.75 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.79.53.211 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.155.88.252 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.21.49.185 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.227.239.11 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.238.197.3 : 2 Time(s)
    User not known to the underlying authentication module for root from 201.238.211.133 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.41.215.154 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.120.46.2 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.147.244.165 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.171.148.106 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.177.24.199 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.39.49.109 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.53.225.162 : 2 Time(s)
    User not known to the underlying authentication module for root from 202.53.250.42 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.71.140.165 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.110.245.243 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.122.225.226 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.183.81.155 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.58.188.17 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.72.59.6 : 1 Time(s)
    User not known to the underlying authentication module for root from 204.38.191.170 : 1 Time(s)
    User not known to the underlying authentication module for root from 208.115.111.200 : 1 Time(s)
    User not known to the underlying authentication module for root from 208.179.176.66 : 1 Time(s)
    User not known to the underlying authentication module for root from 209.203.18.122 : 1 Time(s)
    User not known to the underlying authentication module for root from 209.88.156.132 : 1 Time(s)
    User not known to the underlying authentication module for root from 210.196.168.137 : 1 Time(s)
    User not known to the underlying authentication module for root from 210.51.57.139 : 1 Time(s)
    User not known to the underlying authentication module for root from 211.234.100.205 : 1 Time(s)
    User not known to the underlying authentication module for root from 211.239.172.188 : 1 Time(s)
    User not known to the underlying authentication module for root from 211.9.48.203 : 1 Time(s)
    User not known to the underlying authentication module for root from 212.116.138.149 : 3 Time(s)
    User not known to the underlying authentication module for root from 212.155.135.204 : 1 Time(s)
    User not known to the underlying authentication module for root from 212.224.142.100 : 2 Time(s)
    User not known to the underlying authentication module for root from 212.92.23.139 : 2 Time(s)
    User not known to the underlying authentication module for root from 212.92.23.24 : 1 Time(s)
    User not known to the underlying authentication module for root from 213.129.249.99 : 2 Time(s)
    User not known to the underlying authentication module for root from 213.215.10.116 : 1 Time(s)
    User not known to the underlying authentication module for root from 213.215.247.194 : 1 Time(s)
    User not known to the underlying authentication module for root from 213.23.211.11 : 2 Time(s)
    User not known to the underlying authentication module for root from 213.235.133.209 : 1 Time(s)
    User not known to the underlying authentication module for root from 213.97.211.74 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.119.231.143 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.15.197.136 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.159.148.62 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.166.213.218 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.220.124.90 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.8.80.9 : 1 Time(s)
    User not known to the underlying authentication module for root from 218.241.156.219 : 2 Time(s)
    User not known to the underlying authentication module for root from 219.117.236.219 : 2 Time(s)
    User not known to the underlying authentication module for root from 219.234.81.209 : 1 Time(s)
    User not known to the underlying authentication module for root from 219.94.144.73 : 1 Time(s)
    User not known to the underlying authentication module for root from 220.232.206.71 : 3 Time(s)
    User not known to the underlying authentication module for root from 222.107.61.161 : 2 Time(s)
    User not known to the underlying authentication module for root from 222.173.107.103 : 4 Time(s)
    User not known to the underlying authentication module for root from 24.75.21.4 : 1 Time(s)
    User not known to the underlying authentication module for root from 38.112.30.222 : 1 Time(s)
    User not known to the underlying authentication module for root from 41.204.194.154 : 2 Time(s)
    User not known to the underlying authentication module for root from 58.215.75.55 : 1 Time(s)
    User not known to the underlying authentication module for root from 58.221.249.66 : 1 Time(s)
    User not known to the underlying authentication module for root from 58.246.85.122 : 2 Time(s)
    User not known to the underlying authentication module for root from 59.106.27.49 : 2 Time(s)
    User not known to the underlying authentication module for root from 59.124.223.238 : 1 Time(s)
    User not known to the underlying authentication module for root from 59.124.78.179 : 1 Time(s)
    User not known to the underlying authentication module for root from 61.31.200.49 : 1 Time(s)
    User not known to the underlying authentication module for root from 62.129.164.36 : 1 Time(s)
    User not known to the underlying authentication module for root from 62.94.161.156 : 1 Time(s)
    User not known to the underlying authentication module for root from 62.97.49.6 : 2 Time(s)
    User not known to the underlying authentication module for root from 64.117.46.243 : 1 Time(s)
    User not known to the underlying authentication module for root from 64.164.215.91 : 1 Time(s)
    User not known to the underlying authentication module for root from 64.182.136.46 : 2 Time(s)
    User not known to the underlying authentication module for root from 64.185.113.237 : 1 Time(s)
    User not known to the underlying authentication module for root from 65.111.177.12 : 1 Time(s)
    User not known to the underlying authentication module for root from 65.111.177.212 : 1 Time(s)
    User not known to the underlying authentication module for root from 65.70.247.20 : 1 Time(s)
    User not known to the underlying authentication module for root from 66.115.174.80 : 1 Time(s)
    User not known to the underlying authentication module for root from 66.240.254.216 : 1 Time(s)
    User not known to the underlying authentication module for root from 67.222.236.19 : 1 Time(s)
    User not known to the underlying authentication module for root from 69.159.244.44 : 1 Time(s)
    User not known to the underlying authentication module for root from 70.247.71.201 : 2 Time(s)
    User not known to the underlying authentication module for root from 72.51.43.242 : 1 Time(s)
    User not known to the underlying authentication module for root from 72.54.128.19 : 1 Time(s)
    User not known to the underlying authentication module for root from 72.90.111.10 : 1 Time(s)
    User not known to the underlying authentication module for root from 74.189.117.98 : 1 Time(s)
    User not known to the underlying authentication module for root from 74.55.60.90 : 2 Time(s)
    User not known to the underlying authentication module for root from 74.80.48.25 : 1 Time(s)
    User not known to the underlying authentication module for root from 75.125.235.162 : 2 Time(s)
    User not known to the underlying authentication module for root from 75.125.69.82 : 1 Time(s)
    User not known to the underlying authentication module for root from 75.160.204.13 : 1 Time(s)
    User not known to the underlying authentication module for root from 79.170.186.119 : 1 Time(s)
    User not known to the underlying authentication module for root from 79.38.79.53 : 1 Time(s)
    User not known to the underlying authentication module for root from 80.26.69.233 : 1 Time(s)
    User not known to the underlying authentication module for root from 81.168.103.177 : 1 Time(s)
    User not known to the underlying authentication module for root from 81.18.250.224 : 1 Time(s)
    User not known to the underlying authentication module for root from 81.221.15.140 : 2 Time(s)
    User not known to the underlying authentication module for root from 81.255.107.145 : 1 Time(s)
    User not known to the underlying authentication module for root from 82.119.240.3 : 2 Time(s)
    User not known to the underlying authentication module for root from 82.145.241.5 : 1 Time(s)
    User not known to the underlying authentication module for root from 82.187.183.124 : 1 Time(s)
    User not known to the underlying authentication module for root from 83.238.170.128 : 1 Time(s)
    User not known to the underlying authentication module for root from 84.19.182.97 : 1 Time(s)
    User not known to the underlying authentication module for root from 84.40.53.32 : 1 Time(s)
    User not known to the underlying authentication module for root from 85.145.196.239 : 1 Time(s)
    User not known to the underlying authentication module for root from 85.214.25.226 : 1 Time(s)
    User not known to the underlying authentication module for root from 85.22.60.6 : 2 Time(s)
    User not known to the underlying authentication module for root from 85.24.138.173 : 2 Time(s)
    User not known to the underlying authentication module for root from 87.244.204.196 : 1 Time(s)
    User not known to the underlying authentication module for root from 87.63.208.238 : 1 Time(s)
    User not known to the underlying authentication module for root from 87.86.55.4 : 2 Time(s)
    User not known to the underlying authentication module for root from 88.40.179.242 : 1 Time(s)
    User not known to the underlying authentication module for root from 89.250.247.28 : 2 Time(s)
    User not known to the underlying authentication module for root from 89.251.106.242 : 1 Time(s)
    User not known to the underlying authentication module for root from 89.39.28.239 : 1 Time(s)
    User not known to the underlying authentication module for root from 91.142.242.165 : 3 Time(s)
    User not known to the underlying authentication module for root from 91.144.170.50 : 2 Time(s)
    User not known to the underlying authentication module for root from 93.104.243.162 : 2 Time(s)
    User not known to the underlying authentication module for root from 93.152.158.141 : 2 Time(s)
    User not known to the underlying authentication module for root from 93.157.210.254 : 2 Time(s)
    User not known to the underlying authentication module for root from 93.82.242.114 : 1 Time(s)
    User not known to the underlying authentication module for root from 93.93.191.186 : 2 Time(s)
    User not known to the underlying authentication module for root from 94.127.136.74 : 1 Time(s)
    User not known to the underlying authentication module for root from 94.83.231.154 : 1 Time(s)

 **Unmatched Entries**
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(adsl-pool2-130.metrotel.net.co) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(208-115-111-200-reverse.wowrack.com) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(189-20-205-210.customer.tdatabrasil.net.br) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(5a.3c.374a.static.theplanet.com) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(host89-251-106-242.hnet.ru) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(12-177-111-65.serverpronto.com) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(74-203-204-99.static.twtelecom.net) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(adsl-pool2-143.metrotel.net.co) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(222-237-78-139.tongkni.co.kr) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(fw.mairie-rueilmalmaison.fr) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(host148-106.ipaddress.jp) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(196.201.230.18.reverse.kdn.co.ke) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(170.83-43-196.Admin.morogoro.ttcldata.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(74-80-48-25.GLB.dyn.lusfiber.net.48.80.74.in-addr.arpa) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(189-210-153-50.static.axtel.net) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(212-177-111-65.serverpronto.com) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(pin-064-185-113-237.cust.pocketinet.com) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(su93254216.aspadmin.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(75.25-180.uio.satnet.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(slavierobsb253.static.gvt.net.br) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(austrodach-trading-fo.b.astral.ro) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(q-224.n-81.18.250.qore.nl) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(dsl-201-155-88-252-sta.prod-empresarial.com.mx) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(static-Adsl190-248-8-19.une.net.co) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(ns.km20838-05.keymachine.de) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(adsl-pool2-108.metrotel.net.co) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(pcpQLOGICpcs) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(server150.fiscalia.cl) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(217-220-124-90-static.albacom.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(202-177-24-199.kddi.net.hk) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(93-93-191-186.aspserveur.com) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(dweb35.webfaction.com) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(server.colo250-042.indo.net.id) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(static-adsl190-29-2-204.une.net.co) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(mail.tbmg.com.au) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(89-39-28-239.samtv.ro) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(201-41-215-154.bnut3300.ipd.brasiltelecom.net.br) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(host-49-6.pool.intred.it) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(HOST.FLGR.BG) failed : 3 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(static.kpn.net) failed : 1 time(s)
 syslogin_perform_logout: logout() returned an error : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(customer-static-2-3-85.iplannetworks.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(0x573fd0ee.cpe.ge-0-1-0-1101.arcnqu1.customer.tele.dk) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(202.204.244.87.in-addr.arpa) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(payweb.surguttel.ru) failed : 1 time(s)

 ---------------------- SSHD End -------------------------

I’m reasonably confident that syslogin_perform_logout error is from a botched VM. Fedora 14 needs a more recent kernel than my DomU’s are getting and so that box is hosed. My two attempts to update to Fedora 14 have ended horribly, but that’s a different story.

I really should replace the batteries in this guy (freaking sweet UPS by the way, highly recommended) so he’ll last more than a few minutes.

A friend of mine did a bit more controlled test of his UPS and here’s his blog post with graphs also.

I have zoomed the graph a bit more to get more detail on the last 20 minutes of my servers uptime.

I find it interesting that the UPS temperature actually dropped when the thing was on batteries. I remember reading somewhere that the fan only runs when the inverter is actually active, so I guess that would make sense. I also find it interesting that the input frequency never changed, perhaps the UPS only records that value once every now and then, and doesn’t update it. I would think that with 0 input voltage I wouldn’t have any measurable frequency either.

I wonder if I could/should get those AFCI breakers replaced. They tend to not keep my computers on when there’s a lightning storm, and the only way to turn them back on is to go into the garage and flip it by hand.

Boy, was I wrong. Not that upstart is “bad.” Just that there’s something much better.

This actually makes things better instead of just providing the ability to make things better. It involves less shell, and more configuration. Dependencies are automatic, instead of manually specified. The author of the previously linked post goes into great detail regarding the reasoning behind the decisions made. It’s quite a good, albeit long, post.

I think I will have to get this working on my linux box that I intend to build. Possibly even on my laptop, as the features for enabling and disabling bluetooth would be quite advantageous. Also for the wifi and such. It’d be great if when I fired up the bluetooth, it were to start various things, like trying to connect to my mouse, or enabling the obex ftp thing.

As for a server, it’d be really nice to have if I can ever get my fibre channel setup to work. The Xen VMs won’t start until the Fibre Channel drives are available, and then they’ll all start up. Events could be fired depending on when the UPS was online or on battery.

I’m very impressed with it in concept, I’ll have to see how it goes in practice. Oh, and it’s going to be in Fedora 14. Woot.