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. CESA-2012:1156 Moderate CentOS 6 kernel Update (Johnny Hughes)
----------------------------------------------------------------------
Message: 1
Date: Wed, 15 Aug 2012 04:21:07 +0000
From: Johnny Hughes <johnny(a)centos.org>
Subject: [CentOS-announce] CESA-2012:1156 Moderate CentOS 6 kernel
Update
To: centos-announce(a)centos.org
Message-ID: <20120815042107.GA19050(a)chakra.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2012:1156 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-1156.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
401fe56789a69f3ca2c7f327dca1bedbe3e122b86233f178f7bd47f778c0adb1 kernel-2.6.32-279.5.1.el6.i686.rpm
f7f4959375076ce578db837cff336b5ddcdeed1f72ee5e4dbf1475a8f5fad4af kernel-debug-2.6.32-279.5.1.el6.i686.rpm
4902e0cf5cee8c2fa7314db34498d612abe5e3db22d76cd6e02755f21f0d41ef kernel-debug-devel-2.6.32-279.5.1.el6.i686.rpm
780a2a8ab3b0d2b559179e171edcb1f6c58d15b7c6ce514273699dcdf1ecb19f kernel-devel-2.6.32-279.5.1.el6.i686.rpm
14aa1fc5cfa421605236ebb4e79aa4ef0b4dde974255398dd3b50932f581c1a6 kernel-doc-2.6.32-279.5.1.el6.noarch.rpm
4e4bc121b137cc83dfe9c9ca5497f7fbf1daca41e2668128accd06cc550fe04e kernel-firmware-2.6.32-279.5.1.el6.noarch.rpm
f2d9d272cb1bcf13f821b0b1be2943753a135c33c43cb92642f38c05db461b50 kernel-headers-2.6.32-279.5.1.el6.i686.rpm
71daaf6e22b7f5a71c0d836875c3a1101b5d071c7cebed79b73b5a8244f98ec9 perf-2.6.32-279.5.1.el6.i686.rpm
f00d8c073dfe7b88e9f7caded9be261f8ebc45356c35692554624b8fa713bd98 python-perf-2.6.32-279.5.1.el6.i686.rpm
x86_64:
fdfb26523bcc4ca77ecdd182d31d78d83b866d1283b3dfc624c34e70f69bd61b kernel-2.6.32-279.5.1.el6.x86_64.rpm
bdf821479037c870f2a926fd55509af7ad88cd5c2d312497e61530d0d43f2438 kernel-debug-2.6.32-279.5.1.el6.x86_64.rpm
2c9c0a7d50378f70ac80582cb5636d2b36d9fb8615b4b72ea2fc2df889b5656e kernel-debug-devel-2.6.32-279.5.1.el6.x86_64.rpm
6ad2ed5933e22186c4e97c64ffd0ddfbded48dea2ba5f3291e47963127c56a34 kernel-devel-2.6.32-279.5.1.el6.x86_64.rpm
29319bb3c31c5ee6d370d0da82a51851f24e54688136104c2694b8b0365adcc6 kernel-doc-2.6.32-279.5.1.el6.noarch.rpm
1e144afd01a3be84b9e698dedbe4cd95fc99025f23e583ac7498ac3568dc86b6 kernel-firmware-2.6.32-279.5.1.el6.noarch.rpm
f5bc0117e4371037084181e899b40b6da53e0666d932ba9aacf0950a400cda8d kernel-headers-2.6.32-279.5.1.el6.x86_64.rpm
2394f7b0fa0de3b86d21e9903f6886323fd42ce7ab1f8f3f3a8a52723eb37c75 perf-2.6.32-279.5.1.el6.x86_64.rpm
d9702f2bf017d839e9923df390b31e3e75bca11613672d8c620fe19eb8971f16 python-perf-2.6.32-279.5.1.el6.x86_64.rpm
Source:
2dbace349e15081cbd991c5890958e6a4efcc544de2a04eb7cf5b4cb58d614fe kernel-2.6.32-279.5.1.el6.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 90, Issue 9
**********************************************
On Wed, August 15, 2012 09:15, Reindl Harald wrote:
> did you read the output you posted?
> http://lmgtfy.com/?q=unable+to+load+firmware+patch+rtl_nic%2Frtl8168d-1.fw
r8169 0000:01:00.0: eth1: invalid firwmare
> r8169 0000:01:00.0: eth1: unable to load firmware patch
> rtl_nic/rtl8168d-1.fw (-22)
I cannot seem to find a fix for this even given the references
provided. However, I have discovered that eth1 has problems on the
second host as well, it just does not generate the same messages:
[root@vhost02 ~]# grep eth /var/log/messages
Aug 13 17:10:18 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 13 17:16:19 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:23:39 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:23:41 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:37:42 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:37:44 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:38:51 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:38:53 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:40:17 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:40:19 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:40:50 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:40:52 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 15:26:20 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 15:26:22 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 05:28:39 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 05:28:42 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 05:40:32 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 05:40:34 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 05:47:34 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 05:47:36 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 05:48:21 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 05:48:23 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:16:53 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:16:54 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:18:35 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:18:37 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:22:27 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:22:29 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:31:36 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:31:38 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:40:27 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:40:29 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:41:40 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:41:42 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:49:39 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:49:41 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:01:59 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:02:01 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:04:08 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:04:10 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:07:28 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:07:30 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:09:54 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:09:56 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:12:07 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:12:09 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:13:58 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:14:00 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:17:04 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:17:06 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:20:14 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:20:16 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:29:28 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:29:30 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 09:31:56 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 09:31:58 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 09:33:18 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 09:33:20 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
So, my questions are: What is the problem and how do I fix it for both
hosts?
--
*** 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
I am trying to change my subscription option to a daily digest but am
unable to log in to change my options....
--
Ed Gurski
(ed(a)gurski.com)
Registered Linux User 458454
Hi,
I do have one iscsi storage with 4 GBit nics of which currently only one
is configured with an ip and which is in productive use by one cent os
6.3 server.
Doing some research brought me to the idea to use some nic bonding or
multipathing for that storage, but multipathing I did about four or five
years ago only once :)
Furthormore I can't find the ultimate answer (may be there is not such)
what will be better for us:
bonding or multipathing.
The storage is used for backup; it's connected to an backupserver which
pulls data from different servers ... may be at the same time or one
after an other. The server uses two bonded nics to the LAN.
My question regarding the setup is, what might be good or better:
bonding or multipathing. We'd like to increase performance and nic
failover if one link breaks.
If multipathing is to be preferred, is it possible to preserve the data
currently saved on the storages ext4?
And googling shows up a lot of different how tos and the redhat doc; but
I din not found one describing a straight forward setup.
So thanks a lot for any suggestion or comments!
Regards . Götz
--
Götz Reinicke
IT-Koordinator
Tel. +49 7141 969 82 420
Fax +49 7141 969 55 420
E-Mail goetz.reinicke(a)filmakademie.de
Filmakademie Baden-Württemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de
Eintragung Amtsgericht Stuttgart HRB 205016
Vorsitzender des Aufsichtsrats:
Jürgen Walter MdL
Staatssekretär im Ministerium für Wissenschaft,
Forschung und Kunst Baden-Württemberg
Geschäftsführer:
Prof. Thomas Schadt
On Mon, August 13, 2012 18:48, Ned Slider wrote:
> On 13/08/12 19:50, James B. Byrne wrote:
>>
>> On Mon, August 13, 2012 10:37, Ned Slider wrote:
>>
>>> Faulty hardware maybe? Try a reboot and see if it reappears. If
>>> it's
>>> located on a card try reseating the card (although I suspect this
>>> is
>>> an integrated NIC on the motherboard?).
>>>
>>> The chipset is not necessarily the same in the second example
>>> (different revision); RTL8111/8168B is not RTL8168d/8111d. They
>>> probably do use the same driver but I'd need to see the
>>> Vendor:Device ID pairing to know for sure.
>>
>>
>> Eth1 is an xpci card sold by StarTech. A system with an identical
>> card reports this:
>>
>
> OK, I'd definitely try reseating the card and if you still get no joy
> I'd swap it out for a replacement.
>
>> for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1
>> }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done
I swapped the suspect card and rebooted the host. After some fussing
about with udev I managed to get the new card recognized as eth1 (vice
eth2 as udev kept insisting).
I will do a transfer test later today and see if it stays up. The
original failed in the midst of an sftp transfer.
--
*** 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
On Wed, 2012-08-15 at 12:47 +0100, Nux! wrote:
> On 14.08.2012 14:06, Adam Tauno Williams wrote:
> > On Tue, 2012-08-14 at 07:28 +0100, Nux! wrote:
> >> On 13.08.2012 22:46, Gregory Machin wrote:
> >> > Hi.
> >> > Thanks for the feed back.
> >> Why not Clamav?
> >> It has othe n-access thingy as well.
> >> http://www.clamav.net/doc/latest/html/node21.html
> > "you shouldn't run Dazuko on production systems"
> > But, if your clients are Windows boxes via Samba, you can perform
> > on-demand file access via Samba + CLAMAV using a VFS module. This
> > works
> > very well. Then files detected to contain malware cannot be read or
> > saved, and the administrator can be notified.
> > I don't think that really helps the LINUX desktop however.
> Thanks for the tip with the VFS. Not much of a Samba user here, but
> definitely good advice for the future.
> Searching a bit reveals multiple ways of using this VFS feature; do you
> have a recommended way of doing it?
The examples are pretty straight-forward. Just make sure you are
looking at docs for samba-virusfilter and not the older docs for
samba-vscan.
<http://www.whitemiceconsulting.com/2011/11/samba-vscan-is-dead-long-live-sa…>
<http://www.whitemiceconsulting.com/2011/11/samba-virusfilter-013-released.h…>
Is there any chance the system-config-netboot* rpms upstream removed from
CentOS6 could be provided in extras? The CentOS5 SRPM builds cleanly under
CentOS6, and upstream's workaround is insufficient as it only covers
diskless clients, not helpful if you need pxeos.
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/h…
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-2012:1164 CentOS 6 iok FASTTRACK Update (Johnny Hughes)
2. CEBA-2012:1159 CentOS 5 specspo FASTTRACK Update (Johnny Hughes)
3. CEBA-2012:1167 CentOS 5 mt-st FASTTRACK Update (Johnny Hughes)
----------------------------------------------------------------------
Message: 1
Date: Mon, 13 Aug 2012 18:08:09 +0000
From: Johnny Hughes <johnny(a)centos.org>
Subject: [CentOS-announce] CEBA-2012:1164 CentOS 6 iok FASTTRACK
Update
To: centos-announce(a)centos.org
Message-ID: <20120813180809.GA12006(a)chakra.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2012:1164
Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1164.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
6bad0a5051955559c711206f6a1fd20a011b58abd6774638ecc351a772562cc5 iok-1.3.13-3.el6.i686.rpm
x86_64:
3bca5b14d6a8a8c8f889987a9ff6193a154f60eef5225ba87d19a088910f58d1 iok-1.3.13-3.el6.x86_64.rpm
Source:
106bdcdbe4914d71b8516e9b5386f60945e16102f2b5d8caf52d7a2ba49278da iok-1.3.13-3.el6.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos(a)irc.freenode.net
------------------------------
Message: 2
Date: Mon, 13 Aug 2012 20:26:44 +0000
From: Johnny Hughes <johnny(a)centos.org>
Subject: [CentOS-announce] CEBA-2012:1159 CentOS 5 specspo FASTTRACK
Update
To: centos-announce(a)centos.org
Message-ID: <20120813202644.GA18110(a)chakra.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2012:1159
Upstream details at : http://rhn.redhat.com/errata/RHBA-2012-1159.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
00532d7d2867cf89a8d2d916b462dd755d27cf2ad4e5b49f11ce628b2e24ebec specspo-13-4.el5.centos.noarch.rpm
x86_64:
00532d7d2867cf89a8d2d916b462dd755d27cf2ad4e5b49f11ce628b2e24ebec specspo-13-4.el5.centos.noarch.rpm
Source:
f54b6f21e393d48ce6dbb57ca3bf67b581d283868617c009c78a6c4f067c8232 specspo-13-4.el5.centos.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos(a)irc.freenode.net
------------------------------
Message: 3
Date: Tue, 14 Aug 2012 13:29:48 +0000
From: Johnny Hughes <johnny(a)centos.org>
Subject: [CentOS-announce] CEBA-2012:1167 CentOS 5 mt-st FASTTRACK
Update
To: centos-announce(a)centos.org
Message-ID: <20120814132948.GA2704(a)chakra.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2012:1167
Upstream details at : http://rhn.redhat.com/errata/RHBA-2012-1167.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
5b0aef68a5a3aa5ce3385beaf15d59910683eaa9888a7d6b6aae50ed845bad04 mt-st-0.9b-4.el5.i386.rpm
x86_64:
d266be9a5941fb3f007f8d91eac5a394b5510c72bd1453d259c8d7b424d9f6bb mt-st-0.9b-4.el5.x86_64.rpm
Source:
1c274861c3b06cefa64cf50d5d64decd8275ba40294727116cafff5c449ec377 mt-st-0.9b-4.el5.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 90, Issue 8
**********************************************