Discuss February 2011

discuss@lists.centos.org

267 participants
208 discussions

Re: [CentOS] We haven't had a lot of demand for Fedora...people seem okay with CentOS!
by Larry Vaden 18 Feb '11

18 Feb '11

On Fri, Feb 18, 2011 at 5:09 PM, Rudi Ahlers <Rudi(a)softdux.com> wrote: > Larry, I suggest you leave this group while it's still safe todo so. > > What do you have against CentOS & FOSS ???? This was posted as a compliment to the CentOS Team and to the CentOS Community. Should the vendor be asked for a less ambiguous statement?

2 1

request for a learning moment
by Larry Vaden 18 Feb '11

18 Feb '11

On Fri, Feb 18, 2011 at 1:45 PM, Scot P. Floess <sfloess(a)nc.rr.com> wrote: > > I'd expect better behavior and conduct from someone who holds such a > title... <request for a learning moment> Since beauty is in the eye of the beholder(s), please select my most egregious post(s) and let me know said post(s) so that I have the opportunity to better modify my behavior with the result that we can focus on the business at hand. </request for a learning moment> kind regards/ldv/vaden(a)texoma.net

3 2

OT - simple CAD program to design electronic circuits with
by Keith Roberts 18 Feb '11

18 Feb '11

Hi all. Is there an electronic circuit design CAD package available for Centos 5.5 please? Kind Regards, Keith Roberts ----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------

7 10

nss_ldap: reconnected to LDAP server ldap://127.0.0.1
by Tim Alberts 18 Feb '11

18 Feb '11

Hello, I have a problem that I'm really having trouble figuring out. I run CentOS Linux 5.5. I have three servers. All have been setup and running with LDAP authentication for a couple years with absolutely no problems. Unfortunately a couple weeks ago, we had a power outage. Ever since, I am having continuous problems with authentication to the server. I see in /var/log/messages nss_ldap: reconnected to LDAP server ldap://127.0.0.1 I did run a yum update that installed an update to ldap, however that did not fix the issue. I have seen a post mentioning changing 'nss_connect_policy persist' to 'nss_connect_policy oneshot'. However I don't see this setting in my server, and again, the server was working perfectly fine for years before the power outage. I'm really thinking that some file got corrupted and I just need to clean it out. Maybe a cache file somewhere? Following is ldap.conf file. Any suggestions? <ldap.conf> base dc=inside,dc=msi timelimit 120 bind_timelimit 120 idle_timelimit 3600 nss_initgroups_ignoreusers root,ldap,named,avahi,haldaemon,dbus,radvd,tomcat,radiusd,news,mailman rootbinddn cn=Manager,dc=inside,dc=msi nss_base_passwd ou=People,dc=inside,dc=msi nss_base_shadow ou=People,dc=inside,dc=msi nss_base_group ou=Group,dc=inside,dc=msi uri ldap://127.0.0.1 ldap://my.domain ssl no tls_cacertdir /etc/openldap/cacerts pam_password md5 </ldap.conf>

3 7

Re: [CentOS] Any update on 5.6 / 6?
by Always Learning 18 Feb '11

18 Feb '11

There are lots of people in similar circumstances to Larry. He has a recognised medical syndrome. People get problems. Some do not know how to effectively tackle their major problem so stress increases to a significant and detrimental extent. Often the person is never fully aware of high stress levels they have. Just because someone looks 'normal' it does not mean they are not in someway suffering. A good example is someone suffering from an incurable illness with a year to live. Can anyone really identity their significantly shorted lifespan just by looking at them in the street as they walk by? Diversions into irritating behaviour are a classic example of someone desperately trying to avoid thinking about, and therefore dealing with, a major problem. The reason they try to avoid thinking about the problem is the very high stress levels associated with that problem. It is too much for them to handle. The diversionary behaviour is a form of 'stress relief' and ultimately a cry for help. Larry is very likely curable. He just needs to talk confidentially and openly to someone who can begin to help him. Often a problem shared is a problem halved *and* the stress levels are lowered. Larry, I know you will read this, talk to a friend - Get help. With best regards, Paul. England, EU.

