Please help!! I'm trying to get some work done and I can't load my site.
Cpanel shows this:

apache (1.3.31 (Unix)) failed
bind (9.2.4rc6) up
cppop up
cpsrvd up
exim (exim-4.34-60_cpanel_stmpcontrol_antivirus_rewrite_mailman2_mailtrap_exiscan) up
eximstats up
ftpd up
imap up
mysql (4.0.20-standard) up
syslogd up
Server Load 11.31 (4 cpus)
Memory Used 35.7 %
Swap 0.927 %
Disk sda3 (/) 73 %
Disk sda1 (/boot) 16 %
Disk sdb1 (/home) 100 %


Also, I have a server monitor program running at it shows the access time is very bad tonight. Can something please be done? I have much to do.

9/15/2004 12:32:06 PM 596 Server1 HTTP HTTP Sensor1: OK 596 ms
9/15/2004 1:32:06 PM 583 Server1 HTTP HTTP Sensor1: OK 583 ms
9/15/2004 2:32:07 PM 857 Server1 HTTP HTTP Sensor1: OK 857 ms
9/15/2004 3:32:06 PM 579 Server1 HTTP HTTP Sensor1: OK 579 ms
9/15/2004 4:32:06 PM 591 Server1 HTTP HTTP Sensor1: OK 591 ms
9/15/2004 5:32:06 PM 581 Server1 HTTP HTTP Sensor1: OK 581 ms
9/15/2004 6:32:06 PM 627 Server1 HTTP HTTP Sensor1: OK 627 ms
9/15/2004 7:32:07 PM 1010 Server1 HTTP HTTP Sensor1: OK 1010 ms
9/15/2004 8:32:07 PM 1712 Server1 HTTP HTTP Sensor1: OK 1712 ms
9/15/2004 9:32:06 PM 588 Server1 HTTP HTTP Sensor1: OK 588 ms
9/15/2004 9:43:51 PM 5434 Server1 HTTP HTTP Sensor1: OK 5434 ms
9/15/2004 9:44:18 PM 14835 Server1 HTTP HTTP Sensor1: OK 14835 ms
9/15/2004 9:45:54 PM 7789 Server1 HTTP HTTP Sensor1: OK 7789 ms
9/15/2004 9:54:16 PM 579 Server1 HTTP HTTP Sensor1: OK 579 ms
9/15/2004 9:58:41 PM 3995 Server1 HTTP HTTP Sensor1: OK 3995 ms
9/15/2004 10:01:55 PM 4774 Server1 HTTP HTTP Sensor1: OK 4774 ms

sfworks.com
server 21

Should be ok now.

Hello,

The problem is happening again. From my logs you can see that it started at around 6am Pacific time. Http response time is going very very slow and I am getting some complaints from user. This is happening from different ISPs so I know that it isn't an ISP problem as was suggested in my trouble ticket. Can you please tell me what is happening?

Thank you,

sfworks.com
server 21

9/16/2004 5:28:05 AM 270 Server1 HTTP HTTP Sensor1: OK 270 ms
9/16/2004 5:43:05 AM 271 Server1 HTTP HTTP Sensor1: OK 271 ms
9/16/2004 5:58:22 AM 17091 Server1 HTTP HTTP Sensor1: OK 17091 ms
9/16/2004 6:13:25 AM 20192 Server1 HTTP HTTP Sensor1: Slow 20192 ms
9/16/2004 6:28:23 AM 18158 Server1 HTTP HTTP Sensor1: OK 18158 ms
9/16/2004 6:43:05 AM 263 Server1 HTTP HTTP Sensor1: OK 263 ms
9/16/2004 6:58:05 AM 260 Server1 HTTP HTTP Sensor1: OK 260 ms
9/16/2004 7:13:05 AM 261 Server1 HTTP HTTP Sensor1: OK 261 ms
9/16/2004 7:28:05 AM 283 Server1 HTTP HTTP Sensor1: OK 283 ms
9/16/2004 7:43:05 AM 277 Server1 HTTP HTTP Sensor1: OK 277 ms
9/16/2004 7:58:05 AM 250 Server1 HTTP HTTP Sensor1: OK 250 ms
9/16/2004 8:13:07 AM 2306 Server1 HTTP HTTP Sensor1: OK 2306 ms
9/16/2004 8:28:07 AM 2276 Server1 HTTP HTTP Sensor1: OK 2276 ms
9/16/2004 8:34:32 AM 261 Server1 HTTP HTTP Sensor1: OK 261 ms
9/16/2004 8:46:29 AM 26434 Server1 HTTP HTTP Sensor1: Slow 26434 ms
9/16/2004 8:46:40 AM 9324 Server1 HTTP HTTP Sensor1: OK 9324 ms
9/16/2004 8:46:46 AM 3244 Server1 HTTP HTTP Sensor1: OK 3244 ms

Fixed.
Problem was in temporary fault of Apache web server.
Thank you for the patience.

Problem is still not fixed. My site takes very long to load still and sometimes will not load. Please see my log files. Normal time should be 200-400ms

9/16/2004 9:21:24 AM 10081 Server1 HTTP HTTP Sensor1: OK 10081 ms
9/16/2004 9:22:52 AM 14555 Server1 HTTP HTTP Sensor1: OK 14555 ms
9/16/2004 9:37:42 AM 4153 Server1 HTTP HTTP Sensor1: OK 4153 ms
9/16/2004 9:41:38 AM 3877 Server1 HTTP HTTP Sensor1: OK 3877 ms
9/16/2004 9:53:43 AM 21115 Server1 HTTP HTTP Sensor1: Error: Connection reset by peer. (Socket error: 10054) 21115 ms (Code: 10054)
9/16/2004 9:53:45 AM 1128 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10061 Connection refused. (#2) 1128 ms
9/16/2004 9:56:04 AM 256 Server1 HTTP HTTP Sensor1: OK 256 ms
9/16/2004 10:02:02 AM 7724 Server1 HTTP HTTP Sensor1: OK 7724 ms
9/16/2004 10:06:06 AM 6243 Server1 HTTP HTTP Sensor1: OK 6243 ms
9/16/2004 10:21:12 AM 11916 Server1 HTTP HTTP Sensor1: OK 11916 ms
9/16/2004 10:36:14 AM 14244 Server1 HTTP HTTP Sensor1: OK 14244 ms
9/16/2004 10:51:21 AM 21163 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10060 Connection timed out. (#2) 21163 ms
9/16/2004 10:51:31 AM 9343 Server1 HTTP HTTP Sensor1: OK 9343 ms
9/16/2004 11:06:20 AM 5451 Server1 HTTP HTTP Sensor1: OK 5451 ms
9/16/2004 11:21:44 AM 28911 Server1 HTTP HTTP Sensor1: Error: Connection reset by peer. (Socket error: 10054) 28911 ms (Code: 10054)
9/16/2004 11:21:45 AM 1126 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10061 Connection refused. (#2) 1126 ms
9/16/2004 11:28:29 AM 6060 Server1 HTTP HTTP Sensor1: OK 6060 ms
9/16/2004 11:44:26 AM 63035 Server1 HTTP HTTP Sensor1: Error: Read Timeout (#2) 63035 ms
9/16/2004 11:44:48 AM 21041 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10060 Connection timed out. (#2) 21041 ms
9/16/2004 11:54:05 AM 1127 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10061 Connection refused. (#2) 1127 ms
9/16/2004 12:09:09 PM 4886 Server1 HTTP HTTP Sensor1: OK 4886 ms
9/16/2004 12:24:11 PM 7049 Server1 HTTP HTTP Sensor1: OK 7049 ms
9/16/2004 12:24:56 PM 11343 Server1 HTTP HTTP Sensor1: OK 11343 ms

Check it now please.

I still can not get through to my site. It only loads some times.

Perhaps it is a DNS server issue. When I ping from dnsstuff.com it shows ok but when I do a name server lookup it is bad. I have wasted many hours of work with this issue today. Please help!



Time to look up sfworks.com A record
Generated by www.DNSstuff.com at 22:13:27 GMT on 16 Sep 2004.
Searching for A record for sfworks.com at l.root-servers.net: Got referral to J.GTLD-SERVERS.NET. [took 94 ms]
Searching for A record for sfworks.com at J.GTLD-SERVERS.NET.: Got referral to ns19.hostony.net. [took 220 ms]
Searching for A record for sfworks.com at ns19.hostony.net.: Reports an answer.

Record is:


Domain Type Class TTL Answer sfworks.com. A IN 14400 67.15.36.4 sfworks.com. NS IN 14400 ns18.hostony.net. sfworks.com. NS IN 14400 ns19.hostony.net. ns18.hostony.net. A IN 162901 67.15.24.116 ns19.hostony.net. A IN 14400 67.15.36.4

Looking up at ns18.hostony.net.... Timed out.
Looking up at ns19.hostony.net.... Reports 1 A record(s). 42ms.


Average of all 2 nameservers: 1521ms (plus 314ms overhead).

Score: F

I hope you don't think I'm pestering you too badly but I just need things to work so I'm adding as much information as possbile so you can track down the problems. Here is my log since noon today. As you can see the response time is very bad. It should be under 400 ms. And like I said, sometime it works but most of the time it does not.

9/16/2004 11:54:05 AM 1127 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10061 Connection refused. (#2) 1127 ms
9/16/2004 12:09:09 PM 4886 Server1 HTTP HTTP Sensor1: OK 4886 ms
9/16/2004 12:24:11 PM 7049 Server1 HTTP HTTP Sensor1: OK 7049 ms
9/16/2004 12:24:56 PM 11343 Server1 HTTP HTTP Sensor1: OK 11343 ms
9/16/2004 12:29:59 PM 1194 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10061 Connection refused. (#2) 1194 ms
9/16/2004 12:30:01 PM 1133 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10061 Connection refused. (#2) 1133 ms
9/16/2004 12:41:46 PM 28255 Server1 HTTP HTTP Sensor1: Slow 28255 ms
9/16/2004 12:56:18 PM 288 Server1 HTTP HTTP Sensor1: OK 288 ms
9/16/2004 1:11:32 PM 14572 Server1 HTTP HTTP Sensor1: OK 14572 ms
9/16/2004 1:26:33 PM 15222 Server1 HTTP HTTP Sensor1: OK 15222 ms
9/16/2004 1:41:22 PM 3956 Server1 HTTP HTTP Sensor1: OK 3956 ms
9/16/2004 1:56:24 PM 6337 Server1 HTTP HTTP Sensor1: OK 6337 ms
9/16/2004 2:11:23 PM 5331 Server1 HTTP HTTP Sensor1: OK 5331 ms
9/16/2004 2:26:22 PM 4675 Server1 HTTP HTTP Sensor1: OK 4675 ms
9/16/2004 2:41:24 PM 5948 Server1 HTTP HTTP Sensor1: OK 5948 ms
9/16/2004 2:56:25 PM 7513 Server1 HTTP HTTP Sensor1: OK 7513 ms
9/16/2004 3:11:25 PM 7145 Server1 HTTP HTTP Sensor1: OK 7145 ms
9/16/2004 3:26:39 PM 21197 Server1 HTTP HTTP Sensor1: Error: Socket Error # 10060 Connection timed out. (#2) 21197 ms