Discuss August 2006

discuss@lists.centos.org

269 participants
332 discussions

Bug: lvchange delayed until re-boot. System lock up experienced.
by William L. Maltby 06 Sep '06

06 Sep '06

Did a search for LVM at the CentOS bugzilla. Nothing seems to match this scenario. If no one contradicts me, I'll also post this in the bug reporting system. Wanted to a) get confirmation, if possible before bugging it and b) warn other souls that may be adventurous too! Summary: failings in LVM and kernel(?) seem to make a "freeze" possible. 1) Lvchange --permission=r seems to not take effect until re-boot even though lvdisplay says it has taken effect; 2) Prior to reboot, mount will mount a read-only LV and give no warning that it is read-only and will mount it r/w. The opposite also occurs: if the LV was ro and it is changed to r/w, mount still acts as if read-only is in effect. 3) If these steps are done, *ALL* commands work as if everything is normal *except* "ro" seems to have no effect: - lvchange --permission=r # Seems OK - lvdisplay # Seems OK, says "r" - mount <normal mount args> # Only "t -ext2" extra, no "read # only" warning from mount command - >/mnt/the_mount_point/test # Seems OK, ls shows it - rm /mnt/the_mount_point/test # Seems OK, ls doesn't show it What would happen if I did not umount it here? I guess it would run for at least some time without problem. Then, if LVM truly has it ro, when buffer flush time came there should be some undesirable results. At this point, I issued a umount for the volume and the system froze with blinking keyboard LED. Subsequent re-boot and investigation added the knowledge that the change in lv status was delayed until reboot. Can/will anyone confirm/deny this for me? Thx. Node: Athalon, CentOS-4.3. fully updated, all normal components from base (wine and a few odds and ends from rpmforge). ============ Gory Details Below ====================================== Progressing on LVM education and simplified b/u procedure using it. Covered my butt by setting the lv to read only. Got the hare-brained idea to see what would happen if... >>:-( # Protect fools from themselves. # umount /dev/VolGroupAA/lvol1 # lvchange --permission r VolGroupAA/lvol1 Logical volume "lvol1" changed # lvdisplay VolGroupAA/lvol1 # Edited below to items of interest --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV Write Access read only LV Status available # open 0 LV Size 9.31 GB Current LE 298 Block device 253:3 # Notice: no read-only this mount & no warning from mount command # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 # > /mnt/VolGroupAA_lvol1/test # ls show file created # rm /mnt/VolGroupAA_lvol1/test # ls shows file gone # umount /dev/VolGroupAA/lvol1 # Instant petrification! Purgatory entered: flashing keyboard LED and the usual three-fingered salute and destructive pounding on attached peripherals had the expected results! NADA! Googled here (it wrapped, sorry) http://groups.google.com/groups/search?hl=en&lr=&q=read-only+mount +write+LVM2+kernel+2.6+2006+lock+OR+crash&qt_s=Search Didn't see anything that looks like it. Saw a drbd related elsewhere that might come close... but NOPE! Anyway, since it seems (according to the HOWTO) that only mailing list activities report and address bugs (didn't see a bugzilla: did I look too casually?) I would like to confirm this is not peculiar to my node. I prefer not to subscribe to another list just to belatedly discover nothing of value after searching their archives too! If anyone else has a test machine and time, I will take the trouble to report this if it is confirmed. Subsequent reboot and test from the console gave this surprise. # lvchange --permission rw VolGroupAA/lvol1 Logical volume "lvol1" changed # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 mount: block device /dev/VolGroupAA/lvol1 is write-protected, mounting read-only # There I realized that the status change was not propagated to the system until a re-boot. Later I tried adding a "lvchange --refresh" although the docs didn't seem promising. It had no effect. Confiming again, re-booted and did this. Note the read/write access. # lvdisplay /dev/VolGroupAA/lvol1 --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV UUID jDoW7T-e7IS-Z5Zd-F1lG-3E6S-DvDl-bxYq7d LV Write Access read/write LV Status available # open 0 LV Size 9.31 GB Current LE 298 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:3 # lvchange --permission r VolGroupAA/lvol1 Logical volume "lvol1" changed # lvdisplay /dev/VolGroupAA/lvol1 --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV UUID jDoW7T-e7IS-Z5Zd-F1lG-3E6S-DvDl-bxYq7d LV Write Access read only LV Status available # open 0 LV Size 9.31 GB Current LE 298 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:3 # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 # Note: no warning about read-only issued. # mount <snip uninteresting stuff> /dev/mapper/VolGroupAA-lvol1 on /mnt/VolGroupAA_lvol1 type ext2 (rw) # >/mnt/VolGroupAA_lvol1/test # ls -ltr /mnt/VolGroupAA_lvol1 total 6486852 -rw-r--r-- 1 <snip> 290155835 Jul 25 12:25 ImportedHardDisks.tar.bz2 drwx------ 2 <snip> 16384 Jul 25 16:53 lost+found -rw-r--r-- 1 <snip> 6345862846 Jul 25 20:49 TestDisk_Test.tar.bz2 -rw-r--r-- 1 root root 0 Jul 27 11:56 test # umount here will lock machine. I'll finish mail first. TIA -- Bill

2 1

TARPIT target in iptables
by Barry Brimer 04 Sep '06

04 Sep '06

Has anyone been successful at using the TARPIT target in iptables under CentOS 4? I am using CentOS 4.3, fully updated with iptables-1.2.11-3.1.RHEL4 and kernel-2.6.9-34.107.plus.c4 Doing a locate on TARPIT returns: # locate TARPIT /lib/iptables/libipt_TARPIT.so This makes me think that the TARPIT target would be valid, however when I try to use it, I get the following reponse: # iptables -A INPUT -p tcp -m tcp --dport 80 -j TARPIT iptables: No chain/target/match by that name I am following the example located at the Netfilter website for rule creation: http://www.netfilter.org/patch-o-matic/pom-extra.html#pom-extra-TARPIT I have *NOT* rebuilt my kernel, or any tools because on the surface, as it does not appear necessary. Any help would be greatly appreciated. Thanks, Barry

3 4

Updating Centos Machines
by Rajeev R Veedu 04 Sep '06

04 Sep '06

Hi, I have few machines with Centos 4 I 386. Are there any programs which manage the updates centrally sitting on an intranet? I would like to avoid down loading the upgrades individually for each machine. I am looking for an open source version. Thanks Rajeev

6 6

SELinux Strict Mode
by Leonardo Vilela Pinheiro 04 Sep '06

04 Sep '06

According to http://www.redhat.com/magazine/006apr05/features/selinux/ there is a package named selinux-policy-strict, which contains a series of rules for correctly handling many situations (software) when using strict policy. Does CentOS have this package available ? If not, can someone make it available through Centosplus or Addon, for example ? This package is not part of the upstream main release, but according to the link above it is made available on their website for subscribers who want it. Anyway, I have just tried Fedora 4 package selinux-policy-strict-1.27.1-2.27.noarch.rpm. It might work, as it's just a package containing rules, but it's list of dependencies is incompatible, so I'd better leave it alone: rpm -Uvh selinux-policy-strict-1.27.1-2.27.noarch.rpm warning: selinux-policy-strict-1.27.1-2.27.noarch.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2 error: Failed dependencies: kernel >= 2.6.11-1.1219 is needed by selinux-policy-strict-1.27.1-2.27.noarch libselinux >= 1.23.5-1 is needed by selinux-policy-strict-1.27.1-2.27.noarch policycoreutils >= 1.22-2 is needed by selinux-policy-strict-1.27.1-2.27.noarch Thanks -- Vilela

2 3

pppoe problems
by kai 04 Sep '06

04 Sep '06

I'm having problem connecting to my isp with my sangoma s518. Everything seems to run smooth and wanrouter are training to connect....but forever.. Now, to test the connection i mounted up my standard nic and my old dsl router, to establish a standard basic pppoe connection..... and I can't with centos. I follow this standard setup: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/… tested on two different centos installations, but no. I spent 4 hours I think and needed two minits on my debian installation. Both rp-pppoe and ppp are installed, please someone tell me what am I missing before I totally loose it :-) ? kai # tail -20 /var/log/messages Aug 29 21:40:35 localhost pppd[21465]: pppd 2.4.2 started by root, uid 0 Aug 29 21:40:35 localhost pppd[21465]: Using interface ppp0 Aug 29 21:40:35 localhost pppd[21465]: Connect: ppp0 <--> /dev/pts/4 Aug 29 21:41:06 localhost pppd[21465]: LCP: timeout sending Config-Requests Aug 29 21:41:06 localhost pppd[21465]: Connection terminated. Aug 29 21:41:10 localhost pppoe[21466]: Timeout waiting for PADO packets Aug 29 21:41:10 localhost pppd[21465]: Exit. Aug 29 21:41:10 localhost adsl-connect: ADSL connection lost; attempting re-connection. Aug 29 21:41:15 localhost pppd[21553]: pppd 2.4.2 started by root, uid 0 Aug 29 21:41:15 localhost pppd[21553]: Using interface ppp0 Aug 29 21:41:15 localhost pppd[21553]: Connect: ppp0 <--> /dev/pts/4 Aug 29 21:41:46 localhost pppd[21553]: LCP: timeout sending Config-Requests Aug 29 21:41:46 localhost pppd[21553]: Connection terminated.

