Discuss

discuss@lists.centos.org

34758 discussions

CentOS 6.4 kickstart bonding
by Baptiste AGASSE 18 Mar '13

18 Mar '13

Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for cluster network, two for iscsi network) here is my "network" kickstart section: # "Public" network, bond0 created, it works fine, network --device=bond0 --noipv6 --bootproto=static --onboot=yes --hostname=box.example.com --ip=192.168.1.3 --netmask=255.255.255.0 --gateway=192.168.1.1 --nameserver=192.168.1.1 --bondslaves=p1p1,p1p2 --bondopts=mode=active-backup,primary=p1p1,miimon=80,updelay=60000 # Cluster network, not created on install network --device=bond1 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --ip=192.168.2.2 --netmask=255.255.255.0 --bondslaves=em1,em2 --bondopts=mode=active-backup,primary=em1,miimon=80,updelay=60000 # ISCSI network network --device=p1p3 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --mtu=9000 --ip=192.168.3.1 --netmask=255.255.255.0 network --device=p1p4 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --mtu=9000 --ip=192.168.3.2 --netmask=255.255.255.0 # bond slave network --device=em1 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=em2 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=p1p1 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=p1p2 --noipv6 --nodns --bootproto=static --onboot=yes when i check anaconda-ks.cfg on the installed host, the second bonding iface (bond1) is not present. No error displayed during install or present in install log files on installed hosts. Maybe Have a nice day. Regards. Baptiste.

1 0

evaluating backup systems: rsync
by ken 18 Mar '13

18 Mar '13

Considering using rsync on a couple systems for backup, I was wondering if it's possible, and if so how difficult is it, to delete files which have been backed up (in order to save space on the backup media). Anyone with experience doing this?

13 31

Re: [CentOS] DNS problem
by Weplica 18 Mar '13

18 Mar '13

Hi, Actually, the website is found, but when I create new virtual servers withs virutalmin, noone can be access. I have already try ns.maca.li. IN A 91.121.137.55 NS IN NS maca.li. But it do nothing, Thanks, Ernesto Quoting Banyan He <banyan(a)rootong.com>: > Hi there, > > You can put two NS records for ns.maca.li and ns.kimsufi.com in your > domain conf file. It then will be good. That page is trying find the > matched record from the parent nameserver only. > > Actually, you don't really have to do this. It's like a double confirmation. > > Best regards, > > ------------ > Banyan He > Blog: http://www.rootong.com > Email: banyan(a)rootong.com > > On 3/19/2013 12:56 AM, Weplica wrote: >> >> Hello Banyan He, >> >> Thanks you, but I am beginner, what's kind of record do I need to add? >> >> I have try: >> >> @ IN NS ns.maca.li. >> ns.maca.li. IN A 91.121.137.55 >> >> But I have the same error... >> >> Thanks, >> >> Ernesto >> >> >> >> Quoting Banyan He <banyan(a)rootong.com>: >> >>> It's just saying the records don't match from your parent nameserver. >>> >>> [root@janus ~]# dig ns maca.li +trace >>> >>> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5 <<>> ns maca.li +trace >>> ;; global options: printcmd >>> . 3600 IN NS i.root-servers.net. >>> . 3600 IN NS h.root-servers.net. >>> . 3600 IN NS g.root-servers.net. >>> . 3600 IN NS f.root-servers.net. >>> . 3600 IN NS e.root-servers.net. >>> . 3600 IN NS d.root-servers.net. >>> . 3600 IN NS c.root-servers.net. >>> . 3600 IN NS b.root-servers.net. >>> . 3600 IN NS a.root-servers.net. >>> . 3600 IN NS m.root-servers.net. >>> . 3600 IN NS l.root-servers.net. >>> . 3600 IN NS k.root-servers.net. >>> . 3600 IN NS j.root-servers.net. >>> ;; Received 477 bytes from 172.28.64.17#53(172.28.64.17) in 0 ms >>> >>> li. 172800 IN NS c.nic.li. >>> li. 172800 IN NS e.nic.li. >>> li. 172800 IN NS d.nic.li. >>> li. 172800 IN NS a.nic.li. >>> li. 172800 IN NS h.nic.li. >>> li. 172800 IN NS b.nic.li. >>> li. 172800 IN NS f.nic.li. >>> ;; Received 421 bytes from 192.36.148.17#53(i.root-servers.net) in 7 ms >>> >>> maca.li. 3600 IN NS ns.kimsufi.com. >>> maca.li. 3600 IN NS ns.maca.li. >>> ;; Received 86 bytes from 147.28.0.39#53(c.nic.li) in 204 ms >>> >>> maca.li. 38400 IN NS maca.li. >>> ;; Received 39 bytes from 213.186.33.199#53(ns.kimsufi.com) in 255 ms >>> >>> As you can see, the parent server returns two NS records. But here >>> is the NS records from your server. >>> >>> [root@janus ~]# dig ns maca.li >>> >>> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5 <<>> ns maca.li >>> ;; global options: printcmd >>> ;; Got answer: >>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15214 >>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 >>> >>> ;; QUESTION SECTION: >>> ;maca.li. IN NS >>> >>> ;; ANSWER SECTION: >>> maca.li. 29242 IN NS maca.li. >>> >>> ;; ADDITIONAL SECTION: >>> maca.li. 29242 IN A 91.121.137.55 >>> >>> ;; Query time: 0 msec >>> ;; SERVER: 172.28.64.17#53(172.28.64.17) >>> ;; WHEN: Mon Mar 18 18:34:32 2013 >>> ;; MSG SIZE rcvd: 55 >>> >>> You don't specify these two NS records from your parent. Just need >>> to add these two, you will be fine then. >>> >>> Cheers, >>> >>> ------------ >>> Banyan He >>> Blog: http://www.rootong.com >>> Email: banyan(a)rootong.com >>> >>> On 3/18/2013 4:04 PM, Weplica wrote: >>>> Hello, >>>> >>>> I just get a server with CentOS 6.4, I have install Webmin and >>>> Vitualmin running OK, but I can't run correctly DNS server. >>>> >>>> I set hostname: dns.maca.li >>>> Resolution order: Host file, DNS >>>> DNS servers: 127.0.0.1 and 91.121.137.55 >>>> Search Domain: maca.li >>>> >>>> >>>> When I creta virtual server with virtualmin, all DNS records are >>>> generated automaticaly by virtualmin. But I hace errors withs all >>>> virtual server, and in http://www.intodns.com/maca.li this errorS: >>>> >>>> " Missing nameservers reported by parent FAIL: The following >>>> nameservers are listed at your nameservers as nameservers for your >>>> domain, but are not listed at the parent nameservers (see RFC2181 >>>> 5.4.1). You need to make sure that these nameservers are working.If >>>> they are not working ok, you may have problems! >>>> maca.li >>>> Error Missing nameservers reported by your nameservers ERROR: One or >>>> more of the nameservers listed at the parent servers are not listed as >>>> NS records at your nameservers. The problem NS records are: >>>> ns.kimsufi.com >>>> This is listed as an ERROR because there are some cases where nasty >>>> problems can occur (if the TTLs vary from the NS records at the root >>>> servers and the NS records point to your own domain, for example). " >>>> >>>> >>>> >>>> >>>> // >>>> // named.conf (generated by webmin) >>>> // >>>> // Provided by Red Hat bind package to configure the ISC BIND named(8) DNS >>>> // server as a caching only nameserver (as a localhost DNS resolver only). >>>> // >>>> // See /usr/share/doc/bind*/sample/ for example named configuration files. >>>> // >>>> >>>> options { >>>> listen-on port 53 { >>>> any; >>>> }; >>>> listen-on-v6 port 53 { >>>> any; >>>> }; >>>> directory "/var/named"; >>>> dump-file "/var/named/data/cache_dump.db"; >>>> statistics-file "/var/named/data/named_stats.txt"; >>>> memstatistics-file "/var/named/data/named_mem_stats.txt"; >>>> recursion yes; >>>> >>>> dnssec-enable yes; >>>> dnssec-validation yes; >>>> dnssec-lookaside auto; >>>> >>>> /* Path to ISC DLV key */ >>>> bindkeys-file "/etc/named.iscdlv.key"; >>>> >>>> managed-keys-directory "/var/named/dynamic"; >>>> }; >>>> >>>> logging { >>>> channel default_debug { >>>> file "data/named.run"; >>>> severity dynamic; >>>> }; >>>> }; >>>> >>>> zone "." IN { >>>> type hint; >>>> file "named.ca"; >>>> }; >>>> >>>> include "/etc/named.rfc1912.zones"; >>>> include "/etc/named.root.key"; >>>> >>>> zone "maca.li" { >>>> type master; >>>> file "/var/named/maca.li.hosts"; >>>> allow-transfer { >>>> 127.0.0.1; >>>> localnets; >>>> }; >>>> }; >>>> >>>> >>>> >>>> // >>>> // maca.li (generated by virtualmin) >>>> // >>>> $ttl 38400 >>>> @ IN SOA maca.li. root.maca.li. ( >>>> 1363593549 >>>> 10800 >>>> 3600 >>>> 604800 >>>> 38400 ) >>>> @ IN NS maca.li. >>>> maca.li. IN A 91.121.137.55 >>>> www.maca.li. IN A 91.121.137.55 >>>> ftp.maca.li. IN A 91.121.137.55 >>>> m.maca.li. IN A 91.121.137.55 >>>> localhost.maca.li. IN A 127.0.0.1 >>>> webmail.maca.li. IN A 91.121.137.55 >>>> admin.maca.li. IN A 91.121.137.55 >>>> mail.maca.li. IN A 91.121.137.55 >>>> maca.li. IN MX 5 mail.maca.li. >>>> maca.li. IN TXT "v=spf1 a mx a:maca.li ip4:91.121.137.55 ?all" >>>> >>>> >>>> >>>> >>>> Where is my error? >>>> >>>> Thanks you >>>> >>>> Ernesto >>>> >>>> >>>> _______________________________________________ >>>> CentOS mailing list >>>> CentOS(a)centos.org >>>> http://lists.centos.org/mailman/listinfo/centos >>>> . >>>> >>> >> >> > >

2 1

Mounting USB drives read-only by default?
by James Pearson 18 Mar '13

18 Mar '13

Is it possible to configure the automounting of USB drives to mount read-only? Is there some gconf/udev/udisks/hal/whatever setting to alter the default mount options when USB disks are plugged in by users? Thanks James Pearson

2 2

mount exited with exit code 18
by Mark LaPierre 18 Mar '13

18 Mar '13

Hey Y'all, I'm trying to mount a USB drive with an NTFS file system on it. I need the drive in a win-7 virtual box instance. Error Dialog is: Error mounting: mount exited with exit code 18: Error opening '/dev/sdc1': Read-only file system Failed to mount '/dev/sdc1': Read only file system [root@mushroom /]# ls -l /dev/disk/by-id | grep usb lrwxrwxrwx. 1 root root 9 Mar 17 14:49 usb-TOSHIBA_TOSHIBA_USB_DRV_07082714D41C2837-0:0 -> ../../sdc lrwxrwxrwx. 1 root root 10 Mar 17 14:49 usb-TOSHIBA_TOSHIBA_USB_DRV_07082714D41C2837-0:0-part1 -> ../../sdc1 [root@mushroom /]# ls -l /dev/disk/by-label/ | grep sdc lrwxrwxrwx. 1 root root 10 Mar 17 14:49 FDSADV -> ../../sdc1 [root@mushroom /]# ls -l /dev/disk/by-path/ | grep sdc lrwxrwxrwx. 1 root root 9 Mar 17 14:49 pci-0000:00:10.4-usb-0:7:1.0-scsi-0:0:0:0 -> ../../sdc lrwxrwxrwx. 1 root root 10 Mar 17 14:49 pci-0000:00:10.4-usb-0:7:1.0-scsi-0:0:0:0-part1 -> ../../sdc1 [root@mushroom /]# ls -l /dev/disk/by-uuid/ | grep sdc lrwxrwxrwx. 1 root root 10 Mar 17 14:49 6CA0387BA0384E38 -> ../../sdc1 [root@mushroom /]# fdisk -l /dev/sdc Disk /dev/sdc: 32.0 GB, 32027705344 bytes 64 heads, 32 sectors/track, 30544 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x05b6fb64 Device Boot Start End Blocks Id System /dev/sdc1 1 30544 31277040 7 HPFS/NTFS Any suggestions? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

3 3

Kernel panic after update
by Kwan Lowe 17 Mar '13

17 Mar '13

Hello all: I just updated yesterday and rebooted when I received this error: compat: exports duplicate symbol pcmcia_loop_typle (owned by kernel) FATAL: Error inserting dm_mod (/lib/modules/2.6.32.-358.2.1.el6.centos.plus.x86_64/kernel/drivers/md/dm-mod.ko): Invalid module format compat: exports duplicate symbol pcmcia_loop_tuple (owned by kernel) It is a centos-plus update however. Is this the correct forum to discuss issues with the plus repo? Thanks, Kwan

