I don't have a webhosting business, but have a dedicated server because my site is too large/busy for a virtual account. I realize I have a lot to learn.
So here is my problem... I've been experiencing extremely high loads over the last few weeks, sometimes reaching 30, and frequently reaching about 7. Most of the time, the load is less than 1. I'm trying to find out what is causing the spikes. Also, I frequently receive notices of apache failing. It has failed twice in the last 24 hours.
In similar posts here, others were told to check their apache messages. I've downloaded mine, but don't know what I'm looking for. These are the things that appear out of whack, at least to a novice:
1 There are thousands of entries such as:
Feb 5 05:25:52 server named: lame server resolving '188.8.131.52.in-addr.arpa' (in '95.253.207.in-addr.arpa'?): 184.108.40.206#53
What does this mean, lame server resolving x.x.x.x.in-addr.arpa?
2 There are also countless entries like:
Feb 5 06:57:59 server proftpd: server.mydomain.com (localhost[127.0.0.1]) - FTP login timed out, disconnected.
What would cause this?
3 There are a few instances of other nameservers referenced in my logs, such as:
Feb 5 02:09:13 server named: lame server resolving 'NS2.EMAIL-4-PRIZES.COM' (in 'EMAIL-4-PRIZES.COM'?): 220.127.116.11#53
Feb 3 01:03:17 server named: lame server resolving 'dns1.ded.btitelecom.net' (in 'ded.BTITELECOM.net'?): 18.104.22.168#53
Feb 4 01:16:31 server named: lame server resolving 'RALPH.CI.SEATTLE.WA.US' (in 'SEATTLE.WA.us'?): 22.214.171.124#53
Feb 4 01:16:31 server named: lame server resolving 'ALICE.CI.SEATTLE.WA.US' (in 'SEATTLE.WA.us'?): 126.96.36.199#53
(and many more)
Can any of the issues cause the server load to skyrocket and/or apache to fail?
Btw, I have a server with DedicatedNow. P4 1.7 processor, 1GB Ram. My site is mainly mysql databases, with a vBulletin forum, main site run by Mambo CMS, a recipes database, and a product reviews database by Incursio.
In your httpd.conf (/etc/httpd/conf/) you probably have it enabled to resolve hostnames from IP addresses... this takes time because each time a person visits your site you not only send them the html/php/mysql data you also have to query a nameserver to resolve their ip to a hostname. For example if they are 188.8.131.52 if would resolve them to whatever.domain.com. This also adds to the bulkiness of your log files. I would turn off the option as it is not necessary. As for apache failing... what version are you running? 2.0.x or 1.3.x? As for the proftpd logs you can check in /var/log/ and see what it says in more detail there... probably misconfigured. You can change the proftpd time out value so people cant idle on your FTP server so long. All of the configuration files should be in /etc/ or /usr/local/etc/