Discuss

discuss@lists.centos.org

34758 discussions

Failed boot drive
by Dean Maluski 22 May '08

22 May '08

Unclear on how to recover from failed boot drive? SDA has failed but I'm still able to boot. I need to replace primary boot drive. Upon initial build I created a RAID 1 mirror of /boot dir/partition. How do I get system to boot off second or third drive so that I can replace /sda? I've successfully replaced /sdb & sdc raid 5 drives in the past but have always struggled to get primary boot drive replaced. Read HOWTO's in the past but it's been an unsuccessful pain and eventually just did a full rebuild. I just read another HOWTO and as confused as I was several months ago, nothing on getting system to boot from alternate drive.

2 1

question on minimal install using CF as /dev/sda
by Ray Leventhal 22 May '08

22 May '08

Hi all, We're attempting to use CentOS 5.1 on a test platform which uses a CF card as it's primary storage. (MB: ETX-LX) The BIOS supports booting from CD and/or the CF. Issues we've run into are: During installation of CentOS 5.1, it appears all goes well through partitioning, package selection, interface configuration. Once the install starts in earnest, errors pop up...a snippet is: ================ Traceback (most recent call first): File "/usr/lib/python2.4/site-packages/yum/packageSack.py", line 640, in returnNewestByName raise PackageSackError, 'No Package Matching %s' % name File "/usr/lib/python2.4/site-packages/yum/packageSack.py", line 318, in returnNewestByName return bestofeach.returnNewestByName(name) File "/tmp/treedir.29352/instimage/usr/lib/anaconda/yuminstall.py", line 1093, in getBestKernalByArch pkgs= ayum.pkgSack.returnNewestByName(pkgname) File "/tmp/treedir.29352/instimage/usr/lib/anaconda/yuminstall.py", line 1102, in selectBestKernel kpkg = getBestKernalByArch("kernel", self.ayum) File "/tmp/treedir.29352/instimage/usr/lib/anaconda/yuminstall.py", line 1236 in doPostSelection self.selectBestKernel(anaconda) File "/tmp/treedir.29352/instimage/usr/lib/anaconda/backend.py", line 177 in doPostSelection return anaconda.backend.doPostSelection(anaconda) ================== It appears that we're not writing to the CF and a driver is needed. We have the driver, but are uncertain how to pass the information to the installer. No Floppy is present. Any thoughts or suggestions or pointers to resources would be greatly appreciated. Regards, -Ray

1 0

CentOS-announce Digest, Vol 39, Issue 10
by centos-announce-request＠centos.org 22 May '08