2 2

moderate rant un updates
by m.roth＠5-cent.us 16 Mar '13

16 Mar '13

So, another admin I work with rolled out most (but not kernel) updates to 6.4... but including xorg. I log out the end of the day, and I'm hosed - no X. Now, my not-two-year-old workstation has an nvidia card, and I'd installed kmod-nvidia from elrepo. I figured I'd fix my problem by finishing the upgrade and rebooting. Nope. I try to upgrade kmod-nvidia from elrepo. Anyone got any good explanations as to why they'd put kmod-nvidia-310.40 in the repo, with the previous version not obvious... AND NOT HAVE THE *REQUIRED* nvidia-x11-drv-310.40 in there? Why not wait until both pieces could be uploaded, since kmod-nividia WILL NOT INSTALL without the other...? I then stupidly uninstalled the previous kmod-nvidia & nvidia-x11-drv, hoping it would allow a good install. Nope. Found the proprietary installer on the NVidia site, and I'm up. <rant, snort> On a related note, does anyone have a link to a howto build the NVidia proprietary driver on a kernel that's *not* running, so we could prebuild it before the reboot? I see there are options in the script, but no examples. Also, is dkms coming in, or deprecated? mark

12 32

Lockups with kernel-2.6.32-358.0.1.el6.i686
by Ian Pilcher 16 Mar '13

16 Mar '13

I updated my home server with the 6.4 CR packages, and I've experienced 3 or 4 hard lockups since. The server is a fanless VIA C7 "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of RAM. It has a dual-port Intel 82546GB NIC in its single PCI slot. (It also has an on-board Realtek RTL-8110SC/8169SC NIC that is plugged in, but doesn't currently have an IP address configured.) This server provides a number of services -- DNS, DHCP, routing between VLANs, DLNA media server, CUPS, etc. Most importantly, it runs Asterisk and manages all of the phones in the house. There's absolutely nothing in the logs related to the lockup. The system simply becomes totally unresponsive, to the point that the console cursor stops blinking. A hard reset is required to bring it back. kernel-2.6.32-279.22.1.el6.i686 seems to be completely stable. I don't really expect to be able to figure this out, but I thought I'd post here to see if anyone else is experiencing anything like this with this kernel. Thanks! -- ======================================================================== Ian Pilcher arequipeno(a)gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. ========================================================================

10 25

Re: [CentOS] Kernel panic after update to 6.4
by Emmett Culley 16 Mar '13

16 Mar '13

On 03/12/2013 04:23 PM, lists-centos wrote: > > > ------------ Original Message ------------ >> Date: Tuesday, March 12, 2013 04:05:28 PM -0700 >> From: Emmett Culley <emmett(a)webengineer.com> >> To: centos(a)centos.org >> Cc: >> Subject: Re: [CentOS] Kernel panic after update to 6.4 >> >> On 03/12/2013 01:48 PM, Akemi Yagi wrote: >>> On Tue, Mar 12, 2013 at 1:41 PM, Emmett Culley >>> <emmett(a)webengineer.com> wrote: >>>> After successfully updating three CentOS 6.3 VM guests to 6.4 I >>>> decided to update the host as well. And it failed to boot. >>>> >>>> Kernel panic - Not syncing: Attempted to kill init! >>>> Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1 >>> >>> At the time of this writing, CentOS kernel 2.6.32-358.2.1.el6 is >>> not out yet. Where did you get this one from ??? Did you build it >>> yourself? >>> >>> Akemi >> >> I did yum update --enablerepo=epel. I just checked and it appears >> that kernel was from the updates repo: >> >> [~]# yum list kernel >> Installed Packages >> kernel.x86_64 2.6.32-279.9.1.el6 @updates >> kernel.x86_64 2.6.32-279.14.1.el6 @updates >> kernel.x86_64 2.6.32-279.19.1.el6 @updates >> kernel.x86_64 2.6.32-279.22.1.el6 @updates >> kernel.x86_64 2.6.32-358.0.1.el6 @updates >> >> [~]# rpm -qa |grep kernel >> abrt-addon-kerneloops-2.0.8-15.el6.centos.x86_64 >> kernel-2.6.32-279.19.1.el6.x86_64 >> dracut-kernel-004-303.el6.noarch >> kernel-devel-2.6.32-279.14.1.el6.x86_64 >> kernel-2.6.32-279.14.1.el6.x86_64 >> kernel-devel-2.6.32-279.22.1.el6.x86_64 >> kernel-headers-2.6.32-358.0.1.el6.x86_64 >> kernel-firmware-2.6.32-358.0.1.el6.noarch >> kernel-2.6.32-358.0.1.el6.x86_64 >> kernel-devel-2.6.32-279.19.1.el6.x86_64 >> kernel-devel-2.6.32-358.0.1.el6.x86_64 >> kernel-2.6.32-279.9.1.el6.x86_64 >> libreport-plugin-kerneloops-2.0.9-15.el6.centos.x86_64 >> kernel-2.6.32-279.22.1.el6.x86_64 >> kernel-devel-2.6.32-279.9.1.el6.x86_64 >> >> This is from a VM that succeeded with the update to the "359" >> kernel. There are three more like that. >> >> Emmett >> > > You are giving conflicting information. > > You indicated that the kernel that you are getting the panic on is: > > >> Kernel panic - Not syncing: Attempted to kill init! > >> Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1 > > i.e., ...358.2.1 > > What you are showing as available from @updates and installed in the > VM that is working is: > > kernel.x86_64 2.6.32-358.0.1.el6 @updates > > kernel-2.6.32-358.0.1.el6.x86_64 > > i.e., ...358.0.1 > > > RedHat released ...358.2.1 earlier today, but I haven't seen centos > announce its release yet, and it's not available from the centos > repositories as of a few moments ago. So, the VM that is ok is using > ...358.0.1, the centos released kernel. The one that is panic would > appear to have come from elsewhere. > > Also note, it's the "358", not "359" kernel: > > > This is from a VM that succeeded with the update to the "359" > > kernel. There are three more like that. Yes, kernel "358". the "359" was a typo. And... the kernel panic lines were transcribed for a photo I took of the screen after the failed boot. On second look I see that the version is 2.6.32-358.0.1.el6.x86_64. So let's start again. Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1 After yum upgrade --enablerepo=epel on two of five machines, one of which is the host for the three VM's that succeeded and the one that failed, just as the host. I have a screen shot of that VM's boot failure, but I don't know the proper way to include it in a post. I've uninstalled that kernel and ran yum upgrade again, it still fails on that kernel, on both the host and the VM. I suppose the good thing is that it happened on a VM guest that is not critical, so I don't have to experiment with the host that has four important guests running on it. Any ideas? Emmett

6 16

CentOS-announce Digest, Vol 97, Issue 9
by centos-announce-request＠centos.org 16 Mar '13

16 Mar '13

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. qaweb.dev.centos.org is now gone (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Fri, 15 Mar 2013 13:35:15 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] qaweb.dev.centos.org is now gone To: CentOS Announcements List <centos-announce(a)centos.org> Message-ID: <51432393.1000404(a)centos.org> Content-Type: text/plain; charset=ISO-8859-1 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, It started off by being a great place to share qa content and let people track progress. But over the years, and with every passing release, its become lesser and lesser important. As of today, qaweb.dev.centos.org is now deprecated and is being decomissioned. The url will still respond and redirect people to a page that explains the situation. In the mean time, we are kicking off a stream of efforts to try and get better test coverage, more automation, more frequent test runs and above all - better communication to everyone on what the test results are, while further dropping the barriers for people to come along and write tests, help us push better code. Two efforts currently underway are getting a status like page online, that also shows recent history ( ref: http://lists.centos.org/pipermail/centos-devel/2013-March/009099.html ) and getting the Linux test project content included in the regular test suite that we run ( ref: http://ltp.sourceforge.net/ and http://lists.centos.org/pipermail/centos-devel/2013-March/009099.html ) How can you help ? Drop in on those conversations and talk to us, help us put in place the best possible solution. Contribute time by helping write more kickstart files, contribute tests and maybe even setup a test run environment in your facility that feeds back restults to our status tracker! Lots of opportunities for people to get involved with the CentOS QA and Development process. And as always, we are here to help with answers to questions or concerns you might have. Look at the http://wiki.centos.org/GettingHelp page for details on how you can engage with everyone else in the CentOS Community. Regards, - -- Karanbir Singh, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFDI5MACgkQMA29nj4Tz1uBOgCfZuC+MYuNuWAybChPAPgVu90/ 9KkAoLdWbsU7iFm+tHihMgerjvWCiuDj =ZZqP -----END PGP SIGNATURE----- ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 97, Issue 9 **********************************************

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