Server Crashes & Hangs...

mainarea

New member
Joined
Dec 6, 2003
Messages
3
I've gotten my second DA server (at a different DC than my first), and they've both had problems with crashing. They'll respond to pings & traces, but no services on the box work.

I tried SSH'ing into the box, and it doesn't respond - it doesn't disconnect me though. I can attempt to telnet to open ports such as HTTP, DA and SMTP, and they'll do the same thing, but if I try a port that doesn't exist (i.e. 74), it'll automatically disconnect. I couldn't find anything the last time, but I'll look very carefully this time. Where should I look, besides /var/log/messages ? This has happened twice on this server - with two completely different processors & motherboards, as well as new RAM. RAM was also replaced in my first machine, and it kept crashing. I need to get to the bottom of this problem - it's running RedHat 9.0.

- Matt
The MainArea Network
 
No clue where the problem lies....

/var/log/messages :

Dec 5 00:11:01 kc httpd: httpd shutdown succeeded
Dec 5 00:11:01 kc httpd: httpd startup succeeded
Dec 6 00:11:01 kc httpd: httpd shutdown succeeded
Dec 6 00:11:01 kc httpd: httpd startup succeeded
Dec 6 11:15:09 kc proftpd[11256]: kc.mainarea.com (61.134.32.10[61.134.32.10]) - FTP session opened.
Dec 6 11:15:09 kc proftpd[11257]: 69.44.104.49 (61.134.32.10[61.134.32.10]) - FTP session opened.
Dec 6 11:15:09 kc proftpd[11256]: kc.mainarea.com (61.134.32.10[61.134.32.10]) - FTP session closed.
Dec 6 11:15:09 kc proftpd[11257]: 69.44.104.49 (61.134.32.10[61.134.32.10]) - FTP session closed.
Dec 6 16:28:10 kc syslogd 1.4.1: restart.
Dec 6 16:28:10 kc syslog: syslogd startup succeeded


HTTPD access_log:

65.104.233.2 - - [06/Dec/2003:12:57:37 -0600] "GET http://www.intel.com/ HTTP/1.1" 200 44 "-" "Mozilla/4.0 (compatible; MSIE$
65.104.233.2 - - [06/Dec/2003:12:57:37 -0600] "GET http://www.intel.com/ HTTP/1.1" 200 44 "-" "Mozilla/4.0 (compatible; MSIE$
68.38.113.219 - - [06/Dec/2003:16:30:43 -0600] "GET / HTTP/1.1" 200 44 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.$

HTTPD error_log:
[Sat Dec 6 00:11:00 2003] [notice] caught SIGTERM, shutting down
[Sat Dec 6 00:11:01 2003] [warn] NameVirtualHost 69.44.104.50:80 has no VirtualHosts
[Sat Dec 6 00:11:01 2003] [warn] NameVirtualHost 69.44.104.50:443 has no VirtualHosts
[Sat Dec 6 00:11:01 2003] [notice] Apache/1.3.28 (Unix) mod_ssl/2.8.15 OpenSSL/0.9.7a PHP/4.3.3 mod_perl/1.27 FrontPage/5.0$
[Sat Dec 6 00:11:01 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Dec 6 00:11:01 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Sat Dec 6 16:28:20 2003] [warn] NameVirtualHost 69.44.104.50:80 has no VirtualHosts
[Sat Dec 6 16:28:20 2003] [warn] NameVirtualHost 69.44.104.50:443 has no VirtualHosts
[Sat Dec 6 16:28:21 2003] [notice] Apache/1.3.28 (Unix) mod_ssl/2.8.15 OpenSSL/0.9.7a PHP/4.3.3 mod_perl/1.27 FrontPage/5.0$
[Sat Dec 6 16:28:21 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Dec 6 16:28:21 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)


- Matt
 
What kind of kernel?

Since its at two differnt DCs I doubt its a kernel problem, but I know some Burst boxes that have recently had a kernel upgrade have had a problem about things just randomly crashing...
 
Nope, this box isn't at Burst (it's at Wholesale Internet in KC, MO).

[root@kc root]# uname -a
Linux kc.mainarea.com 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux

- Matt
 
The latest kernel for RH9 is 2.4.20-24.9. You'll want to upgrade to that kernel, especially as there is a security hole in older versions.

up2date -f kernel and then a reboot will update you.
 
Back
Top