Discuss

discuss@lists.centos.org

34753 discussions

Re: [CentOS] "multi-boot" drive partitioning
by Brent L. Bates 18 Dec '07

18 Dec '07

One good thing about a spare UNPLUGGED machine is in case of a lightning strike. We had a customer site get hit by or near by lighting. The unplugged spare wasn't connect in any way shape or form to anything. No power cord, no network connections, nothing. After the strike, they were having problems with their industrial systems and blamed it on the computers we installed. We took the spare system that wasn't plugged into anything, started it up, and things still didn't work. This proved that our system wasn't the problem. It turned out to be their hardware that didn't have adequate surge protection. -- Brent L. Bates (UNIX Sys. Admin.) M.S. 912 Phone:(757) 865-1400, x204 NASA Langley Research Center FAX:(757) 865-8177 Hampton, Virginia 23681-0001 Email: B.L.BATES(a)larc.nasa.gov http://www.vigyan.com/~blbates/

1 0

OpenLDAP auth problems
by юрка олейников 18 Dec '07

18 Dec '07

i have CentOS 4.5 with OpenLDAP 2.2.13. OpenLDAP contains users with SSHA-ed and CRYPT-ed passwords. the one and ugly thing is that users with CRYPT-ed passwords cannot bind to this LDAP server. however users with SSHA passwords do can. is there any solution without recompiling anyhting? -- Be Secure, Stay Open - live w/ OpenBSD

2 1

./configure perfparse -> "configure: error: required library libgd unusable"
by Rogelio 17 Dec '07

17 Dec '07

I recently had a problem with the configure script from perfparse running properly so that I could 'make install' it to work with Nagios 2.10 on latest CentOS 4.x + RPMForge (see http://readlist.com/lists/centos.org/centos/5/28966.html) Thinking it was a problem that was a result of "yum remove gd", I formatted the box and reinstalled everything. Now, oddly, I still have the same problem, and unlike before (before running "yum remove gd"), I cannot configure it without getting the following error: *************************************************** *************************************************** "checking for gdlib-config... /usr/bin/gdlib-config checking for gdMalloc in -lgd... no configure: error: required library libgd unusable. Install required and dependent files and rerun configure. See config.log or FAQs for details." *************************************************** *************************************************** The part of the config.log which looks relevant to the problem is the following: *************************************************** *************************************************** | /* Override any gcc2 internal prototype to avoid an error. */ | #ifdef __cplusplus | extern "C" | #endif | /* We use char because int might match the return type of a gcc2 | builtin and then its argument prototype would still apply. */ | char gdMalloc (); | int | main () | { | gdMalloc (); | ; | return 0; | } configure:26962: result: no configure:26974: error: required library libgd unusable. Install required and dependent files and rerun configure. See config.log or FAQs for details. *************************************************** *************************************************** and in the configure script, this pertains to the error as well *************************************************** *************************************************** LIBS="-lgd $LIBS" else { { echo "$as_me:$LINENO: error: required library libgd unusable. Install required and dependent files and rerun configure. See config.log or FAQs for details." >&5 echo "$as_me: error: required library libgd unusable. Install required and dependent files and rerun configure. See config.log or FAQs for details." >&2;} { (exit 1); exit 1; }; } fi *************************************************** *************************************************** Any suggestions? This was working (in that I could ./configure, just not "make && make install") before I removed gd, and once I formatted and reinstalled everything fresh, none of it works. Any help in the right direction would be greatly appreciated.

4 21

What is the REAL version of Xen in 5.1?
by Ross S. W. Walker 17 Dec '07

17 Dec '07

I have a 5.1 system with Xen installed. The package says 3.0.3, but an 'xm info' shows 3.1. So what is it? Is it 3.0.3 patched to 3.1 or is it 3.1 packaged as 3.0.3? And if it's the former, does anybody have any idea why upstream wouldn't just deploy 3.1 (now 3.1.2) which is more stable? -Ross ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

2 2

Instalation with a customized kernel
by Jerome 17 Dec '07

17 Dec '07

Hi all I don't know if it's the right place to ask for this problem. I just install my server with centos4.5, using PXE/http protocol. ALl goes very well. My asking is that i need a customized kernel to use all of the posibilities of my server. This kernel, made as an rpm file, run well on it. But i would like to be able to install the server directly with this kernel, using PXE/http.. As for any reason, i can have in 10 minutes a new fresh server ready installed. Someone can say me where to search? Thank's a lot. Best regards. -- -- Jérôme La télévision est faite pour ceux qui, n'ayant rien à dire, tiennent absolument à le faire savoir. (Pierre Dac)

2 1

problems with CentOS chroot
by Maxim Soldatov 17 Dec '07

17 Dec '07

Hello, I've got strange problem with centos (as well as rhel btw) chrooted environment. First of all I created simple directory with only the libs for 'bash' and 'id' tools: ---- # chroot testcase/ bash-3.1# id uid=0 gid=0 groups=0,1,2,3,4,6,10 ---- Yes, I even do not have /etc/ directory inside testcase/ , but id shows groups from the _host_ root account. I tried to create full chroot with all the libs and tools based on debian testing, but the same result: # id uid=0 gid=0 groups=0,1,2,3,4,6,10 but if I do # ls /etc/shadow /etc/passwd /etc/group /etc/group /etc/passwd /etc/shadow then # id uid=0(root) gid=0(root) groups=0(root),1(daemon),2(bin),3(sys),4(adm),6(disk),10(uucp) Args, quite strange for me. I tried to use strace to identify where is the problem, and only one thing I found is 530 error on read() : [cut] open("/etc/group", O_RDONLY|0x80000) = -530 getgroups32(0, NULL) = 7 getgroups32(7, [0, 1, 2, 3, 4, 6, 10]) = 7 open("/etc/group", O_RDONLY|0x80000) = -530 open("/etc/group", O_RDONLY|0x80000) = -530 open("/etc/group", O_RDONLY|0x80000) = -530 open("/etc/group", O_RDONLY|0x80000) = -530 open("/etc/group", O_RDONLY|0x80000) = -530 open("/etc/group", O_RDONLY|0x80000) = -530 open("/etc/group", O_RDONLY|0x80000) = -530 write(1, "uid=0 gid=0 groups=0,1,2,3,4,6,1"..., 34) = 34 [cut] 530 is EIOCBRETRY according to errno.h, but, honestly, I do not know what does it mean and what I can do with it. SElinux - disabled via /etc/selinux/config. CentOS release 4.4 (Final) с ядром 2.6.9-67.ELsmp. as well as Red Hat Enterprise Linux Server release 5.1 (Tikanga) 2.6.18-53.1.4.el5 Could anyone please explain what is going on and what have I done wrong? Thanks a lot for your time and sorry for my english. -- Maxim Soldatov

2 2

Re: [CentOS] Expandable network storage
by Ross S. W. Walker 17 Dec '07

17 Dec '07

No it probably would not provide the performance unless run on 10 Gbe. Of course that depends on the number of write transactions, 1Gbe maxs around 100MB/s, so if you need faster performance look elsewhere. I doubt it's reliability too, nbd is a simple protocol, but as such doesn't provide for error recovery. Best bet, build performance storage with redundancy on 1 server, then if budget allows duplicate it on another and use something like drbd to replicate it (synchronous if network speed allows, asynchronous otherwise) for high availability. -Ross -----Original Message----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Mon Dec 17 04:56:57 2007 Subject: RE: [CentOS] Expandable network storage Hi all, I'm currently thinking about similar configurations, and (also for cost reasons :-) am also thinking about GNBD with two standard servers as a "poor man" redundant storage - but I'm wondering if that gives enough performance for running databases (in my case Oracle) on top of it. The configuration I'm thinking about would be two current Dell servers with hardware RAID 10 and connected by a dedicated 1 GBit crossover-cable, running both the cluster software and Oracle. Does anyone use this in "real-World" scenarios and has some practical experience with it? Best regards, __ /homas -- Thomas Bleier, DI Information Management Austrian Research Centers GmbH - ARC HG Wien - FN 115980i - ATU14703506 2444 Seibersdorf, Austria Mobile: +43 (664) 8251279 E-Mail: thomas.bleier(a)arcs.ac.at -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Steve Campbell Sent: Friday, December 14, 2007 8:52 PM To: centos(a)centos.org Subject: [CentOS] Expandable network storage I want to thank everyone who has provided insight into my thread about clustering MySql. I kind of just sat back and watched it develop. I learned a lot from it all. I have been reading all of the documentation on clustering provided by Centos/Red Hat, and find I travel in circles. I read one chapter and answer a self-imposed question but I end up asking myself another. What I really want to do is have HA for any service I run (which is mostly HTTP, MySQL, FTP, and the common things like that). I want to run that to redundant storage somewhere that is real easy to expand by just adding more hardware (server or disk drive). I started exploring this by using the Cluster Suite as a base and then looked into each aspect of the cluster and invariably got stuck on the storage side of this. I see how I can maybe set this up originally, but the expansion just doesn't seem to be there. I don't really want to go the route of Fibre channels and ISCSI, and would prefer to use common hardware (which sort of suggests GNBD). If anyone cares to offer suggestions, with a pretty clear explanation trail (thanks Ken Price for your link to a step-by-step), I would really like to see it, as I'm not getting anywhere with the documentation. I hope to get some hardware to play with shortly, and maybe that'll make things clearer. I'm sure it one of those deals where once I get it done, it'll be so obvious. I just need a little kickstart to help me get there. Thanks, Steve Campbell _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

1 0

Qlogic HBA scanning issues with CentOS 5.1 ?
by Finnur Örn Guðmundsson 17 Dec '07

17 Dec '07

Hi, I got few servers (IBM HS20,HS21 blades, IBM xSeries 3650 & others) connected to a dual fabric san throught Qlogic HBA's (23xx, 24xx). Multipathing is done with device-mapper-multipath. On CentOS 4.x i can scan for new scsi devices without any problems, get them up with multipathing & use them without any problems. However, after i started installing CentOS 5.1 (did not notice this problem with CentOS 5) i cannot seem to rescan without huge problems. Sometimes when i rescan after presenting a new LUN to the server nothing is detected, and sometimes the device comes in without any problems at all. Sometimes i even loose some paths after rescanning.....again, i had no problems at all with CentOS 4.x. I use the Qlogic script (Dynamic Target and LUN Discovery <http://support.qlogic.com/support/EULATemplate/Template.aspx?TemplateID=9&p…> 2.2) to scan for new luns. Has anyone had any issues with scanning for new devices off san after upgrading to 5.1 ? Thanks, Finnur

3 4

Re: [CentOS] Bonding problem in CENTOS4
by Ross S. W. Walker 17 Dec '07

17 Dec '07

Try setting a manual MAC address on the bond interface that is different then any of the physical ones. -Ross -----Original Message----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: centos(a)centos.org <centos(a)centos.org> Sent: Mon Dec 17 07:44:21 2007 Subject: [CentOS] Bonding problem in CENTOS4 I use bonding under CENTOS4.5 x32_62. I have these weird messages when I'm restarting network. Do you have any ideas how to fix this? (there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but the author says that it worked for him in centos4...) Thanks Vitaly Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts. Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth0 Dec 17 08:34:21 3_10 kernel: bonding: bond0: making interface eth1 the new active one. Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth1 Dec 17 08:34:21 3_10 network: Shutting down interface bond0: succeeded Dec 17 08:34:21 3_10 network: Shutting down interface eth2: succeeded ........ Dec 17 08:35:16 3_10 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready Dec 17 08:35:20 3_10 ifup: Enslaving eth0 to bond0 Dec 17 08:35:20 3_10 kernel: bnx2: eth0: using MSI Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth0 as a backup interface with a down link. Dec 17 08:35:20 3_10 ifup: Enslaving eth1 to bond0 Dec 17 08:35:20 3_10 kernel: bnx2: eth1: using MSI Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth1 as a backup interface with a down link. Dec 17 08:35:20 3_10 network: Bringing up interface bond0: succeeded Dec 17 08:35:21 3_10 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready Dec 17 08:35:23 3_10 kernel: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for interface eth0. Dec 17 08:35:23 3_10 kernel: bonding: bond0: making interface eth0 the new active one. Dec 17 08:35:23 3_10 kernel: bonding: bond0: first active interface up! Dec 17 08:35:23 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Dec 17 08:35:23 3_10 kernel: bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for interface eth1. Dec 17 08:35:23 3_10 kernel: tg3: eth2: Link is up at 1000 Mbps, full duplex. Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Dec 17 08:35:24 3_10 kernel: bond0: duplicate address detected! Dec 17 08:35:25 3_10 network: Bringing up interface eth2: succeeded _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

1 0

Bonding problem in CENTOS4
by Vitaly Karasik 17 Dec '07

17 Dec '07

I use bonding under CENTOS4.5 x32_62. I have these weird messages when I'm restarting network. Do you have any ideas how to fix this? (there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but the author says that it worked for him in centos4...) Thanks Vitaly Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts. Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth0 Dec 17 08:34:21 3_10 kernel: bonding: bond0: making interface eth1 the new active one. Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth1 Dec 17 08:34:21 3_10 network: Shutting down interface bond0: succeeded Dec 17 08:34:21 3_10 network: Shutting down interface eth2: succeeded ........ Dec 17 08:35:16 3_10 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready Dec 17 08:35:20 3_10 ifup: Enslaving eth0 to bond0 Dec 17 08:35:20 3_10 kernel: bnx2: eth0: using MSI Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth0 as a backup interface with a down link. Dec 17 08:35:20 3_10 ifup: Enslaving eth1 to bond0 Dec 17 08:35:20 3_10 kernel: bnx2: eth1: using MSI Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth1 as a backup interface with a down link. Dec 17 08:35:20 3_10 network: Bringing up interface bond0: succeeded Dec 17 08:35:21 3_10 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready Dec 17 08:35:23 3_10 kernel: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for interface eth0. Dec 17 08:35:23 3_10 kernel: bonding: bond0: making interface eth0 the new active one. Dec 17 08:35:23 3_10 kernel: bonding: bond0: first active interface up! Dec 17 08:35:23 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Dec 17 08:35:23 3_10 kernel: bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for interface eth1. Dec 17 08:35:23 3_10 kernel: tg3: eth2: Link is up at 1000 Mbps, full duplex. Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Dec 17 08:35:24 3_10 kernel: bond0: duplicate address detected! Dec 17 08:35:25 3_10 network: Bringing up interface eth2: succeeded

1 0

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