Ashoat

Yeah, I think you're right.

Which server are you on?

Hmm seems like cPanel/WHM works on FreeBSD... Probably not a good idea to reinstall everything, though. It would require lots of annoying reconfigurations and/or downtime.

Hey guys, Sorry, Cody had a kernel panic. No idea why that occurred... probably a bug in Linux. Service should be fully restored. Thanks, djbob

The image solution doesn't require Javascript and is more elegant...

I will take a look at this issue in about two weeks when I'm down at the datacenter. Sorry about the issues, guys...

Closing...

To be honest, I probably ought to make it an AJAX request or a 0x0 image or something. The iframe solution is so hacky...

If the script requires that much memory it probably requires far too CPU as well...

Yeah on Johnny we need to run an old version of Rails (2.3, IIRC) for compatibility with Mongrel so cPanel can run RoR apps securely.

Yeah they all go to the same place so it should be okay.

Looks like DNS records are out of sync. I'm resyncing them as we speak, so hopefully you should be okay within 24 hours.

I guess it's okay to have an account on both Stevie and Johnny. I can see the reasoning for wanting that flexibility.

Okay, done. Is it working now?

I'm pretty sure that it's not about too much disk I/O, as I checked that multiple times when Stevie was loading rather slowly. Stevie should be okay now...

I already tried running the CREATE LANGUAGE command, along with the commands specified in the other thread. It seems like I can't create the language for other users without granting them "superuser" privileges, which I don't want to do. Does anyone have any ideas as to what I can do?

Sorry, but I can't run that file for you. Our servers soft-limit memory at 256 MiB and hard-limit it at 512 MiB. If you need a gig you should probably look towards paid hosting...

Though I am able to query your nameserver records from who.is, I am unable to get the NS record from where I am and from Cody. Have you changed your nameservers recently?

Very possibly. To check for memory errors I would have to run memcheck86+ on the machine. This may be pre-installed in the bootloader, which would make it easy to run for the datacenter tech. However, this would involve a reboot to check. Alternately, I could install memcheck86+ on a USB drive and have the datacenter tech run that. I'll be driving down to Silicon Valley within the following month. It might make sense for me to try to take care of the issues once I'm down there. Otherwise, it's very hard for a datacenter tech to communicate what issues are showing up on the screen.

Not sure what's happening... but hopefully this should clear up in a bit. Is your account getting closer to the end of the queue?

byron: I think that's probably because the server only has 1/3 as many accounts at this point... Geoff: There is a limit, but if it was being reached then PHP would just die and return a 500 error instead of timing out.

Closing due to inactivity...

Okay, I've suspended the account.

Okay, I've put the image in locally.

Never mind... after a further look, my theory doesn't make sense. At this point, I really don't know what to say. There's tons of memory available (can't be a RAM issue), CPU load at a reasonable level (can't be a CPU issue), and disk I/O is stable (can't be a disk issue). What could the issue be?