6 6

Release 4.4 and MPC51 ethernet controller
by Jerry Geis 03 Sep '06

03 Sep '06

When using 4.4 to install on gigabyte GA-M51GM-S2 motherboard basically an Nforce 410/430 chipset then network is not initially detect to perform a network install. It let me attempt to manually select a driver but I do not see the driver in the list. After installing the network works and the forcedeth driver is loaded. Is there a way to get this driver detected or manually loaded? THanks, jerry

5 4

Sendmail restriction
by Ugo Bellavance 03 Sep '06

03 Sep '06

Hi, I'm looking for a way, in sendmail, to set access rule, saying: Accept messages for domain.com only from this IP address. I did some research yesterday, but could only find a way to restrict by IP for all domains managed by sendmail. Any ideas? Regards, Ugo

7 12

Yum upgrade to 4.4 problem
by Simen Thoresen 02 Sep '06

02 Sep '06

CentOS 4.3 (SMP, x86_64, Athlon64 X2) with all pre-4.4 release updates applied. Since I ran into the Yum issue at the previous upgrade, I first did yum upgrade to get the list of packages (6 to install, 206 to update). I then did yum upgrade yum (which passed without issues) yum upgrade sqlite (which passed without isseus). Fairly certain that yum now works correctly, I wanted to just do another small upgrade before doing the rest, and did yum upgrade samba [root@naboens ~]# yum upgrade samba Setting up Upgrade Process Setting up repositories Reading repository metadata in from local files <no progress> This seemed to hang, and a look at top showed yum consuming more and more memory, the system starting to swap and bog down and then become unresponsive (all swap exhausted, I was not quick enough to kill yum). I was able to reproduce this on a different machine (also x86_64, SMP and Athlon64 X2), so it seems to be an actual problem. As I can play around a bit more on this machine, I tried doing a yum upgrade (without specifying samba) and it behaves the same (ie yum consuming increasing amounts of memory while "Reading repository metadata (etc)". Has anyone else experienced and been able to resolve this? -S -- Simen Thoresen, Dolphin ICS Systems Administration and Wulfkit Support

