i am trying to install centos 5.5 x86_64 as a guest OS in vmware server 2.0.2 using netinstall iso. Installation runs fine until the point, when it tries to install selinux-policy-targeted-2.4.6-279.el5.noarch, the whole virtual pc hangs at this.any ideas? i tried to google few things about this, but i have found nothing. this has happened 3 times in row, whole virtual pc always hangs at the same package. i dont have any other problems with vmware, gentoo runs and installs fine in it.i would prefer to do installation using netinstall.iso, it would take a lot of time to download all cds or whole dvd and all i require is a very basic set of packages.
My Dell poweredge server running CentOS 5.4 and booting kernel-2.6.18-164.15.1.el5. All boot processes seem okay and the graphical screens for CentOS operate, but just before the desktop loads the screen goes blank and the arrow/cursor is being circled by small spheres. This remains indefinitely. While the arrow is being circled, here are the results of 'getinfo.sh device'
Quote:==================== BEGIN uname -rmi ==================== 2.6.18-164.15.1.el5 i686 i386 ==================== END uname -rmi ====================
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..
I need to set a new centos on an "old" box : PIV 1.8 1.5Gb
The Centos will run on a 40 Gb PATA Hard Drive set as main drive, The Box runs a another SATA Drive with 2 different windows installations.
The installer first hanged on the loading ata_piix driver screen so I restarted with the irqpoll option to complete the wizard. But I'm now stopped on the last X screen : starting installation process please wait.
I have changed the hard drive, the DVD drive, the Centos DVD, tried with a 5.3 and 5.4 with no success.
I'm attempting to install CentOS 5.3 on my IBM IntelliStation Z Pro 6221/37G, powered by some extra equipments as nVidia NV44 GeForce 6200 video card, MV88SX6041 SATA II Controller, 2x1GB DRAM.
The problem: CentOS 5.3 DVD i386 didn't install, the screen becomes unreadable because of vertical bars just after anaconda start running. Choosing at boot time different "linux resolutions" did not help, as well as the "text mode" still useless because Logical Volumes need to be created/handled and the graphical interface is mandatory.
Same result booting CentOS 5.2 Live CD. This sounds really strange to me. I checked iso images against their md5sum and are ok. Centos 5.3 x86_64 does not boot yet :"Your CPU does not support long mode", evem they are 2 x Xeon 2.8GHz / 512KB
I have a strange issue. The only time I have trouble with yum is when awstats is included in an update. When it is, it always hangs on it when it gets to it. Yum will not complete. I have to cancel out... kill the yum pid and do it again. Tonight I did a yum-complete-transaction to do some unfinished actions - one included the removal of an old awstats - it hung on that.
I'm not sure what's going on with this install, but I started with a fresh install on a 250GB IDE disk, assigning /dev/hda1 to linux, and the rest (/dev/hda2) to swap. when it tries to boot.. I just get GRUB hang. Should I have installed a small FAT32 partition in the first sectors of the disk for the bootloader?
The bios in this machine is very old (Dell 410 precision) and Dell offers no updates, so I suspect this has something to do with how the old bios is trying to boot, but ?? not sure how to fix it. try lilo, or alternate bootloader???? Just looking for a fix to the boot problem. I would prefer to boot from the disk, booting from cd/floppy/pxe not so desirable.
I have a centos 5.5 server which hangs with yum update. i did a yum clean all. removed the rpm en /_.rd een did a rebuild. In the logs there are no errors. If there is another update except these to he works just fine. Disk space is enough free. Any ideas? i am runnung yum update as root . when i do a full report of yum i get this:
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 had a spare computer (Dell Optiplex GX270) which I had installed Centos 5 on and have been setting up asterisk (telephony) on it. My main computer has broken down and I need to load Windows XP back on to the Optiplex.
I put the Windows XP disk in the drive and directed the bios to boot from the cd. I get the message "Please wait while windows inspects your current hardware configuration" and then after about 10 seconds the screen goes blank (the cd also slows down and then stops) and then the systems seems to just hang.
If I take the cd out and boot from the hard drive Centos loads normally; therefore I'm assuming my problem is not a defective hard drive.
I've spent quite a bit of time searching online for a solution and although there seems to be several different situations where the above can occur, I'guessing that my ssues are related to either partions/mbr and or the bios/cmos. I'm really new to Linux and not knowledgable on partitions and cmos so I'm hoping someone could help me out here.
I've checked in the bios and could not find an option to restore the settings to factory defaults. Should I pull the csmos datterry out? Does this restore the bios settings to factory defaults?
With the 5.3 CDS I started an install got through to 98% of CD 3 but I was called away. Came back this morning and the box was on, but had frozen. Every time I reboot, cold boot, I come up with black screen. Vers 0.97 <grub> Minimal BASH-like line editing is supported. TAB etc. Is there a way I can get to CD 4 and continue the install, or am I back to the top again?
I recently installed CentOS 5.3 on a Dell PowerEdge 1800 server that used to have Microsoft Windows SBS 2003 on it. Everything seemed to be going fine until a few days ago. Here's the sum of it all...
- System seems to randomly hang, at which it becomes unavailable on the network (can't be pinged, monitor won't come back on, and you can't wake it up... have to reboot, the scroll lock and caps lock keys flash at the same time) - Received this error message...
Uhhuh. NMI received for unknown reason a0. You probably have a hardware problem with your RAM chips. Dazed and confused, but trying to continue.
...it doesn't crash at this point though. I ran memtest86 twice and did not experience any problems. I updated the BIOS to the newest version, which contained a few bug fixes, but still experienced the same problems
I am facing the following issue. My application runs perfectly in red hat linux(32bit, 64bit physical m/c and 32 bit vmWare m/c) and in one version of centOS(32bit physical m/c - don't remember the version:Sorry). However when I am running the same application in CentOS 5.4 (64bit version) I face the following issues -
a. the application gets stuck in the conditional wait even though the signal is sent after the application has moved to conditional wait. b. vsftpd service start fails from within the application even though the service starts and stops peroperly from console.
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.
I have Centos 5 Installation with following Linux ipmpls.mobilink.net.pk 2.6.18-8.el5xen #1 SMP Fri Jan 26 14:42:21 EST 2007 i686 i686 i386 GNU/Linux. I have Nagios running on it for monitoring switches. It also runs postfix to give email alerts in case of a switch is unreachable. The problem is that the server hangs for a minute and returns to normal operation. During this period if a switch is polled it cannot be reached and hence Nagios shows the Flapping state on the switches. I need to understand as to why the server hangs
I just installed 32-bit CentOS 5.5 in a Vmware virtual machine. I'm unable to install RPMs from either the graphical U/I (Pirut) or CLI (Yum). Pirut stops responding (no screen repainting) after displaying the "Updating software" dialog; Yum gets to the display of "Running Transaction" where it hangs. The initial installation (from the net-install ISO) obviously succeeded, and the after-install update of about 50 packages also worked fine.
yum.log contains nothing past the entries made during the initial install. Because I had a problem with corrupted files from a mirror during installation I tried using the baseurl setting in CentOS-Base.repo instead of mirrorlist, but that had no effect.
Installed latest version of sipXecs (PBX system) which is based on CentOS. The install went fine. During the first boot up all the messages come back with OK until it reachs a message about loopback. It hanges on this message and will go no further.
I am trying to do a kickstart installation of CentOS 5.5 x86 using a static IP on eth1. (The machine has 4 ethernet ports). I set ks, ksdevice, ip, netmask, and noipv6 when the boot disc asks for the init commands.I have similar networking information configured in the kickstart script. I have tried switching the order of the network config lines in the kickstart script to place eth1 at the top. Either way the installation hangs. On tty3 I can see that the command last called is getNetConfig. All of this configuration is using static IPs. I'm not sure why it thinks it has to do anything extra... Is there a problem trying to reuse the same eth1 NIC for the second stage? I have tried using the same and different IPs on the same subnet but nothing changes the outcome. Both the kickstart file and the install tree are on the same subnet, the same server in fact. Both are accessed via FTP but I had this problem with NFS as well.
I built a centralized storage system a year ago (Aug. 2010) and for the past 10 months it has preformed flawlessly. About two months ago (July 2011) I began having problems writing to my centralized storage. The copies (cp -rpv) fail whether they are nfs or samba mounted disks to my centralized storage.
Attempting to copy either frame sequence (.dpx, .tiffs, .targas) or .MOV files now lock up my system and knock my storage offline.
The error that continues to echo back when this happens is :
I have not made any changes or updates to my storage configuration since building it last August 2010. I have reached out to Areca, and they found nothing wrong with the Raid Controller or my Raid settings.
I tried to troubleshoot all the basics - swapped out cables, replaced the WD storage disks, changed switches still the problem persists.
If anyone else has experienced this issue please let me know what you did to fix it. I can also post any error logs or message logs if that would be of assistance.
Using the EPEL Repository, I went in and installed Cobbler to my DHCP/Gateway box.Everything went smoothly on the installation front. I went ahead and modified the cobbler settings file (/etc/cobbler/settings) to point to my server IP (same box), and then got tftp running properly. Now here's the problem.Normally, you need to run `cobbler check` to find issues and correct them. I run that, and all I get is blank. Nothing. It just hangs at the prompt until I kill it using CTRL+C.When I CTRL+C from the hanging, it states "cobblerd does not appear to be running/accessible"...
Code: [root@PalaceRedirect ~]# service cobblerd status cobblerd (pid 6991) is running...
most of the time, it will not reboot. I can cycle power, and, eventually, it does boot. So, hardware issue perhaps? Something else?What can I do, or add to the configuration to help debug this and figure out why? For boot options, I have tried noapic, apm=off, noht, nomce, nousb, nousbstorage, and none of those helped. As the machine is remote, to mess with console stuff, I have to get a KVM over IP hooked up, which I can do.
Let me start off with the usual: I'm a linux newbie but am doing pretty good so far with google by my side. I've come across a problem I cant seem to find an answer to:
I just got a CyberPower 685 AVR UPS. I Installed their power panel software and it works great in CentOS 5.4. When I reboot, the system hangs right after the "Red Hat Nash 5.6..... Starting" message. I've left it for 20 mins so far and it's still hanging. If I unplug the USB data/shutdown cable, within about 10 seconds it starts detecting hard drives and continues booting...
Ive even returned the UPS for another to see if it was bad, and it still is giving me problems.
Problem : centos 5.3 hangs while remotely copying data onto this server.
I have A centos 5.3 x86 Version installed on Xeon Quad core , running on 8 GB DDR2 RAM, RAID 1 confgured on SATA drives. this was old installation copy and It has many more things running on it.Therfore, I can't just reinstall it.
I have setup SAMBA PDC + ldap on it. I encounter that system hangs when I copy data into this server from LAN computers.
My troubleshooting steps :
1. I have checked for network issue , My network works fine when I transfer data between other LAN compuers.
2. Even I have tried confguring seprate LAN....
3. I thought their might be some problem with my SAMBA configuration, therefore I did data transfer from sftp .