Jul -- The Cutting Room Floor: sigh (more server issues...)

Xkeeper

Level: 263

Posts: 18506/25343
EXP: 296719701
For next: 2240752

Since: 07-03-07

Pronouns: they/them/????????

Since last post: 9 days
Last activity: 3 days

Posted on 12-22-10 02:40:03 PM

Link | Quote

root@valkyrie:/etc/apache2# tail /var/log/apache2/error.log
[Sun Dec 19 00:43:01 2010] [notice] Apache/2.2.9 (Debian) configured -- resuming normal operations
[Mon Dec 20 09:23:53 2010] [notice] caught SIGTERM, shutting down
[Mon Dec 20 09:23:53 2010] [notice] Apache/2.2.9 (Debian) configured -- resuming normal operations
[Mon Dec 20 09:27:06 2010] [error] server reached MaxClients setting, consider raising the MaxClients setting
apache2: Syntax error on line 185 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/alias.load: Cannot load /usr/lib/apache2/modules/mod_alias.so into server

What the hell?

That downtime service that I signed up for was reporting downtime, and sure enough, the entire thing is dead. Log in, and while nothing is really out of the ordinary, I get this.

apache2 seems to not even be running now, but the system didn't reboot and I honestly can't figure out what's going on.

I can't tell if that error is recent, either, because of the lack of timestamps. But otherwise... I don't know.

Related: Two of the CPUs displayed on htop vanished.

root@valkyrie:/usr/lib/apache2/modules# /etc/init.d/apache2 restart
Restarting web server: apache2.
root@valkyrie:/usr/lib/apache2/modules# htop
root@valkyrie:/usr/lib/apache2/modules# /etc/init.d/mysql restart
Stopping MySQL database server: mysqld failed!
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
root@valkyrie:/usr/lib/apache2/modules#

____________________

Xkeeper

Level: 263

Posts: 18508/25343
EXP: 296719701
For next: 2240752

Since: 07-03-07

Pronouns: they/them/????????

Since last post: 9 days
Last activity: 3 days

Posted on 12-23-10 07:53:43 AM

Link | Quote

Emailed support:

I've had literally nothing but aggravation in the last weeks in regards to my VPS.

The system is painfully slow (it often takes quite some time to even ls/nano a fairly small file), and especially in the last few days the response time for my server has skyrocketed even though actual usage has decreased (often because it just times out or fails to respond). It's gotten to the point where I actually had to get uptime monitoring because it was unreachable way too often.

root@valkyrie:/etc/apache2# tail /var/log/apache2/error.log
[Sun Dec 19 00:43:01 2010] [notice] Apache/2.2.9 (Debian) configured -- resuming normal operations
[Mon Dec 20 09:23:53 2010] [notice] caught SIGTERM, shutting down
[Mon Dec 20 09:23:53 2010] [notice] Apache/2.2.9 (Debian) configured -- resuming normal operations
[Mon Dec 20 09:27:06 2010] [error] server reached MaxClients setting, consider raising the MaxClients setting
apache2: Syntax error on line 185 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/alias.load: Cannot load /usr/lib/apache2/modules/mod_alias.so into server

This should *never* occur, especially when the server has been running unmonitored for days and that file hasn't even been touched. This outage ended up costing me about an hour of downtime, first from the assumption that the server was just choking again, until I logged in and saw that none of the apache processes were even running.

Whatever happened also caused mysqld, cron, and several other processes to simply lock up and stop responding:
root@valkyrie:/usr/lib/apache2/modules# /etc/init.d/apache2 restart
Restarting web server: apache2.
root@valkyrie:/usr/lib/apache2/modules# htop
root@valkyrie:/usr/lib/apache2/modules# /etc/init.d/mysql restart
Stopping MySQL database server: mysqld failed!
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
root@valkyrie:/usr/lib/apache2/modules#

http://share.pingdom.com/banners/212ad2c0
http://share.pingdom.com/banners/2839ae8b

Normally I would be more than willing to blame all of this on me, since I'm not amazingly skilled at debugging issues, but considering that someone else I know with a VPS on the same host as I am and we both have really, really severe performance issues that are only getting worse, even though nothing on my server has changed (other than an upgrade to 2 GB RAM and a slight increase in MySQL's caching to take some advantage of it, still running at about 700M/2GB).

I'm normally really forgiving with issues, but this is getting to the point where I, the other person on this server, and pretty much my entire userbase are fed up with it.

I am sick and tired of this bullshit, and I may very well just say fuck this whole thing and move to Slicehost. I really, really don't want to pack up and leave (AGAIN), but this is beyond any sort of reasonable tolerance.

____________________

Xkeeper

Level: 263

Posts: 18515/25343
EXP: 296719701
For next: 2240752

Since: 07-03-07

Pronouns: they/them/????????

Since last post: 9 days
Last activity: 3 days

Posted on 12-23-10 09:14:17 PM

Link | Quote

This whole thing can be summarized by "fuck."

____________________

Register - Login
Views: 99389381	Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies	04-24-22 08:06:30 AM

Query execution time:	0.387843 seconds
Script execution time:	0.008838 seconds
Total render time:	0.396681 seconds