1 0

Software RAID Level 1, smartd and changing dev numbers
by James Smallacombe 18 Feb '11

18 Feb '11

We have about 50 CentOS servers with software RAID level 1 (mirroring). Each week, we swap out one of the drives (the one in the second of four hot-swap bays, only the first two of which contain drives) on each server and take them offsite for safekeeping. The problem is, the kernel seemingly randomly switches between /dev/sdb and /dev/sdc for these devices. This makes the process slower by requiring more manual input where a script(s) could otherwise suffice. It also confuses smartd, which AFAIK, needs the correct device names to report accurately. Ideally, we'd like to force the OS at some level to always see these devices as /dev/sda and /dev/sdb. If not, is there at least some way to configure smartd to be "smart" and recognize which devices are in use? TIA,

9 16

Re: [CentOS] Authentication Problems
by James Bensley 18 Feb '11

18 Feb '11

On 16 Feb 2011 12:34, "Nico Kadel-Garcia" <nkadel(a)gmail.com> wrote: > > Uh-oh. Has your developer, or you, been editing the /etc/passwd, > /etc/shadow, /etc/group, or /etc/gshadow files manually? Nope. > And do you > use NIS or LDAP for authentication? Nope. > And this is a publicly exposed > webserver, right? How fast can you rebuild it if it's been rootkitted? How long is a peice of string? As quick as I can reupload the data, but thats another issue for another day. > Check the /etc/shadow and /etc/group for consistent numbers of > entries, and /etc/group and /etc/gshadow. Do you mean duplicate entries? If so there are none of those. > Do you have other users who > can still log in or not? There is only the root and web dev user on this box. Thanks for your input Nico :) --James. (This email was sent from a mobile device)

4 5

NIC bonding - missing eth0?
by Smithies, Russell 18 Feb '11

18 Feb '11

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It's always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the port channel. The only difference between the 2 servers is one is running Xen (kernel-xen-2.6.18-194.32.1.el5.centos.plus) so I have a few virtual interfaces and bridges. Any ideas what might be happening? Thanx, Russell Smithies [root@invmhp01 ~]# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: slow Active Aggregator Info: Aggregator ID: 19 Number of ports: 3 <<<<<<<< Actor Key: 17 Partner Key: 5 Partner Mac Address: 00:1b:90:3d:90:c0 Slave Interface: eth0 MII Status: up Link Failure Count: 0 Permanent HW addr: 1c:c1:de:74:97:5c Aggregator ID: 18 Slave Interface: eth1 MII Status: up Link Failure Count: 0 Permanent HW addr: 1c:c1:de:74:97:5d Aggregator ID: 19 Slave Interface: eth2 MII Status: up Link Failure Count: 0 Permanent HW addr: 1c:c1:de:74:97:5e Aggregator ID: 19 Slave Interface: eth3 MII Status: up Link Failure Count: 0 Permanent HW addr: 1c:c1:de:74:97:5f Aggregator ID: 19 [root@invmhp01 ~]# ifconfig bond0 Link encap:Ethernet HWaddr 1C:C1:DE:74:97:5C inet addr:147.158.130.183 Bcast:147.158.131.255 Mask:255.255.252.0 inet6 addr: fe80::1ec1:deff:fe74:975c/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:64087 errors:0 dropped:0 overruns:0 frame:0 TX packets:18179 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8293500 (7.9 MiB) TX bytes:31362799 (29.9 MiB) eth0 Link encap:Ethernet HWaddr 1C:C1:DE:74:97:5C UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:5770 errors:0 dropped:0 overruns:0 frame:0 TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:410102 (400.4 KiB) TX bytes:2524 (2.4 KiB) eth1 Link encap:Ethernet HWaddr 1C:C1:DE:74:97:5C UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:22247 errors:0 dropped:0 overruns:0 frame:0 TX packets:17436 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1424685 (1.3 MiB) TX bytes:31161969 (29.7 MiB) Interrupt:239 eth2 Link encap:Ethernet HWaddr 1C:C1:DE:74:97:5C UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:6223 errors:0 dropped:0 overruns:0 frame:0 TX packets:189 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:442326 (431.9 KiB) TX bytes:19993 (19.5 KiB) Interrupt:235 eth3 Link encap:Ethernet HWaddr 1C:C1:DE:74:97:5C UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:29852 errors:0 dropped:0 overruns:0 frame:0 TX packets:537 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6016657 (5.7 MiB) TX bytes:179281 (175.0 KiB) Interrupt:231 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:26818 errors:0 dropped:0 overruns:0 frame:0 TX packets:26818 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:38558929 (36.7 MiB) TX bytes:38558929 (36.7 MiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:41498 errors:0 dropped:0 overruns:0 frame:0 TX packets:251 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3000012 (2.8 MiB) TX bytes:59877 (58.4 KiB) Interrupt:243 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:127 errors:0 dropped:0 overruns:0 frame:0 TX packets:39354 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15520 (15.1 KiB) TX bytes:2817598 (2.6 MiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:42 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:8160 (7.9 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:38746 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2217067 (2.1 MiB) TX bytes:0 (0.0 b) ======================================================================= Attention: The information contained in this message and/or attachments from AgResearch Limited is intended only for the persons or entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipients is prohibited by AgResearch Limited. If you have received this message in error, please notify the sender immediately. =======================================================================

2 3

working with multiple password protected iSCSI targets on one host
by Rudi Ahlers 18 Feb '11

18 Feb '11

Hi, How do I setup multiple password protected iSCSI targets on Linux? I know that mounting a password protected iSCSI target requires modify these records with the appropriate values: node.session.auth.username = My_ISCSI_USR_NAME node.session.auth.password = MyPassword discovery.sendtargets.auth.username = My_ISCSI_USR_NAME discovery.sendtargets.auth.password = MyPassword But, now I need to mount another iSCSI target, from a different SAN that has a different username & password than whan I have configured here for the one already mounted. How do I tell iscsiadm which CHAP settings to use with which iSCSI target? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532

3 2

write-back cache question
by James Chase 17 Feb '11

17 Feb '11

I have a perc5i (and perc5e) raid controller in my poweredge 2970 running centos 5.5. The RAID controller config is set for write-back policy, which I can confirm by checking in OpenManage. I also called Dell and ran their reporting application and had them double check to make sure everything looks OK hardware wise and they confirm that it does Yet when CentOS boots is appears to use the write through policy as can be seen below from dmesg output. Am I wrong that CentOS should query the RAID controller and go into the correct write mode: write-back? hub 1-5:1.0: 4 ports detected Vendor: DP Model: BACKPLANE Rev: 1.00 Type: Enclosure ANSI SCSI revision: 05 Vendor: DELL Model: PERC 5/i Rev: 1.03 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 2435317760 512-byte hdwr sectors (1246883 MB) sda: Write Protect is off sda: Mode Sense: 1f 00 00 08 SCSI device sda: drive cache: write through SCSI device sda: 2435317760 512-byte hdwr sectors (1246883 MB) sda: Write Protect is off sda: Mode Sense: 1f 00 00 08 SCSI device sda: drive cache: write through sda: sda1 sda2 sda3 sd 0:2:0:0: Attached scsi disk sda megasas: 0x1028:0x0015:0x1028:0x1f01: bus 16:slot 14:func 0 GSI 21 sharing vector 0x62 and IRQ 21 ACPI: PCI Interrupt 0000:10:0e.0[A] -> GSI 18 (level, low) -> IRQ 98 megasas: FW now in Ready state

4 5

← Newer
1
...
6
7
8
9
10
11
12
...
21
Older →

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 February 2011