Category computers

rowla.nuxx.net lives!

PING 204.11.33.41 (204.11.33.41): 56 data bytes
64 bytes from 204.11.33.41: icmp_seq=0 ttl=42 time=44.605 ms
64 bytes from 204.11.33.41: icmp_seq=1 ttl=42 time=34.532 ms
64 bytes from 204.11.33.41: icmp_seq=2 ttl=42 time=31.647 ms
64 bytes from 204.11.33.41: icmp_seq=3 ttl=42 time=37.469 ms
--- 204.11.33.41 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 31.647/37.063/44.605/4.818 ms

I don’t completely understand how / why yet, nor how I’ll manage it, but I’ve got Postfix authenticating against mysql and pulling the virtual user / domain from there. I think that’s enough work for tonight.

Tomorrow the server goes into colocation.

On a suggestion I took a look at using lighttpd instead of Apache. Well, from what I can see for now it looks like an excellent substitute, especially for my needs. As long as I can get its mod_rewrite working as I need, it’ll be exactly what I need.

(Crap, just thought of one thing… Gallery doesn’t know how to deal with it, I don’t think… Must investigate it more… May need Apache. hrm.)

Anyway, here’s another wonderful error I received from DreamHost. Enjoy:

attempt to access field 'dbname' in object of class Ndn::Dreamhost::QueryTime at /usr/local/lib/site_perl/Ndn/Common/Object.pm line 949
Ndn::Common::Object::AUTOLOAD('Ndn::Dreamhost::QueryTime=HASH(0xc0ecc04)', 'undef') called at /usr/local/ndn/web/dhwebpanel/index.cgi line 117
Apache::ROOTpanel_2edreamhost_2ecom::index_2ecgi::handler('Apache=SCALAR(0xba6f09c)') called at /usr/lib/perl/5.8/Apache/Registry.pm line 149
eval {...} called at /usr/lib/perl/5.8/Apache/Registry.pm line 149
Apache::Registry::handler('Apache=SCALAR(0xba6f09c)') called at /dev/null line 0
eval {...} called at /dev/null line 0

So my new server is having a couple of problems. For one, when I tried to turn it on last night, it took three tries to power up. Now today it’s rebooting whenever there is a lot of disk load. See?

/usr/ports/comms/yawmppp/
/usr/ports/comms/zmtx-zmrx/
/usr/ports/comms/zssh/
/usr/ports/converters/Makefile
rm: /usr/ports/converters/Makefile: Bad file descriptor
Read from remote host 192.168.0.2: Connection timed out
Connection to 192.168.0.2 closed.
-bash-3.1$

(That was while running an update to the ports collection.)

I’m starting to think that my server wasn’t really compromised, and it just happened to be having power problems at the time it got hacked, and the massive amount of disk activity during the mass deletion / replacement caused the server to reboot.

So, I’ve ordered a FSP550-80GLC (PDF drawing) to hopefully resolve this problem. I likely won’t get the server into the colocation facility until next week, but I’ll see what I can do to get it limping along for the time being so that the OS can at least be installed and configured.

jawbreaker:~> time ls
bin gallery2_data logs Maildir mysql_backup www
0.000u 0.000s 0:02.84 0.0% 0+0k 0+0io 158pf+0w
jawbreaker:~>

Anyone want another reason why I’m leaving DreamHost?

That’s just absurd.

I can’t wait to get home and (hopefully) start getting the new server together.

I’d forgotten how loud the server formerly known as rez.nuxx.net is.

By the way, what should I call it now? lazerus.nuxx.net? Or…. ?

1) The new 320GB disks in my G5 are a lot quieter.

2) Carbon Copy Cloner does a great job of duplicating OS X disks.

With the move back to Waveform from DreamHost, there are a few domains which I’ll no longer be hosting. If I have opted not to host your domain, you will receive some manner of communication from me. I’m sending out some of these tonight via LJ replies, as DreamHost is once again being ridiculously unreliable and I’m not certain that email is working very well at all. Other people I’ll likely contact directly, possibly via an instant messenger.

I just ordered a 3Ware 8006-2LP (warning, PDF) hardware RAID controller to be put in the server formerly known as bornslippy.nuxx.net.

Why?

It’s going back to Waveform. I’m fed up with DreamHost’s bullshit. Specifically, how processes are killed after either a certain amount of time or load. The result is that Google is incapable of downloading a full sitemap, some pages of my Gallery don’t load, MediaWiki falls over sometimes, I can’t do a backup using rsync over ssh, etc.

Fortunately I’m still within the DreamHost 97-day money back guarantee thing, so I’m going to try and get the server running at Waveform in that time, then get the year’s payment refunded. If they won’t do it, I’ll initiate a charge back.

Fuck them. Their service doesn’t live up to what the site claims, the downtime was ridiculous, and everything is just slow. Someone tell me why an ls should take 2.45 seconds, and why checksumming a few hundred meg file should take an hour?

Fortunately I just purchased two 320GB disks for my G5, and I can use the 160GBs from it in a mirror in the new server.

< sigh >