CentOS 5 :: Udev Hangs On Boot For A Long Time, Suspect Pam_console_apply?
Mar 24, 2010
I'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
I am running Centos 5.3. I ran no updates, performed no installs, nor changed any configuration immediately prior to this issue. My problem is this: when I run the command startx (default runlevel 3), it is a long time (5-10 minutes) before Gnome startx, and once it does start applications will not run. Also, when I try to use sudo (from any environment, even ssh), it is a long time (5-10) before the command is executed.
I cannot say for sure, but it seems like this is an intermittent problem. Sometimes X takes a long time to start, but once it starts it will launch programs. Sometimes X takes a long time to launch, but once it starts it will only launch certain programs. Though presently X always takes a long time to start, and I cannot successfully launch any programs.
A while back a had a similar problem to this (x taking long time to start, sudo taking long time to execute) and it ended up being a DNS problem. Unfortunately, I cannot remember exactly what it was and I stupidly did not document it. Maybe this is also DNS related, I don't know.
I don't know what log files to look at for problems with X, Gnome, and sudo taking a long time to start.
The desktop stops working, the panel stops working.. but compositing, desktop cube etc all work fine.I can still launch a program with Alt-F2.When I try and kill it (to restart) using 'killall plasma' / 'kill -9 <pid> / 'kill -15 pid' from a terminal, nothing happens, the process keeps running. If I leave it for about 30 mins it suddenly dies, allowing me to run 'plasma' from a terminal - then everything is back to normal.
If I log out and try to log back in again, I get a black screen. Only way to fix it is either to kill it and wait for 30 mins or so, or totally reboot the computer.Tail of the xsessions error file:
Sometimes I get this weird thing where typing a name into the kickoff menu hangs after a few letters. It hangs the entire computer! Once it happens, I try to close it but have to wait about 20 seconds before I can do anything on the computer. Then everything else works fine (after it's closed). But if I go back to kickoff and try again, it does the same thing! I can't seem to find anything in "top" to indicate what's happening.
openSUSE 11.2 KDE 4.3.4 Linux 126.96.36.199-0.1-default i686 AMD Sempron(tm) Processor 3100+ 1.8 GHZ nVIDIA G98 GForce 8400 GS with nvidia driver
I have encountered the same problem as indicated in this post: "udev hang after upgrade from 5.3 to 5.4"[URL]... I'm testing the upgrade path to centos 5.4 on several virtual machines prior to upgrading our production systems. I have upgraded centos 5.2 --> centos 5.4 and centos 5.3 to centos 5.4. In both cases udev hangs after the upgrade. The following message is displayed on the console: "Starting udev: Wait timeout. Will continue in the background [FAILED]"
I found another related post: "udev hangs on boot for a long time, suspect pam_console_apply"[URL]..So, I booted by VMs using the "udevdebug" option to grub and received the same error message - "udevd-event [###]: run_program: Waiting ## seconds for output of '/sbin/pam_console_apply /dev/..."
In my /etc/ldap.conf file "bind_policy hard" is commented out. I added a line "bind_policy soft" as described in the post and my VMs booted fine. NOTE: This problem is not encountered with a fresh install of CentOS 5.4 and the "bind_policy hard" option in the /etc/ldap.conf is commented out as in the upgraded systems. What is really causing this problem and how do I get it addressed? I have a couple hundred systems to update from various releases of CentOS 5 to the latest current version 5.4. It would be nice to get this bug squashed..
During the boot process the machine (Fujitsu Celsius M470) hangs about 4 min at udev:loading drivers. After that it continues and I can work with the OpenSuse 11.2 system without problems.I activated the debug log in /etc/udev/udev.confthen I see that it is doing a lot in that time, at the end I see the message:udevadm settle timeout queue contains: a long list of pci/usb entries (no entries in any log for this)
in the logfile I find:udevd-work: '/sbin/modprobe' (stderr) 'FATAL: Error inserting ipmi_si (/lib/modules/188.8.131.52-0.1-desktop/kernel/drivers/char/ipmi/ipmi_si.ko): No such device'there is no ipmi. how can I deactivate the loading of this module?
udevd-work: '/sbin/modprobe' (stderr) 'FATAL: Module input:b0019v0000p0001e0000_e0,1,k74,ramlsfw not found.' Mar 17 11:35:36 mira udevd-work: '/sbin/modprobe' (stderr) 'FATAL: Module
I have just installed slack-13.1 on an acer aspire one netbook from a usb stick by booting the install kernel with noudev. I was able to do a complete install including lilo but upon rebooting my boot hangs when encountering my webcam.I see enough info to note the id as 0c45:62c0. This is a microdia webcam which I may be able to do something about later but in the first instance I'd like to be able to boot my system. The bios is very basic and there is no way to disable devices.
i'm heaving the following message at boot time: "Starting udev: udevd: unknown key 'DEVTYPE' in /etc/udev/rules.d/70-cups-libusb.rules:6", i guess it's something about usb printing support but i am not sure, and i don't know how to fix it, does any of you guys know what this exactly means and how to fix it
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
After I installed a new hard drive, when I booted up into Ubuntu, it would give me this error: "failed command: WRITE DMA". So I tried the workarounds and I guess it just covered the log with the Boot Splash, now it's taking a long time just to boot up.
Now I use mutt to manage the mail list. But when I start to mutt, it takes a long time (about 1~2 minutes) to load all the mail list, about 20 thousands mail. I don't know why it takes such a long time.
I am using KVM and created four guest Operating systems on it.The server host is Ubuntu 10.04.I am using 4 websites in a reverse proxy environment.One of our website is running on CentOS VM.Right now there is no traffic on the website static HTML pages.I do not have any clue as why it was taking longer time to be accessed.
I've setup vsftpd correctly and it's running fine with local users (in the same LAN). However, when remote users wanna login to the server, it takes more than 1 minute to get in. Users do can login from remote. It just took too long. (It prompted for the username and password very fast.) Since the server is behind a router, I did configure the port forwarding for TCP 20-21. The centos version is 5.3. The vsftpd is v2.0.5.
I recently broke down in the face of morbid curiosity and clicked that little version update button. it seems to run flawlessly (after i uninstalled the pesky touchpad) but it takes a long time to boot up now. at least a full minute. is this normal?
I will add also that it said my version of grub had been modified (which i dont remember doing, but may have) so i told it to leave the current one in place.
Have just installed 5.4 64 bit on an AMD64 x2 system with 4 GB ram running ESXi4.Text based install went fine, but on reboot starting up it gets as far as 'Starting udev' and just hangs. Checking the performance in ESXi it appears to be using 100% cpu.I have left it for half an hour and it does not progress and the only thing to do is to power cycle the VM.I have searched and found a few suggestions for kernel parameters but they did not make any difference. I can't even get in to a command line as it doesn't boot up far enough.I have reinstalled it several times and also checked the MD5 of the downloaded file and all appears Ok.
It takes me a while to log in the splash screen just sits there for ages before i get to the desktop. Never used to be this slow and I'm not sure why. Firstly, I'm running Ubuntu 11.04, standard DE. I do have conky starting up in a script but it has the & at the end of the line so I didn't think this would cause it (or is there some special case for log in time on how & is treated?). However as a test I will comment out the line in the script and see if it is the cause.
However just for general knowledge and in case that isn't the problem, how does one go seeing what is happening during the time from when one log's in and the desktop is displayed? Is there some kind of log that shows the date/time that can be enabled or is there a debug mode that can be enabled somehow via special keys or maybe from grub?
It takes a few minutes to start during boot and I just did a fresh install in a virtual machine. Haven't touched sendmail so it has default config. Someone told me it could be a DNS issue, but I can do DNS lookups and navigate the web well.
Ever since the kernel update to 184.108.40.206-47.fc13.x86_64, my boot process hangs at about startx time. I boot cleanly at runlevel 3 in either this or the previous 220.127.116.11 kernel. If I execute startx from here (in either kernel), the system hangs at the same place. During the early troubleshooting, I read in another thread (250929) about installing xorg-x11-drv-catalyst, which I did using yum. This led to the failure of the 2.6.33 kernel; yum remove did not fix this. I have carefully followed the instructions in the fglrx HOWTO (updated a week ago by Hlingler) as they relate to a PAE kernel (including reinstalling mesa-libGL), and that fixed earlier difficulties. Hence, I felt I needed a new thread.
dmesg tells me Code: microcode: CPU0: patch_level=0x2000032 platform microcode: firmware: requesting amd-ucode/microcode_amd.bin Linux video capture interface: v2.00 piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0 microcode: CPU1: patch_level=0x2000032 platform microcode: firmware: requesting amd-ucode/microcode_amd.bin microcode: Microcode Update Driver: v2.00 .....
But the program itself reports Code: # microcode_ctl -h This program is for updating the microcode on Intel processors belonging to the IA32 family - PentiumPro upwards (x86-64 included). It depends on the Linux kernel driver. The website urbanmyth.org/microcode (mentioned by yum info microcode_ctl) clearly indicates that Intel has taken over this microcodecode distribution, and suggests that it is no longer valid for AMD processors.
I found a reference to a kernel configuration flag CONFIG_MICROCODE_AMD (as a plausible subsititute for CONFIG_MICROCODE_INTEL) that possibly belongs in a script in /etc/init.d - but the above context leads me to suspect this is not true any more. In any event, those flags are not mentioned anywhere in my init.d scripts - in fact nowhere in the entire /etc tree. My microcode file exists, and is dated March 23. How do I get it installed? Or is this completely unrelated to my hanging boot problem, as suggested by the "platform microcode" line in the dmesg output? If so, where should I be looking?
I want to try the new 11.1. When I start the installation (x86_64 DVD), the startup is hanging. The last message is "Starting udev...". Keyboard is completely frozen, only reset button is working. Mobo is an Intel DG965WH with 4GB RAM and ATI Graphic card (ASUS1950pro). My opensuse 11.0 runs without any problems.
I have two minor problems with Ubuntu which I've been running on my aging Fujitsu-Siemens Lifebook for a couple of years now.
First, I recently upgraded to v10.04 with no problems. However, I've just applied the latest updates via Update Manager and the laptop will now hang after the welcome screen.
There are no error messages, just a black screen and the case fan runs a full tilt until I force a shutdown. I've waited 5 or so minutes to see if it's actually doing anything but it would appear that it isn't.
The only way to boot the laptop is to choose an older Grub menu option, then it boots up fine. It may very well be a hardware issue because another (newer) laptop in the household has updated no problem.
Next, I tried to change the password of the admin account using "Users and Groups". It appeared to work but then I had to use the old password to log in again. On logging in I am prompted for the new password, the error message saying that the "token ring" password (I think it's token ring, I'm doing this from memory) doesn't match.
Again I can live with this quirk but it would be nice to put it right.
I am trying to boot the CentOS live cd off of usb. I used unetbootin to put CentOS on my 8gb usb drive after downloading the DVD iso. During boot it loads the image and continues until it reaches this point.
>Linux agpgart interface v0.101 (c) Dave Jones >Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
After this it hangs and won't continue. I am using a Compaq evo n800w and the bios is just updated to the latest version.
i have 5.4 installed on a super-micro server motherboard (has two gigabit ether ports). when i boot while its initializing everything it gets to the "starting eth0" and just stays there?
right before it boots up and says press any key for options i press a key and choose "centos (2.6.18-164.el5)" and it boots up fine but when i choose "centos (2,6,18-164.el5xen)" the problem occurs. and that is the default boot option.