- Discuss - lists.centos.org

reload /sbin/init
by Markus Falb 08 Jan '15

08 Jan '15

Hi, There was an update of glibc on CentOS 6 http://lists.centos.org/pipermail/centos-announce/2015-January/020863.html and now: # needs-restarting 1 : /sbin/init How do i tell /sbin/init to use the updated files from glibc without a reboot? -- Kind Regards, Markus Falb

2 1

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

08 Jan '15

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-2015:0013 CentOS 6 resource-agents BugFix Update (Johnny Hughes) 2. CESA-2105:X001 Important xen kernel libvirt python-virtinst e1000e (Xen4CentOS Only) Security Update (Johnny Hughes) 3. CESA-2015:0016 Moderate CentOS 6 glibc Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 7 Jan 2015 15:41:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:0013 CentOS 6 resource-agents BugFix Update Message-ID: <20150107154150.GA48392(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:0013 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0013.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bb3c1912b3220618cec8ff0d98875d9dfabffa44c177e2b18d5f1271e61ab694 resource-agents-3.9.5-12.el6_6.2.i686.rpm x86_64: 1c6dd42edf5201b0ea8dda31cae2d56f645eee09f21a830dec1bf7a4a97a8360 resource-agents-3.9.5-12.el6_6.2.x86_64.rpm 0acba837ca1cd6a19704f2e065009f3d4fb05c4f24607d129ffb87e98a188358 resource-agents-sap-3.9.5-12.el6_6.2.x86_64.rpm Source: 705658c1e708c1d614564800da312149470c77b159bad2d95dcc566b5be0ea10 resource-agents-3.9.5-12.el6_6.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 7 Jan 2015 16:40:55 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2105:X001 Important xen kernel libvirt python-virtinst e1000e (Xen4CentOS Only) Security Update Message-ID: <20150107164055.GA56550(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii The following packages are updated for Xen4CentOS for CentOS 6: Source: 942bc436e401c798991ae4ca956082c12a5a3b65ec53cd7ec9901dda7704f9b7 e1000e-2.5.4-3.10.63.2.el6.centos.alt.src.rpm aa46f97636568c46295d2d99f1e33b5fda50df707a2a8321a516200b8b4e95a6 kernel-3.10.63-11.el6.centos.alt.src.rpm ea44d2658e096ef6f00f7dfd4fecc6bff977d959563e4929539d23643b134c3a libvirt-0.10.2.8-9.el6.centos.alt.src.rpm 6638a40f4a1e1ac6a63aea6256f9f4c43c6281eb7db5f011c327cb3b472de871 python-virtinst-0.600.0-25.el6.centos.alt.src.rpm fac4802834313eb2e4bbfa67e518b2c3f7d5746cf2e3d4d8bf06d9414c1a69ad xen-4.2.5-38.el6.centos.alt.src.rpm x86_64: 2c8f12408cfe619b2cf9d0eaf48df915f5027b835fdcd3011b21a34ae78fa304 e1000e-2.5.4-3.10.63.2.el6.centos.alt.x86_64.rpm c9ff6fde1abc5b7d98f1110149929781a5768e56f49e0f924d3507a780bf8361 kernel-3.10.63-11.el6.centos.alt.x86_64.rpm a4354c3ecb987d8a71cfa2757a97258eaf757c5be8609cd5e591e24b44fa3c7c kernel-devel-3.10.63-11.el6.centos.alt.x86_64.rpm d385b51f0e2df5bcdf6b770b55d6c7b5db838b8082c122eb74bccd708c8e48eb kernel-doc-3.10.63-11.el6.centos.alt.noarch.rpm 7d8e93f0aa85695643272c8fa51aa8cb9b82b542fe458e9a79e068fe6415778c kernel-firmware-3.10.63-11.el6.centos.alt.noarch.rpm 2c52e6f3fad408a4113c1b54c0c23fe3188d7c7d5586ba4d5ea8875b3bdf8351 kernel-headers-3.10.63-11.el6.centos.alt.x86_64.rpm cc449d9ad8ffb0a85594891da53f6574ae1092137e398529322cc8a52cf91708 libvirt-0.10.2.8-9.el6.centos.alt.x86_64.rpm b4e4b4972b7b2d305a415ffb24a56e1ac4ff40f38c183b138be5a6e92c97e0ea libvirt-client-0.10.2.8-9.el6.centos.alt.x86_64.rpm 304794603b7240170b1e0de2fb0dab820b373d8ba99a62157780062bc35b1ace libvirt-daemon-0.10.2.8-9.el6.centos.alt.x86_64.rpm 13247406443b9d1ae7916ef8c527560f44f2b97a79d6a30da05215ccf75abd85 libvirt-daemon-config-network-0.10.2.8-9.el6.centos.alt.x86_64.rpm ba40af0619fe878d0e8a7df4cc7ed18583014b762c7df085c128808b17b082b8 libvirt-daemon-config-nwfilter-0.10.2.8-9.el6.centos.alt.x86_64.rpm 884523cd5effc77a0f1635dbd8b31b65652f0f47c8fa3766e3e1269f8265a3a8 libvirt-daemon-driver-interface-0.10.2.8-9.el6.centos.alt.x86_64.rpm 6b5cf8f1558539dfbc048ffcdfa5c088c91da4eeed3d81271e2e7d463bf857ed libvirt-daemon-driver-libxl-0.10.2.8-9.el6.centos.alt.x86_64.rpm 3ee246afb33447cb498ef380f6cdca7bf30a0e7e214afe741003a0b8a0b52464 libvirt-daemon-driver-lxc-0.10.2.8-9.el6.centos.alt.x86_64.rpm 7e188a365145e1ff3181f6dea5634eecccb6881119d940afe5fa5b7f77ec6df3 libvirt-daemon-driver-network-0.10.2.8-9.el6.centos.alt.x86_64.rpm 819dfe1938e4bd7aed780ce612fa24b60758c7318d5ac30fc9ac049d966bdcfd libvirt-daemon-driver-nodedev-0.10.2.8-9.el6.centos.alt.x86_64.rpm 71ca9d8ea49819c3684cd14d98ae1ab5143c2ac63318c3edff62ebc66b8b6b6b libvirt-daemon-driver-nwfilter-0.10.2.8-9.el6.centos.alt.x86_64.rpm 02507a39ad3614dffc8ad03700709017558fd15818d0f1e838cec8655c54526e libvirt-daemon-driver-qemu-0.10.2.8-9.el6.centos.alt.x86_64.rpm 6674c23f807ab5fd9dd00e658beb2a7d627fa65958fbaa5d1ad46e96f861657e libvirt-daemon-driver-secret-0.10.2.8-9.el6.centos.alt.x86_64.rpm b20cb8588282f47f5dab730ca3320480e0ac1746f8d5723d6517ce3d31861463 libvirt-daemon-driver-storage-0.10.2.8-9.el6.centos.alt.x86_64.rpm a3f2a58fcbe08ecd5c1704e36a81fc86dcec61f38cce7ce70bd4576c6c7d18a9 libvirt-daemon-driver-xen-0.10.2.8-9.el6.centos.alt.x86_64.rpm 06fd6ec2fa6e4175c51770d3a825d3115d731777006908e49378378ccf9bc757 libvirt-daemon-kvm-0.10.2.8-9.el6.centos.alt.x86_64.rpm 81a7f96bd97f7cb746c74ac779d51147f1de9fdc1e01f34cb3ac4a5386e22728 libvirt-daemon-lxc-0.10.2.8-9.el6.centos.alt.x86_64.rpm 471d338d2475f30ad1fc5155ae97b1ce0dc3d8a7021bc9d53eb9f1c4bd1ade0b libvirt-daemon-xen-0.10.2.8-9.el6.centos.alt.x86_64.rpm 06bd1208fbce65935ab192fc75c97ed74e928d4d17e92290d6fed6da57e65f22 libvirt-devel-0.10.2.8-9.el6.centos.alt.x86_64.rpm 61e06ed53b142944ab386587d1242a0f95486ad1935854d7d214508ec81292db libvirt-docs-0.10.2.8-9.el6.centos.alt.x86_64.rpm ce581b3d70d7b4d8982b285315518731f37ffaad2ec78b389e0e074fd020385c libvirt-lock-sanlock-0.10.2.8-9.el6.centos.alt.x86_64.rpm 56106bedfbfc6d8bd5095ea38df236aaed7a462c0cfc07942b51614650f53aa8 libvirt-python-0.10.2.8-9.el6.centos.alt.x86_64.rpm 3c8e89f5029f30574ab6ca88c46eba2af11ff73cc7d92a8a724e7484886c0f21 perf-3.10.63-11.el6.centos.alt.x86_64.rpm d3584e0235562bf5a2225dd7049ca4420b261bc19955009b3ae994a3811af69a python-virtinst-0.600.0-25.el6.centos.alt.noarch.rpm 7b50c868a1a7c92dd1e1bf7f4b05a3abed12561e289e9a41cf87ea18c9925b1c xen-4.2.5-38.el6.centos.alt.x86_64.rpm 1a10b5f778324f946922be87913e0902a15afaf4c3e0f88c38b843292163d578 xen-devel-4.2.5-38.el6.centos.alt.x86_64.rpm cf7de2648cf80e252c16c0c30dca44b064a0f3136b389b990558202c47f9c58c xen-doc-4.2.5-38.el6.centos.alt.x86_64.rpm 65c87da1e0ba2d36458aae2cfbd070843b36b8812432efba3431c8a68d33fadd xen-hypervisor-4.2.5-38.el6.centos.alt.x86_64.rpm d1ed1a6f0b0064251adce3ed501fe16c83139d6e730d77151feb1b6fe1248525 xen-libs-4.2.5-38.el6.centos.alt.x86_64.rpm a98ac4c5120f3a38ff926ea72048b327cc6d26d6de27519eb98b7f134296eccf xen-licenses-4.2.5-38.el6.centos.alt.x86_64.rpm 2fa4564b445251ee6c20ffbc62ac365bf368618c73503b34aceb8934a010add6 xen-ocaml-4.2.5-38.el6.centos.alt.x86_64.rpm 34b975cd3b396ce130819ecc87676fd2437292d8c43f3a3963d67c0e4a438248 xen-ocaml-devel-4.2.5-38.el6.centos.alt.x86_64.rpm 0e7dcd74118cb8c81e3756c9fce7ccc19fa1f0e1bfe2fc670b2f18297731213e xen-runtime-4.2.5-38.el6.centos.alt.x86_64.rpm ======================================================================== These updates address the following issues: e1000e: Just a rebuild of the module for the new kernel. ======================================================================== libvirt: One minor bugfix from the 0.10.2-maint tree at libvirt.org: http://libvirt.org/git/?p=libvirt.git;a=patch;h=a397e887ed40898cc177e118dff… ======================================================================== python-virtinst: 1. Upgraded to the version in CentOS-6.6 which is addressed here: https://rhn.redhat.com/errata/RHBA-2014-1444.html 2. Modified to use the tap2.5 interface in the Xen4CentOS6 tree. ======================================================================== Xen: http://xenbits.xen.org/xsa/advisory-109.html http://xenbits.xen.org/xsa/advisory-110.html http://xenbits.xen.org/xsa/advisory-111.html http://xenbits.xen.org/xsa/advisory-112.html http://xenbits.xen.org/xsa/advisory-113.html http://xenbits.xen.org/xsa/advisory-114.html http://xenbits.xen.org/xsa/advisory-116.html Xen CVE's: CVE-2014-8594, CVE-2014-8595, CVE-2014-8866, CVE-2014-8867, CVE-2014-9030, CVE-2014-9065, CVE-2014-9066, CVE-2015-0361 ======================================================================== Kernel: https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.57 https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.58 https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.59 https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.60 https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.61 https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.62 https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.63 Kernel CVE's: CVE-2014-3601, CVE-2014-3610, CVE-2014-3611, CVE-2014-3647, CVE-2014-7970, CVE-2014-7975 -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos at irc.freenode.net ------------------------------ Message: 3 Date: Wed, 7 Jan 2015 22:45:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:0016 Moderate CentOS 6 glibc Security Update Message-ID: <20150107224541.GA62721(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:0016 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-0016.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 24e8a54841d2f60b571da54c41c8b5e90713c920aa6b8d5fea15f4c59028393d glibc-2.12-1.149.el6_6.4.i686.rpm edc243ccfa7eb89a28cc1082e3155df817c5b34eca0b1bbb3af2b45abe28b25c glibc-common-2.12-1.149.el6_6.4.i686.rpm 2d8f8bef2ce971d98e331362e664e05b88671b05e49e938422fe710ad26cdd6c glibc-devel-2.12-1.149.el6_6.4.i686.rpm 0104e080dd839b3cf7485a8c32bcc2ecc99b46d65864e881dcc7a2b7a35c487c glibc-headers-2.12-1.149.el6_6.4.i686.rpm 96638cb9ac3ea855be459e3991e77e19fc841a3ea6bed0ec4024dfdd6aaab83a glibc-static-2.12-1.149.el6_6.4.i686.rpm c955dfa4af44ebc46209da9cca4fbacb9edea97b98c5df01f4d476a9b4c5d782 glibc-utils-2.12-1.149.el6_6.4.i686.rpm 2a94a269c924e0230c453eb40bed272d4fc602e866b870797f931692bb1e8b70 nscd-2.12-1.149.el6_6.4.i686.rpm x86_64: 24e8a54841d2f60b571da54c41c8b5e90713c920aa6b8d5fea15f4c59028393d glibc-2.12-1.149.el6_6.4.i686.rpm 561da2e99d2ca47f4443ffb6fdd02e44757f7586c3817148ce19efb3f94e20c0 glibc-2.12-1.149.el6_6.4.x86_64.rpm c7683cfbed7ff0f3367b28caa722866aee2df22e9b09eb6499d9b223602e3cee glibc-common-2.12-1.149.el6_6.4.x86_64.rpm 2d8f8bef2ce971d98e331362e664e05b88671b05e49e938422fe710ad26cdd6c glibc-devel-2.12-1.149.el6_6.4.i686.rpm 068c46be355df6e7accd944bb4149591e71b26bc4fc3e5fa104a4f41b80ba7dc glibc-devel-2.12-1.149.el6_6.4.x86_64.rpm 6eb86e7671f1ac126f0fc4fd610ba1d380954e59cfb2da5ca705ed9918af2ba5 glibc-headers-2.12-1.149.el6_6.4.x86_64.rpm 96638cb9ac3ea855be459e3991e77e19fc841a3ea6bed0ec4024dfdd6aaab83a glibc-static-2.12-1.149.el6_6.4.i686.rpm c7972b20d78c1f0c3da9efb0a7b4c5e98b998adea44594e517dcd803962b19d7 glibc-static-2.12-1.149.el6_6.4.x86_64.rpm 73089b23f0475c89c45279f33c19bdfa2d1893c9136ebcb440be1282d27deda7 glibc-utils-2.12-1.149.el6_6.4.x86_64.rpm f96f7bb4cb8b3b6c175b2267afbf8e76cbd1267d9534b12036f4f9ee67215807 nscd-2.12-1.149.el6_6.4.x86_64.rpm Source: 3a9aa47313be89b63fe9b6ce888a896110ccf769698bbbc34594245cd18c418c glibc-2.12-1.149.el6_6.4.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 119, Issue 2 ***********************************************

1 0

dovecot move doesn't work
by Chuck Campbell 08 Jan '15

08 Jan '15

I'm running centos 6.6 with the default 2.0.9-xxx dovecot. I run sa-learn against my spam_to_learn folder, then I wan to move those emails to a learned_spam folder. when I do a doveadm -Dv move -u user learned_spam mailbox 'spam_to_learn' ALL I get this result: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A] [-S <socket_path>] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S <socket_path>] <search query> fetch [-u <user>|-A] [-S <socket_path>] <fields> <search query> force-resync [-u <user>|-A] [-S <socket_path>] <mailbox> help <cmd> import [-u <user>|-A] [-S <socket_path>] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|]<ip/bits> log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [<ip/bits>] purge [-u <user>|-A] [-S <socket_path>] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S <socket_path>] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [<ip/bits>] this doesn't even list a move command, yet the dovecot pages show it and give examples. any suggestions? thanks, -chuck --

4 8

Re: [CentOS] reboot - is there a timeout on filesystem flush?
by John R Pierce 07 Jan '15

07 Jan '15

On 1/7/2015 12:50 PM, m.roth(a)5-cent.us wrote: > Right... but only cost 133% (about) more than consumer drives, as opposed > to the 300% that the "server/enterprise" grade drives' cost. well, those $$$ drives are likely SAS rather than SATA, and that has other advantages... 10k or 15k RPM gives you up to double the IOPS per spindle of a 7200rpm SATA drive (and WD Reds are only 5900 RPM, I believe?)... 2.5" enterprise disks let you have more smaller spindles in the same space (24-25 per 2U vs 12 for 3.5") for higher IO concurrency, and SAS supports multipathing (dual porting) for higher IO bandwidth, also SAS has tagged command queueing which often performs better than SATA NCQ under high IO concurrency workloads, like database servers. -- john r pierce 37N 122W somewhere on the middle of the left coast

2 1

Re: [CentOS] reboot - is there a timeout on filesystem flush?
by John R Pierce 07 Jan '15

07 Jan '15

On 1/7/2015 12:15 PM, m.roth(a)5-cent.us wrote: > Actually, the WD Reds and similar are just fine. those are specifically sold for use in small NAS (raid) environments, so yeah, they are configured 'correctly'. -- john r pierce 37N 122W somewhere on the middle of the left coast

1 0

Re: [CentOS] reboot - is there a timeout on filesystem flush?
by Les Mikesell 07 Jan '15

07 Jan '15

On Wed, Jan 7, 2015 at 10:15 AM, <m.roth(a)5-cent.us> wrote: >>> >> Yes - the unattended fsck fails. Personally, I'd prefer for the >> default run to use '-y' in the first place. It's not like I'm more >> likely than fsck to know how to fix it and it is very inconvenient on >> remote machines. The recent case was an opennms system updating a > <snip> > > In some ways, I prefer the fsck run by reboot to fail - that way, I see > it, and it most probably tells me that it's time to look at replacing the > disk. Seems random to me - not repeating on the same box, and rare enough that it is hard to make any generalization except that it is painful to talk some remote helper through the recovery process - usually involving emailing some cell phone photos of the console to figure out which partition has the problem. -- Les Mikesell lesmikesell(a)gmail.com

1 0

Re: [CentOS] Radeon graphics problems with CentOS 6.6
by Darby Vicker 07 Jan '15

07 Jan '15

I sent this last night but it didn't show up in the archives. Trying again without the attachment. Are messages with attachments blocked on this list? On Tue, Jan 6, 2015 at 11:50 PM, Darby Vicker <darby.vicker(a)gmail.com> wrote: > Thanks a ton for the suggestions and info everyone. > >> Two things I think you should consider doing... >> 1) in your next post (and any bugs you open), include the `uname -a` of >> the last known to work correctly CentOS/RHEL kernel, and the `uname -a` >> of the first known to not work correctly CentOS/RHEL kernel and the >> respective versions of radeon &| flrgx drivers. > > Sure. > > Last known kernel to work (pretty sure this is the last update under > CentOS 6.5): > Linux c6 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > > Kernels I've tried that don't work: > > kernel-2.6.32-504.el6.x86_64 > kernel-2.6.32-504.1.3.el6.x86_64 > kernel-2.6.32-504.3.3.el6.x86_64 > kernel-2.6.32-504.3.3.el6.centos.plus.x86_64 > > Graphics card: > > 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6530D] > > Open source driver version: > > xorg-x11-drv-ati-7.3.99-2.el6.x86_64 > > I tried the proprietary drivers from elrepo too: > > fglrx-x11-drv-14.9-1.el6.elrepo.x86_64 > > But it crashes X and also renders the system unreachable via ssh. When > X crashes with the open source driver, I can still get in via ssh. I > can boot to an older kernel with the fglrx drivers but graphics > performance is awful for some reason. > >> 2) try out elrepo's el6 kernel-lt & kernel-ml and see if they work >> correctly for you. I suggest this, because for me it did workaround an >> issue with intel chips (I guess I need to see what it will take to get >> the elrepo folks to make just a back-ported intel driver from 3.17 >> [first known to work again, 3.16 does not]) . >> http://lists.centos.org/pipermail/centos/2014-November/147579.html > > Great suggestion. I just installed and booted the following kernel-ml. > > Linux c6 3.18.1-1.el6.elrepo.x86_64 #1 SMP Tue Dec 16 20:44:33 EST 2014 x86_64 x86_64 x86_64 GNU/Linux > > And it works! I got A LOT of bad-looking errors on boot but it did > boot and everything seems to work fine. I've attached the boot.log > just FYI. I have not tried kernel-lt but I suspect it will work fine > since it would install a 3.10 kernel. (Based on the bugs below this > problem doesn't appear in the 3.X branch until about 3.16). > > After searching the RHEL bug tracker, I do see some very similar bugs > to what I'm experiencing. > https://bugzilla.redhat.com/show_bug.cgi?id=1161321 > https://bugzilla.redhat.com/show_bug.cgi?id=1151757 > > Both are on 3.X kernels under Fedora so not completely applicable. The > first one even has the same graphics card as I do - no activity > though. The second one is also very similar.and in one of the comments > it was suggested to do this: > >> 2) If not, it looks like everyone else is using an ATI Radeon card and >> likely something broke between 3.15 and 3.16. Please boot with "nomodeset" as >> a grub option and report back. If it boots correctly, try modprobing radeon and >> see if the screen goes black right away > > This sounded worthwhile so I booted successfully on the > 2.6.32-504.3.3.el6.x86_64 kernel with "nomodeset". I tried this before > (as described in my xorg thread) and I get a lot of artifacts in the > graphics but it does work. However, the radeon driver is already > loaded after I boot. This is directly after the boot: > > [root@c6 ~]# lsmod | grep rad > radeon 1536476 0 > ttm 81172 1 radeon > drm_kms_helper 82994 1 radeon > drm 291284 3 radeon,ttm,drm_kms_helper > i2c_algo_bit 5711 1 radeon > i2c_core 29964 12 tda18271,s5h1411,cx25840,cx23885,v4l2_common,videodev,tveeprom,i2c_piix4,radeon,drm_kms_helper,drm,i2c_algo_bit > [root@c6 ~]# > > >>> http://bugs.centos.org/view.php?id=4586 >> >> Actually, I ask that people open a new ticket for each request. :) >> >> Akemi > > Akemi, maybe its not clear yet but would you prefer I submit this bug > under the CentOS or RHEL tracker? (And do you know if I can submit to > the RHEL tracker without a RHEL subscription?) Any advice on where to > submit this info to get this fixed in the CentOS 6 line would be > appreciated. >

1 0

Password Must Change using SSSD in Samba 4.1.10
by Ashish Yadav 07 Jan '15

07 Jan '15

Hi, I am trying to implement the *password must change at next logon* in CentOS 6.5 client using sssd 1.11.6 where Samba 4.1.10 is my backend server. Here are the list of things which I have done, 1. I have setup the CentOS to do the Domain login using sssd service. I can able to login into the CentOS client using Domain user's credentials from display and from SSH also, no problem at all. 2. Next thing which I want to implement is that password must change feature into Samba 4.1.10 server. To do that, I have been using Windows 7 ultimate which is already in Domain and I am using RSAT tools for users and groups where I have a option to check "password must change at next logon" option for particular user. After doing that Windows machine is honoring this and telling user to change the password and allowing user to login after changing the password. 3. As far as the CentOS client is concerned, it was not honoring the password must change and allowing user to login without asking for password change using sssd with current password. Here is the configuration file of sssd service, [sssd] config_file_version = 2 services = nss, pam domains = EXAMPLE sbus_timeout = 30 [nss] filter_users = root filter_groups = root reconnection_retries = 3 [pam] reconnection_retries = 3 offline_credentials_expiration = 0 [domain/EXAMPLE] entry_cache_timeout = 600 entry_cache_group_timeout = 600 min_id = 1000 id_provider = ldap auth_provider = krb5 chpass_provider = krb5 ldap_schema = rfc2307bis ldap_uri = ldap://smbad.intra.example.com:390/ ldap_search_base = dc=intra,dc=example,dc=com cache_credentials = true krb5_server = smbad.intra.example.com:8880 krb5_realm= INTRA.EXAMPLE.COM <http://intra.example.com/> ldap_default_bind_dn = cn=admin,dc=intra,dc=example,dc=com ldap_default_authtok_type = password ldap_default_authtok = 6pNEn7Eo3zmz9MxciGLx 4. I have also tried to achieve above thing using command line tool "pdbedit" but without any luck. Here is the link < http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/passdb.html#pdbe… > which I have followed. Please share your thoughts in order to help me and move forward to solve this problem. Thanks very much and regards, Ashishkumar S. Yadav

1 0

Radeon graphics problems with CentOS 6.6
by Darby Vicker 06 Jan '15

06 Jan '15

Hello, I saw in the CentOS 6.6 release notes that the Xorg ABI has changed but that "This should not concern anyone who uses the default drivers shipped with CentOS." I'm using the ATI drivers in Base but X still fails when I boot a CentOS 6.6 kernel. I was hoping this is a known problem that would get fixed with a kernel update but I'm still having problems with the 2.6.32-504.1.3.el6.x86_64 kernel. Relevant info below. Any ideas? Thanks, Darby [root@c6 ~]# lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6530D] [root@c6 ~]# uname -a Linux c6 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root@c6 ~]# yum list xorg-x11-drv-ati.x86_64 xorg-x11-drv-ati-firmware.noarch Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: repos.dfw.quadranet.com * epel: mirror.compevo.com * extras: repos.dfw.quadranet.com * updates: repos.dfw.quadranet.com Installed Packages xorg-x11-drv-ati.x86_64 7.3.99-2.el6 @base xorg-x11-drv-ati-firmware.noarch 7.3.99-2.el6 @base [root@c6 ~]# Log messages containing "radeon" from booting into the CentOS 6.6 kernel: c6 kernel: [drm] radeon kernel modesetting enabled. c6 kernel: fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver c6 kernel: radeon 0000:00:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 c6 kernel: radeon 0000:00:01.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used) c6 kernel: radeon 0000:00:01.0: GTT: 1024M 0x0000000020000000 - 0x000000005FFFFFFF c6 kernel: [drm] radeon: 512M of VRAM memory ready c6 kernel: [drm] radeon: 1024M of GTT memory ready. c6 kernel: radeon 0000:00:01.0: firmware: requesting radeon/SUMO_pfp.bin c6 kernel: radeon 0000:00:01.0: firmware: requesting radeon/SUMO_me.bin c6 kernel: radeon 0000:00:01.0: firmware: requesting radeon/SUMO_rlc.bin c6 kernel: [drm] radeon: dpm initialized c6 kernel: radeon 0000:00:01.0: firmware: requesting radeon/SUMO_uvd.bin c6 kernel: radeon 0000:00:01.0: WB enabled c6 kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff8801b6e81c00 c6 kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff8801b6e81c0c c6 kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900229b2118 c6 kernel: radeon 0000:00:01.0: radeon: using MSI. c6 kernel: [drm] radeon: irq initialized. c6 kernel: [drm] Radeon Display Connectors c6 kernel: fbcon: radeondrmfb (fb0) is primary device c6 kernel: radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device c6 kernel: radeon 0000:00:01.0: registered panic notifier c6 kernel: [drm] Initialized radeon 2.37.0 20080528 for 0000:00:01.0 on minor 0 c6 kernel: powernow-k8: Found 1 AMD A6-3600 APU with Radeon(tm) HD Graphics (4 cpu cores) (version 2.20.00) Log messages from booting into the CentOS 6.5 kernel: c6 kernel: [drm] radeon kernel modesetting enabled. c6 kernel: fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver c6 kernel: radeon 0000:00:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 c6 kernel: radeon 0000:00:01.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used) c6 kernel: radeon 0000:00:01.0: GTT: 512M 0x0000000020000000 - 0x000000003FFFFFFF c6 kernel: [drm] radeon: 512M of VRAM memory ready c6 kernel: [drm] radeon: 512M of GTT memory ready. c6 kernel: platform radeon_cp.0: firmware: requesting radeon/SUMO_pfp.bin c6 kernel: platform radeon_cp.0: firmware: requesting radeon/SUMO_me.bin c6 kernel: platform radeon_cp.0: firmware: requesting radeon/SUMO_rlc.bin c6 kernel: radeon 0000:00:01.0: WB enabled c6 kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff8801b83aec00 c6 kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff8801b83aec0c c6 kernel: radeon 0000:00:01.0: radeon: using MSI. c6 kernel: [drm] radeon: irq initialized. c6 kernel: [drm] Radeon Display Connectors c6 kernel: [drm] radeon: power management initialized c6 kernel: fbcon: radeondrmfb (fb0) is primary device c6 kernel: radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device c6 kernel: radeon 0000:00:01.0: registered panic notifier c6 kernel: [drm] Initialized radeon 2.30.0 20080528 for 0000:00:01.0 on minor 0 c6 kernel: powernow-k8: Found 1 AMD A6-3600 APU with Radeon(tm) HD Graphics (4 cpu cores) (version 2.20.00) c6 kernel: CPU0: AMD A6-3600 APU with Radeon(tm) HD Graphics stepping 00

6 11

CentOS-announce Digest, Vol 119, Issue 1
by centos-announce-request＠centos.org 06 Jan '15

06 Jan '15

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-2015:0002 CentOS 6 autofs BugFix Update (Johnny Hughes) 2. CEBA-2015:0006 CentOS 5 nss_db BugFix Update (Johnny Hughes) 3. CEBA-2015:0003 CentOS 6 dovecot BugFix Update (Johnny Hughes) 4. CEBA-2015:0005 CentOS 6 gdbm FASTTRACK BugFix Update (Johnny Hughes) 5. CEBA-2015:0007 CentOS 7 mariadb BugFix Update (Johnny Hughes) 6. Improvements in the docker registry for CentOS (Jim Perrin) 7. CESA-2015:0008 Low CentOS 7 libvirt Security Update (Johnny Hughes) 8. Infra - CentOS hardware move [cbs] (Fabian Arrotin) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Jan 2015 11:54:59 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:0002 CentOS 6 autofs BugFix Update Message-ID: <20150105115459.GA34587(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:0002 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0002.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 791e92b38ed363ee16ccb14e67886fa043fc61b78410e5458d8850aac0eb38e9 autofs-5.0.5-109.el6_6.1.i686.rpm x86_64: 7bcd267ca01b2c066570f94f1995abe4914e3f200b01163904e6206776a78319 autofs-5.0.5-109.el6_6.1.x86_64.rpm Source: 304e3d53ec5b2fafa76efb9ad403cfa58450ca62eda799fe8d4a4517eefaa3ce autofs-5.0.5-109.el6_6.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 5 Jan 2015 11:44:01 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:0006 CentOS 5 nss_db BugFix Update Message-ID: <20150105114401.GA20917(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:0006 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0006.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b321179fd1a8daee28d28f2f13bd60effb39cf1cdf4304eedef58b78a0eb4eef nss_db-2.2-38.el5_11.i386.rpm x86_64: b321179fd1a8daee28d28f2f13bd60effb39cf1cdf4304eedef58b78a0eb4eef nss_db-2.2-38.el5_11.i386.rpm c2b5f3a8a8035791ecca4ff65824b800e7bdb631ba9ece5422df6ef287f4ea37 nss_db-2.2-38.el5_11.x86_64.rpm Source: dccdca10a0dab429227be07c89a86e132818ead10015d00bd95a0bb79f3097dc nss_db-2.2-38.el5_11.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Mon, 5 Jan 2015 11:55:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:0003 CentOS 6 dovecot BugFix Update Message-ID: <20150105115544.GA34886(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:0003 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0003.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f5dfa398b4a4814d0b3df88c08f438d027786a0b6c7fabd68457bd770015ec8f dovecot-2.0.9-8.el6_6.4.i686.rpm 078ae9c95a9f2136d29b1688ec9dd15dd66df69767c24ada02836b09f8d5a6c5 dovecot-devel-2.0.9-8.el6_6.4.i686.rpm 374a25e24922394e495c00c40e13fd0c351ce0d8986352e735a48c7929e12a74 dovecot-mysql-2.0.9-8.el6_6.4.i686.rpm 6c3d38ef793830170c8c16d44df855f256ef12371ffa661756ff52e0fb714fbe dovecot-pgsql-2.0.9-8.el6_6.4.i686.rpm 420a71aab3bb3217280308e261f3c9c953e443be745fee06ff5343ff58bfc4ab dovecot-pigeonhole-2.0.9-8.el6_6.4.i686.rpm x86_64: f5dfa398b4a4814d0b3df88c08f438d027786a0b6c7fabd68457bd770015ec8f dovecot-2.0.9-8.el6_6.4.i686.rpm da78ffbf581dea0507ad136791af11ffd553490dce8244c8457242cbb20378b6 dovecot-2.0.9-8.el6_6.4.x86_64.rpm 32b47811c8eeb596ce5b892a877c250d2512f0a83ce2290fe091dc137b2fcadd dovecot-devel-2.0.9-8.el6_6.4.x86_64.rpm 8669e89382754b87b36079d43d27944f2b3a0e2637b9d171874a0b04a24ae7f2 dovecot-mysql-2.0.9-8.el6_6.4.x86_64.rpm a123529a8f012844ddd4eff3755800dd0a180b75ad669b966794aec09e22aee6 dovecot-pgsql-2.0.9-8.el6_6.4.x86_64.rpm c064292f212fb4b4edef71f4c2518878b55f240c184265f78bc03f823875aedc dovecot-pigeonhole-2.0.9-8.el6_6.4.x86_64.rpm Source: 538bbc8052567ca446567d6b2add3d0c14d1f07812bef9024727e1eb6a26a82f dovecot-2.0.9-8.el6_6.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Mon, 5 Jan 2015 11:57:09 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:0005 CentOS 6 gdbm FASTTRACK BugFix Update Message-ID: <20150105115709.GA35122(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:0005 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0005.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 660911546c55027459a45ff052f1f538072a3e97b3e3c789d6926f19978cefc7 gdbm-1.8.0-37.el6.i686.rpm d9268699f04486515df65718b9340c676e5c55aba257de0df560f91d77cea9ec gdbm-devel-1.8.0-37.el6.i686.rpm x86_64: 660911546c55027459a45ff052f1f538072a3e97b3e3c789d6926f19978cefc7 gdbm-1.8.0-37.el6.i686.rpm be5f38297022d57bd20d8563e87c76b6d88620c9802dc9e3433b34936f3201f3 gdbm-1.8.0-37.el6.x86_64.rpm d9268699f04486515df65718b9340c676e5c55aba257de0df560f91d77cea9ec gdbm-devel-1.8.0-37.el6.i686.rpm cb56818edd087de2c9494be61a6d633003689a3d1b957d0804f402101d6d333f gdbm-devel-1.8.0-37.el6.x86_64.rpm Source: 049cc6bbcceadea2f73a4fe1b99f907bc19d4daa4a02e1bfd06517116ceaef9e gdbm-1.8.0-37.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Mon, 5 Jan 2015 16:55:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:0007 CentOS 7 mariadb BugFix Update Message-ID: <20150105165507.GA57424(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:0007 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0007.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: db6838c6927001b1697a9957ff3a808cf6d6a9b75bd0ee82d84e48d3ef866230 mariadb-5.5.40-2.el7_0.x86_64.rpm 3b3a1a61e88b0ab7b7daffe1ac291ba74c8c87ad4de04a552e9b0c9eb836b381 mariadb-bench-5.5.40-2.el7_0.x86_64.rpm b0609f33ae880a70a2ca277085aa6d54d7eaaaf58d65fe9260391ef306156621 mariadb-devel-5.5.40-2.el7_0.i686.rpm 3f7b4806026c1a7fce519184a8065809655b2ec61434eedadf8e280180938ee8 mariadb-devel-5.5.40-2.el7_0.x86_64.rpm 94398a2599786196a7b1a4a2afeb9b5cad29d2d20063bee8620e3957c9fd8daa mariadb-embedded-5.5.40-2.el7_0.i686.rpm 32385d45480c7501ce48ca75d74800f7a916df2d1a7d7368490e0adde9e4b5a8 mariadb-embedded-5.5.40-2.el7_0.x86_64.rpm 8c324b566d62e94fc2bbfaf8ae39a8a5387849cc15f44465e06b1ec1ae667c4f mariadb-embedded-devel-5.5.40-2.el7_0.i686.rpm 5ddbd46ca51b95fc3b6550903d6b6e739699f26d7ad04973dfcbf08958823758 mariadb-embedded-devel-5.5.40-2.el7_0.x86_64.rpm 9fc910f8f0e7b904151418f6482e5e65f04cc0905704b7c294eb318ecb7143f4 mariadb-libs-5.5.40-2.el7_0.i686.rpm b691fb6c023ca8774e4fc2e7e3e37cd7d8dc3193d7306968ae63fa5e7caba936 mariadb-libs-5.5.40-2.el7_0.x86_64.rpm 3a7138879e66dc71b98a628af34cf6a22366472a429cca393f1891c8b4ba9f39 mariadb-server-5.5.40-2.el7_0.x86_64.rpm 6bb25d002d49a3757a8ca6c335041e5b9a588702befc455ddc910ef65b698c56 mariadb-test-5.5.40-2.el7_0.x86_64.rpm Source: 00953a25e858b98b9085c73a4556cb49d6d9de486562965da75bc54eccdbc8ba mariadb-5.5.40-2.el7_0.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 6 Date: Mon, 05 Jan 2015 15:27:00 -0600 From: Jim Perrin <jperrin(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] Improvements in the docker registry for CentOS Message-ID: <54AB01A4.2030601(a)centos.org> Content-Type: text/plain; charset=utf-8 The CentOS images in the docker index have been bumped to 20150102. Additionally there are numbering scheme improvements requested by the community. Fixes ===== 1. All updates through 20150101 applied to rolling builds Enhancements ============ 1. Minor version tags - 5.11, 6.6, and 7.0.1406 These builds are built from install media only. They do not contain updates and will not be updated as part of the rolling/monthly builds. They are meant for use by those with specific vendor versioning requirements. Users are responsible for ensuring that the images are updated as needed via a 'yum update -y' in their Dockerfiles or other method. 2. Short names Users can now use short names to identify specific docker image tags. For example: centos:6 in place of centos:centos6. Both names are now valid and point to the same images. Additional Information ====================== For detailed information or to see the code differences used in building the images, please see https://github.com/CentOS/sig-cloud-instance-build -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 ------------------------------ Message: 7 Date: Mon, 5 Jan 2015 23:41:12 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:0008 Low CentOS 7 libvirt Security Update Message-ID: <20150105234112.GA8196(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:0008 Low Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-0008.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 894858978b69bdb598f5204f77acb5e4ea6693e38d65abe97b5ef58e32ae2c5a libvirt-1.1.1-29.el7_0.4.x86_64.rpm 4b24e70f8b6d5e7e0d973b7a42d7827d049f4f12a4742efcc37977ba275f3f3f libvirt-client-1.1.1-29.el7_0.4.i686.rpm 4f4bf92a200e2543f29dbfe1c5e47153b30243a216d9879c826bef1ea5be12e7 libvirt-client-1.1.1-29.el7_0.4.x86_64.rpm e40b51fbf2ccb1e44d75faaf26b73ce1a0ed79d1d03b41155a298be6e4465d50 libvirt-daemon-1.1.1-29.el7_0.4.x86_64.rpm 09495b7515cb91f6790968c9a029787767f65d2c51e28d1bb32803272ee607c0 libvirt-daemon-config-network-1.1.1-29.el7_0.4.x86_64.rpm 52e4920ecafa3b44e9af130acbf5706ccdf3d85d5a4c5939ee86dc007438a9eb libvirt-daemon-config-nwfilter-1.1.1-29.el7_0.4.x86_64.rpm e6bc0cae1e22179e0f64f2c555183851597052b42d1a52d7cff288aa409b6bf0 libvirt-daemon-driver-interface-1.1.1-29.el7_0.4.x86_64.rpm 16bf347b148a48526afebc5d9840cec1e57542a0fc9304b96117747f05d6daed libvirt-daemon-driver-lxc-1.1.1-29.el7_0.4.x86_64.rpm 2261a527f83dece82d5c38cbaeac4debfd2b0313c91015c87be0707f3cd706bf libvirt-daemon-driver-network-1.1.1-29.el7_0.4.x86_64.rpm 758221a54876d0ce0f77d05e69e623d73a683e30916bcfa89e9063922ab4e95c libvirt-daemon-driver-nodedev-1.1.1-29.el7_0.4.x86_64.rpm 64f4de7b7aa01e614eeb02b9837fd2b77b3709879b751c357f4870b0b5d62875 libvirt-daemon-driver-nwfilter-1.1.1-29.el7_0.4.x86_64.rpm c8117765d8c082244ba68804321507940fff9be04d4667ea56922358173e0713 libvirt-daemon-driver-qemu-1.1.1-29.el7_0.4.x86_64.rpm 9ac66d58a4a8cf7dbec7372f100f8e65ae3cd8b4bd49f6356e3495a1c56b884d libvirt-daemon-driver-secret-1.1.1-29.el7_0.4.x86_64.rpm aaa8acc5a5bbbb05c7b0901e10aab024f985077473be54c7ca059629ebbe710c libvirt-daemon-driver-storage-1.1.1-29.el7_0.4.x86_64.rpm 928dda55b177563b31a726e37c250e39e78fb92f68525599bcda68591921c393 libvirt-daemon-kvm-1.1.1-29.el7_0.4.x86_64.rpm 3b938d206208214bf94f57f48bb95f59b6ff02aeb6b41df48c71e77249287b5e libvirt-daemon-lxc-1.1.1-29.el7_0.4.x86_64.rpm c3c7ee1dbd35e6fcef24bff0aac59babba0a75239ee79195a868f6903ea90347 libvirt-devel-1.1.1-29.el7_0.4.i686.rpm d41dda70cc56438b9116c93dfdfe6ff09185958616a2a875869cd447e1e6077f libvirt-devel-1.1.1-29.el7_0.4.x86_64.rpm f56695af42c48cbc5e531bc05c2b09fb330764308f81887e24d0c1894a80f3d4 libvirt-docs-1.1.1-29.el7_0.4.x86_64.rpm 796ddcea38e014b73cb279d3352196f860cd0ddb3bc0b3d598d8271ef166b5e1 libvirt-lock-sanlock-1.1.1-29.el7_0.4.x86_64.rpm 1009596eb54c376ccc644f98e01306344bbdc5c3be9175ab0c6affd2dbcac2a8 libvirt-login-shell-1.1.1-29.el7_0.4.x86_64.rpm e20301bfee52f98e24a0b54a4b35327a8e7168d00de66916298b89334ff4f42f libvirt-python-1.1.1-29.el7_0.4.x86_64.rpm Source: d9a38c5ca9d6b5c44eb30f485889b51138564c02cbb59580cf6b43488a4d0ef4 libvirt-1.1.1-29.el7_0.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 8 Date: Tue, 06 Jan 2015 08:57:16 +0100 From: Fabian Arrotin <arrfab(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] Infra - CentOS hardware move [cbs] Message-ID: <54AB955C.6020407(a)centos.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Due to a hardware move (machines needing to be powered off, moved in another rack) , some CentOS.org services will be unreachable for a short period of time. Impacted services : * cbs/Community Build System (aka http://cbs.centos.org) Koji web/hub and builders will be down Migration is scheduled for Thursday January 8th, 3:00 pm UTC time. You can convert to local time with $(date -d '2015-01-08 15:00 UTC') The expected "downtime" is estimated to ~30 minutes , time needed to power down, move machines in the rack, power back on Thanks for your comprehending and patience. on behalf of the Infra team, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlSrlVwACgkQnVkHo1a+xU6TagCfQkl3slznEBdQ8T8VYKEcY4AM SDYAnRC0zm+NmlsSVcHoc5b4nHZSN59P =DR4a -----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 119, Issue 1 ***********************************************

1 0

subscription of Cent - OS newletter
by Bijesh Maskey 05 Jan '15

05 Jan '15

Dear Sir/ Ma'am i would like to suscribe to the cenos newletter its update and patches release thanks regards b -- Bijesh Maskey 97719801095233

3 3

additional network config
by ken 05 Jan '15

05 Jan '15

A system whose network routing table looks like this (abbreviated): Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 needs to look like this: Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 10.10.0.0 192.168.0.98 255.255.0.0 UG 0 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 The first table is nicely configured by the files under /etc/sysconfig/. The first table becomes the second when this command is run: route add -net 10.10.0.0/16 gw 192.168.0.98 eth0 The question is, which file(s) need to be configured under /etc/sysconfig/-- and with what-- in order to accomplish what the "route add ..." command does?

2 2

Fetchmail multiple instances increasing load average
by Anshul Chauhan 04 Jan '15

04 Jan '15

Hi, I’m running centos 5.7 with sendmail-8.13.8-8.1.el5_7, fetchmail-6.3.6-4.el5 and procmail-3.22-17.1.el5.centos. My server is having around 2000 mailboxes and this server used to fetch mails for all these users using fetchmail from the other MX server. I’ve configured the below cron job using webmin for downloading these mail 5,10,15,20,25,30,35,40,45,50,55 * * * * /etc/webmin/fetchmail/check.pl --file /var/log/fetchmaillog. But the load average for the server goes high automatically after every 4 to 5 hours due to multiple fetchmail instances and after that I’ve to either kill all the fetchmail jobs or restart the server for making the system up again. Kindly suggest how can i reduce this load average issue or any other way out for downloading the mails from the parent server running on sendmail again. Warm Regards, Anshul Chauhan

3 2

Re: [CentOS] Design changes are done in Fedora
by James B. Byrne 03 Jan '15

03 Jan '15

On Wed, December 31, 2014 12:03, Warren Young wrote: > > So, cope with change. > Is one to infer from your mantra 'cope with change' that one is not supposed to express any opinion whatsoever, ever, on any forum; on the externalised cost of changes made to software with no evident technical justification? And that to do so is evidence of some moral or intellectual defect in oneself? We all cope with change until we die. That is not a philosophy or program. It is an observation on the state of existence; and is no more useful than the observation that, eventually, we all die. -- *** 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 3

Sun Microsystems Quad gigabit ethernet nic compatibility
by mechy2k2000 03 Jan '15

03 Jan '15

Hello I am thinking of buying this card to and wanted to know if this NIC is supported. The card is a Sun Microsystems PCI-X Quad-Port Gigabit Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on how well the card plays with centos and also proxmox ve (if any of you use that distro ) If things don't seem to work I may bite the bullet and buy an Intel card thanks Rafeal Stewart

5 5

Re: [CentOS] how to delete a trashed kernel
by Don Vogt 03 Jan '15

03 Jan '15

Message: 8 On Jan 1, 2015, at 3:49 PM, Don Vogt <dnvot(a)yahoo.com> wrote: > when I select the second kernel it boots OK. Now I would like to remove the bad kernel. The only thing that makes this tricky is that you can?t just say ?rpm -e kernel? because there is more than one ?kernel? package installed. You need to know the exact package name. >> I?m assuming you?re using EL7 and you told it you wanted your user to be a >> trusted admin during install. Otherwise, you might need to su up to root to do >> this. Alas, sudo is not universal: > I have never noticed a "centos-plus" in a kernel name before. Does the centos-plus repo deal out kernels? >>Clearly, the answer is ?yes?. thanks. >> I would appreciate any advice (except "go back to windows?) >You asked for it: Get and read some good books on Linux. I had some books on Unix when I started with Slackware. I downloaded it over Ftp from MIT, I believe it was Slackware 0.8. (maybe 1.0). It came on about 25 floppy disks and (with a 300baud modem) I could only do about two a night. I believe I got in trouble this time while building a centos7 partition. I had some problems getting the music to play and I went back and forth between centos6 and centos7 to see what packages I need (Centos6 was working fine). I think my initial problem was that Rpmforge doesn't have centos7. Thanks for the help. Centos6 and centos7 are now working fine (except 7 only boots about every other try- which I am still working on - I think the bios boot my Hard drives in somewhat random order and I haven't been able to come up with the proper system map -- or it may be a mixup with two SATA drives and an IDE. Pulling the power plug on the IDE drive fixes it.) I will go back to lurking.

1 0

how to delete a trashed kernel
by Don Vogt 03 Jan '15

03 Jan '15

I have a screwed up disk arrangement, but I have had no trouble because of it after using it over a year. Recently I did a yum update. After starting the update, which included a new kernel, it seemed to either freeze or loop. It was a long time at the prompt and I got impatient and did a Ctrl C. I then tried to re-boot. The result was a kernel panic. I am keeping 5 kernels and when I select the second kernel it boots OK. Now I would like to remove the bad kernel. One other thing that I don't understand and may be relevant, the name of the bad package is kernel-2.6.32-504.3.3.el6.centos-plus.i386 I have never noticed a "centos-plus" in a kernel name before. Does the centos-plus repo deal out kernels?I have tried yum remove and "gpk application" (add and remove software) with no luck.I have tried google, but all the solutions for kernel deletions were to delete old kernels. I don't want to do that because I would be deleting my backups. I am in no hurry because I can still boot and it is possible that if I can wait through several kernel updates yum might delete the bad one after an update. I should have mentioned that I am using grub2 to boot, although I don't think that has anything to do with deleting the kernel package.I would appreciate any advice (except "go back to windows")

2 1

ulogd / ulogd packages?
by Adam Tauno Williams 02 Jan '15

02 Jan '15

I am looking for ulog-2.0.x packages and the best I have been able to find [for CentOS6] has been ulog-2.0.0 (which is not an exciting prospect for .0 reasons). Is anyone aware of ulogd packages for CentOS6 [x86_64]? I am kind of surprised this isn't standard fair. -- Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA

1 0

Secret incantations for virt-viewer?
by Bill Gee 02 Jan '15

02 Jan '15

Hello everyone - I am trying to use virt-viewer to connect to KVM virtual machines running on a CentOS7 host. It works great when running directly on the host, but I have not been able to figure out the magic connection string to make it work from another computer. On the host, I set selinux to "permissive" and stopped the firewalld service. No change, so it is not related to them. Almost every command I try gives an immediate dialog box that says "Unable to connect to libvirt with URI ...". The only command line that gets me anything different is this: virt-viewer --connect xen+ssh://root@practice7.billgee.local/ dd2a2ba7-707d-42b5-8c83-94b11ce6e269 This will ask me for the root password on the host machine and then gives me the same "Unable to connect" message. I tried it with a regular user account instead of root and got the same result. I have tried it with and without the "root@" string. I tried using both the UUID and the domain name of the guest. I tried all of the following protocols: ssh:// qemu:// qemu:/// xen:// xen+ssh:// qemu_ssh:// qemu+ssh:// If I open a regular ssh shell using the +X parameter and then launch virt- viewer, it works. The connection string in that case is --connect=qemu:///system Any suggestions? Thanks - Bill Gee

4 8

Happy New Year!
by Ljubomir Ljubojevic 01 Jan '15

01 Jan '15

On behalf of the CentOS project I wish you Happy New Year! Happy New Year! -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant

6 5

Re: [CentOS] Design changes are done in Fedora
by Warren Young 31 Dec '14

31 Dec '14

On Dec 31, 2014, at 11:00 AM, m.roth(a)5-cent.us wrote: > Warren Young wrote: >> >> How many single computers have to be up 24/7? > > A hundred or more, here, individual servers, 24x7. I’m more interested in a percentage than absolute values. And I’m only interested in boxes that simply cannot go down for a bit of maintenance every now and then. As counterexamples, DNS, NTP, and SMTP servers are out, because these protocols were explicitly designed to cope with short temporary outages. > Home directory servers, > backup servers, compute nodes, some of which have jobs that run for days, > or a week or two, and that's not counting the clusters that do the same... > and mostly dump the data to home or project directories. That’s all possible to work around. Home servers: SAN design points the way. Backup servers: Ditto if you mean home directory mirrors. If you mean hot failover nodes in a cluster, I already pointed out that clusters let you upgrade via temporary partitioning. Compute nodes: I didn’t ask how many boxes you have that share the same 9/5/180 usage pattern of our customers. I asked how many you have that must run 24/7/365 or Bad Things happen. When a job that’s been running for 2 weeks finishes, there’s your maintenance window. Take it if you need it, let it go if you don’t.

1 0

X11 console
by Andreas Benzler 31 Dec '14

31 Dec '14

Hello Guys… I need to revert the X11 graphical server to Console 7. and enable VT1 as normal text as it was on the old distr.. Sincerely AndyBe

10 9

CentOS 6.6 - net-snmp process - Too many open files
by Laurent Dumont 31 Dec '14

31 Dec '14

Hi gents, I have a CentOS 6.6 install with net-snmp running. I'm using SNMPv3 Auth and Encryption with Observium polling devices every five minutes. On one of my Centos server, the net-snmp process will die after 24-36 hours of running. It seems to be hitting my system maximum file open limit which is set to 1024. > [root@mail net-snmp-5.7]# ulimit -n > 1024 That number will keep increasing till it trips the 1024 limit. > [root@mail ~]# lsof -p 26907 | wc -l > 1071 > [root@mail net-snmp-5.7]# lsof -p 26907 > snmpd 26907 root 166r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 167r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 168r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 169r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 170r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 171r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 172r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 173r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 174r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 175r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 176r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 177r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 178r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > snmpd 26907 root 179r REG 0,3 0 4026532160 > /proc/26907/net/sctp/snmp > #tail /var/log/snmpd.log > cannot open /proc/net/dev ... > /proc/partitions: Too many open files > /proc/stat: Too many open files > /proc/partitions: Too many open files > /proc/stat: Too many open files > could not create socket > /proc/partitions: Too many open files > /proc/stat: Too many open files > cannot open /proc/net/dev ... > /proc/partitions: Too many open files > /proc/stat: Too many open files > /proc/partitions: Too many open files > /proc/stat: Too many open files It seems that CentOS is frozen to net-snmp 5.5 and I'm don't really want to use anything that I can't easily manage with "yum". The weird thing is that I have another server with the same config/CentOS version/Net-Snmp version and I have no issues with the snmp process on that server. I could raise the open file limit but that just seems unnecessary since I don't think that snmp is supposed to work that way. Anything else I could try to troubleshoot the issue? Thanks!

1 0

Re: [CentOS] can't enable selinux CentOS 6.5
by James B. Byrne 31 Dec '14

31 Dec '14

On Tue, December 30, 2014 03:18, Digimer wrote: > What possible reason could they have for that? > > On 30/12/14 02:17 AM, Laurent Dumont wrote: >> By any change, is it a VPS? I know that my CloudAtCost (very cheap but >> extremely unreliable provider) prevents you from using SeLinux on their >> Centos image. No mysterious breakages == lower support costs. The same reason MicroSoft shipped everything on and open for years and thereby built up the malware industry from scratch. -- *** 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 4

sound oddity on C6
by Fred Smith 31 Dec '14

31 Dec '14

I just encountered an oddity... it may have been this way for millennia :) but somehow I've never noticed it before... say I'm using X (which is pretty normal these days) and I have VLC playing a "radio" station. I do CTRL-ALT-Fx to switch to a text console THAT HAS NO ONE LOGGED IN on it, and voila: no sound! as soon as I log in, the audio returns. what gives here? -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "For the word of God is living and active. Sharper than any double-edged sword, it penetrates even to dividing soul and spirit, joints and marrow; it judges the thoughts and attitudes of the heart." ---------------------------- Hebrews 4:12 (niv) ------------------------------

2 2

Documentation for upstart
by Robert Nichols 31 Dec '14

31 Dec '14

Is there any documentation for the upstart-0.6.5 used in CentOS 6? All I can find online is for much newer versions. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.

1 0

Re: [CentOS] Secret incantations for virt-viewer?
by Bill Gee 30 Dec '14

30 Dec '14

On Tuesday, December 30, 2014 16:15:45 m.roth(a)5-cent.us wrote: > Bill Gee wrote: > > On Tuesday, December 30, 2014 13:01:57 SilverTip257 wrote: > >> On Tue, Dec 30, 2014 at 9:58 AM, Marcelo Roccasalva < > >> > >> marcelo-centos(a)irrigacion.gov.ar> wrote: > >> > On Tue, Dec 30, 2014 at 11:46 AM, Bill Gee <bgee(a)campercaver.net> > >> > >> wrote: > <snip> > > > Thanks! I changed the qemu.conf file to listen on 0.0.0.0. That works - > > I can connect to the virtual machines using a VNC client. > > <snip> > Eeek! > > I'd change that, if I were you, to something on your own network - > 192.168.0.0/24, or whatever. I don't think you want somebody, in, say, > North Korea or Brazil getting in there. > > mark, the unpostable Hi Mark My understanding is that 0.0.0.0 in this context really means "all public network interfaces". There is no man page for qemu.conf, so all I can go by is the comments in the file. There are NAT routers in front of all of this. Bill Gee

1 0

Re: [CentOS] Design changes are done in Fedora
by James B. Byrne 30 Dec '14

30 Dec '14

On Mon, December 29, 2014 21:04, Warren Young wrote: > On Dec 29, 2014, at 4:03 PM, Les Mikesell <lesmikesell(a)gmail.com> wrote: > >> On Mon, Dec 29, 2014 at 3:03 PM, Warren Young <wyml(a)etr-usa.com> wrote: >>> >>> the world where you design, build, and deploy The System is disappearing >>> fast. >> >> Sure, if you don't care if you lose data, you can skip those steps. > > How did you jump from incremental feature roll-outs to data loss? There is no > necessary connection there. > Having written the Cucumber Backgrounder guide I believe that I am well aware of some of the current fashions in software development. The idea of incremental feature enhancement that you introduced is at once orthogonal to my original point and yet forms an ironic counterpoint that highlights the problem. The issue of data integrity is a separate matter entirely. I raised the issues of needless incompatibility and the avoidable costs of retraining and re-implementation of existing, satisfactory, solutions. You reply with a comment extolling incremental featurism. I am all in favour of incrementalism in software development. The problem being that RedHat does not do that. Instead RedHat freezes the product two years before release and then sets about creating a new, equivalent, but significantly different, replacement that you are forced to accept every seven years. In fact, the freeze, release, support and deprecate schedule that RedHat embraces as a corporate policy bears more than a passing similarity to the 'waterfall' process you, evidently prematurely, consigned to the grave. If RedHat actually adopted incremental rollout of new features to their distribution I would be most happy because, incremental rollouts are NOT SUPPOSED TO BREAK ANYTHING ALREADY IN PRODUCTION. And that condition is most certainly not met in every case of RHELx+1 I have dealt with. -- *** 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

1 0

Gnome rebase in 7.2?
by Dave Johansen 30 Dec '14

30 Dec '14

https://bugzilla.redhat.com/show_bug.cgi?id=1109302 https://bugzilla.redhat.com/show_bug.cgi?id=1174442 >From those two bugzillas it looks like Gnome is going to be rebased in 7.2. I understand that that's a "RHEL thing" but does anyone here have any insight to what this will mean. Will applications have to rebuilt? Or what other implications are there? Thanks, Dave

1 0

can't enable selinux CentOS 6.5
by Tim Dunphy 30 Dec '14

30 Dec '14

Hey guys, For some reason I can't seem to enable SELinux on this one host. Here's my SELinux config file: [root@beta-new:~] #cat /etc/sysconfig/selinux # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=enforcing # SELINUXTYPE= can take one of these two values: # targeted - Targeted processes are protected, # mls - Multi Level Security protection. SELINUXTYPE=targeted And when I check if it's enabled this is what I get: [root@beta-new:~] #getenforce Disabled But when I go to set SELinux to enabled, even with the config file set as you see it above, I get this result: [root@beta-new:~] #setenforce 1 setenforce: SELinux is disabled And nothing I can do enables it on this host. So how, can I solve this problem? I would definitely appreciate any advice you may have. Thanks Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

5 5

connect an iphone 5 to centos
by Patrick Bervoets 30 Dec '14

30 Dec '14

Does anyone know if you can connect an iphone 5 with ios 8.1.2 to either Centos 6 or 7? I've installed libimobiledevice but there's nothing happening. Thanks Patrick

1 0

ifcfg-br options
by Steve Clark 30 Dec '14

30 Dec '14

Hi, Does anyone know if there is an option for the ifcfg-br file that matches the brctl setageing parameter? I am using KVM and am running a DPI guest and need this parameter set to 0 to get mirrored span port data to cross the bridge to the guest vnet device. Thanks, -- Stephen Clark *NetWolves Managed Services, LLC.* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark(a)netwolves.com http://www.netwolves.com

2 2

where to get python-dbus?
by ken 30 Dec '14

30 Dec '14

When trying to use some third-party software (from HP written in python), it says "python-dbus not installed". Yet, there's $ rpm -q dbus-python dbus-python-0.70-9.el5_4 Are there really two such distinct libraries...? or is this a coding error? (Obviously I'm no python coder.) $ cat /etc/redhat-release CentOS release 5.11 (Final) tnx

1 0

Develop ineo 25e printer and CUPS
by Mihamina Rakotomandimby 30 Dec '14

30 Dec '14

Hi all, I have a Develop ineo 25e printer, and want to set it up with CUPS. I connect to http://localhost:631/ and add the printer, with uploading the PPD available here: http://www.develop.eu/en/products/office-products/colour/ineo-25/downloads.… (English, Linux, version 1.1 dated 2012) The printer is network connected, and the connection is socket://192.168.129.100 job-sheets=none, none media=iso_a4_210x297mm sides=one-sided I tried several combinations, with or without the PPD, socket:// or ipp://,... no way: The test page prints OK, but any other page is a kind of source code I could not define. Would you know what option could save me? Thanks.

1 0

Re: [CentOS] (py)curl error 7
by Mateusz Guz 29 Dec '14

29 Dec '14

Ip -6 a shows no output after "visual" inspection i don't see any ipv6 addresses assigned to my eth interfaces On Mon, 29 Dec 2014, Mateusz Guz wrote: >On Sun, 28 Dec 2014, Mark Milhollan wrote: >>On Fri, 26 Dec 2014, Mateusz Guz wrote: >>>created /etc/modprobe.d/ipv6_disable.conf file with >>>alias net-pf-10 off >>>alias ipv6 off >>>options ipv6 disable=1 >> >>These only take effect if you reboot or unload the modules manually. > >Tryning not to reboot, when unloading I get the message that the modules is in use. >I think that forcing the unload is too dangerouse, read that it might resolve in kernel panic. Forcing an unload wouldn't be wise. You must stop using the module then you can unload it. Busy usually means you have IPv6 addresses on some interfaces -- ip -6 addr flush dev ethX. /mark

1 0

Re: [CentOS] (py)curl error 7
by Mateusz Guz 29 Dec '14

29 Dec '14

>Added: >>"OPTIONS=-4 -named" to /etc/sysconfig/named, restarted named. >disabled ipv6 per interface, >>Odds are you didn't actually do this, just configured them so that they >>won't pickup a GUA. U were right :D >>created /etc/modprobe.d/ipv6_disable.conf file with >>alias net-pf-10 off >>alias ipv6 off >>options ipv6 disable=1 >These only take effect if you reboot or unload the modules manually. Tryning not to reboot, when unloading I get the message that the modules is in use. I think that forcing the unload is too dangerouse, read that it might resolve in kernel panic. -----Original Message----- From: Mark Milhollan [mailto:mlm@pixelgate.net] Sent: Sunday, December 28, 2014 8:17 PM To: Mateusz Guz Subject: Re: [CentOS] (py)curl error 7 On Fri, 26 Dec 2014, Mateusz Guz wrote: >Added: >"OPTIONS=-4 -named" to /etc/sysconfig/named, This only takes effect if you restart named. Keep in mind it does not stop named from returning IPv6 addresses. >disabled ipv6 per interface, Odds are you didn't actually do this, just configured them so that they won't pickup a GUA. >created /etc/modprobe.d/ipv6_disable.conf file with >alias net-pf-10 off >alias ipv6 off >options ipv6 disable=1 These only take effect if you reboot or unload the modules manually. >> 2a02:2498:1:3d:5054:ff:fed3:e91a: Network is unreachable" I would expect yum to try another address, until one succeeds. Sorry, I don't know why it would not do so. /mark

1 0

Re: [CentOS] CentOS 7 KVM guests no longer get keystrokes after yum update [solved]
by Charles Polisher 29 Dec '14

29 Dec '14

Fixed. I had installed a preview repository from Red Hat for some not-yet-released libguestfs features (libguestfs-RHEL-7.1-preview). There were evidently changes to some release packages in the updates repository that were incompatible with the candidate packages in the preview repository cited above. I disabled the preview repo in /etc/yum.repos.d/..., uninstalled each of its packages, and re-installed the relevant packages (libvirt qemu-kvm qemu-kvm-tools virt-* spice-gtk spice-gtk-python spice-gtk-tools spice-gtk3-vala spice-xpi). Lesson learned: When you install 3rd party repositories you should reserve time for hand-holding your package management system. -- Charles Polisher

1 0

Re: [CentOS] Fetchmail multiple instances increasing load average
by Anshul Chauhan 29 Dec '14

29 Dec '14

Kindly suggest is this right way to start the cronjob with lock if i've not mis understood. */5 * * * * /usr/bin/flock -n */etc/webmin/fetchmail/check.pl <http://check.pl> *>* --file /var/log/fetchmaillog* Warm Regards, Anshul Chauhan

1 0

Re: [CentOS] Fetchmail multiple instances increasing load average
by Anshul Chauhan 29 Dec '14

29 Dec '14

Kindly suggest is this right way to start the cronjob with lock if i've not mis undestood. */5 * * * * /usr/bin/flock -n */etc/webmin/fetchmail/check.pl <http://check.pl> *>* --file /var/log/fetchmaillog* Warm Regards, Anshul Chauhan

1 0

Re: [CentOS] OT: Bittorrent clients
by Alexandru Chiscan 29 Dec '14

29 Dec '14

>Hey, ktorrent looks pretty good! >Thanks for the hint! Maybe it's time to give KDE a second look :) LEC

3 3

OT: Bittorrent clients
by Sorin Srbu 29 Dec '14

29 Dec '14

Hi all, Just switched my home computer from Windows 7 to CentOS 6.6 and I'm having a slight bit of trouble with the bittorrent-clients. * Transmission is fine but lacks "a bit" in features. * Vuze is my preferred bt-client but gives me horrendous gfx-artifacts, like not showing the torrent name (it's white text on a white background or some such...). * Deluge is better, and what I'm using now, but I'm having trouble finding a repo that has the updated versions available for install with yum. I installed v1.3.5 a few days ago and already it's telling me that version is way outdated. Would anybody have any hints as to how and where to get the latest Deluge for CentOS? Or maybe even suggest a better torrent-client? All I'm getting from the Deluge site is some kind of source packages that is of no use for me. 8-/ Thanks in advance for any hints, tips and tricks. -- /Sorin

4 7

Re: [CentOS] OT: Bittorrent clients
by Alexandru Chiscan 28 Dec '14

28 Dec '14

>Isn't that a KDE-specific program? Yes, it's from kde. >Works with Gnome as well? All kde programs work in all desktop managers provided that you install the required libraries. The same is true for gnome programs. LEC ----- Reply message ----- From: "Sorin Srbu" <Sorin.Srbu(a)orgfarm.uu.se> To: "Centos" <centos(a)centos.org> Subject: [CentOS] OT: Bittorrent clients Date: Sun, Dec 28, 2014 13:14 Isn't that a KDE-specific program? Works with Gnome as well? //Sorin Sent from my tablet, please excuse the brevity. Alexandru Chiscan <lec(a)easterng.ro> wrote: ktorrent Lec _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

2 1

Re: [CentOS] OT: Bittorrent clients
by Alexandru Chiscan 28 Dec '14

28 Dec '14

ktorrent Lec

3 8

CentOS 7 KVM guests no longer get keystrokes after yum update
by Charles Polisher 28 Dec '14

28 Dec '14

Dear all, After "yum update" and reboot on a CentOS 7 server running kvm, all VM guests fail to receive keyboard input. Even sending ctrl-alt-delete from the virt-manager "Send Key" menu is inoperative. Most guests are set up as spice + QXL, and viewed on remote X sessions using virt-manager. Extensive browsing for a solution has turned up only dead ends. I tried reverting to the earlier kernel but there was no joy. Possibly I made some config change or installed (or removed) something that didn't take effect until I rebooted, but searching the host's command history has been unhelpful. Has anyone here run into this? Connecting to a CentOS 6 guest with virt-viewer writes some messages to the console, but what little I found in a web search was unhelpful. BTW, I hadn't messed with any guest keymaps, all stock installs with en_US. $ virt-viewer irc.foo.peecee3.com (virt-viewer:6016): GSpice-WARNING **: Warning no automount- inhibiting implementation available (virt-viewer:6016): vnc-keymap-WARNING **: Unknown keycode mapping '(null)'. Please report to gtk-vnc-list(a)gnome.org including the following information: - Operating system - GDK build - X11 Server - xprop -root - xdpyinfo Every attempted keystroke on the guest produces one of these messages: (virt-viewer:6016): GSpice-CRITICAL **: send_key: assertion `scancode != 0' failed What I think is relevant, running on the most recent kernel, all commands run from the host: $ libvirtd --version libvirtd (libvirt) 1.2.8 $ uname -a Linux mencius.peecee3.com 3.10.0-123.13.2.el7.x86_64 #1 SMP Thu Dec 18 14:09:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/redhat-release CentOS Linux release 7.0.1406 (Core) $ systemctl --no-pager list-unit-files 2>&1| egrep -i 'spice|agent|virt|qxl|qemu|kvm' | grep -v '\.socket' machine-qemu\x2dirc.foo.peecee3.com.scope static libvirt-guests.service disabled libvirtd.service enabled virt-who.service disabled virtlockd.service static $ localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: us X11 Layout: us $ rpm -qa | egrep -i 'spice|agent|virt|qxl|qemu|kvm' | sort ipxe-roms-qemu-20130517-5.gitc4bce43.el7.noarch libgovirt-0.1.0-3.el7.x86_64 libvirt-1.2.8-9.el7.x86_64 libvirt-client-1.2.8-9.el7.x86_64 libvirt-daemon-1.2.8-9.el7.x86_64 libvirt-daemon-config-network-1.2.8-9.el7.x86_64 libvirt-daemon-config-nwfilter-1.2.8-9.el7.x86_64 libvirt-daemon-driver-interface-1.2.8-9.el7.x86_64 libvirt-daemon-driver-lxc-1.2.8-9.el7.x86_64 libvirt-daemon-driver-network-1.2.8-9.el7.x86_64 libvirt-daemon-driver-nodedev-1.2.8-9.el7.x86_64 libvirt-daemon-driver-nwfilter-1.2.8-9.el7.x86_64 libvirt-daemon-driver-qemu-1.2.8-9.el7.x86_64 libvirt-daemon-driver-secret-1.2.8-9.el7.x86_64 libvirt-daemon-driver-storage-1.2.8-9.el7.x86_64 libvirt-daemon-kvm-1.2.8-9.el7.x86_64 libvirt-glib-0.1.7-3.el7.x86_64 libvirt-python-1.2.8-5.el7.x86_64 perl-Sys-Virt-1.1.1-5.el7.x86_64 qemu-img-rhev-2.1.2-13.el7.x86_64 qemu-kvm-common-rhev-2.1.2-13.el7.x86_64 qemu-kvm-rhev-2.1.2-13.el7.x86_64 qemu-kvm-tools-rhev-2.1.2-13.el7.x86_64 spice-glib-0.20-8.el7.x86_64 spice-gtk3-0.20-8.el7.x86_64 spice-protocol-0.12.6-2.el7.noarch spice-server-0.12.4-5.el7_0.1.x86_64 virt-install-1.0.1-1.el7.centos.noarch virt-manager-1.0.1-1.el7.centos.noarch virt-manager-common-1.0.1-1.el7.centos.noarch virt-top-1.0.8-7.el7.x86_64 virt-viewer-0.5.7-7.el7.x86_64 virt-what-1.13-5.el7.x86_64 virt-who-0.8-15.el7_0.noarch Ordinarily selinux run on the host, but I temporarily disabled it to facilitate problem solving: $ getenforce Disabled The qemu logs for the guests are unremarkable, and nothing much shows up in /var/log/messages. Thanks, -- Charles Polisher

1 0

Re: [CentOS] CentOS Digest, Vol 119, Issue 26 - Email found in subject
by David Docherty 27 Dec '14

27 Dec '14

Received -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of centos-request(a)centos.org Sent: Saturday, December 27, 2014 6:00 AM To: centos(a)centos.org Subject: CentOS Digest, Vol 119, Issue 26 - Email found in subject Send CentOS mailing list submissions to centos(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos or, via email, send a message with subject or body 'help' to centos-request(a)centos.org You can reach the person managing the list at centos-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS digest..." Today's Topics: 1. Re: (py)curl error 7 (Mateusz Guz) 2. Fail2ban mail failures ??? (Robert G. (Doc) Savage) 3. Re: Fail2ban mail failures ??? (Mike Burger) 4. Re: Fail2ban mail failures ??? (Mike Burger) 5. Re: Fail2ban mail failures ??? (????????? ????????) 6. Re: Fail2ban mail failures ??? (Robert G. (Doc) Savage) 7. Re: CentOS 7 boot network problem (Greg Lindahl) 8. Re: Fail2ban mail failures ??? (????????? ????????) ---------------------------------------------------------------------- Message: 1 Date: Fri, 26 Dec 2014 14:04:08 +0000 From: Mateusz Guz <Mateusz.Guz(a)itworks.pl> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] (py)curl error 7 Message-ID: <6c9b32de4e744a0c859a3c943b4466e1(a)KAEXC.itworks.pl> Content-Type: text/plain; charset="us-ascii" Added: "OPTIONS=-4 -named" to /etc/sysconfig/named, disabled ipv6 per interface, created /etc/modprobe.d/ipv6_disable.conf file with alias net-pf-10 off alias ipv6 off options ipv6 disable=1 but still getting the same error message. Maybe it just needs a reboot (which im trying to avoid) -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Mateusz Guz Sent: Thursday, December 25, 2014 3:16 PM To: CentOS mailing list Subject: Re: [CentOS] (py)curl error 7 Tried that :D yum is still trying to connect via ipv6 (ip_resolve=4 in config file) -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alikhan Damirov Sent: Thursday, December 25, 2014 11:59 AM To: CentOS mailing list Subject: Re: [CentOS] (py)curl error 7 Hi, from man yum.conf: ip_resolve Determines how yum resolves host names. `4' or `IPv4': resolve to IPv4 addresses only. `6' or `IPv6': resolve to IPv6 addresses only. On 25 December 2014 at 11:53, Mateusz Guz <Mateusz.Guz(a)itworks.pl> wrote: > Hi, > > Disabled ipv6 (using sysctl, disabled ip6tables, no reboot, no proxy > present) and still get the message as below. > > Centos 6.3 (i know its old) > Kernel : 2.6.32-279.14.1.el6.x86_64 (I know its old) Standard > /etc/yum.conf (no changes) Standard repos (centos base), enabled > > Cleaned cache: yum metadata (didn't work) > Then: yum clean all (didn't work) > Then yum makecache (didn't work) > > Yum repolist > Could not retrieve mirrorlist > http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os error was > 14: PYCURL ERROR 7 - "Failed to connect to > 2a02:2498:1:3d:5054:ff:fed3:e91a: Network is unreachable" > > Ping on mirrorlist.centos.org is OK > Curl mirrrorlist.centos.org NOT_OK > > Message started to occur suddenly, I didn't even update any package. > Any suggestions ? > > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ------------------------------ Message: 2 Date: Fri, 26 Dec 2014 11:39:32 -0600 From: "Robert G. (Doc) Savage" <dsavage(a)peaknet.net> To: centos(a)centos.org Subject: [CentOS] Fail2ban mail failures ??? Message-ID: <1419615572.4484.6.camel(a)lion.protogeek.org> Content-Type: text/plain; charset="UTF-8" I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's alerts sent to root's mail to be rejected. Here's a clip from one of the error messages: Message 48: From MAILER-DAEMON(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> Date: Sun, 21 Dec 2014 03:09:19 -0600 From: Mail Delivery Subsystem <MAILER-DAEMON(a)lion.protogeek.org> To: postmaster(a)lion.protogeek.org Content-Type: multipart/report; report-type=delivery-status; boundary="sBL97EKS003880.1419152959/lion.protogeek.org" Subject: Postmaster notify: see transcript for details Auto-Submitted: auto-generated (postmaster-notification) Status: R Part 1: The original message was received at Tue, 16 Dec 2014 03:09:17 -0600 from localhost with id sBG97E83025627 ----- The following addresses had permanent fatal errors ----- <fail2ban(a)example.com> ----- Transcript of session follows ----- <fail2ban(a)example.com>... Deferred: Connection timed out with example.com. Message could not be delivered for 5 days Message will be deleted from queue .......... I used to get the messages that are now being deleted after five days. Any suggestions? --Doc Savage Fairview Heights, IL ------------------------------ Message: 3 Date: Fri, 26 Dec 2014 12:59:10 -0500 From: Mike Burger <mburger(a)bubbanfriends.org> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Fail2ban mail failures ??? Message-ID: <ea1a2849d9364fe8cbf306dd40a2a978(a)bubbanfriends.org> Content-Type: text/plain; charset=US-ASCII; format=flowed On 2014-12-26 12:39 pm, Robert G. (Doc) Savage wrote: > I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's > alerts sent to root's mail to be rejected. Here's a clip from one of > the error messages: > > > Message 48: > From MAILER-DAEMON(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON(a)lion.protogeek.org> > To: postmaster(a)lion.protogeek.org > Content-Type: multipart/report; report-type=delivery-status; > boundary="sBL97EKS003880.1419152959/lion.protogeek.org" > Subject: Postmaster notify: see transcript for details > Auto-Submitted: auto-generated (postmaster-notification) > Status: R > > Part 1: > > The original message was received at Tue, 16 Dec 2014 03:09:17 > -0600 > from localhost > with id sBG97E83025627 > > ----- The following addresses had permanent fatal errors > ----- > <fail2ban(a)example.com> > > ----- Transcript of session follows ----- > <fail2ban(a)example.com>... Deferred: Connection timed out with > example.com. > Message could not be delivered for 5 days > Message will be deleted from queue > .......... > > > > I used to get the messages that are now being deleted after five days. > Any suggestions? I would suggest looking at the mailer daemon logs on both the sending and receiving systems. It would appear that the sending system is having difficulties at the receiving system end. You will likely find the root of your issues in the log entries for that message (or those messages) that occurred over the 5 days in question. -- Mike Burger http://www.bubbanfriends.org "It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1 ------------------------------ Message: 4 Date: Fri, 26 Dec 2014 13:05:21 -0500 From: Mike Burger <mburger(a)bubbanfriends.org> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Fail2ban mail failures ??? Message-ID: <09ef054be1244426578ae9b115c3431c(a)bubbanfriends.org> Content-Type: text/plain; charset=US-ASCII; format=flowed On 2014-12-26 12:59 pm, Mike Burger wrote: > On 2014-12-26 12:39 pm, Robert G. (Doc) Savage wrote: >> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's >> alerts sent to root's mail to be rejected. Here's a clip from one of >> the >> error messages: >> >> >> Message 48: >> From MAILER-DAEMON(a)lion.protogeek.org Sun Dec 21 03:09:20 >> 2014 >> Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> >> Date: Sun, 21 Dec 2014 03:09:19 -0600 >> From: Mail Delivery Subsystem >> <MAILER-DAEMON(a)lion.protogeek.org> >> To: postmaster(a)lion.protogeek.org >> Content-Type: multipart/report; report-type=delivery-status; >> boundary="sBL97EKS003880.1419152959/lion.protogeek.org" >> Subject: Postmaster notify: see transcript for details >> Auto-Submitted: auto-generated (postmaster-notification) >> Status: R >> >> Part 1: >> >> The original message was received at Tue, 16 Dec 2014 03:09:17 >> -0600 >> from localhost >> with id sBG97E83025627 >> >> ----- The following addresses had permanent fatal errors >> ----- >> <fail2ban(a)example.com> >> >> ----- Transcript of session follows ----- >> <fail2ban(a)example.com>... Deferred: Connection timed out with >> example.com. >> Message could not be delivered for 5 days >> Message will be deleted from queue >> .......... >> >> >> >> I used to get the messages that are now being deleted after five days. >> Any suggestions? > > I would suggest looking at the mailer daemon logs on both the sending > and receiving systems. It would appear that the sending system is > having difficulties at the receiving system end. > > You will likely find the root of your issues in the log entries for > that message (or those messages) that occurred over the 5 days in > question. PS: "Connection timed out with example.com" is the first thing I'd look at. -- Mike Burger http://www.bubbanfriends.org "It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1 ------------------------------ Message: 5 Date: Fri, 26 Dec 2014 21:30:39 +0300 From: ????????? ???????? <nevis2us(a)infoline.su> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Fail2ban mail failures ??? Message-ID: <fd36bb75c1f5fc608b87419adeef4243@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Robert G. (Doc) Savage ????? 2014-12-26 20:39: > I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's > alerts sent to root's mail to be rejected. Here's a clip from one of > the > error messages: > > > Message 48: > From MAILER-DAEMON(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON(a)lion.protogeek.org> > To: postmaster(a)lion.protogeek.org > Content-Type: multipart/report; report-type=delivery-status; > boundary="sBL97EKS003880.1419152959/lion.protogeek.org" > Subject: Postmaster notify: see transcript for details > Auto-Submitted: auto-generated (postmaster-notification) > Status: R > > Part 1: > > The original message was received at Tue, 16 Dec 2014 03:09:17 > -0600 > from localhost > with id sBG97E83025627 > > ----- The following addresses had permanent fatal errors > ----- > <fail2ban(a)example.com> > > ----- Transcript of session follows ----- > <fail2ban(a)example.com>... Deferred: Connection timed out with > example.com. > Message could not be delivered for 5 days > Message will be deleted from queue > .......... > > > > I used to get the messages that are now being deleted after five days. > Any suggestions? Check your /etc/fail2ban/jail.local /etc/fail2ban/jail.conf. You have to provide valid email addresses for dest= and sender= parameters in sendmail-whois or mail-whois actions for enabled jails. ------------------------------ Message: 6 Date: Fri, 26 Dec 2014 19:00:01 -0600 From: "Robert G. (Doc) Savage" <dsavage(a)peaknet.net> To: centos(a)centos.org Subject: Re: [CentOS] Fail2ban mail failures ??? Message-ID: <1419642001.4484.11.camel(a)lion.protogeek.org> Content-Type: text/plain; charset="UTF-8" -----Original Message----- From: ????????? ???????? <nevis2us(a)infoline.su> Reply-to: CentOS mailing list <centos(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Fail2ban mail failures ??? Date: Fri, 26 Dec 2014 21:30:39 +0300 Robert G. (Doc) Savage ????? 2014-12-26 20:39: > I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's > alerts sent to root's mail to be rejected. Here's a clip from one of > the > error messages: > > > Message 48: > From MAILER-DAEMON(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON(a)lion.protogeek.org> > To: postmaster(a)lion.protogeek.org > Content-Type: multipart/report; report-type=delivery-status; > boundary="sBL97EKS003880.1419152959/lion.protogeek.org" > Subject: Postmaster notify: see transcript for details > Auto-Submitted: auto-generated (postmaster-notification) > Status: R > > Part 1: > > The original message was received at Tue, 16 Dec 2014 03:09:17 > -0600 > from localhost > with id sBG97E83025627 > > ----- The following addresses had permanent fatal errors > ----- > <fail2ban(a)example.com> > > ----- Transcript of session follows ----- > <fail2ban(a)example.com>... Deferred: Connection timed out with > example.com. > Message could not be delivered for 5 days > Message will be deleted from queue > .......... > > > > I used to get the messages that are now being deleted after five days. > Any suggestions? Check your /etc/fail2ban/jail.local /etc/fail2ban/jail.conf. You have to provide valid email addresses for dest= and sender= parameters in sendmail-whois or mail-whois actions for enabled jails. os.org/mailman/listinfo/centos ????????? ????????, I should have made it clear that this is all on one machine. The jail.conf file is the default from the fail2ban package. It used to work perfectly, but now has the mail problem. All I've had to do for years is install the fail2ban package, start it, and make it autostart whenever I reboot. Now it's misbehaving in a way that puzzles me. --Doc Savage Fairview Heights, IL ------------------------------ Message: 7 Date: Fri, 26 Dec 2014 22:17:39 -0800 From: Greg Lindahl <lindahl(a)pbm.com> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] CentOS 7 boot network problem Message-ID: <20141227061739.GA1973(a)bx9.net> Content-Type: text/plain; charset=us-ascii >From reading http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ it seems that this is a common problem, and that systemctl enable NetworkManager-wait-online.service might be a solution. I have a bunch of IP aliases on the same network interface, is that what's caused my problem? On Sat, Dec 20, 2014 at 01:05:01PM -0800, Greg Lindahl wrote: > I rebooted a new CentOS 7 host and it attempted to start postfix and > apache before the network came up. Needless to say both complained > that they couldn't bind to the requested IP address and "entered the > failed state." > > Did I miss an option somewhere? The network config is a manual one, > and I see from the generated file in /etc/sysconfig/network-scripts > that ONBOOT="yes"... > > -- greg > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos ------------------------------ Message: 8 Date: Sat, 27 Dec 2014 12:24:19 +0300 From: ????????? ???????? <nevis2us(a)infoline.su> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Fail2ban mail failures ??? Message-ID: <d0ba95645f021fb68d4cff013c7d5bf3@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed >> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's >> alerts sent to root's mail to be rejected. Here's a clip from one of >> the >> error messages: >> >> >> Message 48: >> From MAILER-DAEMON(a)lion.protogeek.org Sun Dec 21 03:09:20 >> 2014 >> Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> >> Date: Sun, 21 Dec 2014 03:09:19 -0600 >> From: Mail Delivery Subsystem >> <MAILER-DAEMON(a)lion.protogeek.org> >> To: postmaster(a)lion.protogeek.org >> Content-Type: multipart/report; report-type=delivery-status; >> boundary="sBL97EKS003880.1419152959/lion.protogeek.org" >> Subject: Postmaster notify: see transcript for details >> Auto-Submitted: auto-generated (postmaster-notification) >> Status: R >> >> Part 1: >> >> The original message was received at Tue, 16 Dec 2014 03:09:17 >> -0600 >> from localhost >> with id sBG97E83025627 >> >> ----- The following addresses had permanent fatal errors >> ----- >> <fail2ban(a)example.com> >> >> ----- Transcript of session follows ----- >> <fail2ban(a)example.com>... Deferred: Connection timed out with >> example.com. >> Message could not be delivered for 5 days >> Message will be deleted from queue >> .......... >> >> >> >> I used to get the messages that are now being deleted after five days. >> Any suggestions? > > Check your /etc/fail2ban/jail.local /etc/fail2ban/jail.conf. > You have to provide valid email addresses for dest= and sender= > parameters in sendmail-whois or mail-whois actions for enabled jails. > os.org/mailman/listinfo/centos > > > ????????? ????????, > > I should have made it clear that this is all on one machine. The > jail.conf file is the default from the fail2ban package. It used to > work > perfectly, but now has the mail problem. All I've had to do for years > is > install the fail2ban package, start it, and make it autostart whenever > I > reboot. Now it's misbehaving in a way that puzzles me. Robert, If you never changed fail2ban defaults you probably had email aliases defined somewhere in your configurations. Whatever you had it was incorrect and it's not worth the effort to figure out why it ever worked if at all. The "right" way is to use email addresses in (at least locally) routable domains. Alexander ------------------------------ _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos End of CentOS Digest, Vol 119, Issue 26 ***************************************

1 0

Re: [CentOS] Fail2ban mail failures ???
by James B. Byrne 27 Dec '14

27 Dec '14

On Fri, December 26, 2014 12:59, Mike Burger wrote: > On 2014-12-26 12:39 pm, Robert G. (Doc) Savage wrote: >> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's >> alerts sent to root's mail to be rejected. Here's a clip from one of >> the >> error messages: >> >> >> Message 48: >> From MAILER-DAEMON(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 >> Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> >> Date: Sun, 21 Dec 2014 03:09:19 -0600 >> From: Mail Delivery Subsystem >> <MAILER-DAEMON(a)lion.protogeek.org> >> To: postmaster(a)lion.protogeek.org >> Content-Type: multipart/report; report-type=delivery-status; >> boundary="sBL97EKS003880.1419152959/lion.protogeek.org" >> Subject: Postmaster notify: see transcript for details >> Auto-Submitted: auto-generated (postmaster-notification) >> Status: R >> >> Part 1: >> >> The original message was received at Tue, 16 Dec 2014 03:09:17 >> -0600 >> from localhost >> with id sBG97E83025627 >> >> ----- The following addresses had permanent fatal errors >> ----- >> <fail2ban(a)example.com> >> >> ----- Transcript of session follows ----- >> <fail2ban(a)example.com>... Deferred: Connection timed out with >> example.com. >> Message could not be delivered for 5 days >> Message will be deleted from queue >> .......... >> >> >> >> I used to get the messages that are now being deleted after five days. >> Any suggestions? > > I would suggest looking at the mailer daemon logs on both the sending > and receiving systems. It would appear that the sending system is having > difficulties at the receiving system end. > > You will likely find the root of your issues in the log entries for that > message (or those messages) that occurred over the 5 days in question. > Just checking the obvious but can you confirm that you are not actually sending messages to example.com? -- *** 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

1 0

PXE install in a boot on san with LVM environment, fails after reboot
by Damien Gouju 27 Dec '14

27 Dec '14

Hello, I need to automate installation of CentOS 7.0 using PXE and kickstart. My server is diskless, I'm installing CentOS on a 25GB LUN on a FC SAN with 4 paths. This LUN is the only one accessible by the server. Anaconda processes successfully the installation. But on reboot, I get stuck on a prompt after BIOS. I think I have an issue with storage configuration / bootloader configuration... I can install it using the ISO, with basic configuration. The /root/anaconda-ks.cfg looks like the following (I striped some part, I cannot copy past because I have only console access through a secured VPN :-/ ): firstboot --enable ignoredisk --only-use=mpatha,sdc,sdd,sdb,sda bootloader --location=mbr --boot-drive=mpatha autopart --type=lvm clearpart --all --initlabel --drives=mpatha %packages @base @core %end My ks.cfg template is identical (I also cannot attach it unfortunately…). I tried several things like: - put sda as boot-drive for bootloader (according to http://osdir.com/ml/general/2014-09/msg52181.html ), but anaconda fails with error that this drive cannot be found. It asks to choose another disk, mpatha is the only available. - same with dm-0 (as /dev/mapper/mpatha is a symlink to /dev/dm-0) but anaconda also fails - add to bootloader « --append="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap" » I also found some post on the web saying that in the « ignoredisk » mpatha mustn't be used but disk/by-id/scsi-XXXX (chapter 23.3.2 of RHEL 7 installation guide), but I don’t know how to manage that. Is someone ever did that kind of PXE installation, with boot on san & LVM, and help me in the kickstart configuration? Any help would be highly appreciated! Best regards, Damien

1 1

Fail2ban mail failures ???
by Robert G. (Doc) Savage 27 Dec '14

27 Dec '14

I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's alerts sent to root's mail to be rejected. Here's a clip from one of the error messages: Message 48: From MAILER-DAEMON(a)lion.protogeek.org Sun Dec 21 03:09:20 2014 Return-Path: <MAILER-DAEMON(a)lion.protogeek.org> Date: Sun, 21 Dec 2014 03:09:19 -0600 From: Mail Delivery Subsystem <MAILER-DAEMON(a)lion.protogeek.org> To: postmaster(a)lion.protogeek.org Content-Type: multipart/report; report-type=delivery-status; boundary="sBL97EKS003880.1419152959/lion.protogeek.org" Subject: Postmaster notify: see transcript for details Auto-Submitted: auto-generated (postmaster-notification) Status: R Part 1: The original message was received at Tue, 16 Dec 2014 03:09:17 -0600 from localhost with id sBG97E83025627 ----- The following addresses had permanent fatal errors ----- <fail2ban(a)example.com> ----- Transcript of session follows ----- <fail2ban(a)example.com>... Deferred: Connection timed out with example.com. Message could not be delivered for 5 days Message will be deleted from queue .......... I used to get the messages that are now being deleted after five days. Any suggestions? --Doc Savage Fairview Heights, IL

3 5

CentOS 7 boot network problem
by Greg Lindahl 27 Dec '14

27 Dec '14

I rebooted a new CentOS 7 host and it attempted to start postfix and apache before the network came up. Needless to say both complained that they couldn't bind to the requested IP address and "entered the failed state." Did I miss an option somewhere? The network config is a manual one, and I see from the generated file in /etc/sysconfig/network-scripts that ONBOOT="yes"... -- greg

1 1

(py)curl error 7
by Mateusz Guz 26 Dec '14

26 Dec '14

Hi, Disabled ipv6 (using sysctl, disabled ip6tables, no reboot, no proxy present) and still get the message as below. Centos 6.3 (i know its old) Kernel : 2.6.32-279.14.1.el6.x86_64 (I know its old) Standard /etc/yum.conf (no changes) Standard repos (centos base), enabled Cleaned cache: yum metadata (didn't work) Then: yum clean all (didn't work) Then yum makecache (didn't work) Yum repolist Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os error was 14: PYCURL ERROR 7 - "Failed to connect to 2a02:2498:1:3d:5054:ff:fed3:e91a: Network is unreachable" Ping on mirrorlist.centos.org is OK Curl mirrrorlist.centos.org NOT_OK Message started to occur suddenly, I didn't even update any package. Any suggestions ?

2 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss