Discuss

discuss@lists.centos.org

34753 discussions

video capture
by Mark LaPierre 09 Jan '13

09 Jan '13

Hey all, I'm looking for a application that I can use to capture video from a USB web camera. I have Cheese Webcam Booth 2.28.1 installed but it leaves a lot to be desired in the video capture field. Things like actually working. It does an adequate job of snagging a batch of single images in burst mode. Any suggestions? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registerd Linux user No #267004 https://linuxcounter.net/ ****

5 4

CentOS 6.3 as Firewall/Router
by Tim Evans 08 Jan '13

08 Jan '13

I'm replacing an ancient Solaris 'ipf' firewall/router with a brand new CentOS 6.3 system. In the olden days, I successfully used the attached iptables script (as /etc/rc.local) on Red Hat 5.x systems, but this doesn't seem to be quite working on the new system. Specifically, while it seems to be routing ok, you cannot connect to anything on the inside net (e.g., with ssh or a browser) and cannot connect to the system with ssh or anything else from elsewhere on the inside net. Yet arp shows this system active. Is there obsolete stuff here, and/or anything missing that would cause this? Thanks. -- Tim Evans | 5 Chestnut Court UNIX System Admin Consulting | Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | tkevans(a)tkevans.com

11 16

CentOS-announce Digest, Vol 95, Issue 2
by centos-announce-request＠centos.org 08 Jan '13

08 Jan '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. CEBA-2013:0136 CentOS 5 bind Update (Johnny Hughes) 2. CEBA-2013:0138 CentOS 6 biosdevname Update (Johnny Hughes) 3. CEBA-2013:0137 CentOS 6 tomcat6 Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 7 Jan 2013 13:22:14 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0136 CentOS 5 bind Update To: centos-announce(a)centos.org Message-ID: <20130107132214.GA32377(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0136 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0136.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 40fac2e993877328c566ba57246c33b0b9bbcd29a08c7e405ed903c171b3c992 bind-9.3.6-20.P1.el5_8.6.i386.rpm 73379d4dfff47de2d8cc6dfae0e713bc3727708b76f62966775eb67fd9f4efb4 bind-chroot-9.3.6-20.P1.el5_8.6.i386.rpm 11719a1f759e5d98f700f0bd314705956736c3cab0f360c8ecd6bf4a3ca4b001 bind-devel-9.3.6-20.P1.el5_8.6.i386.rpm 2cf1694633dc8503ec601fdf3e7cbdd25c33c3a7d8f3e8a81b5e1d23d8118bc3 bind-libbind-devel-9.3.6-20.P1.el5_8.6.i386.rpm d260b2ba92cf06e58e79509225ad399b4714c321ad496776c913883c0ac09149 bind-libs-9.3.6-20.P1.el5_8.6.i386.rpm 7f1b9e543953776fabc3a3e34ee39e25491bf1b03f389b94c4a51fb9e8717e8a bind-sdb-9.3.6-20.P1.el5_8.6.i386.rpm ccc82d4d8ee1d7bb9282d2da2ed8838a3cba2086c8973506b7814384e6dcb856 bind-utils-9.3.6-20.P1.el5_8.6.i386.rpm 8592a57047db340f21695c6a722181cde81874e27122723844e4a28c2ab99ed3 caching-nameserver-9.3.6-20.P1.el5_8.6.i386.rpm x86_64: 562b9850da0301d447399dc544af3d261ea2cc63e9127ba6f17452796c05026a bind-9.3.6-20.P1.el5_8.6.x86_64.rpm f47c35cc148a9768e694652266e954b5b6ef4553f0618997a8d1423569076fcd bind-chroot-9.3.6-20.P1.el5_8.6.x86_64.rpm 11719a1f759e5d98f700f0bd314705956736c3cab0f360c8ecd6bf4a3ca4b001 bind-devel-9.3.6-20.P1.el5_8.6.i386.rpm 259dbd28bb991d3226d2cc33dc8a1e4f324d9a8e2413f902454587d6f136de18 bind-devel-9.3.6-20.P1.el5_8.6.x86_64.rpm 2cf1694633dc8503ec601fdf3e7cbdd25c33c3a7d8f3e8a81b5e1d23d8118bc3 bind-libbind-devel-9.3.6-20.P1.el5_8.6.i386.rpm a8e43752999deaa5eafef084588c13e5af88477300a2d40dc1a70efa45003030 bind-libbind-devel-9.3.6-20.P1.el5_8.6.x86_64.rpm d260b2ba92cf06e58e79509225ad399b4714c321ad496776c913883c0ac09149 bind-libs-9.3.6-20.P1.el5_8.6.i386.rpm 1f4a495fa32bf2df56f3246862b9137584b70147184e788433a9bda8c97c1202 bind-libs-9.3.6-20.P1.el5_8.6.x86_64.rpm dbce5f540a23e60d9a4983750a9b71ceaf1e83e69c46dd03a5289d3acea3c8ed bind-sdb-9.3.6-20.P1.el5_8.6.x86_64.rpm 82e8317a5c423be7d3f9fa6062aeeab5ce3bbf17c58b6be680eeb4d15337b14f bind-utils-9.3.6-20.P1.el5_8.6.x86_64.rpm d5b94ab5961f2f8e5e3eebf385d306d5a222d7857940e2cf94d324fd5c715711 caching-nameserver-9.3.6-20.P1.el5_8.6.x86_64.rpm Source: be82b584aa7f04cfca033bb0c7f312d032934f4931f51ac1793dbf79bd2ed1a3 bind-9.3.6-20.P1.el5_8.6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 7 Jan 2013 17:10:09 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0138 CentOS 6 biosdevname Update To: centos-announce(a)centos.org Message-ID: <20130107171009.GA11794(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0138 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0138.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ca57b7da61afdaabffd43fb0ee319e16586ff0c40a1bbad1ea229eeba0c311ed biosdevname-0.3.11-1.el6_3.1.i686.rpm x86_64: fd1bd265033694aa12264416e6836f950cb004e08ef82293db850ef3ded3880f biosdevname-0.3.11-1.el6_3.1.x86_64.rpm Source: a4cb2eebd0c298bac1d173eddab9c746c9bc228d17f93c2a3921209bf489f44b biosdevname-0.3.11-1.el6_3.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Mon, 7 Jan 2013 17:10:21 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0137 CentOS 6 tomcat6 Update To: centos-announce(a)centos.org Message-ID: <20130107171021.GA11955(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0137 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0137.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 19f46f7cb3322fb154e89660a8ea3dcf821d3f19f83056498ec5ec5b07da87c6 tomcat6-6.0.24-48.el6_3.noarch.rpm 792b710dadb4cbb005682a6f4df394f0408fac75e5003417bca245c60bca12f8 tomcat6-admin-webapps-6.0.24-48.el6_3.noarch.rpm fc69216cbde615ec6a89d7fd791bf8f40f2ed0365756a7068269bb1db2b03fad tomcat6-docs-webapp-6.0.24-48.el6_3.noarch.rpm e2782440204506f631e347ce5566b2b0f25a56621d23a3cde7e332d1c83eb29e tomcat6-el-2.1-api-6.0.24-48.el6_3.noarch.rpm b2fd68cf9558e3c657d03ba3734bc9462f916b9e0a5539745966d16c504f1474 tomcat6-javadoc-6.0.24-48.el6_3.noarch.rpm a8b7769c604b7d7f73023a5e8ae2cafb7713b229deb1ed1d8039685c94ac830e tomcat6-jsp-2.1-api-6.0.24-48.el6_3.noarch.rpm a965c3f30b9309f732bd711b6311b4f67748958fc329c70c6e0973fde8f07084 tomcat6-lib-6.0.24-48.el6_3.noarch.rpm 898f2db4bfb4825672dc3395612fb7514a8af96b3fd360a9be79efaa7beb54c3 tomcat6-servlet-2.5-api-6.0.24-48.el6_3.noarch.rpm 88f6cfa69cd0fcf1d27f2b894182b4f13cca4f9c3cc24feb58ad7d7173b0e8c3 tomcat6-webapps-6.0.24-48.el6_3.noarch.rpm x86_64: 19f46f7cb3322fb154e89660a8ea3dcf821d3f19f83056498ec5ec5b07da87c6 tomcat6-6.0.24-48.el6_3.noarch.rpm 792b710dadb4cbb005682a6f4df394f0408fac75e5003417bca245c60bca12f8 tomcat6-admin-webapps-6.0.24-48.el6_3.noarch.rpm fc69216cbde615ec6a89d7fd791bf8f40f2ed0365756a7068269bb1db2b03fad tomcat6-docs-webapp-6.0.24-48.el6_3.noarch.rpm e2782440204506f631e347ce5566b2b0f25a56621d23a3cde7e332d1c83eb29e tomcat6-el-2.1-api-6.0.24-48.el6_3.noarch.rpm b2fd68cf9558e3c657d03ba3734bc9462f916b9e0a5539745966d16c504f1474 tomcat6-javadoc-6.0.24-48.el6_3.noarch.rpm a8b7769c604b7d7f73023a5e8ae2cafb7713b229deb1ed1d8039685c94ac830e tomcat6-jsp-2.1-api-6.0.24-48.el6_3.noarch.rpm a965c3f30b9309f732bd711b6311b4f67748958fc329c70c6e0973fde8f07084 tomcat6-lib-6.0.24-48.el6_3.noarch.rpm 898f2db4bfb4825672dc3395612fb7514a8af96b3fd360a9be79efaa7beb54c3 tomcat6-servlet-2.5-api-6.0.24-48.el6_3.noarch.rpm 88f6cfa69cd0fcf1d27f2b894182b4f13cca4f9c3cc24feb58ad7d7173b0e8c3 tomcat6-webapps-6.0.24-48.el6_3.noarch.rpm Source: 5d9fd4691d754158443d9dfbf3a5377dcdd66d6249e7fc56d5f4fb504fb2a5f8 tomcat6-6.0.24-48.el6_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 95, Issue 2 **********************************************

1 0

Re: [CentOS] rsync and selinux
by James B. Byrne 08 Jan '13

08 Jan '13

On Mon, January 7, 2013 06:59, lhecking(a)users.sourceforge.net wrote: > I'm trying to use rysnc to back up some directories on a CentOS6 > machine that uses selinux in enforcing mode. Most files didn't > transfer, so I tried the example from rsync_selinux(8): > > Allow rsync servers to read the /var/rsync directory by adding > the pub- > lic_content_t file type to the directory and by restoring > the file > type. > > semanage fcontext -a -t public_content_t "/var/rsync(/.*)?" > restorecon -F -R -v /var/rsync > > except I substituted /etc for /var/rsync. > > Big mistake. Most or all services with config files under /etc could > no longer read their config files, including ssh. It looks like the > selinux type was substituted rather than added? Thankfully, I was > able to recover. > > What is the correct way to give rsync full access to everything under > selinux? > I use rsync extensively to transfer entire systems from and to SElinux enforcing environments and have never had a problem with reads using rsync when logged on as the root user. My typical command line is some variation of the following: /usr/bin/rsync -avX --delete-after --specials --times \ --exclude-from=/root/rsync.d/exclude.list \ 192.168.216.29:/* /. Are you connecting as the root user? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

4 5

Disk error
by Emmett Culley 08 Jan '13

08 Jan '13

For some time I have been seeing disk errors in the syslog every seven days. Until today it always happens Sunday morning at 8:13 AM, plus or minus a minute or two. Yesterday it happened at 1:13 AM. Here are the pertinent log entries for the latest occurrence: Jan 6 01:12:29 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:12:29 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:12:29 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:12:29 g2 kernel: ata9.00: cmd 25/00:00:00:fe:d5/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:12:29 g2 kernel: res 51/40:00:19:ff:d5/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:12:29 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:12:29 g2 kernel: ata9.00: error: { UNC } Jan 6 01:12:29 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:12:29 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:12:29 g2 kernel: ata9: EH complete Jan 6 01:12:33 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:12:33 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:12:33 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:12:33 g2 kernel: ata9.00: cmd 25/00:00:00:fe:d5/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:12:33 g2 kernel: res 51/40:00:7c:ff:d5/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:12:33 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:12:33 g2 kernel: ata9.00: error: { UNC } Jan 6 01:12:33 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:12:33 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:12:33 g2 kernel: ata9: EH complete Jan 6 01:13:06 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:13:06 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:13:06 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:13:06 g2 kernel: ata9.00: cmd 25/00:00:00:bf:d6/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:13:06 g2 kernel: res 51/40:00:db:bf:d6/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:13:06 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:13:06 g2 kernel: ata9.00: error: { UNC } Jan 6 01:13:07 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:13:07 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:13:07 g2 kernel: ata9: EH complete Jan 6 01:13:10 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:13:10 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:13:10 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:13:10 g2 kernel: ata9.00: cmd 25/00:00:00:bf:d6/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:13:10 g2 kernel: res 51/40:00:db:bf:d6/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:13:10 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:13:10 g2 kernel: ata9.00: error: { UNC } Jan 6 01:13:10 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:13:10 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:13:10 g2 kernel: ata9: EH complete Jan 6 01:13:14 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:13:14 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:13:14 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:13:14 g2 kernel: ata9.00: cmd 25/00:00:00:bf:d6/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:13:14 g2 kernel: res 51/40:00:db:bf:d6/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:13:14 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:13:14 g2 kernel: ata9.00: error: { UNC } Jan 6 01:13:14 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:13:14 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:13:14 g2 kernel: ata9: EH complete Jan 6 01:13:17 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:13:17 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:13:17 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:13:17 g2 kernel: ata9.00: cmd 25/00:00:00:bf:d6/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:13:17 g2 kernel: res 51/40:00:db:bf:d6/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:13:17 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:13:17 g2 kernel: ata9.00: error: { UNC } Jan 6 01:13:18 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:13:18 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:13:18 g2 kernel: ata9: EH complete Jan 6 01:13:21 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:13:21 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:13:21 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:13:21 g2 kernel: ata9.00: cmd 25/00:00:00:bf:d6/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:13:21 g2 kernel: res 51/40:00:db:bf:d6/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:13:21 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:13:21 g2 kernel: ata9.00: error: { UNC } Jan 6 01:13:21 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:13:21 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:13:21 g2 kernel: ata9: EH complete Jan 6 01:13:25 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:13:25 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:13:25 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:13:25 g2 kernel: ata9.00: cmd 25/00:00:00:bf:d6/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:13:25 g2 kernel: res 51/40:00:db:bf:d6/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:13:25 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:13:25 g2 kernel: ata9.00: error: { UNC } Jan 6 01:13:25 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:13:25 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:13:25 g2 kernel: sd 8:0:0:0: [sdg] Unhandled sense code Jan 6 01:13:25 g2 kernel: sd 8:0:0:0: [sdg] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jan 6 01:13:25 g2 kernel: sd 8:0:0:0: [sdg] Sense Key : Medium Error [current] [descriptor] Jan 6 01:13:25 g2 kernel: Descriptor sense data with sense descriptors (in hex): Jan 6 01:13:25 g2 kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Jan 6 01:13:25 g2 kernel: 04 d6 bf db Jan 6 01:13:25 g2 kernel: sd 8:0:0:0: [sdg] Add. Sense: Unrecovered read error - auto reallocate failed Jan 6 01:13:25 g2 kernel: sd 8:0:0:0: [sdg] CDB: Read(10): 28 00 04 d6 bf 00 00 02 00 00 Jan 6 01:13:25 g2 kernel: ata9: EH complete There is nothing in /etc/cron.weekly, nor are there any root crontab entries. Any suggestions for investigating this issue would be much appreciated. Emmett

4 5

rsync and selinux
by lhecking＠users.sourceforge.net 07 Jan '13

07 Jan '13

I'm trying to use rysnc to back up some directories on a CentOS6 machine that uses selinux in enforcing mode. Most files didn't transfer, so I tried the example from rsync_selinux(8): Allow rsync servers to read the /var/rsync directory by adding the pub- lic_content_t file type to the directory and by restoring the file type. semanage fcontext -a -t public_content_t "/var/rsync(/.*)?" restorecon -F -R -v /var/rsync except I substituted /etc for /var/rsync. Big mistake. Most or all services with config files under /etc could no longer read their config files, including ssh. It looks like the selinux type was substituted rather than added? Thankfully, I was able to recover. What is the correct way to give rsync full access to everything under selinux?

3 3

pavucontrol
by Phil Savoie 06 Jan '13

06 Jan '13

Hello, I have not been able to find this util for centos 6.3. Is it around somewhere? Thanks, Phil

2 2

CentOS 5.7 eth0, eth1 and arpwatch flip flops
by Gavin Henry 05 Jan '13

05 Jan '13

Dear all, Has anyone experienced this whilst running DRBD over eth1 between two CentOS 5.7 servers? eth1 is a private IP address, unroutable. eth0 is the public address. CentOS will reply sometimes once every 3 days or every 14mins~ saying "My public IP is on eth1" to arp requests when it's not, it's eth0. This freezes traffic and causes issues. We've looked at arp* /etc/sysctl.conf etc. and arptables, but wondered if anyone had a recipe? We have this already which didn't help as it happened Christmas Eve too as we kept eth1 up for a few days to test: # For the dual interface - 06.12.12 net.ipv4.conf.eth0.arp_filter = 1 net.ipv4.conf.eth0.arp_ignore = 1 net.ipv4.conf.eth1.arp_filter = 1 net.ipv4.conf.eth1.arp_ignore = 1 net.ipv4.conf.all.arp_filter = 1 eth0 and eth1 are on the same VLAN/broadcast domain, but eth1 is a 169.xx and eth0 is a routable public IP. We're having to shut eth1 down and bring it up for sync at night. Thanks, Gavin.

4 9

High Availability questions
by Steve Campbell 04 Jan '13

04 Jan '13

I'm trying to set up a small cluster using the High Availability and High Availability Management groups. I'd like to run this on 3 different machines, one being a "management" machine and the other two being the actual cluster. It doesn't seem to want to cooperate. I can set the cluster nodes up just fine, working from the management server. As soon as I try adding an "IP address" to the cluster, everything goes south. I can no longer use luci on any of the three machines. I can start luci on any of the 3 servers, but the cluster doesn't show any more. If I try and recreate the cluster, it indicates the cluster already exists. I can't find anything in the logs other than a bunch of python errors similar to perl errors, and those don't really seem to be indicative of hard errors. I've got this scheme running successfully on 3 virtual machines on a single host, and that seems to work just fine. Real servers are beating me up. Any suggestions, please? steve campbell

2 2

rup on CentOS6
by lhecking＠users.sourceforge.net 04 Jan '13

04 Jan '13

I just noticed an interesting behaviour of rup on CentOS5/6: run without any host args, it never prints results for CentOS6 machines. However, if a CentOS6 machine is queried directly, there is a result. It doesnt't matter whether the querying host runs CentOS5 or CentOS6. # rup |grep centos6host # rup centos6host centos6host up 12 days, 19:33, load average: 0.22 0.18 0.11 # With tcpdump, I can see that no rpc requests are issued to the host in the first case. Is there an explanation?

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