22 May '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2008:0275 Important CentOS 5 i386 kernel Update (Karanbir Singh) 2. CESA-2008:0275 Important CentOS 5 x86_64 kernel Update (Karanbir Singh) 3. CEBA-2008:0280 CentOS 5 i386 xen Update (Karanbir Singh) 4. CEBA-2008:0280 CentOS 5 x86_64 xen Update (Karanbir Singh) 5. CESA-2008:0287 Important CentOS 3 i386 libxslt - security update (Tru Huynh) 6. CESA-2008:0287 Important CentOS 3 x86_64 libxslt - security update (Tru Huynh) 7. CESA-2008:0287 Important CentOS 5 i386 libxslt Update (Karanbir Singh) 8. CESA-2008:0287 Important CentOS 5 x86_64 libxslt Update (Karanbir Singh) 9. CESA-2008:0489 Critical CentOS 5 i386 gnutls Update (Karanbir Singh) 10. CESA-2008:0489 Critical CentOS 5 x86_64 gnutls Update (Karanbir Singh) 11. CESA-2008:0287-01: Important CentOS 2 i386 libxslt security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Wed, 21 May 2008 13:48:13 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0275 Important CentOS 5 i386 kernel Update To: centos-announce(a)centos.org Message-ID: <20080521124813.GA3073(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2008:0275 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0275.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: e16e0e18187d9d931228c6e11c2d89bf kernel-2.6.18-53.1.21.el5.i686.rpm 84a3d53a655a9abbaa1bbc9e2a74d007 kernel-debug-2.6.18-53.1.21.el5.i686.rpm 54854a7515043387932785d0ca5a5b37 kernel-debug-devel-2.6.18-53.1.21.el5.i686.rpm cacfe849df6d086fe0df5ba2548e54d2 kernel-devel-2.6.18-53.1.21.el5.i686.rpm bc8dc922d73b61515b0b502b60e5e084 kernel-doc-2.6.18-53.1.21.el5.noarch.rpm 52cc1bf88bc8d423151a6841c2705166 kernel-headers-2.6.18-53.1.21.el5.i386.rpm 5539c13872ad6708ab0377e85d50e372 kernel-PAE-2.6.18-53.1.21.el5.i686.rpm dae280d46074f4d34a4a2386c04aa972 kernel-PAE-devel-2.6.18-53.1.21.el5.i686.rpm 4ab36b9e7adf36ca15b337c1bcb4021d kernel-xen-2.6.18-53.1.21.el5.i686.rpm 3fcf05e0c22b3a6eaaf13bd73554960a kernel-xen-devel-2.6.18-53.1.21.el5.i686.rpm Source: 6db1dbe7a05d80061bd593bfa16b90ea kernel-2.6.18-53.1.21.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 21 May 2008 13:48:13 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0275 Important CentOS 5 x86_64 kernel Update To: centos-announce(a)centos.org Message-ID: <20080521124813.GA3086(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2008:0275 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0275.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 78271de2d69838649627edabf22065a3 kernel-2.6.18-53.1.21.el5.x86_64.rpm 867eea6bf5aad07eb555ebbdaf1ffbd4 kernel-debug-2.6.18-53.1.21.el5.x86_64.rpm c43110331d753e6a8bdd9d92648fb367 kernel-debug-devel-2.6.18-53.1.21.el5.x86_64.rpm 42779778f08052c98118eecbb3952880 kernel-devel-2.6.18-53.1.21.el5.x86_64.rpm 3417b759c192526d881d73af4b12d5d8 kernel-doc-2.6.18-53.1.21.el5.noarch.rpm 9b23032f049ad4aecd77a83cd2b328d4 kernel-headers-2.6.18-53.1.21.el5.x86_64.rpm 51bdb647b793105738ff423845bcc11f kernel-xen-2.6.18-53.1.21.el5.x86_64.rpm 4d8896b2d8495b5f043e298cac809f67 kernel-xen-devel-2.6.18-53.1.21.el5.x86_64.rpm Source: 6db1dbe7a05d80061bd593bfa16b90ea kernel-2.6.18-53.1.21.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 21 May 2008 14:01:45 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEBA-2008:0280 CentOS 5 i386 xen Update To: centos-announce(a)centos.org Message-ID: <20080521130145.GA3738(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2008:0280 Upstream details at : https://rhn.redhat.com/errata/RHBA-2008-0280.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: fe1476d70e4b6587e5b400aa87d98e33 xen-3.0.3-41.el5_1.6.i386.rpm d816b1d9bcd821873c2795fc5653a50d xen-devel-3.0.3-41.el5_1.6.i386.rpm 446c29eeb926276cee3958194e888edb xen-libs-3.0.3-41.el5_1.6.i386.rpm Source: 16062424fe0d1d8f0e60d69c6a1e82ad xen-3.0.3-41.el5_1.6.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Wed, 21 May 2008 14:01:45 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEBA-2008:0280 CentOS 5 x86_64 xen Update To: centos-announce(a)centos.org Message-ID: <20080521130145.GA3752(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2008:0280 Upstream details at : https://rhn.redhat.com/errata/RHBA-2008-0280.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 00aac74a24738e20b60422d7f6095c20 xen-3.0.3-41.el5_1.6.x86_64.rpm 550be917a166ef10df70d94347ad4a4c xen-devel-3.0.3-41.el5_1.6.i386.rpm d11145a16d9781dc33d5368c2e76e317 xen-devel-3.0.3-41.el5_1.6.x86_64.rpm 34a5389dbc59e7feefcd0c1bda13ba79 xen-libs-3.0.3-41.el5_1.6.i386.rpm f9623d0a717a6d1f7fd3d391432d04d7 xen-libs-3.0.3-41.el5_1.6.x86_64.rpm Source: 16062424fe0d1d8f0e60d69c6a1e82ad xen-3.0.3-41.el5_1.6.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Wed, 21 May 2008 15:50:56 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2008:0287 Important CentOS 3 i386 libxslt - security update To: centos-announce(a)centos.org Message-ID: <20080521135056.GA12715(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2008:0287 libxslt security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2008-0287.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/libxslt-1.0.33-6.i386.rpm updates/i386/RPMS/libxslt-devel-1.0.33-6.i386.rpm addons/i386/RPMS/libxslt-python-1.0.33-6.i386.rpm source: updates/SRPMS/libxslt-1.0.33-6.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update libxslt Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

