Discuss June 2008

discuss@lists.centos.org

353 participants
415 discussions

Reg. VNC server and Windows and Centos interworking
by Padmaja 13 Jul '08

13 Jul '08

Hi all, I have a Windows XP PC and a Centos PC (Centos 4.3 release, kernel- 2.6.9-34.EL) which are in the same LAN. Currently, I am able to use VNC server on the centos to view the Windows PC, but not able to view the Centos PC from the Windows PC. This applies for even file sharing also. The samba server is running and I can view the windows network from Centos PC but in the Windows network, not able to view the Centos PC. Also not able to print from Centos to the LAN printer. Any help is greatly appreciated. Thank You, Padmaja

7 10

NFS options on kernel parameters
by vincenzo romero 13 Jul '08

13 Jul '08

Hello, I am running an NFS server/PXE on a Cent OS 5.1 server. I have defined an NFS export with "no_root_squash" option in my /etc/exports file: # # NFS Export Files # /export/images *(rw,sync,no_root_squash) ... A client PXE boots as a diskless station to the above server into a root-NFS directory underneath the above /export/images export. When the client boots; the NFS export is NOT root-Squashing - whenever I touch a file, it is created as user nobody and NOT root. I would like to NFS root-squash the root directory. I believe that I am missing to pass a parameter in my kernel - (defined in .. /pxelinux.cfg/default) .. currently my kernel parameters are: APPEND root=/dev/nfs rw nfsroot=192.1.2.5:/export/images/root-fs ip=dhcp ... would anyone be kind to provide advise on how I can mount my client so that I am ensure that the "no_root_squash" setting is enabled? thanks in advace. -- best, Vince

3 3

CentOS 5.2 kernel [2.6.18-92.1.1.el5] crashes on dual-PIII Compaq ProLiant 3000
by Wojtek Pilorz 10 Jul '08

10 Jul '08

After yum upgrade, the new CentOS5 kernel [ kernel-2.6.18-92.1.1.el5.i686 ] crashes each time early in boot process on Compaq ProLiant 3000 with dual Pentium3 CPU (600 MHz, CPU0: Intel Pentium III (Katmai) stepping 03, CPU1 the same). I get kernel panic at powernowk8_init+0x05e/0x1c3. The previous kernel [ kernel-2.6.18-53.1.21.el5.i686 ] seems to work fine. I am wondering if anyone has met this on PIII CPU ? I have found 99.9% identical problem on http://www.nabble.com/net-5501-and-RHEL5.2-td18024549.html (only esp and task slightly different from what I have seen on screen after crash, all other registers, call trace, code bytes identical to my case) , but that was on a different CPU. On the other hand, I run CentOS upgraded to 5.2 on a home PC with PIII (single CPU, Abit motherboard with i440BX chipset) with no problem. Is it normal, that powernowk8_init gets called on PIII CPU? Best regards, Wojtek

13 18

Problems with some rpms in my local repo
by Robert Moskowitz 09 Jul '08

09 Jul '08

This is perplexing. on a Centos 5.1 box that I am trying to upgrade, I keep getting: [Errno 4] IOError: <urlopen error unknown url type: media> from my local repo. I did a blank system install via http from this server with no problem. For instance, if I limit myself to: yum upgrade yum I get: Loading "priorities" plugin Loading "installonlyn" plugin Setting up Upgrade Process Setting up repositories Reading repository metadata in from local files 0 packages excluded due to repository priority protections Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package yum.noarch 0:3.2.8-9.el5.centos.2.1 set to be updated --> Running transaction check --> Processing Dependency: yum-metadata-parser >= 1.1.0 for package: yum --> Processing Dependency: yum-fastestmirror for package: yum --> Processing Dependency: python-iniparse for package: yum --> Processing Dependency: yum = 3.0.5-1.el5.centos.5 for package: yum-updatesd --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Downloading header for yum-metadata-parser to pack into transaction set. media://1213888991.267240%231/CentOS/yum-metadata-parser-1.1.2-2.el5.i386.rpm: [Errno 4] IOError: <urlopen error unknown url type: media> Trying other mirror. Error: failed to retrieve CentOS/yum-metadata-parser-1.1.2-2.el5.i386.rpm from base error was [Errno 4] IOError: <urlopen error unknown url type: media> Yet on the system I built, yum-metadata-parser-1.1.2-2.el5.i386.rpm is there, and I have done a yum update on that system already (how I learned there are bunches of updates out there). I suggestions on how to troubleshoot this? BTW, I did a yum upgrade kernel* and that worked fine. I was going to try to upgrade piece-by-piece, as this is a slow box.

10 19

Root-filesystem remounts as read-only during 5.2 upgrade (system completely shoot)
by Bernhard Gschaider 04 Jul '08

04 Jul '08

Judging from the frequency of my messages here one could think that I'm too stupid to upgrade a workstation to 5.2 (but the servers I've tried work without problem) OK. The problem: I've tried to upgrade a 5.1-x86_64-workstation to 5.2. During the upgrade immidiatly after (according to the /var/log/messages) upgrading the two (64 & 32-bit) libgcc-packages an EXT3-error occurs and the root-partition gets remounted in read-only-mode. Consequently ALL following package upgrades throw errors saying this or that can't be done because he can't write to /etc, /usr but in the end yum says everything is OK. (Side info: /var is on a different partition, so it is still writeable) At reboot the machine wants a manual fsck which throws a lot of errors. Then the machine reboots with with a lot of error messages (basically because it can't find /lib64/libgcc_s.so.1 (nothing a symlink can't fix). After that I try to fix things by manually upgrading the libgcc-packages (otherwise yum won'T run). "rpm -q" for selected packages shows that the majority of the packages is still in 5.1-state. Trying to "yum upgrade" again fail because the machine can't find any servers (but network functionality seems OK) So I try to reboot. And now the really strange thing happens: A simple "rpm -q rpm" says that no rpm is installed. Rebuilding the rpm-database doesn't help. So I'm a bit stuck here with a machine that is in limbo. My questions: what could have been the cause for this (the machine was working OK before that). The only thing I feel a little guilty about was deinstalling the nvidia-kernel-driver and not reboot, but this can't f### up the file-system, can it? Any suggestions what I can do to get the machine into a normal state again (apart from reinstall from scratch)

5 10

FF3 printing problem on Centos 4.x
by fred smith 03 Jul '08

03 Jul '08

I'm using Centos 4.x (fully up to date) on a system at work. I have also been using firefox 2 (directly from mozilla.org) on it for a long time, and it tends to work just fine. yesterday I installed the new FF3 release. It works fine too, with one exception: The print dialog shows no printers! The print button is greyed out! There actually four or five printers defined on the system, and all other apps find them fine, including FF2. So far no one has replied to my query on the mozillazine forums. Anyone here got any suggestions I can try? Thanks! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ------------------------ ---- Do you not know? Have you not heard? The LORD is the everlasting God, the Creator of the ends of the earth. He will not grow tired or weary, and his understanding no one can fathom. ----------------------------- Isaiah 40:28 (niv) -----------------------------

3 3

INIT 5 and system is gone
by Robert Moskowitz 03 Jul '08

03 Jul '08

I had been running a system on Centos 5.1 at INIT 3. I did the upgrade to Centos 5.2 with the aid of the powernowk8 patch. Previously I would VNC into the unit when I needed to do admin stuff with a GUI. Well I noticed that I was NOT getting GNOME via VNC since the upgrade (worked before just fine with 5.1). So I tried an INIT 5 from the command line (always worked before), but the system seemed to hang. Video was off. I rebooted, went to INITTAB and changed init to 5 and rebooted. Probably a tragic mistake. Now on boot, right after UDEV gets an OK, the screen goes blank and the drive stops turning. I tried booting with the 5.1 kernel, and same behaviour with the system blanking out and all load activity stopping after UDEV loads. So I am quite stuck at this point. Is there an option that I can edit into the kernel command at boot time to init in 3? And then what do I try? If I have to reload Centos, I have to pull the drive, put it into another system, install there, etc. Not my idea of a fun day....

6 11

Recall: CentOS Digest, Vol 41, Issue 29
by Matt Seitz (matseitz) 02 Jul '08

02 Jul '08

Matt Seitz (matseitz) would like to recall the message, "CentOS Digest, Vol 41, Issue 29".

3 2

Rebuild of kernel 2.6.9-67.0.20.EL failure
by John 02 Jul '08

02 Jul '08

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/john/rpmbuild/tmp/kernel-2.6.9-67.0.20.EL-root RPM build errors: In my setup rebuilding the 2.6.9-67.0.15.EL kernel went ok Does anybody knows what I do miss or what is going wrong? For the curios: Why to recompile the kernel? I want to rebuild the kernel because I created a patch to decrease the kernel timer frequency from 1000 to 100 HZ. The CentOS4.6 kernel doesn't have the divider option available in CentOS5.2 This prevent timing problems and high CPU load in VMware ESX.

17 30

Problem with nvidia-drv-x11 when upgrading to CentOS 5.2
by Bernhard Gschaider 02 Jul '08

02 Jul '08

Hi! I know that the nvidia-drv-x11-package is from RPMForge, but I thought I might mention it here. I have a machine with a NVidia-card and because of the ease of use I use the rpmforge-package for that. After upgrading the problem was that during rebooting as soon as the machine hit the RHGB (which implicitly uses that driver) the machine froze. I booted into the old kernel removed rhgb, rebooted. Now the machine froze when starting X. Same procedure: Old Kernel. Remove nvidia-drv-x11. Reboot into the new kernel and reinstall nvidia-drv-x11. After a reboot everything works as it used to. The cause of the problem could have been (sorry, I didn't do any thorough forensic) that the nvidia.ko that was used in the new kernel was a symbolic link from the "weak-updates"-directory into the old kernel "extra"-directory. Is it possible that this only works inside of kernels with the same x in CentOS 5.x ? For the other machines I am upgrading I plan to 1. deinstall nvidia-x11-drv 2. do a regular "yum upgrade" 3. reinstall nvidia-x11-drv after reboot Is there any better way to do it? Bernhard PS: the main purpose of this message is to alert others to this problem, not to get an answer, although that would be nice

6 12

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2008