I have just completed an upgrade from 5.3 to 5.4 (64bit) Now when the system starts it gets to Staring udev and then hangs for about 2mins before printing "Timeout" and then continuing.
At various stages during the boot process it just stops with no warning and takes a while to restart.
My boot time in 5.3 was about 50seconds, now with 5.4 it is about 4mins.
My issue is: I am "locked" on kernel 2.6.18-164, I just can't get my server up and running with any later release. It simply hangs at "Starting udev".
The hardware is:
MB: Asus M2N32-Deluxe
CPU: AMD Phenom(tm) II X4 920 Processor
Boot FS: Ext2
RootFS: xfs
RAM: 4Gb
I have 2.6.18-194.el5 running on other machines.
PS: I'm about to install/update a fresh 5.5 disc for testing purpose anyway. I'll update here if it works.
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..
[Code]...
I've been having problems with start_udev on my machine post kernel 2.6.18-162 on my CentOS machine. A previous install would work on the old kernelut not the newer ones. I recently did a completely fresh install of CentOS 5.5o see if maybe there was a orruption in my install when it upgraded,t I still have the problem of udev hanging on startup.Using the rescue option on the disk, I've managed to track the problem down to the 50-udev.rules file. Through trial and error, I moved all the .rules files out of the rules.d directory, and added them back one at a time to see which one(s) caused the system to hang, and which ones it carried on booting as normal with. The only one that causes it to hang is the 50-udev.rules.
From what I can tell, this rules file is responsible for letting udev check various pieces of hardware. I think that it is failing whent runs modprobe on a pci device address.Only problem is I don't understand the rules file syntax, so I don't know if I can simply comment out or change a line in this file to skip the device that its looking for.Can anybody help me track down the specific device/line that is doing this?(I've kept the file out of the folder for now and my system appears to continue operating, but I get the occasional problem that for all I know could be due to udev not having a complete start up).
on bootime the system hangs till pressed <alt><esc> a couple of times. The splash image is shown and the bright spot nearly full. The network and disk led's are off. System is hanging.After <alt><esc> ing a couple of times the leds blink,, the system comes up and the gnome login screen appears. The same behaviour ( exept of the gnome login screen )if starting with runlevel 3.Press 'I' to enter interactive startup.udev starten: %G[60G[[0;32m OK [0;39m] Is it possible that the udev error is responsible for the stattup - hang?
View 6 Replies View RelatedI am trying to set up a usb weather station (WMR100) on my SUSE 11.1 system. It appears as /dev/hiddev0 (and /dev/hidraw0) when it is plugged in with:
crw-rw---- 1 root root ...
It is the only hiddev device that appears in /dev
I have added this to /etc/udev/rules.d code...
(I will add idVendor/Product values later)
The above successfully sets the access codes for hiddev0 when examined from command line (crw-rw-rw- ...). However, the file browser is fine until I look at the properties for /dev/hiddev0 when it hangs - showing nothing.
Can anyone shed light on this - especially as to if I have done something wrong or this might be a 'bug'
Boot from DVD 11.4 586 32 bit is fine. Loads up and offers me install, boot from HD, check media, firmware etc. Select text output, no acpi, check media. Linux kernel loads, then black screen showing progress in white text.
At "Starting udev..." process hangs. Eventually (several minutes later) message is returned about "worker" not able to read from "sr0" which I believe is the DVD drive which it has been using to this point.
I'm running 11.3 normally, udev is not a problem on boot from HD. The DVD media works fine on a Windows laptop showing "Starting udev... ok" and continues. Media checks ok on this machine.
I'm thinking that no matter what medium I use to install from, HD, DVD, net etc this udev problem is going to hit me again unless there is a hint I can pass to the bootup process.
After reading about other experiences with this issue I removed all the non-standard hardware and no difference. The DVD drive seems to be the issue. Bootup is already using it, and yet udev cannot find it.
Upgraded dual boot XP / Ubuntu 2.6.31-22 (still works) to 2.6.32-22, which hangs on boot. "2.6.32-22 recovery mode"(and "continue" dies at "Checking battery state". Ctrl Alt F3 gets a prompt and the login works.
The machine is a Thinkpad g40, which has worked on 9.10, except for wireless distance issues (the G40 has the Atheros AR5211, which seems to be a problem, at least per the forums, and my distance limits experience)
I get the same mount and chroot messages, followed by scrolling msgs, and then a blank screen on attempting to boot 2.6.32-22. And, as indicated, 2.6.31-22 boots and the apps I checked work fine. On the upgrade, there were several msgs about non supported apps and a grub question, which I (naively) answered as use the package version (and was somewhat surprised when dual boot still worked - but impressed and happy
I cloned my hard drive prior to the upgrade, so can revert to 9.10, but would like to run 10.04 LTS. Any suggestions. or should I wait for a while to upgrade?
After yesterdays upgrade of Squeeze, my Synaptics touchpad's udev configuration is ignored on my EeePC. It was working fine before. Are there any changes in how it is supposed to be configured or is it just broken?
View 3 Replies View RelatedI've done an upgrade from lenny to squeeze.Now, I'm getting a lot of udev warning messages at the boot time.Knows someone howto remove them?
View 6 Replies View RelatedI'll say up front I'm still new to Ubuntu, so if I've missed anything obvious please forgive me. I chose to upgrade my 9.10 installation to 10.04 via the update manager. Especially since I was going to be gone for long periods of time, this seemed like a good idea.
Downloading went fine, but I had to leave for a two day trip once I clicked install. When I returned, I noticed the machine was still on the purple loading screen with four dots. When I shut it down and rebooted, it got to the same screen. Pressing escape to show the text behind the screen showed two fails and one oddity:
(1) Setting sensors limits "Rather than invoking init scirpts through /etc/init.d, use the service( utility, e.g. service S49console-setup start
Since the script you are attempting to invoke has been converted to an upstart job, you may also use the start( utility, e.g. start S49console-setup start: Unkown job: S49consile-setup"
(2) Starting VirtualBox kernel modules No suitable module for running kernels found
[Code]...
Debian testing: Kernel: Linux 2.6.32-5-amd64I can now only boot into safemode because I cannot get these 4 packages to upgrade:
udev
media-player-info
xserver-xorg-core
[code]....
Seems that my kernel was the problem then I update it manually but I want a update in Kernel, but keep in boot my current kernel and add the update kernel on boot, how to? The X, mouse and other freeze but audio still running along with crtl+alt+f2:[URL].. Jay Ashworth 2010-09-05 04:03:09 UTC
"2) Flashplayer in fullscreen freezes X; the audio from the video keeps playing continuously, not in a loop, but the video freezes, and (in some cases) the user can switch to a text console--possibly only once--and kill X without having to reboot. This latter description is pretty clearly the actual bug here on 620157, and if you read all 4 descriptions, you can see that the other three are *not* this particular failing."
I have Cent OS 5.1
I also have http://phpsysinfo.sourceforge.net/
I have asterisk running .
Now when I look at System Information ,
I see that "Physical Memory" keep increasing and at one point it reaches 96%. Then my sever get hang and then I have to restart it.
I have 4 GB RAM.
Processors 2
Model Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz
CPU Speed 2.53 GHz
Cache Size 3.00 MB
System Bogomips 10135.71
Kernel Version 2.6.18-53.el5 (SMP)
Distro Name CentOS release 5 (Final)
Load Averages 0.27 0.35 0.31
What could be the reason ?
I'm trying to arrange my 4 NIC's on CentOS 5. Two of them are build-in motherboard nic's and the others are PCI-E Dual Intel card. I'm wondering if someone succeed with udev renaming rule based on BUS location like ID=="0000:03:00.0" ... etc
View 4 Replies View RelatedI'm trying to install CentOS 5.4-x86 on a "new" motherboard, it's an ABIT Fatal1ty AN9 32X. I have a AMD 6000+ Dual Core running stable at 3.01 ghz. 4GB of ram(4x 1GB). nVidia GeForce 7600. 2x SATA II 160GB WD RAID 0 and 2x SATA II 1TB Seagate RAID 0. This setup has been running fine as a FTP server for months and has been flawless for games for about 3 years.Right off the bat during initial install it hangs before loading any GUI.Last lines:
NFORCE-MCP55: IDE controller PCI slot 0000:00:0c.0
NFORCE-MCP55: chipset revision 161
NFORCE-MCP55: not 100% native mode: will probe irqs later
[code]....
I'm running into what is quite possibly one of the strangest problems I've ever encountered. We recently had a power loss, and some of our vmware instances didn't shut down correctly. Once of those is our Zabbix testing monitor. From that point on, whenever I run the "ll" command, my terminal freezes. This happens over both ssh and the local console. I've forced a disk check via the "shutdown -rF now" command, and it returned no errors. Since ll is simply an alias for ls, I copied ls (and the entire bin directory) from another Centos 5.3 instance, with no change in behavior.
View 4 Replies View RelatedKeyboard Hanging, in CentOS. Some time when I login to Linux or when we come back to use Keyboard after a long time work with mouse, my keyboard will hang for few seconds. I don't know its my USB keyboard problem or another issue. I doubt it started after I install opera browser in CentOS or by VNC setup.
View 3 Replies View RelatedI'm trying to disable TCP Segmentation offloading across the board in our datacenter to improve performance. Reading the history in the CentOS Bugzilla and the upstream's Bugzilla, they recommend doing this within the udev rules. See:[URL].. So, I created a new udev rules file that looks like this, as filename /etc/udev/rules.d/50-eth_tso.rules:
ACTION=="add", SUBSYSTEM=="net", NAME=="eth0", RUN+="/sbin/ethtool -K eth0 tso off"
ACTION=="add", SUBSYSTEM=="net", NAME=="eth1", RUN+="/sbin/ethtool -K eth1 tso off"
[Code]...
Can anyone out there figure out just what I'm doing wrong - I've been struggling with this for about 2 hours trying to make it work, and simply can not figure it out - and would like to not resort to hacking the problem and adding the ethtool commands to /etc/rc.d/rc.local!
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.
View 2 Replies View RelatedI haven't updated my centos box for almost about a year, my theory is if it ain't broke don't fix it.These last two weeks I've been replacing hardware, a motherboard, memory, processor, and a hard-disk. Everything worked fine with the current 2.6.18-128.1.10, but I decided that I should upgrade to the latest along with all the new packages. But in doing so I would need to recompile the driver module for the raid controllers, rr1740. So I recompiled them using the 2.6.18-164.1 build while I was in kernel 128. When I was done, I restarted the machine and when it booted to the new 164 kernel, it came back very long error messages but here's what I can remember off the top of my head.
View 14 Replies View RelatedI'm running V5.3 (newly installed) on an FJ E8020 laptop. The problem I have is when shutting down (*not* rebooting). NetworkManager fails to stop and after (during?) the postfix shutdown, the system seems to hang.I cannot access via another screen or remotely. I can't find any clues in the log files.
[Code]...
I have an annoying problem with a 2 nodes cluster that I don't understand.
One of my server is totally shutdown.
When I start cman after a reboot on the other server, it hangs on "Starting fencing...". The process which is actually hanging is : /sbin/fence_tool -w -t 300 -m 45 join
When I start this program manually, I get this output :
# /sbin/fence_tool -w -t 300 -m 45 join
Waiting for all 2 nodes to be members
Waiting for all 2 nodes to be members
Waiting for all 2 nodes to be members
Waiting for all 2 nodes to be members
(and so on...)
What I don't understand is why the fence_tool program wait for the 2nd node to join the cluster and don't fence the other node.
Here is my cluster.conf :
<?xml version="1.0"?>
<cluster name="ctpsrv-bdd" config_version="7">
<fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="20"/>
<cman expected_votes="1" two_node="1"/>
[Code]....
Would it be a good idea to edit the cman startup script and remove the "-w" option of command fence_tool join, so the command do not hang up ?
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.
for a x problem I reinstall the complete x packages. I remove some packages with force.Before this yum works perfect. Exact at this time we have problem with our internet connections and yum hangs somewhere when yum load the repositories and or start the update process.Now yum hangs at start from the command. I can start yum some times and no locking error is rise.strace brings:
stat("/var/lib/rpm/Packages", {st_mode=S_IFREG|0644, st_size=79855616, ...}) = 0
open("/var/lib/rpm/Packages", O_RDONLY) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
[code]....
I am running Centos 5.5 with all the GUI stuff, including nx server and webmin.Sometimes while watching the bootup messages because my eyesight is very poor.I hit <ctrl s> to pause the output so I can read some details. If I do this late in the init sequence - it often briefly stops the output then the screen disappears under a blue wash (presumably something to do with the GUI login screen ot screensaver??)but the login screen never appears. Also it seems that the script never completes because the imap, webmin and http servers don't appear to have started.
I haven't found any satisfactory way out of it. I can't get back to a console terminal (I've tried ctrl c, d, z, etc.). As luck would have it the nx server has started so I can open an nx session. If I open a terminal in an nx session as root.I can't do a normal restart (shutdown -r now). Nothing happens presumably it can't run the init script because it is still running.The only way I have found to get the system back to life is to run "shutdown -r -n now" in the nx terminal session.There are probably better ways out of this predicament that I am unaware of. Otherwise it is probably somewhere between an annoyance and a bug. I would be interested in any advice the centos "board" may have as to whether this is worth raising as a redhat bug.
I recently bought a Toshiba Portege M200 tablet PC and it's caused me no end of grief to load linux on it. I would like to load CentOS 5.x (because my hosting company uses it and I will be able to learn as I run it).
Here are my resources:
I found internet resources to create a boot disk that enables me to see my 8GB Sony USB flash drive via DOS. It works nicely.
I have a laptop drive to USB converter and can access the hard drive directly from my Win XP desktop. I have PowerQuest's Partition Magic Pro (v8.0) and can make Ext2 and Ext3 partitions at will. I have also loaded a program that allows Windows XP to read and write from Ext2 and Ext3. It works well.
I have tried loading boot images from PXE. This option is mostly out because it seems to be a couple levels past my competency (I haven't been able to get it to work).
Given those resources, what's the best way to load either the CentOS live CD... or some other approach?
Since I wrote this, I figured out how to make a boot floppy that can start an external USB CD-ROM/DVD drive. Here are the files on the floppy:
Here's the contents of my config.sys:
Here's the contents of my autoexec.com:
I can boot to the CD and launch linld.com. The problem is that I keep getting a kernal panic message, saying that a memory block could not be addressed. And when I add the following part to the line above: "initrd=d:isolinuxinitrd.img" the install fails and reboots. I have tried to expand the initrd.img and it appears... blank?
I just finished installing CentOS 5.2 x86_64 on a Dell Dimension 3100 (Pentium 4 with 64-bit support). On the first boot, after completing the final config steps (firewall, SELinux, time server, etc), the boot hangs on "Starting xend:". I have completed a successful installation on another Dell machine (different processor), with the same installation options (I recorded all of the steps and followed them for the second installation).
My boot commands in grub are:
root (hd0,0)
kernel /xen.gz-2.6.18-128.el5
module /vmlinuz-2.6.18-128.el5xen ro root=LABEL=/1 rhgb quiet
module /initrd-2.6.18-128.el5xen.img
This is probably not possible, but just wondering, restarted centos 5.2 remotely, hung at shutdown, kvm'ed to see what was hanging it up, control c'ed and then ctl alt del, just trying to kill the process, was brought back to the login screen, but unable to type anything. Alt-f1 switched to a different virtual console, which was just a blank screen and a blinking cursor, but now able to type things. Want to avoid hard shutdown. Is there anyway to force shutdown/reboot the machine from this console?
View 1 Replies View RelatedI recently added an external hard drive through a IEEE 1394 interface. I'm finding that during large file transfers the system slows to a crawl. It's still running: routing for example seems fine. But running applications are pretty much unusable: Apache is unusably slow, SSH login is very slow, etc. Currently I'm using the IEEE 1394 drivers from Axel's ATRpms but I'm pretty sure I saw this with the default kernel IEEE 1394 drivers too.
View 4 Replies View Related