broken GFS
by Doug Tucker 22 May '08

22 May '08

This is the 2nd time this has happened to me. There was a kernel release over the weekend to .67.0.15, yet, they did not release the updated GFS to go along with it, so when the machine rebooted, there was no gfs file system in the new running kernel which in turn wreaked havoc on my cluster. I truly wish they would not do that :). I guess I shall have to not allow automatic yum updates from these machines.

40 110

Maybe OT: Some strange problem with postfix
by carlopmart 22 May '08

22 May '08

Hi all, I have a strange problem with postfix on a CentOS 5.1 (fully patched). Every time that postfix sends a message to public smtp servers generates an autoresponse mail to sender about delay ... Somebody knows how can I fix this?? -- CL Martinez carlopmart {at} gmail {d0t} com

7 12

Need help with rsync.
by James B. Byrne 21 May '08

21 May '08

I have two hosts which have their respective keys loaded into each others .ssh/authorized-keys2 file for root. I want to move a directory tree from one host to the other via rsync to maintain a shadow structure of the application provided on the main host. This is the relevant part of the command: rsync -avz --rsh=ssh --delete-after /var/data/pas-redmine root@inet01.mississauga.harte-lyne.ca:/var/data The connection is made and a good deal of material is successfully transferred. I am however getting a number of permission errors: rsync: readlink "/var/data/pas-redmine/lib/tabular_form_builder.rb" failed: Permission denied (13) rsync: readlink "/var/data/pas-redmine/lib/redmine.rb" failed: Permission denied (13) rsync: readlink "/var/data/pas-redmine/lib/diff.rb" failed: Permission denied (13) and many more: The permissions and owner for these are: -rw-r--r-- 1 pas pas 2341 May 9 13:57 \ /var/data/pas-redmine/lib/tabular_form_builder.rb -rw-r--r-- 1 pas pas 7934 May 9 13:57 \ /var/data/pas-redmine/lib/redmine.rb -rw-r--r-- 1 pas pas 5602 May 9 13:57 \ /var/data/pas-redmine/lib/diff.rb ... The host application directory structure is a checked out svn repository, but some of the files that are giving errors are created locally such as the database dump file. I am at a loss to explain this since the rsync and ssh user, so far as I can tell, is root and this, so far as I understand, should allow unrestricted access to the files regardless of the ownership or permissions. If someone can clue me in as to what I am misapprehending here I would be much appreciative. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 4

service --status-all hangs CentOS-4.6?
by James B. Byrne 21 May '08

21 May '08

Is there a problem with running # service --status-all as root over ssh? A system that I performed this command upon has become non-responsive on all ports, leading me to conclude that it is either hung or the cpu is completely consumed with some task. Regards, Output to point of failure: ... Active Mount Points: -------------------- hcid is stopped sdpd is stopped hidd is stopped cpuspeed is stopped crond (pid 3334) is running... cupsd (pid 3806) is running... cups-config-daemon (pid 3404) is running... dc_client is stopped dc_server is stopped dhcpd is stopped Device not specified in /etc/sysconfig/diskdump Usage: /etc/init.d/dkms_autoinstaller {start|stop} -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Re: [CentOS-announce] CESA-2008:0275 Important CentOS 5 i386 kernel Update
by Ralph Angenendt 21 May '08