14 27

Postfix won't relay after update to CentOS 4.4
by Kanwar Ranbir Sandhu 02 Sep '06

02 Sep '06

Hi Everyone, My CentOS 4.4 mail server is having problems sending mail after updating it to 4.4 Before the update, I did not have any problems. My ISP requires that email clients must authenticate to their mail servers before mail can be sent out. I setup smtp auth to get postfix to relay mail through the ISP's mail servers. Here's my config: main.cf -------- relayhost = [smtp.broadband.rogers.com] smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_security_options = sasl_passwd --------------- smtp.broadband.rogers.com blah@blah.com:password I've done the usual run through of config files after an update, and made some small changes to main.cf (just added in comments and examples that were in main.cf.rpmnew). When I try to send a message, this is the error I get: F060D1C068: to=<m3freak(a)rogers.com>, relay=smtp-rog.mail.yahoo2.akadns.net[206.190.36.18], delay=1, status=bounced (host smtp-rog.mail.yahoo2.akadns.net[206.190.36.18] said: 530 authentication required - for help go to http://help.yahoo.com/help/us/mail/pop/pop-11.html (in reply to MAIL FROM command)) Just in case the ISP had done something, I manually tested authenticating to the ISP's mail server, and it worked just fine: Connected to smtp.broadband.rogers.com (206.190.36.18). Escape character is '^]'. 220 smtp105.rog.mail.re2.yahoo.com ESMTP ehlo krs 250-smtp105.rog.mail.re2.yahoo.com 250-AUTH LOGIN PLAIN XYMCOOKIE 250-PIPELINING 250 8BITMIME AUTH PLAIN blahblahblahblahblahblahblahblahblah 235 ok, go ahead (#2.0.0) So, the problem is on the Postfix end. I must assume something in the Postfix update broke my setup, but I can't figure out what it is. Has anyone else run into this? Am I missing something obvious? Hints appreciated. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2142_FC4 i686 GNU/Linux 16:11:07 up 2 days, 9:40, 3 users, load average: 1.06, 0.75, 0.62

9 17

upgrade to 4.4 hangs
by Zube 02 Sep '06

02 Sep '06

Two identical machines, both running CentOS 4.3 plus all the errata. First one: yum update went for a while and hung. At the bottom of the yum.log file was this: Aug 31 06:58:01 Updated: control-center.i386 1:2.8.0-12.rhel4.5 Aug 31 06:58:09 Updated: iiimf-le-unit.i386 1:12.1-13.EL.5 Aug The python process was in the process list, but it was consuming no CPU time. I let it go for a couple of hours, then killed it and played with the duplicate removal script posted previously. Second one: I tried a combination of suggestions previously posted: yum clean all yum update yum sqlite python-sqlite python-urlgrabber python-elementtree yum clean all yum upgrade This also ran for a while and then hung in a similar fashion. The tail of the yum.log is: Aug 31 11:29:08 Updated: at.i386 3.1.8-80_EL4 Aug 31 11:29:09 Updated: samba-client.i386 3.0.10-1.4E.9 Aug 31 11:29:21 Updated: anaconda.i386 10.1.1.46-1.cento Suggestions for future tries on other machines? Thanks much, Zube

4 6

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 August 2006