Hi. I have a CentOS 4.2 server running. I've just experience that it stops responding (http, ssh) when doing yum update pam xorg-x11 gnupg
This has happened two times in a row, so I'm curious if anyone has experienced anything like this? Could it be yum or should I look for the explanation elsewhere?
[root@machine ~]# yum update pam xorg-x11 gnupg Setting up Update Process Setting up repositories update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files
And here everything stops. Any tips on troubleshooting? According to nmap port 80 is open.
white:~ morten$ nmap -p 80 213.150.40.246
Starting Nmap 4.10 ( http://www.insecure.org/nmap/ ) at 2007-03-26 18:53 CEST Interesting ports on 213.150.40.246: PORT STATE SERVICE 80/tcp open http
Nmap finished: 1 IP address (1 host up) scanned in 0.134 seconds
But no HTTP traffic:
white:~ morten$ wget 213.150.40.246 --18:53:42-- http://213.150.40.246/ => `index.html.1' Connecting to 213.150.40.246:80... connected. HTTP request sent, awaiting response...
It just hangs. Any tips much appreciated. Thanks.
Morten
Morten spake the following on 3/26/2007 9:54 AM:
Hi. I have a CentOS 4.2 server running. I've just experience that it stops responding (http, ssh) when doing yum update pam xorg-x11 gnupg
This has happened two times in a row, so I'm curious if anyone has experienced anything like this? Could it be yum or should I look for the explanation elsewhere?
[root@machine ~]# yum update pam xorg-x11 gnupg Setting up Update Process Setting up repositories update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files
And here everything stops. Any tips on troubleshooting? According to nmap port 80 is open.
white:~ morten$ nmap -p 80 213.150.40.246
Starting Nmap 4.10 ( http://www.insecure.org/nmap/ ) at 2007-03-26 18:53 CEST Interesting ports on 213.150.40.246: PORT STATE SERVICE 80/tcp open http
Nmap finished: 1 IP address (1 host up) scanned in 0.134 seconds
But no HTTP traffic:
white:~ morten$ wget 213.150.40.246 --18:53:42-- http://213.150.40.246/ => `index.html.1' Connecting to 213.150.40.246:80... connected. HTTP request sent, awaiting response...
It just hangs. Any tips much appreciated. Thanks.
Morten
Is the server secure enough that you could disable firewall for a few minutes and try the yum update again? That would help eliminate the firewall as the problem.
It just hangs. Any tips much appreciated. Thanks.
Morten
Is the server secure enough that you could disable firewall for a few minutes and try the yum update again? That would help eliminate the firewall as the problem.
I'd prefer not to. Yum is able to download files just fine, it's the install process that breaks somehow. I just found that the hang is due to yum taking up 100% and stays there for like 20 minutes before it exits.
Br,
Morten
On Mon, 26 Mar 2007 20:49:41 +0200, Morten wrote:
I'd prefer not to. Yum is able to download files just fine, it's the install process that breaks somehow. I just found that the hang is due to yum taking up 100% and stays there for like 20 minutes before it exits.
Maybe it's choking through bad data in the RPM database. Have you tried a "rpmdb --rebuilddb"?
Miark
Miark wrote:
On Mon, 26 Mar 2007 20:49:41 +0200, Morten wrote:
I'd prefer not to. Yum is able to download files just fine, it's the install process that breaks somehow. I just found that the hang is due to yum taking up 100% and stays there for like 20 minutes before it exits.
Maybe it's choking through bad data in the RPM database. Have you tried a "rpmdb --rebuilddb"?
Thanks for the tip. It didn't work but I googled your suggestion and found the underlying problem to be a sqlite/python binding issue. So I manually installed python-sqlite-1.1.7-1.2.x86_64.rpm and things work again :-)
Thanks.
Morten
-
Miark -
Morten -
Scott Silva