21 May '08

Karanbir Singh wrote: > > CentOS Errata and Security Advisory 2008:0275 Important > > Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0275.html This update seems to break IPsec in the kernel, see <http://bugs.centos.org/view.php?id=2853>. Cheers, Ralph

1 0

Re:Can't get past the splash screen
by Eon Strife 21 May '08

21 May '08

Hi, Thanks for the reply. I already checked the the current user logged in the freenx by using "nxserver --list", it's only the root (the one I currently using). And yeah, I'm stuck in this screen : http://img.photobucket.com/albums/v708/EonStrife/stuck.jpg I wonder, just say if we don't use the remote desktop, but we access or use the computer directly/physically as usual, what do we do if we're stuck on that screen ? About the log of the nomachine, I think the most interesting part is the bottomost part. Note, there are many occurences of "NXFileMonitor::readData", and some 'stop' and 'destructor' words in the end, even though the nomachine is still running. === [Wed 21. May 09:48:18 2008]: Setting environment variable 'NX_HANDLEPROXY' to '28077c' [Wed 21. May 09:48:18 2008]: NXService::getWin32DisplayHandler: NX_HANDLEPROXY=28077c [Wed 21. May 09:48:18 2008]: NXService::getWin32DisplayHandler: end [Wed 21. May 09:48:18 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:21 2008]: LoginDialog: Agent found closing windows... [Wed 21. May 09:48:21 2008]: LoginDialog: Slotsingleapplication: setting automatic reconnect to true. [Wed 21. May 09:48:21 2008]: Settings::flush [Wed 21. May 09:48:21 2008]: Settings::flush [Wed 21. May 09:48:21 2008]: LoginDialog: closeEvent received! [Wed 21. May 09:48:21 2008]: LoginDialog::destructor called begin [Wed 21. May 09:48:21 2008]: LoginDialog: stopAllTimers [Wed 21. May 09:48:21 2008]: LoginDialog: stopProgressTimer [Wed 21. May 09:48:21 2008]: Utility::getPreferencesFile: 'nxclient' -> 'C:\Users\Eon Strife/.nx/config/nxclient.cfg' [Wed 21. May 09:48:21 2008]: Settings::flush [Wed 21. May 09:48:21 2008]: Called destructor for protocol class [Wed 21. May 09:48:21 2008]: LoginDialog::destructor called end === Thanks === Eon Strife wrote: > > Hi, > I have a remote frontend (it's kept in the room which I don't have access) which is installed with CentOS 4 and Rocks . So, to use the desktop(Gnome) of the frontend I use the freenx + nomachine following the guide in http://www.centos.org/modules/newbb/viewtopic.php?forum=20&topic_id=1640&vi…. It worked. Then, I intended to add user, but I couldn't create the home folder in /home/ for the new user. After browsing, I found that somebody mentioned it's because of the automounter/autofs. So, I played around, enabled and disabled the autofs, and yes, I could create the home folder for the new user. The problem is that, when I tried to log-in to the front end using nomachine (using root) again, I could only get as far as the splash screen of the CentOS. I tried to connect using the putty (terminal), and I could interact (issuing command to the terminal), but I couldn't use the Gnome anymore. So, why in the nomachine I could not pass the splash > screen anymore ? Any solution ? Thanks. Although I can not answer your question directly, did you see anything logged on the system that you are connecting to via the nomachine client? Also, the Nomachine client provides some logging of its own as well. You may want to check for any error or permissions related information in the client's directory. That may point you in the right direction. Sincerely, Alex White -- ethericalzen at gmail.com Life is a prison, death is a release=== Send instant messages to your online friends http://uk.messenger.yahoo.com

2 1

Show IP Traffic on a port
by Joseph L. Casale 21 May '08

21 May '08

I am trying to determine the root of an issue I am having. How can I watch traffic destined to a specific port on my CentOS 5.1 box to see if its even hitting it? It would be udp traffic. Thanks! jlc

5 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss