Discuss

discuss@lists.centos.org

34753 discussions

Heads up: ip_nat_ftp module can cause FTP problems in 5.7
by Dennis Jacobfeuerborn 21 Sep '11

21 Sep '11

Hi, after updating one of my systems to 5.7 FTP connections stopped working. After a bit of debugging I found out that the ip_nat_ftp module apparently breaks things in 5.7. So I you update your systems and suddenly FTP starts acting up check if you have that module in /etc/sysconfig/iptables-config. Details: http://bugs.centos.org/view.php?id=5135 Regards, Dennis

1 0

Re: [CentOS] (yum) Error: Cannot retrieve repository metadata (repomd.xml)....
by ken 21 Sep '11

21 Sep '11

Cool++. That fixed it. (Thanks much.) And now I have an example of something meant to fix problems causing problems. :) On 09/21/2011 12:05 PM lists-centos wrote: > > ------------ Original Message ------------ >> Date: Wednesday, September 21, 2011 11:52:11 AM -0400 >> From: ken <gebser(a)mousecar.com> >> >> On 09/21/2011 11:45 AM lists-centos wrote: >>> ------------ Original Message ------------ >>>> Date: Wednesday, September 21, 2011 11:27:44 AM -0400 >>>> From: ken <gebser(a)mousecar.com> >>>> To: CentOS mailing list <centos(a)centos.org> >>>> >>>> This error: >>>> >>>> Error: Cannot retrieve repository metadata (repomd.xml) for >>>> repository: debug. Please verify its path and try again >>>> >>>> occurs every time I run yum (and is where execution stops). Why? >>>> and/or What can be done to fix yum so I can use it again? >>>> >>> Have you tried: >>> >>> yum clean all >>> >>> then: >>> >>> yum check-update >>> >>> >>> - Richard >> yum check-update yields: >> >> http://debuginfo.centos.org/5/i386/repodata/repomd.xml: [Errno 4] >> IOError: <urlopen error (110, 'Connection timed out')> >> Trying other mirror. >> Error: Cannot retrieve repository metadata (repomd.xml) for >> repository: debug. Please verify its path and try again >> > > disable the debuginfo repository, either on the yum command line, or > better, in the /etc/yum.repos.d directory. it's not enabled by > default, and i suspect you don't need it, at least not at this stage. > > > - Richard > >

1 0

sudo wildcards problem: for every argument a *-wildcard? Better solution?
by Sven Aluoor 21 Sep '11

21 Sep '11

Hi folks I allow the user tommy to run this command as root sudoCommand: /app/appname/connectors/*/*/current/bin/* With "sudo -l" he sees the sudoers, but is unable to execute. $ sudo /app/appname/connectors/zur/namename/current/bin/othername agentsvc --i --u root --sn 1m7command Sorry, user tommy is not allowed to execute '/app/appname/connectors/zur/namename/current/bin/othername agentsvc --i --u root --sn 1m7command' as root on testcentbox07. I guess because of wildcard arguments. Does every argument needs a *-wildcard? How to do when I don't know the number of arguments? cheers Sven

2 3

Re: [CentOS] (yum) Error: Cannot retrieve repository metadata (repomd.xml)....
by ken 21 Sep '11

21 Sep '11

On 09/21/2011 11:45 AM lists-centos wrote: > > ------------ Original Message ------------ >> Date: Wednesday, September 21, 2011 11:27:44 AM -0400 >> From: ken <gebser(a)mousecar.com> >> To: CentOS mailing list <centos(a)centos.org> >> >> This error: >> >> Error: Cannot retrieve repository metadata (repomd.xml) for >> repository: debug. Please verify its path and try again >> >> occurs every time I run yum (and is where execution stops). Why? >> and/or What can be done to fix yum so I can use it again? >> > > Have you tried: > > yum clean all > > then: > > yum check-update > > > - Richard yum check-update yields: http://debuginfo.centos.org/5/i386/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (110, 'Connection timed out')> Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: debug. Please verify its path and try again So same problem.

1 0

(yum) Error: Cannot retrieve repository metadata (repomd.xml)....
by ken 21 Sep '11

21 Sep '11

This error: Error: Cannot retrieve repository metadata (repomd.xml) for repository: debug. Please verify its path and try again occurs every time I run yum (and is where execution stops). Why? and/or What can be done to fix yum so I can use it again? tnx. -- War is a failure of the imagination. --William Blake

1 0

Installation of 6.0
by Al Sparks 21 Sep '11

21 Sep '11

Some observations. When I installed 6.0 (base install), the installation interface did not guide me through a network configuration. I do static IP addresses, not DHCP. I ended up manually configuring the various /etc/sysconfig files. I forgot to do the GATEWAY configuration and it took me awhile to figure out why I wasn't able to connect to the server from outside the LAN. I also forgot to do the DNS settings. It's deja-vu all over again, going back to the older Red Hat Linux distros. Anyway, I wasn't able to find a configuration program like "netconfig" to help me out. Seems like a pretty big omission. Any thoughts? Am I missing something? === Al

6 10

selinux policy remnant according to /bin/ls on CentOS 6.0 box
by Jon Detert 21 Sep '11

21 Sep '11

I installed CentOS 6.0 on 2 different x86_64 boxen. Both originally had selinux installed and enabled. I never touched selinux other than to remove as much of it as I could via rpm -e. As far as I can tell, here are the remaining packages that have something to do with it: # rpm -qa | grep -iE 'sel|pol' checkpolicy-2.0.22-1.el6.x86_64 libselinux-2.0.94-2.el6.x86_64 libsepol-2.0.41-3.el6.x86_64 polkit-0.96-2.el6_0.1.x86_64 # Both boxen have those packages. However: 1) box1 still has files in /selinux whereas box2's /selinux is empty; 2) ls -l on box1 shows a '.' at the end of file/directory, which means a SELinux security context applies, according to https://fedoraproject.org/wiki/Fedora_11_FAQ#Why_does_ls_show_a_dot_.28..29… Any idea why box1 still seems to have an selinux policy applied, and how to un-apply it? Thanks, Jon

4 5

mdadm and drive identification?
by David C. Miller 21 Sep '11

21 Sep '11

I have a server that has 16 drives in it. They are connected to a 3ware 9650SE-16ML SATA RAID card. I have the card set to export all the drives as JBOD because I prefer Linux to do the reporting of drive and RAID health . I'm using mdadm to create a RAID6 with a hot spare. Doing this I can take the disks and put them on a completely different SATA controller/computer and still have the RAID intact. My problem is that I have no "for sure" way of matching a drive assigned to one of the /dev/sd[a-z]. Normally I could use a number of methods to match up what /dev/sd[a-z] is to a drives serial number. smartctl, hdparm, udevinfo, /dev/disk/by-uuid, or /dev/disk/by-id. However, the 3ware card obfuscates the drives from the OS and those methods don't work. The only way I know how to get a drives serial number is via the smartctl command like "smartctl -d 3ware,[0-15] -i /dev/twa0", but that does not tell me which sd[a-z] the drive is assigned to. Here is what I have tried. Creating a single large partition with fdisk on each drive as linux autoraid to get a uuid. for some reason the OS assigns the same uuid and only one uuid to the last drive I partition from the 3ware card. Basically all drives on the 3ware card have the same uuid.. Using the /dev/disk/by-id/. For some reason the 3ware card does not always assign the same id to a drive after a reboot. Is there another easy way I can positively ID a drive by serial number and the /dev/sd[a-z] that mdadm sees? Thanks. David.

3 3

eth enumeration order
by Volker Poplawski 20 Sep '11

20 Sep '11

I have installed Centos 6 on a server with two NICs. It so happens that the NIC with the lower ARP adr is assigned 'eth1' and the NIC with the higher ARP 'eth0'. (Not sure if this a bug but it is at least inconvenient) I have modified the udev rules in /etc/udev/rules.d/70-persistent-net.rules by swapping eth0 with eth1 in the NIC's rules. However: the file gets changed on reboot. A third rule is automaticaly added for some reason, for one of the NICs which already has a rule. See below. The system ends up with no network interface set up at all, because the init-script gets confused. So.... How do you specifiy the order in which NICs are enumerated? or at least how to tell centos to stop messing with the 70-persistent-net.rules? Regards .....Volker Contents of /etc/udev/rules.d/70-persistent-net.rules (arps anonymized): (These are the two rules modified by me, assigning eth0/eth1 in ascending arp order) # PCI device 0x8086:0x10d3 (e1000e) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:8f:ea", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x1502 (e1000e) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:8f:eb", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" (This is the rule which gets automaticaly added on reboot) # PCI device 0x8086:0x1502 (e1000e) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:8f:eb", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

3 4

PDF Reader/Editor for CentOS 5.7 (32 bit)?
by Lanny Marcus 20 Sep '11

20 Sep '11

I had, in the past, a .pdf reader that also permitted me to fill in some information, when I received a .pdf file. I have KPDF installed, but that seems to only have Reader capability. Trying to install xpdf, with yum, I get this dependency error from rpmforge: 1:xpdf-3.02-8.el5.rf.i386 from rpmforge has depsolving problems --> Missing Dependency: libXm.so.4 is needed by package 1:xpdf-3.02-8.el5.rf.i386 (rpmforge) Error: Missing Dependency: libXm.so.4 is needed by package 1:xpdf-3.02-8.el5.rf. Then, if I try to yum install libXm.so.4 I get this error: No package libXm.so.4 available. Received a contract via email and I would like to add some information and send it back via email. If someone can recommend a Package that I can install, that will be appreciated. Hopefully, something as easy to use as what I had before. It just worked. :-) Unfortunately, I cannot remember which package it was. :-) TIA! Lanny http://www.magazines-magazine.com/

12 15

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