- Discuss - lists.centos.org

None
by None 07 Sep '16

07 Sep '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u8727fcW006708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Tue, 6 Sep 2016 22:07:42 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> <c29b1a4f-a3d5-b61e-7206-b6e32a89f72c(a)mit.edu> <CAJCQCtQ6vq6OQsbgZjxz2qqgjGwh-XEwsoeBYjzwNMMcvQkDrQ(a)mail.gmail.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <8b172cfc-7a1a-39e2-a259-a698f2fa63ba(a)mit.edu> Date: Tue, 6 Sep 2016 22:07:35 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <CAJCQCtQ6vq6OQsbgZjxz2qqgjGwh-XEwsoeBYjzwNMMcvQkDrQ(a)mail.gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOIsWRmVeSWpSXmKPExsUixG6nrptXdj7cYP5DE4tlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CVMbv5EVPBCfGKBZ/CGxhnCHcxcnJICJhInGh6ydzFyMUhJNDG JHG/8yobhHOCUeLq/8ksEM4BJomW/suMIC3CAo4SL15uZwOxRQREJXoWv4LquMIsMeHuRyaQ BJuAgsS6W2fYQWxeASuJqXdvgDWzCKhI7Dv+ihnEFhWIkLi16iMjRI2gxMmZT1hAbE6BQIm5 E2eC2cwCthJ35u5mhrDlJba/ncM8gZF/FpKWWUjKZiEpW8DIvIpRNiW3Sjc3MTOnODVZtzg5 MS8vtUjXVC83s0QvNaV0EyM4/FyUdjBO/Od1iFGAg1GJh7di97lwIdbEsuLK3EOMkhxMSqK8 aoFAIb6k/JTKjMTijPii0pzU4kOMEhzMSiK8swrPhwvxpiRWVqUW5cOkpDlYlMR5u2YcCBcS SE8sSc1OTS1ILYLJynBwKEnwVpcCNQoWpaanVqRl5pQgpJk4OEGG8wANzwCp4S0uSMwtzkyH yJ9iVJQS550JkhAASWSU5sH1gtODGvuhV4ziQK8I8y4HqeIBpha47ldAg5mABq/bfRpkcEki QkqqgdHumJ85C5vW18rsVTyCu9hbrXdG2i/MkH2WXn78eE+i2V6Lk/ebckNVCli+3O24tr6E bfeV0xsEjxTsCnVyNN0hMzf47a/tF/aLrCntn2w/MVOm4uYq+am5pdVfVWufLhcQn1Nz3Db2 jNUdszzZz0YlYSf0ikR1G3PO+afcqT8ke64wUXd1ixJLcUaioRZzUXEiANN4uRjqAgAA Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Wed, 07 Sep 2016 02:07:43 -0000 Trying the gluster client seems to fix the problem. On 09/02/2016 12:57 AM, Chris Murphy wrote: > On Thu, Sep 1, 2016, 8:11 AM Pat Haley <phaley(a)mit.edu> wrote: > >> For the enforcing=0, is that referring to SELinux? If so, we are not >> running SELinux. >> > > OK so neither that nor chcon nor context mount option apply. It's something > else. > > > > > >> On 08/31/2016 11:38 PM, Chris Murphy wrote: >> >> ---------------------------------------------------------------------------------------- >>> Try booting with enforcing=0 and if that fixes it, you need to find out >>> what security label is needed for gluster. >> ---------------------------------------------------------------------------------------- >> For the enforcing=0, is that referring to SELinux? If so, we are not >> running SELinux. >> >> ----------------------------------------------------------------------------------------- >> >>> Chances are it's easiest to use -o context= mount option on the brick, >> but >>> if the brick is not exclusive to gluster you'll need chcon -R. >> ----------------------------------------------------------------------------------------- >> We aren't sure exactly what you mean by this second paragraph, can >> you expand on this? Are these two exclusive options exclusive? We aren't >> sure what you what you mean by "exclusive to gluster" >> >> ----------------------------------------------------------------------------------------- >>> If that's not it, maybe try the gluster client instead of using NFS. See >> if >>> you get a different result that narrows down what's going on. >>> >>> My vague recollection is for Samba, without the correct SELinux label, I >>> could neither read nor write. >>> >>> >>> Chris Murphy >>> _______________________________________________ >>> CentOS mailing list >>> CentOS(a)centos.org >>> https://lists.centos.org/mailman/listinfo/centos >> -- >> >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> Pat Haley Email: phaley(a)mit.edu >> Center for Ocean Engineering Phone: (617) 253-6824 >> Dept. of Mechanical Engineering Fax: (617) 253-8125 >> MIT, Room 5-213 http://web.mit.edu/phaley/www/ >> 77 Massachusetts Avenue >> Cambridge, MA 02139-4301 >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

389 Directory Server
by Paolo Rughetti 06 Sep '16

06 Sep '16

Hi all, I would like install 389 Directory Server on a Centos 6.8 server. I followed the instructions reported in : https://wiki.centos.org/HowTos/DirectoryServerSetup?highlight=%28directory%… and installed with yum the following packages : 389-ds-base-1.2.11.15-75.el6_8.x86_64 389-ds-console-1.2.6-1.el6.noarch 389-ds-base-libs-1.2.11.15-75.el6_8.x86_64 389-adminutil-1.1.19-1.el6.x86_64 389-admin-1.1.35-1.el6.x86_64 To proceed with the installation I would like to read the instructions reported here : https://access.redhat.com/documentation/en/red-hat-directory-server/ where I can choose the product version between 8.0 to 10. I would like to know which version of 389 Directory Server match installed packages so I can select the right manual. I would like also to know if it is better install the last version of 389 from http://www.port389.org. Thanking you in advance. Bets regards. -- *---*---*---*---*---*---*---*---*---*---*---*---*---*---* Paolo Rughetti Consiglio Nazionale delle Ricerche Istituto per le Applicazioni del Calcolo "M. Picone" Via dei Taurini 19 00185 ROME ITALY _____________________________ |\___________________________/| |E-mail: p.rughetti(a)iac.cnr.it| |Tel: 039-06-49270956 | |Fax: 039-06-4404306 | |_____________________________| *---*---*---*---*---*---*---*---*---*---*---*---*---*---*

2 1

more than one IP address on network device?
by Walter H. 06 Sep '16

06 Sep '16

Hello /etc/sysconfig/network-scripts/ifcfg-eth0 looks like this: # Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) TYPE=Ethernet NAME=eth0 NM_CONTROLLED=no IPV4_FAILURE_FATAL=yes UUID=cc2635ff-3c14-48ba-b19a-84c5b9d36a9d ONBOOT=yes DEVICE=eth0 BOOTPROTO=none HWADDR=00:50:56:01:00:01 BROADCAST=192.168.0.255 IPADDR=192.168.0.10 NETMASK=255.255.255.0 NETWORK=192.168.0.0 GATEWAY=192.168.0.1 DNS1=192.168.0.1 DNS2=192.168.0.100 DOMAIN='domain.tld' USERCTL=no IPV6INIT=yes IPV6ADDR=ipv6addr IPV6_AUTOCONF=no IPV6_DEFAULTGW=ipv6addr-gateway IPV6_DEFAULTDEV=eth0 if I would need an additional IPv6 address I'd just add IPV6ADDR_SECONDARIES="ipv6addr" to this file; if I would need an additional IPv4 address this works only by a virtual device e.g. eth0:1 like this: /etc/sysconfig/network-scripts/ifcfg-eth0:1 # Intel Corporation 82545EM Gigabit Ethernet Controller (Copper), Alias 1 TYPE=Ethernet DEVICE=eth0:1 ONPARENT=yes BOOTPROTO=none BROADCAST=192.168.0.255 IPADDR=192.168.0.17 NETMASK=255.255.255.0 NETWORK=192.168.0.0 GATEWAY=192.168.0.1 DNS1=192.168.0.1 DNS2=192.168.0.100 why can't I add this to the virtual device eth0:1, if I needed both an additional IPv4 and an additional IPv6 address? IPV6INIT=yes IPV6ADDR=ipv6addr IPV6_AUTOCONF=no IPV6_DEFAULTGW=ipv6addr-gateway IPV6_DEFAULTDEV=eth0:1 Thanks, Walter

12 20

/etc/sysconfig/network HOSTNAME settings
by Walter H. 06 Sep '16

06 Sep '16

Hello, I found different ways to define the hostname ... this HOSTNAME="host.domain.tld" or this: HOSTNAME="host" DOMAIN="domain.tld" what is the correct way? Thanks, Walter

2 1

mounting lvm2
by Alice Wonder 06 Sep '16

06 Sep '16

CentOS 7 for everything I am probably never using lvm again. I have never not once actually benefited from its capabilities but this is probably the third or fourth time it has gotten in my way. Issue is that I use the tools so rarely that I can't recall what needs to be done to properly mount the drives on another system and finding that info on the web is becoming more difficult as the noise in search results increases, more and more results are damn youtube videos, and my eyes are deteriorating. So its just fixed ext4 for me in the future, KISS. End of rant. PC mobo died. Most data I need from it backed up to github, few things done that day didn't make the last commit and I'd rather not do them again. Trying to mount drive on my laptop via USB interface. Which is easy when drives are plain old ext4 and not ext4 sitting on top lvm2. * end frustrated rant * [root@localhost ~]# vgs VG #PV #LV #SN Attr VSize VFree centos 1 3 0 wz--n- 111.30g 0 centos 1 3 0 wz--n- 223.08g 0 [root@localhost ~]# vgscan Reading all physical volumes. This may take a while... Found volume group "centos" using metadata type lvm2 Found volume group "centos" using metadata type lvm2 [root@localhost ~]# [root@localhost ~]# pvdisplay /dev/sdb2 --- Physical volume --- PV Name /dev/sdb2 VG Name centos PV Size 111.30 GiB / not usable 4.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 28492 Free PE 0 Allocated PE 28492 PV UUID mnFTy9-PoVX-paaA-iBML-kXh5-1Zk5-PQTPW1 [root@localhost ~]# That's the volume that I need to mount, it is in a VG named centos which is the same VG name as what the laptop I am using uses. I have created /mnt/tmp which is where I want to mount it. I am a bit worried both having the same VG name (centos) may be an issue, I believe the next step is suppose to be to use vgchange to activate the volume group but I am a bit hesitant to issuing that command with an argument that includes a volume group that is already active. There is only one physical disc in the volume I need to mount, that was a lesson I learned the hard way previously - don't use multiple disks in a LVM2 volume without hardware redundancy. And with today's disk sizes it really isn't needed, not for what I do. Where do I go from here to mount that volume? Thanks. -- -=- Sent my from my laptop, may not be able to respond timely

4 4

Network manager cannot connet to the Internet
by sunyeping 06 Sep '16

06 Sep '16

Dear all, I find out of a sudden my Network manager cannot connect to the Internet. My OS is Centos 6.7, and the version of Network manager is Applet 0.8.1. When clinking the Network manager icon at the upper right conner at the Desktop of my compuer, I can see in the pop-up manu that there are two network cards (Intel 82573E Gigabit Ethernet Controller (Copper) and Intel 82573L Gigabit Ethernet Controller) but only one link (System eth1) available. Usually when clicking the "System eth1" the Internet connection would be established. However from this morning clicking the "System eth1" only gives connect failure information. I don't know whether this is caused by intalling a large software package (ambertool 16 ) which requires many updates in my system yesterday. But when I give "ifconfig" command in a gnome terminal, the output information seems to be correct: [sunyp@localhost Desktop]$ ifconfig eth0 Link encap:Ethernet HWaddr 00:25:90:72:E2:86 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:16 Memory:faee0000-faf00000 eth1 Link encap:Ethernet HWaddr 00:25:90:72:E2:87 inet6 addr: fe80::225:90ff:fe72:e287/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16386 (16.0 KiB) TX bytes:3038 (2.9 KiB) Interrupt:17 Memory:fafe0000-fb000000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:90 errors:0 dropped:0 overruns:0 frame:0 TX packets:90 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6737 (6.5 KiB) TX bytes:6737 (6.5 KiB) What I can do now? Could anyone help me with this problem? Best regards. Yeping Sun

3 2

Whether to use systemd to start services
by Stalker, Tim 06 Sep '16

06 Sep '16

I'm wondering if it's normally required to start services with systemd as opposed to sysv? I currently load a few services using the old init.d/service funtionality, which still works fine. Is this ok or is sysv going to be fully discontinued in the future? The service I load is celeryd via init.d but so far finding few pointers as to how to do this with a celery.service file. I can load the service with this line execStart=/etc/init.d/celeryd Thanks, Tim

2 1

CentOS-announce Digest, Vol 139, Issue 1
by centos-announce-request＠centos.org 06 Sep '16

06 Sep '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2016:1797 Moderate CentOS 6 ipa Security Update (Johnny Hughes) 2. CESA-2016:1809 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 3. CESA-2016:1809 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 4. CESA-2016:1797 Moderate CentOS 7 ipa Security Update (Johnny Hughes) 5. CEBA-2016:1782 CentOS 5 kernel BugFix Update (Johnny Hughes) 6. CEEA-2016:1780 CentOS 7 megaraid_sas Enhancement Update (Johnny Hughes) 7. CESA-2016:1809 Important CentOS 5 thunderbird Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Sep 2016 21:43:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1797 Moderate CentOS 6 ipa Security Update Message-ID: <20160905214335.GA53161(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1797 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1797.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9a76945f5e53fe3c46ba6b2e8d41153083e277ed1489e061e0362b367cf24d4c ipa-admintools-3.0.0-50.el6.centos.2.i686.rpm 6f680dcb53cac90df163ec295785294f0ec32f24b15597a5daca0313b08381ee ipa-client-3.0.0-50.el6.centos.2.i686.rpm 84e184732f6308d01aafb08ab5fb9a1ae598e8e7571ff3e0f3a1ffdf7ab7ea1e ipa-python-3.0.0-50.el6.centos.2.i686.rpm 07fef5c092bac45a50d3247960ecdc0dec541fbfbec477d3349e1448d35c14d6 ipa-server-3.0.0-50.el6.centos.2.i686.rpm 4d5b11679dc5e57df4fa0dc140286d0b9ef412427595428b34082022512b3d76 ipa-server-selinux-3.0.0-50.el6.centos.2.i686.rpm deeeed4c887d0e4e30d89488530783aa9753a5b745a4ecbe693871a48304acea ipa-server-trust-ad-3.0.0-50.el6.centos.2.i686.rpm x86_64: 587735bf88f12a0bafd20ee1a9705a95005bc96a0de2e38af2b7fda50000ef0e ipa-admintools-3.0.0-50.el6.centos.2.x86_64.rpm 031cba9a9b15305d4012ec302075d00775177f2b90edc81708d05e7d3eb6231f ipa-client-3.0.0-50.el6.centos.2.x86_64.rpm be36a599f91e5145e3bfe7f2667df00bc8ce3a687116faf44319b4aa489cb11a ipa-python-3.0.0-50.el6.centos.2.x86_64.rpm eb88f0ebfae6ab06720dd9e7fc39084f49be08e779348489881a89e784727ef6 ipa-server-3.0.0-50.el6.centos.2.x86_64.rpm 83f5893b4987c35cec70208fc24b6d4b791711b98c872af999ffd65174e7feb5 ipa-server-selinux-3.0.0-50.el6.centos.2.x86_64.rpm bafa5aff6a70875f2c61f6b98743d699e33ba416d14cfc8376fe9942c8455b3f ipa-server-trust-ad-3.0.0-50.el6.centos.2.x86_64.rpm Source: eedfa288be6cc62b86d9256c2858fcf24a0ee92f76ae69bed4c6138e3a1a651c ipa-3.0.0-50.el6.centos.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 6 Sep 2016 00:52:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 6 thunderbird Security Update Message-ID: <20160906005240.GA57754(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 160bf41d5398da8512e7fa77a05c3a0dc80d7360cfa79391a8a81cfc4ecb6352 thunderbird-45.3.0-1.el6.centos.i686.rpm x86_64: 6373b92e88b90d043376aa5d712bf272ad3ef57cdf869ffced7c8ab225c121e2 thunderbird-45.3.0-1.el6.centos.x86_64.rpm Source: 30a522d59cf4ea68f38a2abaeff0678b933f47ac3f24d488548a33d66c50d526 thunderbird-45.3.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 6 Sep 2016 01:03:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 7 thunderbird Security Update Message-ID: <20160906010339.GA611(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b27f983a9dec3f17f00b47d9d7666b09f4cec07dda59f802698355cb03f7637f thunderbird-45.3.0-1.el7.centos.x86_64.rpm Source: 6212956c18c7e6d7dde1b6008ef6ce2ba4b4cbe1be20ab3a7df8760c9d64074d thunderbird-45.3.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 6 Sep 2016 01:06:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1797 Moderate CentOS 7 ipa Security Update Message-ID: <20160906010650.GA738(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1797 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1797.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a7723ce570b09c36f1ada06495f1f94a29da95d4c67fd0e65bef2b88887e3759 ipa-admintools-4.2.0-15.0.1.el7.centos.19.x86_64.rpm d87a6bb3956f5260d41dcedfe36a9baec7769896554203cb2aae40094f84d19f ipa-client-4.2.0-15.0.1.el7.centos.19.x86_64.rpm edef4178644b2c9563a267ffa829b27788e2835a4f3da1c99e41298ff181ddda ipa-python-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 6e4ec8cea775914ea5901ca0cb79f11784382402a2d3dee3087c292e2941f47d ipa-server-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 008c9b943528d60aac4f50114a3b414d969f3d8833a70d2384370b48d2c93501 ipa-server-dns-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 4d05bc6e0bbb71e03c1b30875ab2753510885e2b31af15039c05c12960c30b4e ipa-server-trust-ad-4.2.0-15.0.1.el7.centos.19.x86_64.rpm Source: 02a7bacd4d9918c760425e5dbefd0f3fddfbbc7ea676f2d6e5ac05f62b689a49 ipa-4.2.0-15.0.1.el7.centos.19.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Tue, 6 Sep 2016 02:32:18 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1782 CentOS 5 kernel BugFix Update Message-ID: <20160906023218.GA2750(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1782 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1782.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1cceade3db635e6bf40767b8aa889f606f9cd2dc520fb052a96b6e57238feaa0 kernel-2.6.18-412.el5.i686.rpm 8945438f684a6aa25b76fd80feb732b9ac3e255d04b58de5505564a7145bd3b5 kernel-debug-2.6.18-412.el5.i686.rpm 61d2a461ba59ac6e320467b30bf6c42e987404f38d66cb31a5dd79521d3b3687 kernel-debug-devel-2.6.18-412.el5.i686.rpm 72605760160a752047e16fd5df9ed9fe570adc9971cff8541cee85c0c8b46a53 kernel-devel-2.6.18-412.el5.i686.rpm 42f7cc1cbb5cef688e2ce0c2eb08762893388a62d82abf9c29e9177c925aa805 kernel-doc-2.6.18-412.el5.noarch.rpm 2d9bb3dec0d4fc5d10c0b0387f29548873e4a1f392a6ab6942d1b89aa59ff438 kernel-headers-2.6.18-412.el5.i386.rpm b4172316d3e8f8abf971e584ff1f6430608ecd3a39a1905eb100b863a326779b kernel-PAE-2.6.18-412.el5.i686.rpm e6ab24b639e50767707b7f12db2df390bd3ca890dfae45a1a3f8d3140c5fd72a kernel-PAE-devel-2.6.18-412.el5.i686.rpm cb983ecf3dfc441fab4fce2d37b3bf7f7ff5aac9fe540b7f9f2960314e62c54e kernel-xen-2.6.18-412.el5.i686.rpm 65ae34ecd9bea1bf2602db9a86c2c18cf092def5f66974c355ea406d6e1a141f kernel-xen-devel-2.6.18-412.el5.i686.rpm x86_64: 84f47ad942923cf26eee3b7d5b11f568432dd0254f4134e00e691e44a05ce487 kernel-2.6.18-412.el5.x86_64.rpm 05514dabf3ebedfdc73dac2f3a6b5fa225652a6b975466e5dcbfad6750600b77 kernel-debug-2.6.18-412.el5.x86_64.rpm ff51e7bcf97ce8d7e06ba182b887c027179d8b8f098ea27e4fce26b742735997 kernel-debug-devel-2.6.18-412.el5.x86_64.rpm ba7bb3a039d17b1b77c6b61d1bcb10a5b525d86409b5d62675f6e3050fd74491 kernel-devel-2.6.18-412.el5.x86_64.rpm 42f7cc1cbb5cef688e2ce0c2eb08762893388a62d82abf9c29e9177c925aa805 kernel-doc-2.6.18-412.el5.noarch.rpm 7fc9955692715dbdc376b44010bea114e71f4504c31174102edc4666242111bc kernel-headers-2.6.18-412.el5.x86_64.rpm 8e2b726c35e8abf898ba536ae46bd2d5dda07e05ccaabb20149e36cdbfe2a632 kernel-xen-2.6.18-412.el5.x86_64.rpm 69087d91bc243cbea186d77f15ed57b5f53da6871ab9fe2d8a71484bf7f6a04e kernel-xen-devel-2.6.18-412.el5.x86_64.rpm Source: 396e2d189ecfb2c31254e7d657e208ac3c9ea0e31f7ae399ca7a5f9b36b97495 kernel-2.6.18-412.el5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 6 Date: Tue, 6 Sep 2016 03:16:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2016:1780 CentOS 7 megaraid_sas Enhancement Update Message-ID: <20160906031644.GA4629(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2016:1780 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1780.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3f942683663a5acf3ec76fbc4da33363451ff5778ea1da2dec382806510af15f kmod-megaraid_sas-06.811.02.00-1.el7_2.x86_64.rpm Source: 1433047acea21ed246eb8eaf21f0b6856722158687bdc521ab9a6466566d798d megaraid_sas-06.811.02.00-1.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Tue, 6 Sep 2016 03:19:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 5 thunderbird Security Update Message-ID: <20160906031956.GA4578(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4cb84a2e017f0e5ed15f2c76e633f1ed84c23d466fb11c856847cbd3e49a3533 thunderbird-45.3.0-1.el5.centos.i386.rpm x86_64: 5ef01b379661dcf482838ccac167aeb9fca091b6fa2cfab1ca0a0facf3d41523 thunderbird-45.3.0-1.el5.centos.x86_64.rpm Source: f6a805f44b19087570cae54f6790916279351bf878bd9f51f742bd7175803877 thunderbird-45.3.0-1.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 139, Issue 1 ***********************************************

1 0

hacking grub to control number of retained kernels.
by Fred Smith 06 Sep '16

06 Sep '16

I've recently had this problem on two C7 systems, wherein when doing "yum update", I get a warning about /boot being low on space. both systems were installed using the partition size recommended by Anaconda, right now "df -h" shows /boot as 494M, with 79M free. I don't store unrelated crap on /boot, I assume that yum and/or grub will manage it for me. So, why, after over a year, is it running low on space on two different systems? Is there some location in /boot where junk piles up, but shouldn't, that I have to know about so I can clean it out? I see EIGHT initramfs files in /boot, two per kernel, same name but one has a kdump just before the .img suffix. do I need those for old kernels that I may or may not ever boot? (they're 30 to 50 MB each). For the moment I've edited /etc/grub.conf and changed installonly_limit from 4 to 3. (related question: do I need to manually remove the oldest kernel, having done this, or will yum/grub clean it up the next time there's a kernel to install?) thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- I can do all things through Christ who strengthens me. ------------------------------ Philippians 4:13 -------------------------------

4 4

Centos7 kickstart & pxe
by johan.vermeulen7＠telenet.be 05 Sep '16

05 Sep '16

Hello All, I'm trying to get kickstart to work through pxe. So far I've set up dhcp server, tftp and so on. But it seems at some point I always get stuck because the iso file is write-protected. I've tried remounting it rw, and I 've dd the iso first, I then get EM not a block device. Any help would be appreciated. Greetings, J.

3 4

/etc/sysconfig/network HOSTNAME settings
by Walter H. 04 Sep '16

04 Sep '16

Hello, I found different ways to define the hostname ... this HOSTNAME="host.domain.tld" or this: HOSTNAME="host" DOMAIN="domain.tld" what is the correct way? Thanks, Walter

3 2

How do I install uwsgi + python 3?
by Yuri Kanivetsky 04 Sep '16

04 Sep '16

Hi, >From what I can see, epel doesn't have python 3's pip. But when I install python35u (ius) and uwsgi-python-plugin3, uwsgi's python doesn't seem to find virtual env's packages. When I install python34u (ius) and uwsgi-plugin-python3, I get a conflict. Am I doing anything wrong? Regards, Yuri

1 0

Re: [CentOS] Networking/routing issue
by tdukes＠palmettoshopper.com 03 Sep '16

03 Sep '16

-------- Original Message -------- Subject: Re: [CentOS] Networking/routing issue From: Ulf Volmer <u.volmer(a)u-v.de> Date: Sat, September 03, 2016 5:47 am To: centos(a)centos.org On 09/03/2016 01:31 PM, TE Dukes wrote: > Centos 6.8 server eth0 > 192.168.1.110 > gateway 192.168.1.111 > eth1 > 192.168.1.111 > gateway > 192.168.1.100 > | > | > Switch > other computers and devices > gateway 192.168.1.110 > > I want to send all internal traffic through 192.168.1.110, all external > traffic through 192.168.1.111, then back through 192.168.1.110. As far as i understand, you have two interfaces in the same subnet. This is usually a bad idea. best regards Ulf Volmer A few of the examples I tried, had them on different subnets. I will change that and see what happens. Thanks

1 0

Networking/routing issue
by TE Dukes 03 Sep '16

03 Sep '16

Hello, I've been working on this for over a week. I don't think its working the way it should. Here's what I'm trying to do: I have a Windstream dsl router with wireless > 192.168.1.100 | | Centos 6.8 server eth0 > 192.168.1.110 > gateway 192.168.1.111 eth1 > 192.168.1.111 > gateway 192.168.1.100 | | Switch > other computers and devices > gateway 192.168.1.110 I want to send all internal traffic through 192.168.1.110, all external traffic through 192.168.1.111, then back through 192.168.1.110. I did an iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE Issues: Outside connectivity for all other computers and devices only works if eth0 is also connected to the router, server works Iptraf shows no traffic on eth1 Hope I haven't confused you as I have thoroughly confused myself. TIA TE Dukes

3 3

Re: [CentOS] Network manager cannot connet to the Internet
by sunyeping 03 Sep '16

03 Sep '16

Hi, Earl, Thank you very much for your prompt response.There is no output for "ip route"I don't know what is my default gateway and how to check it? And how to check the device that I am connecting to? Best regards. Yeping------------------------------------------------------------------From:Earl A Ramirez <earlaramirez(a)gmail.com>Time:2016 Sep 3 (Sat) 18:38To:CentOS mailing list <centos(a)centos.org>Subject:Re: [CentOS] Network manager cannot connet to the Internet What is the output of ip route show, can you ping your gateway, first see if you can ping your default gateway and if you can't you will have to check the device that your are connecting to. -- Kind Regards Earl Ramirez _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] CentOS Digest, Vol 140, Issue 1
by SUDHANSHU BHUTANI 02 Sep '16

02 Sep '16

On Thu, Sep 1, 2016 at 5:30 PM, <centos-request(a)centos.org> wrote: > Send CentOS mailing list submissions to > centos(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://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: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 2. Re: NODEJS010-NPM is not getting installed due to dependency > errors on Custom Centos ISO installation (Jim Perrin) > 3. Re: CentOS 6 - logwatch report not in HTML format > (Alexander Farber) > 4. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 5. Re: CentOS 6 - logwatch report not in HTML format > (Alexander Farber) > 6. Re: group write permissions not being respected (Gordon Messmer) > 7. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 8. Re: group write permissions not being respected (Pat Haley) > 9. Re: group write permissions not being respected (m.roth(a)5-cent.us) > 10. Re: group write permissions not being respected (Pat Haley) > 11. Re: group write permissions not being respected (Chris Murphy) > 12. Perl Unsafe Module Path Handling Directory Traversal > Vulnerability ( CVE-2016-1238) (Sidharth Sharma) > 13. Bind Vulnerability CVE-2016-2775 (Sidharth Sharma) > 14. Re: "Windows" share issue; access via smb:// fails, "mount -t > cifs" works (Toralf Lund) > 15. Re: Bind Vulnerability CVE-2016-2775 (James Pearson) > 16. Re: Bind Vulnerability CVE-2016-2775 (Mike Burger) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 31 Aug 2016 07:11:11 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gCz6SDqu8i5aHkUU58Sb91cHdNKUy=J_rYP25X48gk22Q(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber > <alexander.farber(a)gmail.com> wrote: >> No, I mean there is sometimes a variable for mail format too: > > The HTML formatting is a logwatch option, invoked through the > logwatch.conf file. > > -- Arun Khan > > > ------------------------------ > > Message: 2 > Date: Wed, 31 Aug 2016 09:20:26 -0500 > From: Jim Perrin <jperrin(a)centos.org> > To: centos(a)centos.org > Subject: Re: [CentOS] NODEJS010-NPM is not getting installed due to > dependency errors on Custom Centos ISO installation > Message-ID: <a607d751-c5e7-91eb-9e81-b6cdb379ecfa(a)centos.org> > Content-Type: text/plain; charset=windows-1252 > > > > On 08/31/2016 03:48 AM, SUDHANSHU BHUTANI wrote: >> Hi, >> >> I have built successfully all the dependent packages of nodejs010 and npm. >> >> I have used following command:- >> *rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec* > > You should really use mock, so that you don't have unintended libraries > from your build host included/linked/required in the resulting rpm. Thanks Jim for responding. I tried with mock configuration, but, not sure, i am still getting the same errors via repoclosre tool:- This directory has got all the RPMs formed by mock. [root@localhost YUM_CISCO_RPMS]# repoclosure -r Cisco-yum-dep-check Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 1 Cisco-yum-dep-check Num Packages in Repos: 1515 package: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(readable-stream) < 0:2 package: nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(graceful-fs) < 0:4 package: nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(strip-ansi) >= 0:2.0.0 package: nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(minimatch) < 0:3 package: nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(has-unicode) < 0:2 package: nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(promzard) >= 0:0.3.0 package: nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(retry) >= 0:0.8.0 nodejs010-npm(request) >= 0:2.47.0 nodejs010-npm(concat-stream) >= 0:1.4.6 package: nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(is-absolute) < 0:0.2 The only difference from my (for build of nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch.rpm) build-log and http://cbs.centos.org/kojifiles/packages/nodejs010-nodejs-are-we-there-yet/… is following line:- *Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) nodejs010-npm(readable-stream)* - >> THIS IS FROM CBS mock log and following is my build log:- *Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0 nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >= 1.1.13 nodejs010-npm(readable-stream) < 2* I am not sure, why parsing of these version is defining a range, maybe its coming from package.json file. I feel, its related to nodejs010-build package which has root/usr/lib/rpm/nodejs010.req, i defined mock configuration like this:- config_opts['root'] = 'epel-7-x86_64' config_opts['target_arch'] = 'x86_64' config_opts['legal_host_arches'] = ('x86_64',) config_opts['chroot_setup_cmd'] = 'install @buildsys-build scl-utils-build nodejs010-build' Do they look good? Following is my build.log [sbhutani@localhost ~]$ cat nodejs-build/nodejs010- Display all 316 possibilities? (y or n) [sbhutani@localhost ~]$ cat nodejs-build/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.src.rpm/build.log Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Falseenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x22e3390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Trueenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x1772390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Falseenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x142d390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 ENTER ['do'](['bash', '--login', '-c', u'/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=Falseuid=1000env={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0private_network=Truelogger=<mockbuild.trace_decorator.getLog object at 0x142d390>printOutput=False) Executing command: ['bash', '--login', '-c', u'/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.cNqdgI + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf package + /usr/bin/gzip -dc /builddir/build/SOURCES/are-we-there-yet-1.0.4.tgz + /usr/bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd package + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + rm -rf node_modules + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.iiP8RP + umask 022 + cd /builddir/build/BUILD + cd package + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.IFmFuX + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 ++ dirname /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + cd package + mkdir -p /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/lib/node_modules/are-we-there-yet + cp -pr package.json index.js /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/lib/node_modules/are-we-there-yet + /usr/lib/rpm/nodejs010-symlink-deps /opt/rh/nodejs010/root/usr/lib/node_modules + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/package /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match. + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/brp-scl-compress /opt/rh/nodejs010/root + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-scl-python-bytecompile /usr/bin/python 1 /opt/rh/nodejs010/root + /usr/lib/rpm/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.7DYIy5 + umask 022 + cd /builddir/build/BUILD + cd package + DOCDIR=/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + cp -pr README.md /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + exit 0 Finding Provides: /usr/lib/rpm/nodejs010.prov Finding Requires(interp): Finding Requires(rpmlib): Finding Requires(verify): Finding Requires(pre): Finding Requires(post): Finding Requires(preun): Finding Requires(postun): Finding Requires(pretrans): Finding Requires(posttrans): Finding Requires: /usr/lib/rpm/nodejs010.req Provides: nodejs010-nodejs-are-we-there-yet = 1.0.4-1.el7.centos nodejs010-npm(are-we-there-yet) = 1.0.4 Requires(rpmlib): rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0 nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >= 1.1.13 nodejs010-npm(readable-stream) < 2 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 Wrote: /builddir/build/RPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.yi6hbn + umask 022 + cd /builddir/build/BUILD + cd package + /usr/bin/rm -rf /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + exit 0 Child return code was: 0 [sbhutani@localhost ~]$ Can any one catch difference between my build.log and CBS build.log. If hhorak is on this mailing list who actually built this package on CBS, can help? Appreciate your inputs. >> >> Following is the list of RPMs cloned and built from GIT:- >> > > <snip> > > >> >> *However, when we copy these RPMS to our ISO, anaconda installer fails >> to install due to dependency errors:-* > > > You should use the 'repoclosure' utility to make sure that you have met > all the dependencies of packages in the repo on your iso. > > > >> How is it possible, to get these errors, how come packages are not >> satisfying minimum dependency for working of NPM? > > > repoclosure should tell you. You may be missing something scl related. > > >> >> If i do yumdownloader for all these above RPMs from repo: [centos-sclo-rh] >> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) then i >> get following RPMs without "centos" name:- > > > Correct. This is an rpm macro change. by default the 'centos' is added > in there. > > >> >> *If i copy paste above RPMS to my custom ISO, then anaconda >> successfully installs these packages, without any errors* > > > This would suggest something is wrong with your build. See previous > statement about using mock vs rpmbuild. > > >> *What is there is these already built RPMs (taken from repo: [centos-sclo-rh] >> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) which >> is not there in my built RPMS?* > > That's kind of up to you to figure out, since we can't see your custom > built ones. > > >> Any pointers for this, as we feel, there is some inconsistency in the >> version available on git.centos.org/git/rpms/<name_of_pkg>.git ? > > More likely it's in your build method. > > > -- > Jim Perrin > The CentOS Project | http://www.centos.org > twitter: @BitIntegrity | GPG Key: FA09AD77 > > > ------------------------------ > > Message: 3 > Date: Wed, 31 Aug 2016 16:58:17 +0200 > From: Alexander Farber <alexander.farber(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAADeyWiMVpHh=CDZ6zi_OEq+5HwysoqTAOABDnM4mkYeFDhxYA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > logwatch is run as cronjob. > > On Wed, Aug 31, 2016 at 4:11 PM, Arun Khan <knura9(a)gmail.com> wrote: > >> On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber >> <alexander.farber(a)gmail.com> wrote: >> > No, I mean there is sometimes a variable for mail format too: >> >> The HTML formatting is a logwatch option, invoked through the >> logwatch.conf file. >> >> -- Arun Khan >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > > ------------------------------ > > Message: 4 > Date: Wed, 31 Aug 2016 08:31:28 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gDhhgRNb1C2rKRdE+v8w_fEhBmCvarf3MxO=njxL7w3-g(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber > <alexander.farber(a)gmail.com> wrote: >> logwatch is run as cronjob. > > Let's take cron out of the picture. Invoking logwatch from an > interactive shell -- no joy. The report still goes out in text > format. > > -- Arun Khan > > > ------------------------------ > > Message: 5 > Date: Wed, 31 Aug 2016 17:59:44 +0200 > From: Alexander Farber <alexander.farber(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAADeyWiYQ_TNjZHZ9af2x3TM_Lq+U9LE+y4aheb6BXV_TBwGaQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > You should have provided more info initially. > > "goes out in text format" might mean several things. > > On Wed, Aug 31, 2016 at 5:31 PM, Arun Khan <knura9(a)gmail.com> wrote: > >> On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber >> <alexander.farber(a)gmail.com> wrote: >> > logwatch is run as cronjob. >> >> Let's take cron out of the picture. Invoking logwatch from an >> interactive shell -- no joy. The report still goes out in text >> format. >> >> -- Arun Khan >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > > ------------------------------ > > Message: 6 > Date: Wed, 31 Aug 2016 09:50:45 -0700 > From: Gordon Messmer <gordon.messmer(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 08/30/2016 03:01 PM, Pat Haley wrote: >> the owner of a directory can still write to that directory but any >> other member of the associated group cannot, even though the directory >> clearly has group write permissions set > > > Use "getfacl" on both the client and server side to view the complete > permission set. What do those look like? > > > > ------------------------------ > > Message: 7 > Date: Wed, 31 Aug 2016 10:00:42 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gBBc+i9VH=eiGM+K7ePerQbv4Nraa5ck7YMEixrhbzaoQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Wed, Aug 31, 2016 at 8:59 AM, Alexander Farber > <alexander.farber(a)gmail.com> wrote: >> You should have provided more info initially. >> >> "goes out in text format" might mean several things. >> > > I don't know what you mean by "several things" > > In the context of logwatch the only options are HTML or TEXT. Please see my OP. > > Thanks for your assistance. > > -- Arun Khan > > > ------------------------------ > > Message: 8 > Date: Wed, 31 Aug 2016 13:11:09 -0400 > From: Pat Haley <phaley(a)mit.edu> > To: centos(a)centos.org > Cc: Steve Postma <SPostma(a)ztechnet.com> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > So far, those look the same > > client: > > [root@mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ > getfacl: Removing leading '/' from absolute path names > # file: gdata/bibliography/Work/GroupBib/trunk/ > # owner: phaley > # group: mseasweb > # flags: -s- > user::rwx > group::rwx > other::r-x > > server: > > [root@mseas-data2 ~]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ > getfacl: Removing leading '/' from absolute path names > # file: gdata/bibliography/Work/GroupBib/trunk/ > # owner: phaley > # group: mseasweb > # flags: -s- > user::rwx > group::rwx > other::r-x > > > On 08/31/2016 12:50 PM, Gordon Messmer wrote: >> On 08/30/2016 03:01 PM, Pat Haley wrote: >>> the owner of a directory can still write to that directory but any >>> other member of the associated group cannot, even though the >>> directory clearly has group write permissions set >> >> >> Use "getfacl" on both the client and server side to view the complete >> permission set. What do those look like? >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > > > ------------------------------ > > Message: 9 > Date: Wed, 31 Aug 2016 14:04:28 -0400 > From: m.roth(a)5-cent.us > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: > <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> > Content-Type: text/plain;charset=utf-8 > > Stupid question, and note I missed most of the earlier posts in this > thread: what are the permissions on the directory that this directory are > in? > > mark > > > > ------------------------------ > > Message: 10 > Date: Wed, 31 Aug 2016 15:06:25 -0400 > From: Pat Haley <phaley(a)mit.edu> > To: centos(a)centos.org > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > For example the directory /gdata/bibliography/Work/GroupBib/trunk/ can > be written in by user phaley but not by other users who are member of > the group mseasweb. The directory has permissions > > [root@mseas ~]# ls -lh /gdata/bibliography/Work/GroupBib > total 12K > drwxrwsr-x 4 phaley mseasweb 4.0K Aug 30 12:31 trunk > > The parent directory (/gdata/bibliography/Work/GroupBib) has permissions > > [root@mseas ~]# ls -lh /gdata/bibliography/Work/ > total 8.0K > drwxrwsr-x 6 phaley mseasweb 4.0K Aug 30 14:01 GroupBib > > > > On 08/31/2016 02:04 PM, m.roth(a)5-cent.us wrote: >> Stupid question, and note I missed most of the earlier posts in this >> thread: what are the permissions on the directory that this directory are >> in? >> >> mark >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > > > ------------------------------ > > Message: 11 > Date: Thu, 01 Sep 2016 03:38:11 +0000 > From: Chris Murphy <lists(a)colorremedies.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: > <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Try booting with enforcing=0 and if that fixes it, you need to find out > what security label is needed for gluster. > > Chances are it's easiest to use -o context= mount option on the brick, but > if the brick is not exclusive to gluster you'll need chcon -R. > > If that's not it, maybe try the gluster client instead of using NFS. See if > you get a different result that narrows down what's going on. > > My vague recollection is for Samba, without the correct SELinux label, I > could neither read nor write. > > > Chris Murphy > > > ------------------------------ > > Message: 12 > Date: Thu, 1 Sep 2016 11:03:30 +0530 > From: Sidharth Sharma <sharma.sidharth86(a)gmail.com> > To: centos(a)centos.org > Subject: [CentOS] Perl Unsafe Module Path Handling Directory Traversal > Vulnerability ( CVE-2016-1238) > Message-ID: > <CAAQ4EFk7qgWvq=ZtSOugxsgQ1S54y8cFbiG33POQme8+cDrcSw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Experts, > > When we can expect Security Update for Perl Vulnerability CVE-2016-1238 on > CentOS 6.8 and 7.2? > > -- > With Thanks & Regards: > Sidharth Sharma > > > ------------------------------ > > Message: 13 > Date: Thu, 1 Sep 2016 11:05:36 +0530 > From: Sidharth Sharma <sharma.sidharth86(a)gmail.com> > To: centos(a)centos.org > Subject: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: > <CAAQ4EF=2AeThtVjJitR3JHGhuunRJ4AZHiYDcrp4vcKFxUV=UQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Experts, > > When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? > ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: > CVE-2016-2775 > > -- > With Thanks & Regards: > Sidharth Sharma > > > ------------------------------ > > Message: 14 > Date: Thu, 1 Sep 2016 10:26:34 +0200 > From: Toralf Lund <toralf.lund(a)pgs.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] "Windows" share issue; access via smb:// fails, > "mount -t cifs" works > Message-ID: <2265d62b-32b6-6d51-5848-df84f5800723(a)pgs.com> > Content-Type: text/plain; charset="utf-8"; format=flowed > > On 30/08/16 10:00, Toralf Lund wrote: >> Hi, >> >> Is anyone here using smb:// URLs to access "Windows" shares? I've been >> doing this for a while with common file systems at work, and it used >> to work just fine. Then I while back, I started getting issues; I will >> now just keep getting asked for a password when I try to access >> something through smb://. I thought at first that this meant there had >> been some kind of change related to permissions on the shares, but now >> I find that I can mount them just fine using "mount -t cifs". > I found out a bit more about this - I believe that I have the issue > described here: > > http://community.netapp.com/t5/Network-Storage-Protocols-Discussions/samba-… > > In other words, the problem is that "SPNEGO" fails. If I add "client use > spnego = no" to /etc/samba/smb.conf, smbclient access works (I found > that I also got a problem there), but unfortunately, gvfs-mount still > doesn't. The debug output that I get if I run gvfsd on the command line > with "GVFS_DEBUG=1" and "GVFS_SMB_DEBUG=99" actually still report SPNEGO > errors, so it would appear that the smp.conf option is for some reason > ignored. In other words the question may be: > > How do I disabled SPNEGO for gvfs-mount? > > Also, the above suggest that whether this problem occurs depends on > whether "you have SMB signing turned on or not under the 'cifs' options > section", but it not clear to me what options exactly this refers to. > Anyone? > > Oh, and some other posts I found seem to indicate that mount.cifs > doesn't support SPNEGO yet, so I guess that's why a "normal" mount works. > > - Toralf > > >> >> In other words, I get: >> >> gvfs-mount smb://mydomain\;toralf.lund@theserver/myshare >> Password required for share myshare on theserver >> Password: >> Password required for share myshare on theserver >> Password: >> Password required for share myshare on theserver >> Password: >> >> [ I enter the correct password, but gvs-mount keeps asking... >> Behaviour is the same if I try to open the URL in the file manager >> instead. ] >> >> mount -t cifs -o user=toralf.lund,workgroup=mydomain >> //theserver/myshare /tmp_mnt/ >> Password: >> >> [ At this stage the filesystem is mounted, as long as I enter the >> correct password. ] >> >> Does anyone have any idea what is going on here? Why does the VFS >> mount fail when mount.cifs works on the same share? Is there a >> difference in the way authentication works, or something? Has there >> been a change to the smb support that might explain this? >> >> This is on a CentOS 6 x86_64 installation with all updates applied. >> >> - Toralf >> > > > > ------------------------------ > > Message: 15 > Date: Thu, 1 Sep 2016 08:34:08 +0000 > From: James Pearson <james-p(a)moving-picture.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: > <85C0B54E4752CA4F873E7C78CF0B26F5010FB3748D(a)LNDWSMBX01.ad.mpc.local> > Content-Type: text/plain; charset="us-ascii" > > Sidharth Sharma: >> >> When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? >> ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: > >CVE-2016-2775 > > See: > > https://access.redhat.com/security/cve/cve-2016-2775 > > James Pearson > > ------------------------------ > > Message: 16 > Date: Thu, 01 Sep 2016 07:45:04 -0400 > From: Mike Burger <mburger(a)bubbanfriends.org> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: <400e82588e4172b96a928e1e3aeef9e3(a)bubbanfriends.org> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On 2016-09-01 4:34 am, James Pearson wrote: >> Sidharth Sharma: >>> >>> When we can expect Security Update for Bind Vulnerability on Centos >>> 6.8/7.2? >>> ISC BIND Lightweight Resolver Protocol Req Processing Dos >>> Vulnerability: >> >CVE-2016-2775 >> >> See: >> >> https://access.redhat.com/security/cve/cve-2016-2775 > > Ouch! > > Affected Packages State > Platform Package State > Red Hat Enterprise Linux 5 bind97 Will not fix > Red Hat Enterprise Linux 6 bind Will not fix > Red Hat Enterprise Linux 5 bind Will not fix > Red Hat Enterprise Linux 7 bind Will not fix > > -- > 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 > > > ------------------------------ > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > > > End of CentOS Digest, Vol 140, Issue 1 > **************************************

1 0

Re: [CentOS] group write permissions not being respected
by Chris Murphy 02 Sep '16

02 Sep '16

On Thu, Sep 1, 2016, 8:11 AM Pat Haley <phaley(a)mit.edu> wrote: > > For the enforcing=0, is that referring to SELinux? If so, we are not > running SELinux. > OK so neither that nor chcon nor context mount option apply. It's something else. > > On 08/31/2016 11:38 PM, Chris Murphy wrote: > > ---------------------------------------------------------------------------------------- > > Try booting with enforcing=0 and if that fixes it, you need to find out > > what security label is needed for gluster. > > ---------------------------------------------------------------------------------------- > For the enforcing=0, is that referring to SELinux? If so, we are not > running SELinux. > > ----------------------------------------------------------------------------------------- > > > Chances are it's easiest to use -o context= mount option on the brick, > but > > if the brick is not exclusive to gluster you'll need chcon -R. > > ----------------------------------------------------------------------------------------- > We aren't sure exactly what you mean by this second paragraph, can > you expand on this? Are these two exclusive options exclusive? We aren't > sure what you what you mean by "exclusive to gluster" > > ----------------------------------------------------------------------------------------- > > If that's not it, maybe try the gluster client instead of using NFS. See > if > > you get a different result that narrows down what's going on. > > > > My vague recollection is for Samba, without the correct SELinux label, I > > could neither read nor write. > > > > > > Chris Murphy > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos >

1 0

Centos v6.8 and double received bytes
by Steve Malenfant 02 Sep '16

02 Sep '16

I'm observing double the amount of "recv" bytes in latest Centos v6.8 with ixgbe 4.2.1-k. Anybody seeing the same? $ ethtool -i em1 driver: ixgbe version: 4.2.1-k $ uname -an Linux chndcdmid01.rd.ph.cox.net 2.6.32-642.4.2.el6.x86_64 #1 SMP Tue Aug 23 19:58:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Doing comparison on 2 days at same hour just to show the difference. This is an HTTP cache server, having higher RX than TX means something is bad... We don't rely much on the RECV side, but our graph showed a huge difference between upgrades. Before upgrade (v6.7, 4.0.1-k) : 07:00:01 PM IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s txcmp/s rxmcst/s 07:00:01 PM em1 3971.90 5384.15 14981.65 26376.80 0.00 0.00 0.00 07:10:01 PM em1 3918.26 5367.79 13136.21 25528.40 0.00 0.00 0.00 07:20:01 PM em1 3868.94 5273.08 11997.37 25155.92 0.00 0.00 0.00 07:30:01 PM em1 3895.50 5597.56 10851.74 28583.84 0.00 0.00 0.00 07:40:01 PM em1 3956.80 5706.12 12230.66 29553.73 0.00 0.00 0.00 07:50:01 PM em1 4016.39 5801.69 11957.35 29979.04 0.00 0.00 0.00 After upgrade (v6.8, 4.2.1-k) : 07:00:01 PM IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s txcmp/s rxmcst/s 07:00:01 PM em1 20857.40 8736.13 59710.07 35102.76 0.00 0.00 0.00 07:10:01 PM em1 19508.00 8429.40 58120.70 36036.64 0.00 0.00 0.00 07:20:01 PM em1 19128.20 8471.45 55502.07 37312.56 0.00 0.00 0.00 07:30:01 PM em1 19402.55 8329.93 53586.60 35386.52 0.00 0.00 0.00 07:40:01 PM em1 19188.27 8105.83 51463.72 33585.55 0.00 0.00 0.00 07:50:01 PM em1 19544.32 7843.08 49590.64 30981.99 0.00 0.00 0.00 Steve

1 0

Perl Unsafe Module Path Handling Directory Traversal Vulnerability ( CVE-2016-1238)
by Sidharth Sharma 01 Sep '16

01 Sep '16

Hello Experts, When we can expect Security Update for Perl Vulnerability CVE-2016-1238 on CentOS 6.8 and 7.2? -- With Thanks & Regards: Sidharth Sharma

3 2

None
by None 01 Sep '16

01 Sep '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u81EAcLM001706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Thu, 1 Sep 2016 10:10:39 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <c29b1a4f-a3d5-b61e-7206-b6e32a89f72c(a)mit.edu> Date: Thu, 1 Sep 2016 10:10:37 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBIsWRmVeSWpSXmKPExsUixG6novvA7ES4wbKPehbLzixgdmD0WNk2 mTmAMYrLJiU1J7MstUjfLoEro2v1ZZaCOfwVK46dZmxgPMPTxcjJISFgInF78VLGLkYuDiGB NiaJ20cnsEM4Jxglzs1sYoNwDjBJrJ+7ig2kRVjAUeLFy+1gtoiAqETP4ldQRXeYJI60zQJL sAkoSKy7dYYdxOYVsJL4d3IFI4jNIqAi8aJxLiuILSoQIXFr1UdGiBpBiZMzn7CA2JwCgRLr Lh1iArGZBWwl7szdzQxhy0tsfzuHeQIj/ywkLbOQlM1CUraAkXkVo2xKbpVubmJmTnFqsm5x cmJeXmqRrrFebmaJXmpK6SZGUABySvLtYJzU4H2IUYCDUYmHl8PoRLgQa2JZcWXuIUZJDiYl UV61uOPhQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4D5sAlfOmJFZWpRblw6SkOViUxHm7ZhwI FxJITyxJzU5NLUgtgsnKcHAoSfA+NwVqFCxKTU+tSMvMKUFIM3FwggznARruCVLDW1yQmFuc mQ6RP8WoKCXOuw9kqwBIIqM0D64XnCDU2A+9YhQHekWY9xNIOw8wucB1vwIazAQ0uOTacZDB JYkIKakGxoOFsj1Rp4xfa7cUW2gsW9+qayH73/TzFO/+g6u3Wb6v+HPW0z8uKeiJLaPmsu11 l026ZTQmeqT62Nhkb1h4eObdzGncssKrr2y7/M3yebNoiKDarJbj2px6ziePT344Q5vRWchE c7qp9Kldn943ef0s3M7aGtRsOuFFWdDBrh/ap1R3TYrmUWIpzkg01GIuKk4EAG7WrU3rAgAA Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Thu, 01 Sep 2016 14:10:40 -0000 For the enforcing=0, is that referring to SELinux? If so, we are not running SELinux. On 08/31/2016 11:38 PM, Chris Murphy wrote: ---------------------------------------------------------------------------------------- > Try booting with enforcing=0 and if that fixes it, you need to find out > what security label is needed for gluster. ---------------------------------------------------------------------------------------- For the enforcing=0, is that referring to SELinux? If so, we are not running SELinux. ----------------------------------------------------------------------------------------- > Chances are it's easiest to use -o context= mount option on the brick, but > if the brick is not exclusive to gluster you'll need chcon -R. ----------------------------------------------------------------------------------------- We aren't sure exactly what you mean by this second paragraph, can you expand on this? Are these two exclusive options exclusive? We aren't sure what you what you mean by "exclusive to gluster" ----------------------------------------------------------------------------------------- > If that's not it, maybe try the gluster client instead of using NFS. See if > you get a different result that narrows down what's going on. > > My vague recollection is for Samba, without the correct SELinux label, I > could neither read nor write. > > > Chris Murphy > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Bind Vulnerability CVE-2016-2775
by Sidharth Sharma 01 Sep '16

01 Sep '16

Hello Experts, When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: CVE-2016-2775 -- With Thanks & Regards: Sidharth Sharma

4 3

"Windows" share issue; access via smb:// fails, "mount -t cifs" works
by Toralf Lund 01 Sep '16

01 Sep '16

Hi, Is anyone here using smb:// URLs to access "Windows" shares? I've been doing this for a while with common file systems at work, and it used to work just fine. Then I while back, I started getting issues; I will now just keep getting asked for a password when I try to access something through smb://. I thought at first that this meant there had been some kind of change related to permissions on the shares, but now I find that I can mount them just fine using "mount -t cifs". In other words, I get: gvfs-mount smb://mydomain\;toralf.lund@theserver/myshare Password required for share myshare on theserver Password: Password required for share myshare on theserver Password: Password required for share myshare on theserver Password: [ I enter the correct password, but gvs-mount keeps asking... Behaviour is the same if I try to open the URL in the file manager instead. ] mount -t cifs -o user=toralf.lund,workgroup=mydomain //theserver/myshare /tmp_mnt/ Password: [ At this stage the filesystem is mounted, as long as I enter the correct password. ] Does anyone have any idea what is going on here? Why does the VFS mount fail when mount.cifs works on the same share? Is there a difference in the way authentication works, or something? Has there been a change to the smb support that might explain this? This is on a CentOS 6 x86_64 installation with all updates applied. - Toralf

1 1

Re: [CentOS] group write permissions not being respected
by Chris Murphy 01 Sep '16

01 Sep '16

Try booting with enforcing=0 and if that fixes it, you need to find out what security label is needed for gluster. Chances are it's easiest to use -o context= mount option on the brick, but if the brick is not exclusive to gluster you'll need chcon -R. If that's not it, maybe try the gluster client instead of using NFS. See if you get a different result that narrows down what's going on. My vague recollection is for Samba, without the correct SELinux label, I could neither read nor write. Chris Murphy

1 0

None
by None 31 Aug '16

31 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7VJ6PIp019192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Wed, 31 Aug 2016 15:06:26 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> Date: Wed, 31 Aug 2016 15:06:25 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBIsWRmVeSWpSXmKPExsUixCmqrLtJ63i4wb2P5hbLzixgdmD0WNk2 mTmAMYrLJiU1J7MstUjfLoEr4/byu8wFPzgrrs+7zNjA+Im9i5GTQ0LARGLh8c1sXYxcHEIC bUwSi39fYIZwTjJKLLyznRXCOcgkcWvPV7AWYQFHiRcvt7OB2CICohI9i19BtT9hlPj2ayoT SIJNQEFi3a0zYA28AlYSzVcOgDWwCKhKLFndxQJiiwpESNxa9ZERokZQ4uTMJ2BxToEAiTVH L7GC2MwCthJ35u5mhrDlJba/ncM8gZF/FpKWWUjKZiEpW8DIvIpRNiW3Sjc3MTOnODVZtzg5 MS8vtUjXTC83s0QvNaV0EyMoANldlHcwvuzzPsQowMGoxMPr8OZYuBBrYllxZe4hRkkOJiVR 3pZXQCG+pPyUyozE4oz4otKc1OJDjBIczEoivMc0j4cL8aYkVlalFuXDpKQ5WJTEebtmHAgX EkhPLEnNTk0tSC2CycpwcChJ8M4CaRQsSk1PrUjLzClBSDNxcIIM5wEafkQDZHhxQWJucWY6 RP4Uo6KUOO8CkIQASCKjNA+uF5wg1NgPvWIUB3pFmJcNmC6EeIDJBa77FdBgJqDBBXcOgwwu SURISTUwekkEz/r5Ts9xgmniZrvezD3CvKIqb+P5P7Azrpy5cn5G7td1kfqrlaa+VBA73XvY ZouP+Ivat6VOp7UWyp70ygmaZWdk1XxgxvSrG8NWq98uvbZ9SdDf16tCGhUapSbLbogpWLg4 4YjHrLdMmouWrTp5Z9rsdxN3z2/M+KtT5s2zT+ad3u3EViWW4oxEQy3mouJEAMZPH+/rAgAA Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Wed, 31 Aug 2016 19:06:26 -0000 For example the directory /gdata/bibliography/Work/GroupBib/trunk/ can be written in by user phaley but not by other users who are member of the group mseasweb. The directory has permissions [root@mseas ~]# ls -lh /gdata/bibliography/Work/GroupBib total 12K drwxrwsr-x 4 phaley mseasweb 4.0K Aug 30 12:31 trunk The parent directory (/gdata/bibliography/Work/GroupBib) has permissions [root@mseas ~]# ls -lh /gdata/bibliography/Work/ total 8.0K drwxrwsr-x 6 phaley mseasweb 4.0K Aug 30 14:01 GroupBib On 08/31/2016 02:04 PM, m.roth(a)5-cent.us wrote: > Stupid question, and note I missed most of the earlier posts in this > thread: what are the permissions on the directory that this directory are > in? > > mark > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Re: [CentOS] group write permissions not being respected
by m.roth＠5-cent.us 31 Aug '16

31 Aug '16

Stupid question, and note I missed most of the earlier posts in this thread: what are the permissions on the directory that this directory are in? mark

1 0

None
by None 31 Aug '16

31 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7VHB9vm012262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 31 Aug 2016 13:11:10 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> Date: Wed, 31 Aug 2016 13:11:09 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsUixG6nrrue/3i4wZSrFhbLzixgtpjy+x2T A5PHyrbJzB4XG5ewBjBFcdmkpOZklqUW6dslcGV8u2xY8Iq7oqd/OmMD4z7OLkYODgkBE4np a6K6GLk4hATamCSOdD1kgXA2Mkq8OLSFDcJZySQx5fg2xi5GTg5hAUeJFy+3s4HYIgKiEj2L X4HZQgK5EjNPHGQDmcosoC7RvpQVJMwmoCCx7tYZdhCbV8BKYvmPZ2A2i4CqxMTPH5lAbFGB CIlbqz4yQtQISpyc+YQFxOYUsJVYc/8QWA0zkH1n7m5mCFteYvvbOcwTGAVmIWmZhaRsFpKy BYzMqxhlU3KrdHMTM3OKU5N1i5MT8/JSi3SN9HIzS/RSU0o3MYKClFOSdwfjv7tehxgFOBiV eHgd3hwLF2JNLCuuzD3EKMnBpCTK2/IKKMSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmEN4fneLgQ b0piZVVqUT5MSpqDRUmct2vGgXAhgfTEktTs1NSC1CKYrAwHh5IEbwYfUKNgUWp6akVaZk4J QpqJgxNkOA/Q8A8gNbzFBYm5xZnpEPlTjIpS4rx3eYESAiCJjNI8uF5wElFjP/SKURzoFWFe E5B2HmACgut+BTSYCWhwwZ3DIINLEhFSUg2MW8WcvRwnrJQpPGj6JO7Mjrup8+QnHfE2yHkh feS98eZoudO7Ti/PjZrzfUGd1fkVN6onGvKEzHjbKJ9wrrthyjrn+H/bG/OzzjAuDWaoKZjC x/Tlc9TrqfXiNZmXf+3s6Mk2LGQ3VEoRKrhyoCz4jM/zKU9+ZzlNP1jnIqd469Nuiw4NMdk9 SizFGYmGWsxFxYkAxP5Cf/0CAAA= Cc: Steve Postma <SPostma(a)ztechnet.com> Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Wed, 31 Aug 2016 17:11:11 -0000 So far, those look the same client: [root@mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ getfacl: Removing leading '/' from absolute path names # file: gdata/bibliography/Work/GroupBib/trunk/ # owner: phaley # group: mseasweb # flags: -s- user::rwx group::rwx other::r-x server: [root@mseas-data2 ~]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ getfacl: Removing leading '/' from absolute path names # file: gdata/bibliography/Work/GroupBib/trunk/ # owner: phaley # group: mseasweb # flags: -s- user::rwx group::rwx other::r-x On 08/31/2016 12:50 PM, Gordon Messmer wrote: > On 08/30/2016 03:01 PM, Pat Haley wrote: >> the owner of a directory can still write to that directory but any >> other member of the associated group cannot, even though the >> directory clearly has group write permissions set > > > Use "getfacl" on both the client and server side to view the complete > permission set. What do those look like? > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

CentOS 6 - logwatch report not in HTML format
by Arun Khan 31 Aug '16

31 Aug '16

CentOS 6 (amd64) up to date with latest security / bug fixes. The logwatch reports come in plain text even though the config states HTML. <begin /etc/logwatch/conf/logwatch.conf> mailer = "/usr/sbin/sendmail -t" TmpDir = /tmp MailFrom = logwatch(a)example.com MailTo = admin1 admin2 admin3 Range = yesterday Detail = Medium HostName = www.example.com Print = No Output = mail Format = html <end /etc/logwatch/conf/logwatch.conf> The same settings in Debian/Ubuntu servers send the reports in HTML format. In my search, I did not come across any solution for CentOS 6. Any ideas on how to get logwatch to generate HTML reports? Thanks for your help. -- Arun Khan

2 8

Re: [CentOS] group write permissions not being respected
by Gordon Messmer 31 Aug '16

31 Aug '16

On 08/30/2016 03:01 PM, Pat Haley wrote: > the owner of a directory can still write to that directory but any > other member of the associated group cannot, even though the directory > clearly has group write permissions set Use "getfacl" on both the client and server side to view the complete permission set. What do those look like?

1 0

NODEJS010-NPM is not getting installed due to dependency errors on Custom Centos ISO installation
by SUDHANSHU BHUTANI 31 Aug '16

31 Aug '16

Hi, I have built successfully all the dependent packages of nodejs010 and npm. I have used following command:- *rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec* Following is the list of RPMs cloned and built from GIT:- nodejs010-2.1-5.el7.centos.x86_64.rpm nodejs010-http-parser-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm nodejs010-http-parser-devel-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm nodejs010-libuv-0.10.30-1.el7.centos.x86_64.rpm nodejs010-libuv-devel-0.10.30-1.el7.centos.x86_64.rpm nodejs010-node-gyp-3.2.0-2.el7.centos.noarch.rpm nodejs010-nodejs-0.10.40-1.el7.centos.x86_64.rpm nodejs010-nodejs-abbrev-1.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-ansi-0.3.0-1.el7.centos.noarch.rpm nodejs010-nodejs-ansicolors-0.3.2-1.el7.centos.noarch.rpm nodejs010-nodejs-ansistyles-0.1.3-1.el7.centos.x86_64.rpm nodejs010-nodejs-archy-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch.rpm nodejs010-nodejs-array-index-0.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-asap-1.0.0-4.el7.centos.noarch.rpm nodejs010-nodejs-async-some-1.0.2-2.el7.centos.noarch.rpm nodejs010-nodejs-balanced-match-0.2.1-2.el7.centos.noarch.rpm nodejs010-nodejs-bl-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-block-stream-0.0.7-2.el7.centos.noarch.rpm nodejs010-nodejs-brace-expansion-1.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-builtin-modules-1.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-builtins-1.0.2-2.el7.centos.noarch.rpm nodejs010-nodejs-caseless-0.11.0-1.el7.centos.noarch.rpm nodejs010-nodejs-char-spinner-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-chmodr-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-chownr-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-clone-0.2.0-3.el7.centos.noarch.rpm nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch.rpm nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch.rpm nodejs010-nodejs-concat-map-0.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-concat-stream-1.4.4-5.el7.centos.noarch.rpm nodejs010-nodejs-config-chain-1.1.9-1.el7.centos.noarch.rpm nodejs010-nodejs-core-util-is-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-debug-2.2.0-2.el7.centos.noarch.rpm nodejs010-nodejs-debuglog-1.0.1-4.el7.centos.noarch.rpm nodejs010-nodejs-defaults-1.0.0-5.el7.centos.noarch.rpm nodejs010-nodejs-delegates-0.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-devel-0.10.40-1.el7.centos.x86_64.rpm nodejs010-nodejs-dezalgo-1.0.2-3.el7.centos.noarch.rpm nodejs010-nodejs-editor-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-forever-agent-0.5.0-2.el7.centos.noarch.rpm nodejs010-nodejs-fstream-1.0.3-2.el7.centos.noarch.rpm nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-fstream-npm-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-fs-vacuum-1.2.6-3.el7.centos.noarch.rpm nodejs010-nodejs-fs-write-stream-atomic-1.0.3-3.el7.centos.noarch.rpm nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch.rpm nodejs010-nodejs-github-url-from-git-1.4.0-1.el7.centos.noarch.rpm nodejs010-nodejs-github-url-from-username-repo-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-glob-5.0.15-1.el7.centos.noarch.rpm nodejs010-nodejs-graceful-fs-4.1.2-3.el7.centos.noarch.rpm nodejs010-nodejs-has-unicode-2.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-hosted-git-info-2.1.4-3.el7.centos.noarch.rpm nodejs010-nodejs-inflight-1.0.4-2.el7.centos.noarch.rpm nodejs010-nodejs-inherits-2.0.0-13.el7.centos.noarch.rpm nodejs010-nodejs-ini-1.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch.rpm nodejs010-nodejs-is-absolute-0.2.3-3.el7.centos.noarch.rpm nodejs010-nodejs-isarray-0.0.1-3.el7.centos.noarch.rpm nodejs010-nodejs-is-builtin-module-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-is-relative-0.2.1-2.el7.centos.noarch.rpm nodejs010-nodejs-is-unc-path-0.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-is-windows-0.1.0-3.el7.centos.noarch.rpm nodejs010-nodejs-jju-1.2.1-1.el7.centos.noarch.rpm nodejs010-nodejs-json-parse-helpfulerror-1.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-json-stringify-safe-5.0.0-2.el7.centos.noarch.rpm nodejs010-nodejs-lockfile-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash._basetostring-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash._createpadding-3.6.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.pad-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.padleft-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.padright-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.repeat-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lru-cache-2.7.0-1.el7.centos.noarch.rpm nodejs010-nodejs-mime-db-1.15.0-3.el7.centos.noarch.rpm nodejs010-nodejs-mime-types-2.1.3-1.el7.centos.noarch.rpm nodejs010-nodejs-minimatch-3.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-minimist-0.0.8-1.el7.centos.noarch.rpm nodejs010-nodejs-mkdirp-0.5.0-1.el7.centos.noarch.rpm nodejs010-nodejs-ms-0.7.1-2.el7.centos.noarch.rpm nodejs010-nodejs-mute-stream-0.0.4-3.el7.centos.noarch.rpm nodejs010-nodejs-node-uuid-1.4.1-2.el7.centos.noarch.rpm nodejs010-nodejs-nopt-3.0.6-1.el7.centos.noarch.rpm nodejs010-nodejs-normalize-git-url-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-normalize-package-data-2.3.5-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-cache-filename-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-install-checks-1.0.6-1.el7.centos.noarch.rpm nodejs010-nodejs-npmlog-2.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-package-arg-4.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-user-validate-0.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-once-1.3.0-1.el7.centos.noarch.rpm nodejs010-nodejs-opener-1.4.1-1.el7.centos.noarch.rpm nodejs010-nodejs-osenv-0.1.3-1.el7.centos.noarch.rpm nodejs010-nodejs-os-homedir-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-os-tmpdir-1.0.1-3.el7.centos.noarch.rpm nodejs010-nodejs-path-array-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-path-is-absolute-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-path-is-inside-1.0.0-1.el7.centos.x86_64.rpm nodejs010-nodejs-process-nextick-args-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-promzard-0.2.0-7.el7.centos.noarch.rpm nodejs010-nodejs-proto-list-1.2.2-5.el7.centos.noarch.rpm nodejs010-nodejs-qs-0.6.5-5.el7.centos.noarch.rpm nodejs010-nodejs-read-1.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-readable-stream-2.0.2-3.el7.centos.noarch.rpm nodejs010-nodejs-readdir-scoped-modules-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-read-installed-4.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-read-package-json-2.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-realize-package-specifier-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-request-2.42.0-6.el7.centos.noarch.rpm nodejs010-nodejs-retry-0.6.0-6.el7.centos.noarch.rpm nodejs010-nodejs-rimraf-2.4.3-1.el7.centos.noarch.rpm nodejs010-nodejs-semver-5.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-sha-2.0.1-2.1.el7.centos.noarch.rpm nodejs010-nodejs-slide-1.1.6-1.el7.centos.noarch.rpm nodejs010-nodejs-sorted-object-1.0.0-3.el7.centos.noarch.rpm nodejs010-nodejs-spdx-correct-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-exceptions-1.0.4-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-expression-parse-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-license-ids-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-string_decoder-0.10.31-1.el7.centos.noarch.rpm nodejs010-nodejs-strip-ansi-0.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-tar-2.2.1-1.el7.centos.noarch.rpm nodejs010-nodejs-text-table-0.2.0-1.el7.centos.x86_64.rpm nodejs010-nodejs-tunnel-agent-0.3.0-2.el7.centos.noarch.rpm nodejs010-nodejs-uid-number-0.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-umask-1.1.0-4.el7.centos.noarch.rpm nodejs010-nodejs-unc-path-regex-0.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-util-deprecate-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-util-extend-1.0.1-4.el7.centos.noarch.rpm nodejs010-nodejs-validate-npm-package-license-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-validate-npm-package-name-2.2.2-3.el7.centos.noarch.rpm nodejs010-nodejs-wcwidth-1.0.0-4.el7.centos.noarch.rpm nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-wrappy-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-write-file-atomic-1.1.2-3.el7.centos.noarch.rpm nodejs010-npm-2.14.13-7.el7.centos.noarch.rpm nodejs010-runtime-2.1-5.el7.centos.x86_64.rpm nodejs010-scldevel-2.1-5.el7.centos.x86_64.rpm *However, when we copy these RPMS to our ISO, anaconda installer fails to install due to dependency errors:-* nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch requires nodejs010-npm(readable-stream) < 2 nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch requires nodejs010-npm(graceful-fs) < 4 nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch requires nodejs010-npm(strip-ansi) >= 2.0.0 nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch requires nodejs010-npm(minimatch) < 3 nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch requires nodejs010-npm(has-unicode) < 2 nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch requires nodejs010-npm(promzard) >= 0.3.0 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(concat-stream) >= 1.4.6 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(request) >= 2.47.0 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(retry) >= 0.8.0 nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch requires nodejs010-npm(is-absolute) < 0.2 How is it possible, to get these errors, how come packages are not satisfying minimum dependency for working of NPM? If i do yumdownloader for all these above RPMs from repo: [centos-sclo-rh] : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) then i get following RPMs without "centos" name:- nodejs010-2.1-5.el7.x86_64.rpm nodejs010-http-parser-2.0-6.20121128gitcd01361.el7.x86_64.rpm nodejs010-http-parser-devel-2.0-6.20121128gitcd01361.el7.x86_64.rpm nodejs010-libuv-0.10.30-1.el7.x86_64.rpm nodejs010-libuv-devel-0.10.30-1.el7.x86_64.rpm nodejs010-node-gyp-3.2.0-2.el7.noarch.rpm nodejs010-nodejs-0.10.40-1.el7.x86_64.rpm nodejs010-nodejs-abbrev-1.0.5-1.el7.noarch.rpm nodejs010-nodejs-ansi-0.3.0-2.el7.noarch.rpm nodejs010-nodejs-ansicolors-0.3.2-1.el7.noarch.rpm nodejs010-nodejs-ansistyles-0.1.3-1.el7.x86_64.rpm nodejs010-nodejs-archy-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.noarch.rpm nodejs010-nodejs-array-index-0.1.1-1.el7.noarch.rpm nodejs010-nodejs-asap-1.0.0-4.el7.noarch.rpm nodejs010-nodejs-async-some-1.0.2-2.el7.noarch.rpm nodejs010-nodejs-balanced-match-0.2.1-2.el7.noarch.rpm nodejs010-nodejs-bl-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-block-stream-0.0.7-2.el7.noarch.rpm nodejs010-nodejs-brace-expansion-1.1.1-2.el7.noarch.rpm nodejs010-nodejs-builtin-modules-1.1.0-1.el7.noarch.rpm nodejs010-nodejs-builtins-1.0.2-2.el7.noarch.rpm nodejs010-nodejs-caseless-0.11.0-1.el7.noarch.rpm nodejs010-nodejs-char-spinner-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-chmodr-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-chownr-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-clone-0.2.0-3.el7.noarch.rpm nodejs010-nodejs-cmd-shim-2.0.0-2.el7.noarch.rpm nodejs010-nodejs-columnify-1.3.2-3.el7.noarch.rpm nodejs010-nodejs-concat-map-0.0.1-1.el7.noarch.rpm nodejs010-nodejs-concat-stream-1.4.4-5.el7.noarch.rpm nodejs010-nodejs-config-chain-1.1.9-1.el7.noarch.rpm nodejs010-nodejs-core-util-is-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-debug-2.2.0-2.el7.noarch.rpm nodejs010-nodejs-debuglog-1.0.1-4.el7.noarch.rpm nodejs010-nodejs-defaults-1.0.0-5.el7.noarch.rpm nodejs010-nodejs-delegates-0.1.0-1.el7.noarch.rpm nodejs010-nodejs-devel-0.10.40-1.el7.x86_64.rpm nodejs010-nodejs-dezalgo-1.0.2-3.el7.noarch.rpm nodejs010-nodejs-editor-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-forever-agent-0.5.0-2.el7.noarch.rpm nodejs010-nodejs-fstream-1.0.3-2.el7.noarch.rpm nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-fstream-npm-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-fs-vacuum-1.2.6-3.el7.noarch.rpm nodejs010-nodejs-fs-write-stream-atomic-1.0.3-3.el7.noarch.rpm nodejs010-nodejs-gauge-1.2.2-3.el7.noarch.rpm nodejs010-nodejs-github-url-from-git-1.4.0-1.el7.noarch.rpm nodejs010-nodejs-github-url-from-username-repo-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-glob-5.0.15-1.el7.noarch.rpm nodejs010-nodejs-graceful-fs-4.1.2-3.el7.noarch.rpm nodejs010-nodejs-has-unicode-2.0.0-1.el7.noarch.rpm nodejs010-nodejs-hosted-git-info-2.1.4-3.el7.noarch.rpm nodejs010-nodejs-inflight-1.0.4-2.el7.noarch.rpm nodejs010-nodejs-inherits-2.0.0-13.el7.noarch.rpm nodejs010-nodejs-ini-1.2.0-1.el7.noarch.rpm nodejs010-nodejs-init-package-json-1.9.1-1.el7.noarch.rpm nodejs010-nodejs-is-absolute-0.2.3-3.el7.noarch.rpm nodejs010-nodejs-isarray-0.0.1-3.el7.noarch.rpm nodejs010-nodejs-is-builtin-module-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-is-relative-0.2.1-2.el7.noarch.rpm nodejs010-nodejs-is-unc-path-0.1.1-2.el7.noarch.rpm nodejs010-nodejs-is-windows-0.1.0-3.el7.noarch.rpm nodejs010-nodejs-jju-1.2.1-1.el7.noarch.rpm nodejs010-nodejs-json-parse-helpfulerror-1.0.3-1.el7.noarch.rpm nodejs010-nodejs-json-stringify-safe-5.0.0-2.el7.noarch.rpm nodejs010-nodejs-lockfile-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-lodash._basetostring-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-lodash._createpadding-3.6.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.pad-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.padleft-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.padright-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.repeat-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-lru-cache-2.7.0-1.el7.noarch.rpm nodejs010-nodejs-mime-db-1.15.0-3.el7.noarch.rpm nodejs010-nodejs-mime-types-2.1.3-1.el7.noarch.rpm nodejs010-nodejs-minimatch-3.0.0-1.el7.noarch.rpm nodejs010-nodejs-minimist-0.0.8-1.el7.noarch.rpm nodejs010-nodejs-mkdirp-0.5.0-1.el7.noarch.rpm nodejs010-nodejs-ms-0.7.1-2.el7.noarch.rpm nodejs010-nodejs-mute-stream-0.0.4-3.el7.noarch.rpm nodejs010-nodejs-node-uuid-1.4.1-2.el7.noarch.rpm nodejs010-nodejs-nopt-3.0.6-1.el7.noarch.rpm nodejs010-nodejs-normalize-git-url-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-normalize-package-data-2.3.5-1.el7.noarch.rpm nodejs010-nodejs-npm-cache-filename-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-npm-install-checks-1.0.6-1.el7.noarch.rpm nodejs010-nodejs-npmlog-2.0.0-1.el7.noarch.rpm nodejs010-nodejs-npm-package-arg-4.1.0-1.el7.noarch.rpm nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.noarch.rpm nodejs010-nodejs-npm-user-validate-0.1.1-1.el7.noarch.rpm nodejs010-nodejs-once-1.3.0-1.el7.noarch.rpm nodejs010-nodejs-opener-1.4.1-1.el7.noarch.rpm nodejs010-nodejs-osenv-0.1.3-1.el7.noarch.rpm nodejs010-nodejs-os-homedir-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-os-tmpdir-1.0.1-3.el7.noarch.rpm nodejs010-nodejs-path-array-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-path-is-absolute-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-path-is-inside-1.0.0-1.el7.x86_64.rpm nodejs010-nodejs-process-nextick-args-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-promzard-0.2.0-7.el7.noarch.rpm nodejs010-nodejs-proto-list-1.2.2-5.el7.noarch.rpm nodejs010-nodejs-qs-1.2.2-1.el7.noarch.rpm nodejs010-nodejs-read-1.0.5-1.el7.noarch.rpm nodejs010-nodejs-readable-stream-2.0.2-3.el7.noarch.rpm nodejs010-nodejs-readdir-scoped-modules-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-read-installed-4.0.3-1.el7.noarch.rpm nodejs010-nodejs-read-package-json-2.0.2-1.el7.noarch.rpm nodejs010-nodejs-realize-package-specifier-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-request-2.42.0-6.el7.noarch.rpm nodejs010-nodejs-retry-0.6.0-6.el7.noarch.rpm nodejs010-nodejs-rimraf-2.4.3-1.el7.noarch.rpm nodejs010-nodejs-semver-5.0.3-1.el7.noarch.rpm nodejs010-nodejs-sha-2.0.1-2.1.el7.noarch.rpm nodejs010-nodejs-slide-1.1.6-1.el7.noarch.rpm nodejs010-nodejs-sorted-object-1.0.0-3.el7.noarch.rpm nodejs010-nodejs-spdx-correct-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-spdx-exceptions-1.0.4-1.el7.noarch.rpm nodejs010-nodejs-spdx-expression-parse-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-spdx-license-ids-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-string_decoder-0.10.31-1.el7.noarch.rpm nodejs010-nodejs-strip-ansi-0.2.0-1.el7.noarch.rpm nodejs010-nodejs-tar-2.2.1-1.el7.noarch.rpm nodejs010-nodejs-text-table-0.2.0-1.el7.x86_64.rpm nodejs010-nodejs-tunnel-agent-0.3.0-2.el7.noarch.rpm nodejs010-nodejs-uid-number-0.0.5-1.el7.noarch.rpm nodejs010-nodejs-umask-1.1.0-4.el7.noarch.rpm nodejs010-nodejs-unc-path-regex-0.1.1-2.el7.noarch.rpm nodejs010-nodejs-util-deprecate-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-util-extend-1.0.1-4.el7.noarch.rpm nodejs010-nodejs-validate-npm-package-license-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-validate-npm-package-name-2.2.2-3.el7.noarch.rpm nodejs010-nodejs-wcwidth-1.0.0-4.el7.noarch.rpm nodejs010-nodejs-which-1.2.0-1.el7.noarch.rpm nodejs010-nodejs-wrappy-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-write-file-atomic-1.1.2-3.el7.noarch.rpm nodejs010-npm-2.14.13-6.el7.noarch.rpm nodejs010-runtime-2.1-5.el7.x86_64.rpm *If i copy paste above RPMS to my custom ISO, then anaconda successfully installs these packages, without any errors* *What is there is these already built RPMs (taken from repo: [centos-sclo-rh] : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) which is not there in my built RPMS?* Any pointers for this, as we feel, there is some inconsistency in the version available on git.centos.org/git/rpms/<name_of_pkg>.git ? Regards Sudhanshu Bhutani

2 1

None
by None 30 Aug '16

30 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7UM1iPO028599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Tue, 30 Aug 2016 18:01:45 -0400 To: centos(a)centos.org From: Pat Haley <phaley(a)mit.edu> Message-ID: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> Date: Tue, 30 Aug 2016 18:01:44 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPIsWRmVeSWpSXmKPExsUixG6nouvFdCzc4PUCIYtlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CV0bNoOlPBCc6KTQ9PsDcwTmfvYuTkkBAwkXjZsomti5GLQ0ig jUni8MVtUM5JRokZM6ZAOQeZJKY/2c8I0iIiICrRs/gVG4jNJqAgse7WGbBRwkCjmldeZAKx eQWsJL43bQezWQRUJeZOaGcGsUUFIiRurfrICFEjKHFy5hMWEJtZwExi3uaHzBC2vMT2t3OY JzDyzkJSNgtJ2SwkZQsYmVcxyqbkVunmJmbmFKcm6xYnJ+blpRbpGurlZpbopaaUbmIEhROn JM8OxjNvvA4xCnAwKvHwZsw4Gi7EmlhWXJl7iFGSg0lJlDf8L1CILyk/pTIjsTgjvqg0J7X4 EKMEB7OSCO91xmPhQrwpiZVVqUX5MClpDhYlcd6uGQfChQTSE0tSs1NTC1KLYLIyHBxKErw7 QBoFi1LTUyvSMnNKENJMHJwgw3mAhnuDDS8uSMwtzkyHyJ9iVJQS5xUFSQiAJDJK8+B6wfGu xn7oFaM40CvCvJcYgKp4gKkCrvsV0GAmoMEFdw6DDC5JREhJNTDOn+LY8sOJSVhFfnV4VzaH T8iDcx+0dvn36Fluta5/vWa3rODTN3LmNl7/W21uh59fwpKvfHjqMtdZ9z/tc/MKZN9/zYhn ocKdJ3P7bu9nyWx6U+Q44dhR8+nzNdf0b5hqFX9bxvtEguS/b/MebPXkTHr/ZmV4+PPttabT hGf57usu5fV/dH+mEktxRqKhFnNRcSIAKBIMXtICAAA= Subject: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Tue, 30 Aug 2016 22:01:46 -0000 Hi We have just migrated our data to a new file server (more space, old server was showing its age). We have a volume for collaborative use, based on group membership. In our new server, the group write permissions are not being respected (e.g. the owner of a directory can still write to that directory but any other member of the associated group cannot, even though the directory clearly has group write permissions set). This is occurring regardless of how many groups the user is a member of (i.e. users that are members of fewer then 16 groups are still affected). the relevant fstab line from the server looks like localhost:/data-volume /gdata glusterfs defaults 0 0 and for a client: mseas-data2:/gdata /gdata nfs defaults 0 0 Any help would be greatly appreciated. Thanks -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

None
by None 30 Aug '16

30 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7ULNSNq006624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Tue, 30 Aug 2016 17:23:29 -0400 To: centos(a)centos.org References: <d80864bd-9497-86be-d8db-cdf3c0378d7c(a)mit.edu> <20160829172355.849cf429eb17bf94dd738fa0(a)melvilletheatre.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <2e155be1-9265-a189-724b-3ab2659d38dc(a)mit.edu> Date: Tue, 30 Aug 2016 17:23:27 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160829172355.849cf429eb17bf94dd738fa0(a)melvilletheatre.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKIsWRmVeSWpSXmKPExsUixCmqrRv082i4wc2bKhbLzixgdmD0WNk2 mTmAMYrLJiU1J7MstUjfLoErY8oKr4I7QhWPvy9mbmC8xdfFyMkhIWAiMeHnW7YuRi4OIYE2 Jonvr+8xQTgnGSWeblnADuEcZJI4+7aHGaRFWMBB4s/PdjYQW0RAVKJn8SswW0igSuL9pIus IDabgILEultngJo5OHgFrCTurdECCbMIqErs7pjBAmKLCkRI3Fr1kRHE5hUQlDg58wlYnFPA S2LpSpBWTg5mAVuJO3N3M0PY8hLb385hnsDIPwtJyywkZbOQlC1gZF7FKJuSW6Wbm5iZU5ya rFucnJiXl1qka6aXm1mil5pSuokRFHrsLso7GF/2eR9iFOBgVOLhzZhxNFyINbGsuDL3EKMk B5OSKO+eDqAQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd7P34ByvCmJlVWpRfkwKWkOFiVx3q4Z B8KFBNITS1KzU1MLUotgsjIcHEoSvJe/AzUKFqWmp1akZeaUIKSZODhBhvMADZf8ATK8uCAx tzgzHSJ/ilFRSpz3JchWAZBERmkeXC84NaixH3rFKA70ijDvBJB2HmBaget+BTSYCWhwwZ3D IINLEhFSUg2MXoXXLeI4mYVE/+/6wH6wcoE9U0T+PJM1BlkHD9Wf0vBY8KxlmrXtvGccL6Sj 7i79srzxJr9ZlPiykLwtlgyeWz8o+dev1xDPb1llFMNy/n4Bx6+UoNfBix8Hq6552ppktzJu y4MgFr6g7y9qb/DKnzLobU95usB1rsxeP72OdVU5x4UWtz9SYinOSDTUYi4qTgQA4LNe++gC AAA= Subject: Re: [CentOS] CentOS 6: files now owned by nobody:nobody X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Tue, 30 Aug 2016 21:23:31 -0000 The setting the Domain = line in /etc/idmapd.conf option solved our problem Thanks On 08/29/2016 07:23 PM, Frank Cox wrote: > On Mon, 29 Aug 2016 18:59:31 -0400 > Pat Haley wrote: > >> We noticed that all the files were owned by nobody > Here are my notes for dealing with this issue: > > If all users come up as nobody on a nfs mount: > > Add nfs server name to the Domain = line in /etc/idmapd.conf on both the server and the clients, i.e. Domain = nameof.server > > /sbin/service rpcidmapd restart > /sbin/service nfslock restart > /sbin/service nfs restart > > Also, the complete hostname as specified (nameof.server) must be in /etc/hosts on the nfs clients as well as the server > > --------------- > try > /usr/sbin/nfsidmap -c > on the client. > Since I put this into my /etc/rc.local , I don't have the problem any > longer. > --------------- > 1) /etc/idmapd.conf > # Set domain to the domain name shared by your NFS servers. > Domain: mycompany.com > Set local-realms to the name of the nfs servers you'll be using. THIS > WASN'T MENTIONED ELSEWHERE. > Local-Realms: nfs1.mycompany.com,nfs2.mycompany.com > # make the above changes on all the servers in question. > > 2) /etc/hosts: list with all the NFS servers you specified in local-realms above. This way DNS errors don't make your servers get hung > 1.2.3.4 nfs1.mycompany.com > 1.2.3.5 nfs2.mycompany.com > > 3) Make sure you synchronize your /etc/passwd files so that the account > IDs match up or you'll get very strange results. > > 4) Reboot EVERYTHING. Restarting services was not enough. > For documentation's sake, I restarted rpcidmapd, nfslock, and nfs, but didn't get the correct permissions until reboot. It doesn't seem important to run the nfs service on the > clients. > > 5) Client mount: > # CLI > /bin/mount -t nfs servername:/path/to/share /local/mount/point > > # /etc/fstab > servername.com:/path/to/share /local/mount/mount nfs ro,nolock 0 0 > > # mount -a > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Re: [CentOS] CentOS 6: files now owned by nobody:nobody
by Jonathan Billings 30 Aug '16

30 Aug '16

On Mon, Aug 29, 2016 at 06:59:31PM -0400, Pat Haley wrote: > ... We > noticed that all the files were owned by nobody (with nobody as the group). If its NFSv4, then its most likely a problem with your idmapper. Make sure that the rpc.idmapd is running on your client, and that your server has appropriate ID mapping enabled. If its NFSv4, are you using sec=krb5*? -- Jonathan Billings <billings(a)negate.org>

2 1

.htaccess file
by TE Dukes 30 Aug '16

30 Aug '16

Hello, My home system on a DSL line is getting worn out by bad behavior robots. Awhile back, I created a .htaccess file that block countries by IP blocks. Its 2MB in size. I have been running Linux since Slackware 1.0 and moved to Redhat around 2.0. I started after running a BBS using a doorway for newsgroups. Been hooked ever since. So, today, I tried following the directions for apache.org website, https://httpd.apache.org/docs/current/howto/htaccess.html to move the .htaccess <https://httpd.apache.org/docs/current/howto/htaccess.html%20to%20move%20the %20.htaccess> file to a file located in a directory /var/www/htdocs. I'm just not following or understanding. The .htaccess file works but on a slow DSL, I don't want the hits. I added the following to my httpd.conf: <Directory "/var/www/htdocs"> AddType text/htdocs ".txt" </Directory> And copied my .htaccess to /var/www/htdocs as htaccess.txt In the example from the apache website, I don't get the: AddType text/example ".exm" Where did they come up .exm? TIA

6 16

None
by None 29 Aug '16

29 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7TNPWl1024422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Mon, 29 Aug 2016 19:25:33 -0400 To: centos(a)centos.org References: <d80864bd-9497-86be-d8db-cdf3c0378d7c(a)mit.edu> <73650851-909c-c43a-a926-53cbdf14af6f(a)hogranch.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <7fe0f111-e54b-6f26-d816-a82851ddd0bd(a)mit.edu> Date: Mon, 29 Aug 2016 19:25:28 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <73650851-909c-c43a-a926-53cbdf14af6f(a)hogranch.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOIsWRmVeSWpSXmKPExsUixG6nrpt35Ei4wYsubotlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CVcfjCYsaCi3wVl2beZGlgbObuYuTkkBAwkXi19idjFyMXh5BA G5PEgemTmSCck4wS7X9vsEM4B5kk7jx+wwzSIizgIPHnZzsbiC0iICrRs/gVmC0kUCBxcdVH JhCbTUBBYt2tM+wgNq+AlcSdttNgNSwCqhIbzy1hBLFFBSIkbq36yAhRIyhxcuYTFhCbE2j+ snOLwOYwC9hK3Jm7mxnClpfY/nYO8wRG/llIWmYhKZuFpGwBI/MqRtmU3Crd3MTMnOLUZN3i 5MS8vNQiXSO93MwSvdSU0k2MoPDjlOTdwfjvrtchRgEORiUeXgunI+FCrIllxZW5hxglOZiU RHmnxgOF+JLyUyozEosz4otKc1KLDzFKcDArifBmHgDK8aYkVlalFuXDpKQ5WJTEebtmHAgX EkhPLEnNTk0tSC2CycpwcChJ8EocBmoULEpNT61Iy8wpQUgzcXCCDOcBGv7zEMjw4oLE3OLM dIj8KUZFKXFeR5CEAEgiozQPrhecHtTYD71iFAd6RZj3EMgKHmBqget+BTSYCWhwwZ3DIINL EhFSUg2MtRuzrx96Znrb3Jt1f0vz9MNWL/5JBMb1/RXy/fB5Q+S907I8qTN2M14+rpuzfO68 mWuTyy+/PL6g0WS56+LWBIuKnRatOnlWseeTJ3M5RHeeDpqVttdg0RyGQBflxju85xlOVFzd 5/+Oy7lEeWp0Q1zWW7mp4m+9HzTMurBGZKFZZIeT2P1QJZbijERDLeai4kQAP19NXOoCAAA= Subject: Re: [CentOS] CentOS 6: files now owned by nobody:nobody X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Mon, 29 Aug 2016 23:25:35 -0000 I believe NFSv4. On the machine that contains the physical disks (is that the "server" or the "NSF mount"?) the relevant line from /etc/fstab seems to be UUID=bde58f42-4ac4-4763-b0a8-f83723f0e2a0 /home ext4 defaults 1 2 while on my front-end machine its mseas-data2:/home /home nfs defaults 0 0 where mseas-data2 is the name of the machine that contains the physical disks. Note that it isn't just root that's becoming "nobody" but all the users Thanks On 08/29/2016 07:14 PM, John R Pierce wrote: > On 8/29/2016 3:59 PM, Pat Haley wrote: >> We are running a cluster under CentOS 6.6. We recently attached a >> new NAS device, running CentOS 6.8 and rsync'd our user file system >> to it. We noticed that all the files were owned by nobody (with >> nobody as the group). We copied over the /etc/passwd and /etc/group >> files from our front-end server to our NAS server. If we log in to >> the NAS server we see the files owned by their correct owners. >> However, doing an ls from the front-end server or any of the compute >> nodes still shows the files owned by "nobody". We rebooted one of >> the compute nodes but it still sees the files owned by nobody. > > a CentOS server isn't really a 'NAS device', as NAS implies an > appliance storage device. > > this is NFS? NFSv3, or NFSv4? what NFS options are on the server > and on the NFS mount? quite often NFS servers force root to nobody. > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Re: [CentOS] CentOS 6: files now owned by nobody:nobody
by Frank Cox 29 Aug '16

29 Aug '16

On Mon, 29 Aug 2016 18:59:31 -0400 Pat Haley wrote: > We noticed that all the files were owned by nobody Here are my notes for dealing with this issue: If all users come up as nobody on a nfs mount: Add nfs server name to the Domain = line in /etc/idmapd.conf on both the server and the clients, i.e. Domain = nameof.server /sbin/service rpcidmapd restart /sbin/service nfslock restart /sbin/service nfs restart Also, the complete hostname as specified (nameof.server) must be in /etc/hosts on the nfs clients as well as the server --------------- try /usr/sbin/nfsidmap -c on the client. Since I put this into my /etc/rc.local , I don't have the problem any longer. --------------- 1) /etc/idmapd.conf # Set domain to the domain name shared by your NFS servers. Domain: mycompany.com Set local-realms to the name of the nfs servers you'll be using. THIS WASN'T MENTIONED ELSEWHERE. Local-Realms: nfs1.mycompany.com,nfs2.mycompany.com # make the above changes on all the servers in question. 2) /etc/hosts: list with all the NFS servers you specified in local-realms above. This way DNS errors don't make your servers get hung 1.2.3.4 nfs1.mycompany.com 1.2.3.5 nfs2.mycompany.com 3) Make sure you synchronize your /etc/passwd files so that the account IDs match up or you'll get very strange results. 4) Reboot EVERYTHING. Restarting services was not enough. For documentation's sake, I restarted rpcidmapd, nfslock, and nfs, but didn't get the correct permissions until reboot. It doesn't seem important to run the nfs service on the clients. 5) Client mount: # CLI /bin/mount -t nfs servername:/path/to/share /local/mount/point # /etc/fstab servername.com:/path/to/share /local/mount/mount nfs ro,nolock 0 0 # mount -a -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

Re: [CentOS] CentOS 6: files now owned by nobody:nobody
by John R Pierce 29 Aug '16

29 Aug '16

On 8/29/2016 3:59 PM, Pat Haley wrote: > We are running a cluster under CentOS 6.6. We recently attached a new > NAS device, running CentOS 6.8 and rsync'd our user file system to > it. We noticed that all the files were owned by nobody (with nobody > as the group). We copied over the /etc/passwd and /etc/group files > from our front-end server to our NAS server. If we log in to the NAS > server we see the files owned by their correct owners. However, doing > an ls from the front-end server or any of the compute nodes still > shows the files owned by "nobody". We rebooted one of the compute > nodes but it still sees the files owned by nobody. a CentOS server isn't really a 'NAS device', as NAS implies an appliance storage device. this is NFS? NFSv3, or NFSv4? what NFS options are on the server and on the NFS mount? quite often NFS servers force root to nobody. -- john r pierce, recycling bits in santa cruz

1 0

None
by None 29 Aug '16

29 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7TMxYi2018663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Mon, 29 Aug 2016 18:59:35 -0400 To: centos(a)centos.org From: Pat Haley <phaley(a)mit.edu> Message-ID: <d80864bd-9497-86be-d8db-cdf3c0378d7c(a)mit.edu> Date: Mon, 29 Aug 2016 18:59:31 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPIsWRmVeSWpSXmKPExsUixCmqrRux70i4wcJOMYtlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CVcf70RNaC2RwVk/dMY2pgnMvWxcjJISFgIrGldTJrFyMXh5BA G5PEmwOT2SGck4wSfx/1sUA4B5kkjvW9ZQVpEREQlehZ/AqsnU1AQWLdrTPsILawgLHE3ua3 zCA2r4CVxPGHvxhBbBYBVYlLM+aA1YsKREjcWvWREaJGUOLkzCcsIDazgJnEvM0PmSFseYnt b+cwT2DknYWkbBaSsllIyhYwMq9ilE3JrdLNTczMKU5N1i1OTszLSy3SNdPLzSzRS00p3cQI Cid2F+UdjC/7vA8xCnAwKvHwWjgdCRdiTSwrrsw9xCjJwaQkyjs1HijEl5SfUpmRWJwRX1Sa k1p8iFGCg1lJhNd/E1CONyWxsiq1KB8mJc3BoiTO2zXjQLiQQHpiSWp2ampBahFMVoaDQ0mC l3UvUKNgUWp6akVaZk4JQpqJgxNkOA/Q8DCQGt7igsTc4sx0iPwpRkUpcd7SPUAJAZBERmke XC843tXYD71iFAd6RZhXG6SdB5gq4LpfAQ1mAhpccOcwyOCSRISUVAOjXLhTjFpr1FumG1/e yu09w9DuVbNZTuJk4jPXvRyHVbvEGhunT5ZIN6wyd0pjkj3HJq2gf+nhVe9Y6/MPrcRURdiW 8T4+IfCG4fqRE4GrfRi4NgcfrdK3mffA53rf31wjY2bWSWkT2ErO62i8jZ4sc/XUWea/dVHF s5/vuLg31zr/m1Zw5yolluKMREMt5qLiRADDYFna0gIAAA== Subject: [CentOS] CentOS 6: files now owned by nobody:nobody X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Mon, 29 Aug 2016 22:59:36 -0000 Hi, We are running a cluster under CentOS 6.6. We recently attached a new NAS device, running CentOS 6.8 and rsync'd our user file system to it. We noticed that all the files were owned by nobody (with nobody as the group). We copied over the /etc/passwd and /etc/group files from our front-end server to our NAS server. If we log in to the NAS server we see the files owned by their correct owners. However, doing an ls from the front-end server or any of the compute nodes still shows the files owned by "nobody". We rebooted one of the compute nodes but it still sees the files owned by nobody. Any advice would be greatly appreciated. Thanks -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

ipsets/iptables question
by TE Dukes 29 Aug '16

29 Aug '16

Hello, I have ipsets setup with a set of ip address that are badbots that won't comply with robots.txt This is a home server and these are most likely up to no good. I came up with a script to extract ip address from my access_log then another script to take ips and import them into my blacklist set. (see my scripts in the .htaccess thread) I can set these up as cron jobs but I'm not sure about the following: 1) after importing/updating the set, do I need to perform a, ipset save blacklist Since I haven't changed the rule in iptables, do I need to run these? 2) service iptables save 3) service iptables restart Thank!!

1 0

Loaded: not-found (Reason: No such file or directory)
by Kaushal Shriyan 29 Aug '16

29 Aug '16

Hi, I am seeing the below issue. [user~]# systemctl list-unit-files | grep nrpe [user~]# service nrpe status Redirecting to /bin/systemctl status nrpe.service ● nrpe.service * Loaded: not-found (Reason: No such file or directory)* Active: inactive (dead) [user~]# rpm -qa | grep nrpe nrpe-3.0-1.x86_64 nrpe-plugin-3.0-1.x86_64 [user~]#cat /etc/redhat-release *CentOS Linux release 7.2.1511 (Core)* [user~]# Any help will be highly appreciable and please let me know if anyone needs any additional information. Regards, Kaushal

3 2

Gnome weather applet stranded
by isdtor 29 Aug '16

29 Aug '16

The Gnome weather report applet has ceased working on CentOS5/6. http://weather.noaa.gov/ says "This service is no longer available". Are there any good alternatives? I liked the applet as it allowed the use of a custom radar map. As I just discovered, the weather functionality of the CentOS6 Gnome clock applet was using the same service.

10 21

Off Topic: CentOS Public mirror question
by Valeri Galtsev 29 Aug '16

29 Aug '16

Dear All, My apologies for asking my question on less appropriate list. I did ask it on centos-mirror(a)centos.org, but that list is really low traffic (and slow response probably - I only got acknowledgement of my post...). On the other hand, I'm sure there are many public mirror maintainers on this list who may help me with my trouble. Upon replacing faulty machine hosting public mirrors I have noticed that I can not rsync CentOS (all other mirrors do rsync happily as they did on failed box). I probably have missed some announcement, so my apologies for asking what I should know already myself. Which higher tier mirror should I use to rsync CentOS from (including DVDs) to public mirror I maintain? I use probably outdated source to rsync from. Namely, here is my rsync line (in longer cron job): rsync -aqH --exclude .~tmp~/ --exclude .~tmp~ --delete\ msync-dvd.centos.org::CentOS-incdvd /data/mirror/centos - and I'm getting the following error: @ERROR: Unknown module 'CentOS-incdvd' I also tried what CentOS public mirror wiki suggests, and get similar error: rsync -aqH --exclude .~tmp~/ --exclude .~tmp~ --delete\ us-msync.centos.org::CentOS /data/mirror/centos @ERROR: Unknown module 'CentOS' Independent on this error I also have a bit strange answer in DNS resolution of msync-dvd.centos.org: # host msync-dvd.centos.org msync-dvd.centos.org has address 209.44.106.213 Host msync-dvd.centos.org not found: 2(SERVFAIL) I would appreciate any help or pointers. Thanks a lot in advance for all your answers! Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

2 1

BIND (named) as secondary and .jnl files
by Walter H. 28 Aug '16

28 Aug '16

Hello, I have two running BINDs in my LAN, one on my router box and one as VM; both are caching DNS servers, and a few zones are on both, on the box as master and on the VM as slave, but how can I cleanup/flush the growing .jnl files; rndc freeze rndc thaw doesn't work as these are not master ... Thanks, Walter

2 1

Kickstart issue with UEFi
by Phil Manuel 28 Aug '16

28 Aug '16

Hi, I have a test system that booted fine using "Legacy Bios” mode and using the following Kickstart snippet configured the disks correctly:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow --ondisk=sda --size=1 part raid.03 --fstype="raid" --ondisk=sdb --size=500 part raid.04 --fstype="raid" --grow --ondisk=sdb --size=1 raid /boot --device=0 --fstype="xfs" --level=RAID1 raid.01 raid.03 raid pv.01 --device=1 --level=RAID1 raid.02 raid.04 For UEFi I changed it to the following:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow --ondisk=sda --size=1 part raid.03 --fstype="raid" --ondisk=sdb --size=500 part raid.04 --fstype="raid" --grow --ondisk=sdb --size=1 raid /boot --device=0 --fstype="xfs" --level=RAID1 raid.01 raid.03 part /boot/efi —fstype=“efi” --grow --maxsize=200 --size=20 raid pv.01 --device=1 --level=RAID1 raid.02 raid.04 The install fails under UEFi due to the fact the partitions are not cleared, and it doesn’t have any space to continue. Is there an extra step I need to do to remove the original partitions before the new layout will work ? Thanks

6 13

CentOS 7 : keyboard shortcut for mouse gesture?
by Nicolas Kovacs 28 Aug '16

28 Aug '16

Hi, I have a CentOS 7 (GNOME) desktop installed as a VirtualBox guest on my Slackware64 14.1 workstation, to fiddle with it. Guest Additions are installed and configured OK, and 3D acceleration is working too. In its default configuration, the GNOME desktop under CentOS shows an "exposé" (I don't know how you call this), a list of all open windows, when you move the mouse cursor to the upper left corner of the screen. When no window is open, you just see the sidebar with the application launchers, and on the right side you see the empty virtual desktops. Is there a keyboard shortcut for this mouse gesture? I'm asking because on my dual-monitor workstation, the CentOS guest is displayed full-screen on my right monitor, and the mouse gesture seems to be ineffective. Thanks, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 2

Samba DC NT4 Style is Gone. When AD-DC will enable for default into Centos/RedHat Samba4 packages?
by Dario Lesca 27 Aug '16

27 Aug '16

This recent Microsoft's Patch https://lists.samba.org/archive/samba/2016-August/202197.html disable password change for all server Domain Controller NT4 Style, Samba 3 and 4 included. Then is urgent to enable, into Samba 4 Centos package by default support to AD-DC mode, or release another renamed packages with AD-DC support enable. For now, I must download the samba.src rpm, modify the spec file > sed \ > -e 's/%global with_mitkrb5 1/%global with_mitkrb5 0/' \ > -e 's/%global with_dc 0/%global with_dc 1/' \ > ~/rpmbuild/SPECS/samba.spec then rebuild the package after all update. My question is: There is some hope that in the short this flags are enable by default? Many thanks for your reply -- Dario Lesca (inviato dal mio Linux Fedora 24 Workstation)

1 0

CentOS-announce Digest, Vol 138, Issue 9
by centos-announce-request＠centos.org 27 Aug '16

27 Aug '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2016:1776 Important CentOS 5 java-1.6.0-openjdk Security Update (Johnny Hughes) 2. CESA-2016:1776 Important CentOS 6 java-1.6.0-openjdk Security Update (Johnny Hughes) 3. CESA-2016:1776 Important CentOS 7 java-1.6.0-openjdk Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 26 Aug 2016 14:36:52 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1776 Important CentOS 5 java-1.6.0-openjdk Security Update Message-ID: <20160826143652.GA17670(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1776 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1776.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d6d0f386a6f9d22a393a247f7cd7c58b1239c6ae7b313828b87fcdfa65a68b1e java-1.6.0-openjdk-1.6.0.40-1.13.12.4.el5_11.i386.rpm 003823d694e9316c0f58b2cef8ec2f1c5a785a0548a5ae82b9c8c00ed42a5e3a java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.4.el5_11.i386.rpm a901afc3d0ab6313a4b1f95e7af4a6d452925643899807365453285232c320db java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.4.el5_11.i386.rpm daf59f8a6ba2bb995a58c9bf836130882508d4cd0df923078e11ba7b622437cd java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.4.el5_11.i386.rpm 26112915bd3ce6e56f376abe8d6c7c7c3ec34bd291ab024171941082191c5ab2 java-1.6.0-openjdk-src-1.6.0.40-1.13.12.4.el5_11.i386.rpm x86_64: 7facd58d760041b41707cbc04fea6404e5760aa89a64b09a63d0f642453e601c java-1.6.0-openjdk-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm acdd1a149a650802bab713348efed3cea94c3fa1e4a3eedef0b14dc530f63e11 java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm faa0bb044816096b5c322ed889500fab4226b773add9da74ac3785533a06233b java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm 9098ab7a6fa89b673952660495ff0fe4814ba653bcb36e58d3b40514398fd057 java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm ac196f3ec06eb8008d9104d9bb8b27ca9142e2bdaff848053c7ad25f9765656b java-1.6.0-openjdk-src-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm Source: dfc80c864a12dd91aa6b026969da5dfceeafbce0c3ee8862ee8ec892943ddae6 java-1.6.0-openjdk-1.6.0.40-1.13.12.4.el5_11.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 26 Aug 2016 14:45:12 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1776 Important CentOS 6 java-1.6.0-openjdk Security Update Message-ID: <20160826144512.GA47992(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1776 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1776.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 85a42b9dc7548e3f8b86cacd1609fc14bc8e8e519a4ce4858e15d320d09d6c9d java-1.6.0-openjdk-1.6.0.40-1.13.12.6.el6_8.i686.rpm a44a315add63888bdb90fd5c6dec550396d8c6a3ac3daa0dba40f07520927d6c java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.6.el6_8.i686.rpm 358bda472da2634563588274cd6f8f8095dd7af95fc6ecc1b28c6eabcde63a1b java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.6.el6_8.i686.rpm 4365bf6681d15abcb1967eb66c365ea867ed39e9272a6b2babfadbf9dc5faf70 java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.6.el6_8.i686.rpm 64b7542290a9531ee58d69027f060fabb9d87bd0a3c1c56856e4993a0b69048c java-1.6.0-openjdk-src-1.6.0.40-1.13.12.6.el6_8.i686.rpm x86_64: 867d64c8e0b0a7ab80aa705b96f64ea8c2a8637374dca25707180cb9fe3a55a8 java-1.6.0-openjdk-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm 3ec19d952f64d6a3b5cdbb5d0012117d842128474f880f621a77f67381e66149 java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm ec5818e8e2670df9b68140febdbcccb1cab99cf016b7fc1f57442bbe03579ac1 java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm e582a9589e7f51391dbb900eb0b9e6d7872e1382a1ab23aa9f41fb64254c5109 java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm 05cca14dd0a3ba8fa4e8c794ac83610766104ce9215141148da92730754db124 java-1.6.0-openjdk-src-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm Source: 2ca712c6daf3a2597d52228823cf01e58a77613f07bd201ae1739a32d32090db java-1.6.0-openjdk-1.6.0.40-1.13.12.6.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 26 Aug 2016 15:40:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1776 Important CentOS 7 java-1.6.0-openjdk Security Update Message-ID: <20160826154017.GA60948(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1776 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1776.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f2a27f7b6061bed7fc189feb3b25b63319d8b41f6d0c67c3feebcc297aa7487f java-1.6.0-openjdk-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm b685ba29ba96991483b3120219338e90919708d21b2ac4a4b68100ad022ce381 java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm 0a136da5d7ed5a505effabe1218ff47245c84c4cbb2fa59cfbe5d248dceb4310 java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm 3ec9d367a743952bf34c36152e087e9b071f1d07fa7cac3fc7bed03a2748e559 java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm 2eeabee30ab8056b61e4b2f258b973586edc47eb9d23aed27c972f12022bef40 java-1.6.0-openjdk-src-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm Source: e9a9b3b63cdfd7cec648b4893ba5f09c1c3ee68a9e3e9079ad5c67d7aafac10f java-1.6.0-openjdk-1.6.0.40-1.13.12.5.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 138, Issue 9 ***********************************************

1 0

kernel/iptables state match support
by Richard B. Pyne 26 Aug '16

26 Aug '16

I just noticed that the stock Centos7 kernels no longer include state/match support. What happened and what can be done to get it? --Richard

2 1

I need glibc 2.19+ for 32 bit CentOS 6.8 or CentOS7
by Kay Schenk 26 Aug '16

26 Aug '16

Hello all-- Due to a proposed changeover to build machines for a project I'm involved with, I need at least glib 2.19. Right now I have glib 2.12, and even on CentOS7-32 bit, what I see is glib 2.14. Is a higher glib available anywhere that might work with my current 6.8. I see I can download it from SourceForge but I am wondering what the results might me. I really like CentOS and would hate to change distros at this point, but, well, it might come to that. :( Any advice truly appreciated. -- -------------------------------------------- MzK "God helps those who help themselves." -- popular adage

7 13

info wanted about meaning of boot messages ...
by Walter H. 26 Aug '16

26 Aug '16

Hello, I've got CentOS 6.8 x64, updated today to the latest by 'yum update' this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 in /var/log/boot.log I found these 3 lines ... No kdump initial ramdisk found. [WARNING] Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img cp: cannot stat `/lib/firmware/i915/bxt_dmc_ver1.bin': No such file or directory the first two are logic to me, but the 3rd line, did there something fail at the update? Thanks, Walter

2 6

KDE 4.14.8 -- 'Leave' - no suspend to disk
by geo.inbox.ignored 26 Aug '16

26 Aug '16

greetings one and all. just what is a better way to suspend kde on a laptop? for a programmer to write 'leave' routines and not have option to 'suspend to disk', tells me the programmer; does not own a laptop is mad at laptop owners because he does not have one has stock in companies that make batteries for laptops to be serious about this, just where should i post/write to get in contact with someone who can see about getting this problem corrected? any/all suggestions/answers greatly needed. tia. -- peace out. CentOS GNU/Linux 7.1511 tc,hago. g . =+= Tired of having your microsoft os hacked? Change to Linux os, used by microsoft hackers. =+= in a world with out fences, who needs gates. =+=

1 1

users unable to log into kde after 6.8 update
by geo.inbox.ignore 26 Aug '16

26 Aug '16

greetings to all. centos = 6.8 current system = toshiba l455d-s5976 laptop a new problem has developed after 1st updating of 6.8. regular user is not able to open kde desktop, can open gnome desktop. root user can open either kde or gnome desktop. as a user, when i try to open kde, after entering password, screen goes to a solid blue, then shows a quick full screen view of command line text, too quick to read, then screen changes back to login prompt. logged in as root, i created a second user, still have same results as above. searching thru 2+ years of local archives revealed nothing, nor does web searching. any advise, recommendation, suggestion appreciated. tia. -- peace out. -+- Tired of having your microsoft os hacked? Change to Linux os, used by microsoft hackers. -+- in a world with out fences, who needs gates. -+- CentOS GNU/Linux 6.8 tc,hago. g .

4 6

[OT] disk utility showing message "the partition is misaligned by"
by g 26 Aug '16

26 Aug '16

greetings. centos 6.7 [current] 'disk utility' has started showing message; WARNING: The partition is misaligned by 2560 bytes. This may result in very poor performance. Repartitioning is suggested. for sdc5 - /home partition. /dev/sdc5 302243312 156348604 130534968 55% /home /dev/sdc7 80854912 57088 76683952 1% /hdd/c/07 other than time involved to backup sdc5, repartition is not a problem. to my thinking, but not recalling, with fsck; fsck -rN -t ext4 /dev/sdc5 * to check repairs fsck -r -t ext4 /dev/sdc5 * to repair gparted was used to partition drive. is pmagic live a better choice, or should i return fdisk because; =+=+= $ sudo fdisk -l /dev/sdc [sudo] password for geo: Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0009ede7 Device Boot Start End Blocks Id System /dev/sdc1 * 1 103 819200 83 Linux Partition 1 does not end on cylinder boundary. /dev/sdc2 103 230 1024000 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/sdc3 230 2107 15073280 83 Linux /dev/sdc4 2107 121602 959844352 5 Extended /dev/sdc5 2108 42019 320587970+ 83 Linux Partition 5 does not start on physical sector boundary. =+=+= suggestions for correcting above boundaries also appreciated. help needed and greatly appreciated. -- peace out. If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.7 tc,hago. g .

7 9

systemd not restarting daemon
by Chris Adams 26 Aug '16

26 Aug '16

On an up-to-date CentOS 7 system, I am running named-sdb (pulling domain records from MySQL), which is segfaulting randomly (after 3-8 hours or so it appears) in libmysqlclient (I've opened a bug). Since this is an internal service, until the segfault can be addressed, I wanted systemd to restart it for me. I created a file called /etc/systemd/system/named-sdb-chroot.service.d/service.conf with: [Service] Restart=always in it. I did "systemctl daemon-reload" and restarted the service, but systemd is not restarting it. It knows it died, because that's in the log (and it ran the chroot cleanup service): Aug 25 12:03:39 dnssql systemd: named-sdb-chroot.service: main process exited, code=killed, status=11/SEGV Aug 25 12:03:39 dnssql systemd: named-sdb-chroot.service: control process exited, code=exited status=1 Aug 25 12:03:39 dnssql systemd: Unit named-sdb-chroot.service entered failed state. Aug 25 12:03:39 dnssql systemd: named-sdb-chroot.service failed. Aug 25 12:03:39 dnssql systemd: Stopping Set-up/destroy chroot environment for named-sdb... Aug 25 12:03:39 dnssql systemd: Stopped Set-up/destroy chroot environment for named-sdb. I see the file listed in the output of systemd-delta, so I know it is being seen. Any idea why systemd isn't restarting it? -- Chris Adams <linux(a)cmadams.net>

2 3

Email pid issue
by Jay Hart 26 Aug '16

26 Aug '16

Hello gents, First time poster here! Current system running Centos 6.8. Buddy of mine posted a few days back about me wanting to move from Postfix 2.6.x to 2.8 to above, still under centos 6.8. I might move over to 7, but probably not for a while, don't have the resources presently to make this happen. Running Centos 6.8, postfix 2.6.6, clamav 0.99.1. Basic Centos 6.8 box fully patched using stable repos. ____ISSUE_____ Logwatch is reporting this error, which I'm going to assume has been occurring for a few years but doesn't affect sending/receiving emails, so I haven't chased it down, now I'm looking to fix that. 1 (06498-19) ClamAV-clamd: All attempts (1) failed connecting to /var/spool/amavisd/clamd.sock, retrying (1) Since this is reported by "ClamAV-clamd", I am assuming this is coming from amavisd.conf. My logic on this is that a grep search for that particular string only shows up in the /etc/amavisd.conf file, when its calling the scanner. Pasted code from file below: @av_scanners = ( ['ClamAV-clamd', \&ask_daemon, ["CONTSCAN {}\n", "/var/spool/amavisd/clamd.sock"], qr/\bOK$/m, qr/\bFOUND$/m, qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ], Best I can determine /var/spool/amavisd/clamd.sock file exists. So, not sure what is causing this or why, or how to fix. Here is /var/spool/amavisd contents: [run]# ls -al /var/spool/amavisd/ total 64 drwxr-x--- 7 amavis amavis 4096 Aug 21 19:10 . drwxr-xr-x. 15 root root 4096 Mar 15 2012 .. srwxr-x--- 1 amavis amavis 0 Aug 21 19:10 amavisd.sock srw-rw-rw- 1 amavis amavis 0 Aug 21 19:10 clamd.sock drwxr-x--- 2 amavis amavis 4096 Aug 21 19:10 db drwxr-x--- 2 amavis amavis 36864 Aug 21 19:50 quarantine drwxr-x--- 2 amavis amavis 4096 Aug 21 09:23 .razor drwx------ 2 amavis amavis 4096 Aug 21 20:42 .spamassassin drwxr-x--- 4 amavis amavis 4096 Aug 21 20:42 tmp Seems to be owned by the right group, I rebooted at 19.10 today hence timestamp date/time. So, my question is, what do I need to do to eliminate this error? How can I chase it down? TIA, Jay

3 4

Fail on start x server
by Edwin Agudelo 25 Aug '16

25 Aug '16

Good Day. Recently buy an lenovo laptop (110 Ideapad 14IBR). Install (with problems) Centos 7, but when start the first time, get the fail screen. Then, I try to start the x server (startx) get the error: FBIOBLANK invalid argument. This laptop have an Intel HD graphics 400 and a Intel Celeron N3060; googling , I concluded that is a fail in the driver, but don’t know how resolve. Please help me. Sorry For my English. Best regards.

5 10

how to find recently installed font packages
by geo.inbox.ignored 25 Aug '16

25 Aug '16

greetings. in an attempt to display correct fonts in firefox instead of squares with binary values, i installed wrong fonts and made things worse. how do i find out what fonts are, as i did not think to make note of what i was adding? tia. -- peace out. CentOS GNU/Linux 6.8 tc,hago. g . =+= Tired of having your microsoft os hacked? Change to Linux os, used by microsoft hackers. =+= in a world with out fences, who needs gates. =+=

7 9

Centos 7 and php 5.5
by Richard B. Pyne 25 Aug '16

25 Aug '16

I am hoping that the wisdom of the group here can at least point me in the right direction. I have a Centos7 server that I need to upgrade php from 5.4 to 5.5. I've tried several tutorials to add the remi repository and enable php55, but I always end up at the same result: Error: Package: php-5.5.38-1.el6.remi.x86_64 (remi-php55) Requires: httpd-mmn = 20051115 Installed: httpd-2.4.6-40.el7.centos.4.x86_64 (@updates) httpd-mmn = 20120211 httpd-mmn = 20120211x8664 httpd-mmn = 20120211-x86-64 Available: httpd-2.4.6-40.el7.centos.x86_64 (base) httpd-mmn = 20120211x8664 httpd-mmn = 20120211-x86-64 httpd-mmn = 20120211 Available: httpd-2.4.6-40.el7.centos.1.x86_64 (updates) httpd-mmn = 20120211x8664 httpd-mmn = 20120211-x86-64 httpd-mmn = 20120211 Error: Package: php-pecl-jsonc-1.3.10-1.el7.remi.5.4.x86_64 (remi) Requires: php(api) = 20100412-64 Removing: php-common-5.4.45-11.el7.remi.x86_64 (@remi) php(api) = 20100412-64 Updated By: php-common-5.5.38-1.el6.remi.x86_64 (remi-php55) php(api) = 20121113-64 Available: php-common-5.4.16-36.el7_1.x86_64 (base) php(api) = 20100412-64 Available: php-common-5.4.16-36.1.el7_2.1.x86_64 (updates) php(api) = 20100412-64 Available: php-common-5.4.16-36.3.el7_2.x86_64 (updates) php(api) = 20100412-64 Available: php-common-5.4.45-10.el7.remi.x86_64 (remi) php(api) = 20100412-64 Available: php-common-5.5.37-1.el6.remi.x86_64 (remi-php55) php(api) = 20121113-64 Error: Package: php-pecl-jsonc-1.3.10-1.el7.remi.5.4.x86_64 (remi) Requires: php(zend-abi) = 20100525-64 Removing: php-common-5.4.45-11.el7.remi.x86_64 (@remi) php(zend-abi) = 20100525-64 Updated By: php-common-5.5.38-1.el6.remi.x86_64 (remi-php55) php(zend-abi) = 20121212-64 Available: php-common-5.4.16-36.el7_1.x86_64 (base) php(zend-abi) = 20100525-64 Available: php-common-5.4.16-36.1.el7_2.1.x86_64 (updates) php(zend-abi) = 20100525-64 Available: php-common-5.4.16-36.3.el7_2.x86_64 (updates) php(zend-abi) = 20100525-64 Available: php-common-5.4.45-10.el7.remi.x86_64 (remi) php(zend-abi) = 20100525-64 Available: php-common-5.5.37-1.el6.remi.x86_64 (remi-php55) php(zend-abi) = 20121212-64 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest If I try --skip-broken, I get: Packages skipped because of dependency problems: gd-last-2.2.3-1.el7.remi.x86_64 from remi libpng12-1.2.50-7.el7_2.x86_64 from updates libzip-last-1.1.3-1.el7.remi.x86_64 from remi php-5.5.38-1.el6.remi.x86_64 from remi-php55 php-cli-5.5.38-1.el6.remi.x86_64 from remi-php55 php-common-5.5.38-1.el6.remi.x86_64 from remi-php55 php-gd-5.5.38-1.el6.remi.x86_64 from remi-php55 php-mbstring-5.5.38-1.el6.remi.x86_64 from remi-php55 php-mcrypt-5.5.38-1.el6.remi.x86_64 from remi-php55 php-mysqlnd-5.5.38-1.el6.remi.x86_64 from remi-php55 php-pdo-5.5.38-1.el6.remi.x86_64 from remi-php55 php-pecl-jsonc-1.3.10-1.el7.remi.5.4.x86_64 from remi php-pecl-zip-1.13.4-1.el6.remi.5.5.x86_64 from remi-php55 php-process-5.5.38-1.el6.remi.x86_64 from remi-php55 php-xml-5.5.38-1.el6.remi.x86_64 from remi-php55 Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for php-common which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of php-common of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude php-common.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of php-common installed, but yum can only see an upgrade for one of those architectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of php-common installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: php-common-5.5.37-1.el6.remi.x86_64 != php-common-5.4.45-11.el7.remi.x86_64

3 5

Stopping NetworkManager doesn't shut down network interfaces
by Joe Smithian 25 Aug '16

25 Aug '16

Hi All, When I stop NetworkManager using the "systemctl stop NetworkManager", it doesn't bring network interfaces down. This behaviour is different than network service in CentOS 5/6. Is this the expected behaviour or a bug or configurable? I expected all networking to be shut down down after stopping NetworkManager. Please comment.

1 1

Re: [CentOS] Gnome weather applet stranded
by adrian＠pa0rda.nl 25 Aug '16

25 Aug '16

Hi, NOAA moved the url on which you can get the data. I use clweather, a little command-line util, I just change the URL in the sourcecode and it worked again. The move happen a couple of weeks ago. The new URL to point the application to is: http://tgftp.nws.noaa.gov/data/observations/metar/decoded/ Good luck & 73, Adrian -- Adri P. van Bloois Antonlaan 104 email: adrian(a)pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax: NONE 52 05'15.77"N 5 4'44.56"E QTH-locater JO 22 OC "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

1 0

CentOS 6 : TigerVNC auto disconnect in version 1.1.0-18
by K Shen 25 Aug '16

25 Aug '16

Hi, When TigerVNC was updated from version 1.1.0-16.el6 to 1.1.0-18.el6, our VNC client kept getting killed after connecting for about 180s. We had to downgrade back to -16 to avoid this issue. We have a setup which allows users to log into our system via a web browser, with TigerVNC as the VNC server, noVNC as the client, and connecting via Websockify. With the update of TigerVNC, the VNC client kept getting killed 180s after logging in -- the user is returned to the login page. We are using CentOS 6.8. We can't figure out what the problem might be -- the update seem to be mostly changes related to x11-server - could this be somehow related? The timing of the logout seems quite precise, as if it is triggered by some timer. Does anyone have any idea what the problem might be? Is this the best place to ask about this? The changes between -16 and -18 seem specific to CentOS (I can't find them on the source at TigerVNC's website), so I assume that is not the place to ask about this issue. Kish Shen

1 0

Transparent HugePages question
by Laurentiu Soica 24 Aug '16

24 Aug '16

Hello, I have a CentOS 7 installation on baremetal with 2 CPUs, 10 cores each and HT enabled, 128 GB RAM. The system has transparent hugetables enabled. cat /sys/kernel/mm/transparent_hugepage/enabled [always] madvise never The system reports anonymous hugepages pages usage and a size of hugepage of 2048Kb cat /proc/meminfo |grep -i hugepages|grep AnonHugePages AnonHugePages: 35491840 kB cat /proc/meminfo |grep -i hugepages|grep Hugepagesize Hugepagesize: 2048 kB Anyway, checking the /proc/<pid>/smaps for each and every process on the system, the KernelPageSize reports 4K pages only. for i in `ls /proc/|egrep '[0-9]+'` ; do grep 'KernelPageSize: ' /proc/$i/smaps; done|grep ' 4 kB'|wc -l 9758 for i in `ls /proc/|egrep '[0-9]+'` ; do grep 'KernelPageSize: ' /proc/$i/smaps; done|grep -v ' 4 kB'|wc -l 0 So it turns out that even is I have the THP enabled the pages still have a size of 4K . Is there any extra setup in order to get 2MB pages ? Thanks, Laurentiu -- Laurentiu Soica

3 4

Broadcom BCM4313 support broken with kernel 2.6.32-573.7.1.el6.centos.plus.x86_64?
by wwp 24 Aug '16

24 Aug '16

Hello, I noticed that with latest kernel (2.6.32-573.7.1.el6.centos.plus.x86_64), my laptop's Wifi doesn't work, whereas with previous kernel (2.6.32-504.30.3.el6.centos.plus.x86_64), it works fine. Is this a known issue or did I miss something new? BTW, `lspci` says: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) Regards, -- wwp

2 2

Problem with CentOS 5.11 virtual machine
by Kaplan, Andrew H. 24 Aug '16

24 Aug '16

Hello -- We completed an installation of CentOS 5.11 32-bit onto a Vmware ESXi 6.0.0 appliance for the purpose of running a legacy application. The hardware in question is a Dell PowerEdge R730xd system. The Vmware tools utility was installed onto the virtual machine, and that initially provided access to the network. Once that was done, patches from the CentOS repository were installed onto the virtual machine, and it was rebooted. The problem we are experiencing is that after that last reboot the network card is not recognized, and there is no connectivity. The error message we are getting is the following: vmxnet3 device eth0 does not seem to be present, delaying initialization. The setup utility within CentOS recognizes the card being present, but the running ifup command, and turning off the NetworkManager daemon did not help. I also went to the /etc/udev/rules.d directory, removed the existing 60-net.rules file, and recreated it with the echo command. A reboot did not populate the file. I then tried creating a 70-persistent-net.rules file, and that did not work either. Running the command ls /sys/class/net listed only the lo interface. So far, the only solution that I can think of is to recreate the virtual machine, install the Vmware Tools utility, and forget about installing any patches. Before I do that, I wanted to know if anyone has any other ideas. Thanks. The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

4 4

CentOS-announce Digest, Vol 138, Issue 8
by centos-announce-request＠centos.org 24 Aug '16

24 Aug '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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-2016:C002 pcs Update (Johnny Hughes) 2. CEBA-2016:1658 CentOS 5 cman BugFix Update (Johnny Hughes) 3. CEBA-2016:1665 CentOS 6 pcs BugFix Update (Johnny Hughes) 4. CEBA-2016:1659 CentOS 6 udev BugFix Update (Johnny Hughes) 5. CEBA-2016:1663 CentOS 6 avahi BugFix Update (Johnny Hughes) 6. CEBA-2016:1667 CentOS 6 cronie BugFix Update (Johnny Hughes) 7. CEBA-2016:1670 CentOS 6 lvm2 BugFix Update (Johnny Hughes) 8. CEBA-2016:1668 CentOS 6 net-snmp BugFix Update (Johnny Hughes) 9. CEBA-2016:1662 CentOS 6 pacemaker BugFix Update (Johnny Hughes) 10. CEBA-2016:1661 CentOS 6 pki-core BugFix Update (Johnny Hughes) 11. CEBA-2016:1669 CentOS 6 samba BugFix Update (Johnny Hughes) 12. CEBA-2016:1666 CentOS 6 tcsh BugFix Update (Johnny Hughes) 13. CESA-2016:1664 Important CentOS 6 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 23 Aug 2016 12:32:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:C002 pcs Update Message-ID: <20160823123246.GA8839(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and BugFix Advisory 2016:C002 Upstream details at : https://bugs.centos.org/view.php?id=9426 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 05e2ee1776051c71336590221267c2a894778919f394ffdb70395f50ccc8b266 pcs-0.9.143-15.el7.centos.x86_64.rpm Source: 8256450c3e7b8233872f0eab8b56c7d3702847d6812912a40118bcbc233df0ba pcs-0.9.143-15.el7.centos.src.rpm Note: This update was done to remove Red Hat branding and replace it with CentOS Branding. -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos at irc.freenode.net ------------------------------ Message: 2 Date: Tue, 23 Aug 2016 18:10:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1658 CentOS 5 cman BugFix Update Message-ID: <20160823181039.GA7711(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1658 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1658.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7e60ccf2518f1d21f09b8dd19edb4130d43fe0442b3d0a9446aa78ec16d62763 cman-2.0.115-124.el5_11.4.i386.rpm 880b26278978f8914f99d5806222bca5330ec8be676c771fafd6006000343678 cman-devel-2.0.115-124.el5_11.4.i386.rpm x86_64: 8110f74a704c1781138723ceb87df217fddca982fea77581689b94a85dfbd514 cman-2.0.115-124.el5_11.4.x86_64.rpm 880b26278978f8914f99d5806222bca5330ec8be676c771fafd6006000343678 cman-devel-2.0.115-124.el5_11.4.i386.rpm c22ca2a878e14a8014f27b25575cf742f5e6b6ef9691b37827efd3a4f7a84765 cman-devel-2.0.115-124.el5_11.4.x86_64.rpm Source: b8dabe80d52a9088ff08f0005ddd82810efd7d3048a2eb9ede5934bae7214053 cman-2.0.115-124.el5_11.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 23 Aug 2016 19:07:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1665 CentOS 6 pcs BugFix Update Message-ID: <20160823190733.GA36032(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1665 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1665.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d3ee157cdb3844dbc90dc1f9ba763d0fc73f645386dcf7bc22d6a1b9f4e6cbde pcs-0.9.148-7.el6.centos.1.i686.rpm x86_64: 18ae6e255e0d2e59900333b568b541bd76cb5e50a3c76c749d14aafcb765f36f pcs-0.9.148-7.el6.centos.1.x86_64.rpm Source: bce3d0d0e8861c0f97f1527b1c71ef81503f23c875339355781918592ddf1b42 pcs-0.9.148-7.el6.centos.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 23 Aug 2016 19:07:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1659 CentOS 6 udev BugFix Update Message-ID: <20160823190747.GA36145(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1659 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1659.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2f54dd9f507ca47e2d2c835d7371a2edd3ac447134ac28fbd6ace5b8870e0cb4 libgudev1-147-2.73.el6_8.1.i686.rpm 53d805b37ec63ce390a4fbdde04160bb1bccf83323be09ce9e4f2b6e842ce440 libgudev1-devel-147-2.73.el6_8.1.i686.rpm f61e8fb204faa4e07e964b26df6867458a9cb9350019132d18149e23301fca7c libudev-147-2.73.el6_8.1.i686.rpm 7d9a0621d471856e4fecd33498ae0294408af9cfbc605059c5c68986a9755876 libudev-devel-147-2.73.el6_8.1.i686.rpm 568b6c9b6d507997db7328ce05a6fb6cd9eede306d8ab663877d70c0cb39c12c udev-147-2.73.el6_8.1.i686.rpm x86_64: 2f54dd9f507ca47e2d2c835d7371a2edd3ac447134ac28fbd6ace5b8870e0cb4 libgudev1-147-2.73.el6_8.1.i686.rpm 63dcc5be85f77f52b4897e00d42e6067346a0ee2e06fc5b413d06e79091f06c9 libgudev1-147-2.73.el6_8.1.x86_64.rpm 53d805b37ec63ce390a4fbdde04160bb1bccf83323be09ce9e4f2b6e842ce440 libgudev1-devel-147-2.73.el6_8.1.i686.rpm 79f1a919847f1ae6d5c6949787aaba20641563e911f5ee92fdf2e3f5542690ef libgudev1-devel-147-2.73.el6_8.1.x86_64.rpm f61e8fb204faa4e07e964b26df6867458a9cb9350019132d18149e23301fca7c libudev-147-2.73.el6_8.1.i686.rpm aa5d64ec6285ac23ef8a560c76151d1f6d75d40f5afb7fab70d122f89596cf51 libudev-147-2.73.el6_8.1.x86_64.rpm 7d9a0621d471856e4fecd33498ae0294408af9cfbc605059c5c68986a9755876 libudev-devel-147-2.73.el6_8.1.i686.rpm b650d142ee383c33b93f28cc1f8bec543b4135e6b1476adb61fd280adf471690 libudev-devel-147-2.73.el6_8.1.x86_64.rpm 47960c08d390f209fc7b328915bb9e2b31aa79eb4f5061eda33ce0cc3fd8542c udev-147-2.73.el6_8.1.x86_64.rpm Source: 6861aef9d2f0e7307dc259466045854ecf68c295b7300bcb992cd0a40d17f649 udev-147-2.73.el6_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Tue, 23 Aug 2016 19:08:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1663 CentOS 6 avahi BugFix Update Message-ID: <20160823190817.GA36943(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1663 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1663.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2da08ce1a4e3ab757f29c482bc187f630bd756c987d9c7d084b9778e7a4f7277 avahi-0.6.25-15.el6_8.1.i686.rpm ab8a4cc31915ce46c2fad566a96925cd8a174bd424db6f3d2df2afa40019c040 avahi-autoipd-0.6.25-15.el6_8.1.i686.rpm 1c86318ed404bb778352799f08b2fb1a50ef3561e58bb5100897ac8158c8f3a7 avahi-compat-howl-0.6.25-15.el6_8.1.i686.rpm ae6819eda67a34d43a8288ad63bfcf4d03ec9cf7027d3bd73433911115e6e6c1 avahi-compat-howl-devel-0.6.25-15.el6_8.1.i686.rpm 807cfb26768ecaf5a13052291228390fd36a09b02bd60281e6fbe06e3c5ffeed avahi-compat-libdns_sd-0.6.25-15.el6_8.1.i686.rpm b1dd4656a6fe62fc5c64cec1bccb42c670e10072c82d118c2d30efd11db47140 avahi-compat-libdns_sd-devel-0.6.25-15.el6_8.1.i686.rpm 45456f586f1f90142bf2d50e0da606fc0502fe9c3d32e68cd8822977e30d3f69 avahi-devel-0.6.25-15.el6_8.1.i686.rpm c2e05acac8896194405e5aedf5623a1a8e5340df7678230e9add61167cfd143a avahi-dnsconfd-0.6.25-15.el6_8.1.i686.rpm 00d291eefe76b370b0d34550735e9bc25b52419ba2b4ec0c5a5ef11c5f10a0df avahi-glib-0.6.25-15.el6_8.1.i686.rpm 19129941ada18e1e8429b33f092aaa2ff3d13e1944adfe823f5619e248e92323 avahi-glib-devel-0.6.25-15.el6_8.1.i686.rpm fecc678248c6dd23e2b92673e6a1ecd7eb7658be3c728b8fdb0aa89ee6098bb9 avahi-gobject-0.6.25-15.el6_8.1.i686.rpm b8ee777883f5c63df34f71a29c11fe08d1a71f6d1374886ff293bb34deafeda4 avahi-gobject-devel-0.6.25-15.el6_8.1.i686.rpm 926c94db33c0b9cd9bdb0a40a6afd24b88a78c69f03ddbe1cac4bca4ee4227d3 avahi-libs-0.6.25-15.el6_8.1.i686.rpm d1e76b17b6ad25d32c3e0b881f40d0970b61819cbed2428d4aae402d3a30b2fc avahi-qt3-0.6.25-15.el6_8.1.i686.rpm 86e409cac76fc3899c8a25042d32456db54cfd6f2577c658d8e7acb39e46bfef avahi-qt3-devel-0.6.25-15.el6_8.1.i686.rpm 06d9b6affaafe71a84c2a965c4e76104ad85183f905f54edf7f356cd1dc969c3 avahi-qt4-0.6.25-15.el6_8.1.i686.rpm 410bb827ac0a5504bcb818d05498058993a39793ab252350f6646478a97146e6 avahi-qt4-devel-0.6.25-15.el6_8.1.i686.rpm 9f3b0f07c426a12f6f6fa67f85afde219f2469fa4d816247cec42b8e4eb034fd avahi-tools-0.6.25-15.el6_8.1.i686.rpm 90f580cd8656864c01d480e51adce74a5faf139ad756449a77e5cf40eeda6ca1 avahi-ui-0.6.25-15.el6_8.1.i686.rpm 389e2ab4ed01c19835903eda8f27a763e02ebb0a03f2874cd6a19395ee3695d1 avahi-ui-devel-0.6.25-15.el6_8.1.i686.rpm b976b58fac5dd7ab25f2b5056a345736d85203d92cf9a7a8faa66852ecc94d9f avahi-ui-tools-0.6.25-15.el6_8.1.i686.rpm x86_64: 2da08ce1a4e3ab757f29c482bc187f630bd756c987d9c7d084b9778e7a4f7277 avahi-0.6.25-15.el6_8.1.i686.rpm 4b0801b77db3a557dc38e91b5efbc8843d13c6f66f10da4b1f4ac666c786920c avahi-0.6.25-15.el6_8.1.x86_64.rpm 0a485805a8eb11f1886625bcb161466cf42f0a62ad0e2b63111b22f1e606668b avahi-autoipd-0.6.25-15.el6_8.1.x86_64.rpm 1c86318ed404bb778352799f08b2fb1a50ef3561e58bb5100897ac8158c8f3a7 avahi-compat-howl-0.6.25-15.el6_8.1.i686.rpm 98e884c58a3752480472a56bd3602f4da4197d0e2cb4aa0cd51b20d6a1c43694 avahi-compat-howl-0.6.25-15.el6_8.1.x86_64.rpm ae6819eda67a34d43a8288ad63bfcf4d03ec9cf7027d3bd73433911115e6e6c1 avahi-compat-howl-devel-0.6.25-15.el6_8.1.i686.rpm 3f298b5c53b1e8ac637533db5a8951710095593e6178ab6ad1d1250d46c3ea55 avahi-compat-howl-devel-0.6.25-15.el6_8.1.x86_64.rpm 807cfb26768ecaf5a13052291228390fd36a09b02bd60281e6fbe06e3c5ffeed avahi-compat-libdns_sd-0.6.25-15.el6_8.1.i686.rpm 1591f9fa5a8337ebfd4ef10f95211d18835972ba2c309d781e3d2597fae111b8 avahi-compat-libdns_sd-0.6.25-15.el6_8.1.x86_64.rpm b1dd4656a6fe62fc5c64cec1bccb42c670e10072c82d118c2d30efd11db47140 avahi-compat-libdns_sd-devel-0.6.25-15.el6_8.1.i686.rpm a533b5d4d5a948761acec760e45f6c2f5d7f11385bf11fe2725ac8a1c60bf05e avahi-compat-libdns_sd-devel-0.6.25-15.el6_8.1.x86_64.rpm 45456f586f1f90142bf2d50e0da606fc0502fe9c3d32e68cd8822977e30d3f69 avahi-devel-0.6.25-15.el6_8.1.i686.rpm ad16fbf059b2fc3992bd2a5b08cae6d83db0896c86a9229d301c962b19868e52 avahi-devel-0.6.25-15.el6_8.1.x86_64.rpm 8f12a25451d122354fd1451223afd9d66e4788ba63ebf0c36a28a004d1e21be1 avahi-dnsconfd-0.6.25-15.el6_8.1.x86_64.rpm 00d291eefe76b370b0d34550735e9bc25b52419ba2b4ec0c5a5ef11c5f10a0df avahi-glib-0.6.25-15.el6_8.1.i686.rpm d73949c9b1058c0620a9f475d32c9ee4aff39fc805a71f1755160a3b4949cdde avahi-glib-0.6.25-15.el6_8.1.x86_64.rpm 19129941ada18e1e8429b33f092aaa2ff3d13e1944adfe823f5619e248e92323 avahi-glib-devel-0.6.25-15.el6_8.1.i686.rpm 7dc370beee2ed4f5a3e71d4a1a7ecd785131420773ef2cb25923530be37e21ec avahi-glib-devel-0.6.25-15.el6_8.1.x86_64.rpm fecc678248c6dd23e2b92673e6a1ecd7eb7658be3c728b8fdb0aa89ee6098bb9 avahi-gobject-0.6.25-15.el6_8.1.i686.rpm c051aa6b6271b0ae1989a5d3b9337b557d33bb29fb6f1935308189a428caec16 avahi-gobject-0.6.25-15.el6_8.1.x86_64.rpm b8ee777883f5c63df34f71a29c11fe08d1a71f6d1374886ff293bb34deafeda4 avahi-gobject-devel-0.6.25-15.el6_8.1.i686.rpm b3468c658f0a806610279320734eecb08985b5e2f553ad1e2bac4e0a52308fdd avahi-gobject-devel-0.6.25-15.el6_8.1.x86_64.rpm 926c94db33c0b9cd9bdb0a40a6afd24b88a78c69f03ddbe1cac4bca4ee4227d3 avahi-libs-0.6.25-15.el6_8.1.i686.rpm 589cf55426eefdf913e642ef143d02f35feca5833e05a4a22fb668479f511a7c avahi-libs-0.6.25-15.el6_8.1.x86_64.rpm d1e76b17b6ad25d32c3e0b881f40d0970b61819cbed2428d4aae402d3a30b2fc avahi-qt3-0.6.25-15.el6_8.1.i686.rpm fc898bb00b4400d44b60a86e46ca77a5bc52920f606c508bde151660b18e7c7c avahi-qt3-0.6.25-15.el6_8.1.x86_64.rpm 86e409cac76fc3899c8a25042d32456db54cfd6f2577c658d8e7acb39e46bfef avahi-qt3-devel-0.6.25-15.el6_8.1.i686.rpm 4a2a73611398e7e283bff835a4dcb95d9202024aaa72c8e9ec7feaf6f360a7ab avahi-qt3-devel-0.6.25-15.el6_8.1.x86_64.rpm 06d9b6affaafe71a84c2a965c4e76104ad85183f905f54edf7f356cd1dc969c3 avahi-qt4-0.6.25-15.el6_8.1.i686.rpm 179b6d176f064a9d4ccab63ba3bf8b7b8b987912ac0cbe16b36a374f3e93347c avahi-qt4-0.6.25-15.el6_8.1.x86_64.rpm 410bb827ac0a5504bcb818d05498058993a39793ab252350f6646478a97146e6 avahi-qt4-devel-0.6.25-15.el6_8.1.i686.rpm 304150a35d63157090c7ea08ca2407a52b7fe3cf54e839fe01322c33ea3bfd7e avahi-qt4-devel-0.6.25-15.el6_8.1.x86_64.rpm a3660e3a78c987334f04cd3230e3f07ac6a23f9f58704f80b025e7dffafdea3e avahi-tools-0.6.25-15.el6_8.1.x86_64.rpm 90f580cd8656864c01d480e51adce74a5faf139ad756449a77e5cf40eeda6ca1 avahi-ui-0.6.25-15.el6_8.1.i686.rpm ab3e69ae865007d22ba8f697ed1ccdaff2b5c12295d850fbe9b705b1eab43d6a avahi-ui-0.6.25-15.el6_8.1.x86_64.rpm 389e2ab4ed01c19835903eda8f27a763e02ebb0a03f2874cd6a19395ee3695d1 avahi-ui-devel-0.6.25-15.el6_8.1.i686.rpm 9c6fd42c95543adcd1a2c4c3fed3397d39463226848e9836a9c3808fa77b8301 avahi-ui-devel-0.6.25-15.el6_8.1.x86_64.rpm b4f8d55f6e1e3b7aedb85b71453e7ac29b046692362aef3b1c0e57f0e0d5ec1c avahi-ui-tools-0.6.25-15.el6_8.1.x86_64.rpm Source: 41c2b606ed52dc56b3c8ed17026c225987518cd29da0dfb5e2e49a2a5cf7f8f5 avahi-0.6.25-15.el6_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Tue, 23 Aug 2016 19:08:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1667 CentOS 6 cronie BugFix Update Message-ID: <20160823190841.GA37200(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1667 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1667.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0711d1d646ba76fa488cf72f4a952abbb26440ddfb23df9ad6a3b6be2cb341b0 cronie-1.4.4-16.el6_8.2.i686.rpm d431438e49c24edcbea7c890218b57c64817c2bb8705584885bbed08260516bc cronie-anacron-1.4.4-16.el6_8.2.i686.rpm 9fc4e616a0f1c0253d9df1bca7cf2244bf4e06f432948086c333fe34279a824e cronie-noanacron-1.4.4-16.el6_8.2.i686.rpm x86_64: ed3509d74350050ac6b5b6a8be909e3ed3f1497393eba9319ad4b44165ed0ce8 cronie-1.4.4-16.el6_8.2.x86_64.rpm 96aa4dc6614b0c0ffb7c5156df4cb90a89b155c55dbdab41fb566834df91a9cb cronie-anacron-1.4.4-16.el6_8.2.x86_64.rpm d86bf494bc634e1c714eb0d91dae43a74ad0f718659d61e176a33c60f9ddcd9b cronie-noanacron-1.4.4-16.el6_8.2.x86_64.rpm Source: e96f13ca4ae8900d9dddc3c7dcf65d84c2c5a03d03ae77562cbd73e1183f7d8d cronie-1.4.4-16.el6_8.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Tue, 23 Aug 2016 19:09:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1670 CentOS 6 lvm2 BugFix Update Message-ID: <20160823190907.GA37669(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1670 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1670.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6150d8a5c016f0fb4e8ef2717f9e36e5740b3473c52b05b3a62a8d91425ef291 cmirror-2.02.143-7.el6_8.1.i686.rpm d10a39ff9a7a0cefa39611147e3c76e90c0835a2850226be7e1bf989b51c184f device-mapper-1.02.117-7.el6_8.1.i686.rpm b9efcdd3d4416c087e1f01cfb522167961eaed59d3d6fb6358e269526add370f device-mapper-devel-1.02.117-7.el6_8.1.i686.rpm ecdf03ea08b172a04736ac92121a599093d993d619a8f820c08a01061bb85b52 device-mapper-event-1.02.117-7.el6_8.1.i686.rpm c59e4aaf4a2de0f5d80f5d581b83d1847822ced2895eff33af53b2fa9830ee09 device-mapper-event-devel-1.02.117-7.el6_8.1.i686.rpm f21ab80068e583b520bb1fcb0fdc9276a464b0b91c945a82070a869cac88f34d device-mapper-event-libs-1.02.117-7.el6_8.1.i686.rpm a17b2eb4084ed4fa96e6767c67ea48e4138a3f189607437773211d2315ae5be5 device-mapper-libs-1.02.117-7.el6_8.1.i686.rpm 02344e868bd2ce5e0cc18d3e416bb042b51263a693fe09c622a1d129bbe11afb lvm2-2.02.143-7.el6_8.1.i686.rpm 6a38597f4bb1322dcc19e09b8e93c1d743f9e73f56830aa638a87040265cf670 lvm2-cluster-2.02.143-7.el6_8.1.i686.rpm 4edf04ed800077a26a1b65724bae277a86da555199f11f0e79b71fb44aaf3857 lvm2-devel-2.02.143-7.el6_8.1.i686.rpm 834f1fac99a7912ca1d3f45d166b0caa3abb961cf3c64632420b151b8eaef011 lvm2-libs-2.02.143-7.el6_8.1.i686.rpm x86_64: 444f077702ba4efa2d8c0dacf95cf55969dbf4da66539c1b440a5bfa228b0a09 cmirror-2.02.143-7.el6_8.1.x86_64.rpm 92e94a9bfe2ba14b21a8bfce15a54824134df63634c848830909939aafb02599 device-mapper-1.02.117-7.el6_8.1.x86_64.rpm b9efcdd3d4416c087e1f01cfb522167961eaed59d3d6fb6358e269526add370f device-mapper-devel-1.02.117-7.el6_8.1.i686.rpm 6f430ccb3160c6fd696547851b1d36caf7ff3d6a24d46293f8a68a83527f2369 device-mapper-devel-1.02.117-7.el6_8.1.x86_64.rpm f3ebc0902a938d92a016008013484a6ff8a80f28dc45c0ec26c567de33cb5864 device-mapper-event-1.02.117-7.el6_8.1.x86_64.rpm c59e4aaf4a2de0f5d80f5d581b83d1847822ced2895eff33af53b2fa9830ee09 device-mapper-event-devel-1.02.117-7.el6_8.1.i686.rpm dbd095e2b22a8b0b86ca9937c44ad5f21ecedc832f5aafb10a411f88361e18ff device-mapper-event-devel-1.02.117-7.el6_8.1.x86_64.rpm f21ab80068e583b520bb1fcb0fdc9276a464b0b91c945a82070a869cac88f34d device-mapper-event-libs-1.02.117-7.el6_8.1.i686.rpm 7fa9aff8cded473418a86aa9c0a60043a0b8393111651423cd57c28cee3aa595 device-mapper-event-libs-1.02.117-7.el6_8.1.x86_64.rpm a17b2eb4084ed4fa96e6767c67ea48e4138a3f189607437773211d2315ae5be5 device-mapper-libs-1.02.117-7.el6_8.1.i686.rpm 3da97c7a9f2203d55957fb07a41fa8468fd28add0ebf40849381053a2e07bbf9 device-mapper-libs-1.02.117-7.el6_8.1.x86_64.rpm 0c8cd71d9af57edc1a838ff1a856e5dd43468b3d1ab2eb152b79eedecef151f7 lvm2-2.02.143-7.el6_8.1.x86_64.rpm 0f83b3e7920599547ca03490bd6ae2baefa0eb3d6c100b84d557e05188460a21 lvm2-cluster-2.02.143-7.el6_8.1.x86_64.rpm 4edf04ed800077a26a1b65724bae277a86da555199f11f0e79b71fb44aaf3857 lvm2-devel-2.02.143-7.el6_8.1.i686.rpm 61a8545887b866c24e9f06bc830c409795d3f1faaa04dd36c836d53337b14fed lvm2-devel-2.02.143-7.el6_8.1.x86_64.rpm 834f1fac99a7912ca1d3f45d166b0caa3abb961cf3c64632420b151b8eaef011 lvm2-libs-2.02.143-7.el6_8.1.i686.rpm 56bd8e13b2da158d071ca41e4bbf0e0a27be8502be823bed6cc48c1595cf9c72 lvm2-libs-2.02.143-7.el6_8.1.x86_64.rpm Source: b68e65ce455e8c424d4fefe4bf0cd556e3b0f507a67935056c637540177451aa lvm2-2.02.143-7.el6_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 8 Date: Tue, 23 Aug 2016 19:09:27 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1668 CentOS 6 net-snmp BugFix Update Message-ID: <20160823190927.GA38013(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1668 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1668.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 708db5b3290b9dc00c99a87d77d8832e23c596a24860c58ffe0e631e0fd7f671 net-snmp-5.5-57.el6_8.1.i686.rpm 5c2541c1684739843682340dc45ca29003af4403cde4affb3558a916a61da350 net-snmp-devel-5.5-57.el6_8.1.i686.rpm dbd5198e966121595952d90d9023e0a875b84de1280e9039bb9bfb7053c4be83 net-snmp-libs-5.5-57.el6_8.1.i686.rpm 99f909a52844fc7779d67246067eeb3fa31cc4f195d613c546492a9b96d46287 net-snmp-perl-5.5-57.el6_8.1.i686.rpm 213aa33f202ceed83aa0c7170a7ea5f3117bb4a92b36643bb91f95aafb5ef739 net-snmp-python-5.5-57.el6_8.1.i686.rpm fa8d7389e6334d703464a98cd74b12c90f414573ca66ad88bc397b24f5db4b21 net-snmp-utils-5.5-57.el6_8.1.i686.rpm x86_64: 414294e1ef7eeb7d4e2fdcffc7da2a4b1c6ba12c0ed852e2afe1d5c1c779050a net-snmp-5.5-57.el6_8.1.x86_64.rpm 5c2541c1684739843682340dc45ca29003af4403cde4affb3558a916a61da350 net-snmp-devel-5.5-57.el6_8.1.i686.rpm 3532ee6d3d1c25039fd1e7220c54b25699c21037e1bd1bea9b2e58463b0de298 net-snmp-devel-5.5-57.el6_8.1.x86_64.rpm dbd5198e966121595952d90d9023e0a875b84de1280e9039bb9bfb7053c4be83 net-snmp-libs-5.5-57.el6_8.1.i686.rpm 1a5a75a63c4ec891f31fed0dadfcde5a02a618a8e2cc8f9e5f17d3216ca6ddef net-snmp-libs-5.5-57.el6_8.1.x86_64.rpm d2570a9238fe6e2935ed2412effd2553f37bbcb7328f31c0ed733120758f060a net-snmp-perl-5.5-57.el6_8.1.x86_64.rpm 6c42b0c2a0ad0ce208d7a080ef3716102205d4fa52d4ecc11af00f0540e3b39c net-snmp-python-5.5-57.el6_8.1.x86_64.rpm 56e420d5e62e58bf8d30e6020d4f2a23429f4abd6db66389448a5442ff40daa6 net-snmp-utils-5.5-57.el6_8.1.x86_64.rpm Source: 965336bf8507f40ebb921cf4e715a041fcac654ee395af86902241d4d98ad8e8 net-snmp-5.5-57.el6_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 9 Date: Tue, 23 Aug 2016 19:09:52 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1662 CentOS 6 pacemaker BugFix Update Message-ID: <20160823190952.GA38408(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1662 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1662.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 09ca910e5ca10c0dd44f8209dab24ed755f572bcde9fe74aea197aeda6d55013 pacemaker-1.1.14-8.el6_8.1.i686.rpm 0d8fbacd0ec152b04af9ff89b2d1977d0fdd0f27bb091493f1642f9f8e4b97fc pacemaker-cli-1.1.14-8.el6_8.1.i686.rpm 7e32a981ffd193c1b6af8d1dbc7b9e01d5555a6bcffadce5270fde59ce51d485 pacemaker-cluster-libs-1.1.14-8.el6_8.1.i686.rpm 2f45bc3706da586817ccf19b7b5ceaaaf583dba5a0cb0216ee8a50772592b791 pacemaker-cts-1.1.14-8.el6_8.1.i686.rpm e307d0b8cd9329049dc8b1e90811d7a6d74692015328a748ca19d4ac7578343d pacemaker-doc-1.1.14-8.el6_8.1.i686.rpm e109d461e62f34be1324e1a241171699f2823f9b17012bd7e942474a35c88821 pacemaker-libs-1.1.14-8.el6_8.1.i686.rpm a74dd6e9849e9990738926729dbd492342b9400f922f9188567d02206a0c3700 pacemaker-libs-devel-1.1.14-8.el6_8.1.i686.rpm 9a94ee7fdd872e33d6d6a1be032a330cba53da98d71e9a7369aa0c2d6884c060 pacemaker-remote-1.1.14-8.el6_8.1.i686.rpm x86_64: 1fbf3e6a71d9aa0cee058af53753e69b40db7e249764154aea9fdc9be5a39546 pacemaker-1.1.14-8.el6_8.1.x86_64.rpm 309c3fe253f1b5ef60702ba33786cb8d190365da4d1cdbdf7ba234462c5e98d0 pacemaker-cli-1.1.14-8.el6_8.1.x86_64.rpm 7e32a981ffd193c1b6af8d1dbc7b9e01d5555a6bcffadce5270fde59ce51d485 pacemaker-cluster-libs-1.1.14-8.el6_8.1.i686.rpm f78487389e804b79e45b13b4323bc0ef327214a2c6170fc9d6e7ee652150088b pacemaker-cluster-libs-1.1.14-8.el6_8.1.x86_64.rpm e6d27d450b01dbb59989d04676858b799ac4697579e2361b04959be2644bc5ea pacemaker-cts-1.1.14-8.el6_8.1.x86_64.rpm 4ece77b4a4d86676b9fb73f0e7c9d33f76b16bf7aded93c3bc0380a36290910e pacemaker-doc-1.1.14-8.el6_8.1.x86_64.rpm e109d461e62f34be1324e1a241171699f2823f9b17012bd7e942474a35c88821 pacemaker-libs-1.1.14-8.el6_8.1.i686.rpm a578a9536fc844a6d10a12d84588337efd9eccaabf0d61fb14dd3c8785344b70 pacemaker-libs-1.1.14-8.el6_8.1.x86_64.rpm a74dd6e9849e9990738926729dbd492342b9400f922f9188567d02206a0c3700 pacemaker-libs-devel-1.1.14-8.el6_8.1.i686.rpm afbe7a2a5bd47d5e211c4e47993a8c0ea28f5e8ef65de2ca396b5f342142d1b3 pacemaker-libs-devel-1.1.14-8.el6_8.1.x86_64.rpm 377425b9e405ef21db256448c14e9c373ff7498bbd5c2e0befab53b949bb8023 pacemaker-remote-1.1.14-8.el6_8.1.x86_64.rpm Source: 2d4a2278725a9f6e39c9885f850d8e59a827657a72822d6ea6901a4b4aa6cec6 pacemaker-1.1.14-8.el6_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 10 Date: Tue, 23 Aug 2016 19:10:14 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1661 CentOS 6 pki-core BugFix Update Message-ID: <20160823191014.GA38882(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1661 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1661.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 05d3cf577d439c3558c77a89b029f56633b4734c8fc43612a3d14f23c232c9b3 pki-ca-9.0.3-50.el6_8.noarch.rpm 62a15c868c1d9cbcce42e8b47196a244f0e4df2919ed5d7a1711f847c552e81b pki-common-9.0.3-50.el6_8.noarch.rpm e5725a415fdcb3791ffb7b489a1d6ae187926c0f26c8ad7d2b6836328cf3e487 pki-common-javadoc-9.0.3-50.el6_8.noarch.rpm fc8731b7149b0f4982ba60be4010d4d220a56e57418633578ac3af15e979ada8 pki-java-tools-9.0.3-50.el6_8.noarch.rpm cfd7c339491cac202b2313229bcd166c8b6bc2154005cc6a4b7014c0fc817027 pki-java-tools-javadoc-9.0.3-50.el6_8.noarch.rpm ba42f5d7c73a9779d2e9f2f3135db2a2e01cc5cc9e3d3a441a6f5661445f08f7 pki-native-tools-9.0.3-50.el6_8.i686.rpm 7561ff0a658954b2600fcf980b7dbbd4213c25543e84ab82695245f944724fc4 pki-selinux-9.0.3-50.el6_8.noarch.rpm 0570298fe46d2fff7de28bbce04a4e205951a9367d0c47348542c74e1a564f67 pki-setup-9.0.3-50.el6_8.noarch.rpm db69ce03afc2e41155751a52a526a6b79c6600043d7cdaa065aff4a7ba3af8bb pki-silent-9.0.3-50.el6_8.noarch.rpm 8e90e90ee15e81bb4d691b8a008895af42dc5bee8d0b4b915c978eeaca1bea4f pki-symkey-9.0.3-50.el6_8.i686.rpm 4141ee0d9d8b8163eb6638e49a91d830becd55a265ebe29d2081d88ba8f3bb74 pki-util-9.0.3-50.el6_8.noarch.rpm 0433819d7aaa05237f18a441cec9c2ca0c43bcb2f08157f6212f938ecc99069f pki-util-javadoc-9.0.3-50.el6_8.noarch.rpm x86_64: 05d3cf577d439c3558c77a89b029f56633b4734c8fc43612a3d14f23c232c9b3 pki-ca-9.0.3-50.el6_8.noarch.rpm 62a15c868c1d9cbcce42e8b47196a244f0e4df2919ed5d7a1711f847c552e81b pki-common-9.0.3-50.el6_8.noarch.rpm e5725a415fdcb3791ffb7b489a1d6ae187926c0f26c8ad7d2b6836328cf3e487 pki-common-javadoc-9.0.3-50.el6_8.noarch.rpm fc8731b7149b0f4982ba60be4010d4d220a56e57418633578ac3af15e979ada8 pki-java-tools-9.0.3-50.el6_8.noarch.rpm cfd7c339491cac202b2313229bcd166c8b6bc2154005cc6a4b7014c0fc817027 pki-java-tools-javadoc-9.0.3-50.el6_8.noarch.rpm 10071a394ebce5a808636e9e1fe5be762993c25a5e21e3e7ba47437efe9123bb pki-native-tools-9.0.3-50.el6_8.x86_64.rpm 7561ff0a658954b2600fcf980b7dbbd4213c25543e84ab82695245f944724fc4 pki-selinux-9.0.3-50.el6_8.noarch.rpm 0570298fe46d2fff7de28bbce04a4e205951a9367d0c47348542c74e1a564f67 pki-setup-9.0.3-50.el6_8.noarch.rpm db69ce03afc2e41155751a52a526a6b79c6600043d7cdaa065aff4a7ba3af8bb pki-silent-9.0.3-50.el6_8.noarch.rpm d6f339dcae8da606a403148e56cf728e348155500543d6d7e565f37128132c92 pki-symkey-9.0.3-50.el6_8.x86_64.rpm 4141ee0d9d8b8163eb6638e49a91d830becd55a265ebe29d2081d88ba8f3bb74 pki-util-9.0.3-50.el6_8.noarch.rpm 0433819d7aaa05237f18a441cec9c2ca0c43bcb2f08157f6212f938ecc99069f pki-util-javadoc-9.0.3-50.el6_8.noarch.rpm Source: 943e5f84b784b09e1da326eb7e8c9f7194a154f2c6e5425b1672f48c73d2b704 pki-core-9.0.3-50.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 11 Date: Tue, 23 Aug 2016 19:10:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1669 CentOS 6 samba BugFix Update Message-ID: <20160823191053.GA39439(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1669 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1669.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6631a16567d567a5f7dfadd4b04c0e405030129bfa0e57270b7eaee0538c84b8 libsmbclient-3.6.23-36.el6_8.i686.rpm 7125fea3ffcdecfe56bcbdb68d3392ff7ea84aa682064eca29233763d30e7c94 libsmbclient-devel-3.6.23-36.el6_8.i686.rpm 2f91c5e1b5fd38eb900fd59f96e1ef9ce035eace3142cc28155f8172bb8c9f9c samba-3.6.23-36.el6_8.i686.rpm ba96439258a473663e499068fd1fb714e66d7e9f868f825fb7dc602b0f11814d samba-client-3.6.23-36.el6_8.i686.rpm afd0bb78b22a1a0bf925fd3542aff81a64760dd594aeb8d81a32f62ce7f35d15 samba-common-3.6.23-36.el6_8.i686.rpm 850d4eafad645d0140f7cfe54f4479d4d747c5e90c55e4e5cc05607f3b7d130b samba-doc-3.6.23-36.el6_8.i686.rpm a975284f77d86f9828ae276aa4d00479349d412de42c8eee4118a0e08b007a2e samba-domainjoin-gui-3.6.23-36.el6_8.i686.rpm eb113138cd656f40b2ab004799d357c89a1471d6894659894574b5606963fb83 samba-swat-3.6.23-36.el6_8.i686.rpm 53bb93615d8452b8446da327be0ac8177704e7aed76f0953b9a77709750bf164 samba-winbind-3.6.23-36.el6_8.i686.rpm c84d03b32de19c5185717fc921022ae905326aa62f478a2e926d369644fa90ed samba-winbind-clients-3.6.23-36.el6_8.i686.rpm 8b995e094fcec99b668cbf6d61687550ab39d31425b80cde58095d3e7a142e8b samba-winbind-devel-3.6.23-36.el6_8.i686.rpm 5b9116ebf28e9de1b464554ba81ed9272d55bd171eb1dc2f16365354b294f532 samba-winbind-krb5-locator-3.6.23-36.el6_8.i686.rpm x86_64: 6631a16567d567a5f7dfadd4b04c0e405030129bfa0e57270b7eaee0538c84b8 libsmbclient-3.6.23-36.el6_8.i686.rpm 08a090af59252ffa38d6e3aa004bd4c983bb1b658daddcc00cbebb88d872a676 libsmbclient-3.6.23-36.el6_8.x86_64.rpm 7125fea3ffcdecfe56bcbdb68d3392ff7ea84aa682064eca29233763d30e7c94 libsmbclient-devel-3.6.23-36.el6_8.i686.rpm b21e665deefcebbf8f0d9bed51a224026befc2aa323be84ac8b79edc88a26b36 libsmbclient-devel-3.6.23-36.el6_8.x86_64.rpm 69ec12282fbfe8183c472429206fa14b58747d6dc06f03f6525a8282066f1ef6 samba-3.6.23-36.el6_8.x86_64.rpm 4690d95ff2d72c485416eef26e23f234129ebdb6e550cb00d1db40c71520a68e samba-client-3.6.23-36.el6_8.x86_64.rpm afd0bb78b22a1a0bf925fd3542aff81a64760dd594aeb8d81a32f62ce7f35d15 samba-common-3.6.23-36.el6_8.i686.rpm f94521e9972533a209a7ec7d19a1bcfc259e76aa63359365917bef1da58f5094 samba-common-3.6.23-36.el6_8.x86_64.rpm 35a9e1d4fc8355d77fbbc6d3a2bb42c4c451e8e77aef0f7f62b675d88c71fda2 samba-doc-3.6.23-36.el6_8.x86_64.rpm 8bf6db693cc5a4d8603c93454b53dca7284e658c83b8c3457aa630fa86e7a1ad samba-domainjoin-gui-3.6.23-36.el6_8.x86_64.rpm c60909b3bd51e66aa120220774c244648280391ea844b23703ee3b279e1434c9 samba-glusterfs-3.6.23-36.el6_8.x86_64.rpm 285a46465f733f5a1319d0cf89fae11df1f05a194e8315a939a7448d6190d7f1 samba-swat-3.6.23-36.el6_8.x86_64.rpm 693b25063c4add60f4fd17ce8a37ebe6cc5a4d45939e894696a3e6fe6a94001b samba-winbind-3.6.23-36.el6_8.x86_64.rpm c84d03b32de19c5185717fc921022ae905326aa62f478a2e926d369644fa90ed samba-winbind-clients-3.6.23-36.el6_8.i686.rpm 238e17824adb3fbbeeac9d0d2e2cdd5650371b2ff77c5612e1b8a2733312beb6 samba-winbind-clients-3.6.23-36.el6_8.x86_64.rpm 8b995e094fcec99b668cbf6d61687550ab39d31425b80cde58095d3e7a142e8b samba-winbind-devel-3.6.23-36.el6_8.i686.rpm 8bee8eea039b4296dcadb09666b672746268baee0b414d47d0a77bc2b1b0d5b8 samba-winbind-devel-3.6.23-36.el6_8.x86_64.rpm cad79cadce0a64a033914dfc781c997323db6f259ad536f8b2837633e94e4921 samba-winbind-krb5-locator-3.6.23-36.el6_8.x86_64.rpm Source: aa56d9e0948215d6cd356ea6eaecfe503add4b274aba46d21b25319ba2682ef3 samba-3.6.23-36.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 12 Date: Tue, 23 Aug 2016 19:11:13 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1666 CentOS 6 tcsh BugFix Update Message-ID: <20160823191113.GA39658(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1666 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1666.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 95a733f6d235e9e1eac6a235851f5acfc1dae08a112cd5e186b16bd17f8596d6 tcsh-6.17-35.el6_8.1.i686.rpm x86_64: f0816398c41d44b6c537c6eeab2e948329c86575456323f46a8ad4b8853cb440 tcsh-6.17-35.el6_8.1.x86_64.rpm Source: 675b771e9d517926e6a314f18f1d17ffad9f60e30163975a4436850a23be530b tcsh-6.17-35.el6_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 13 Date: Tue, 23 Aug 2016 20:59:58 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1664 Important CentOS 6 kernel Security Update Message-ID: <20160823205958.GA2581(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1664 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1664.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: da36d88f406d58de35b6e77fdf46ec48e8dc64f02c23d8b17471cb8f8fda2eb2 kernel-2.6.32-642.4.2.el6.i686.rpm 25072df3d8420ac35312d69ce6fac6b78f438fd5ea2e1d97bb166f782dba3fe0 kernel-abi-whitelists-2.6.32-642.4.2.el6.noarch.rpm 68621e2fd2ea1bbb8c99cc1cacc0a852a12907db8838d3402d996cc9c4056f12 kernel-debug-2.6.32-642.4.2.el6.i686.rpm d0d83d507c6828bf029b64624fbc293346f3fe80413f5cfc043ca0ba47366954 kernel-debug-devel-2.6.32-642.4.2.el6.i686.rpm 00808bae55a4ccc8b3d4bd78e576e4abe801fda3cd32ef7c1a52f5b2108178fe kernel-devel-2.6.32-642.4.2.el6.i686.rpm a2b8e7402c375a214974398310b3337e1b6bfd75732048436b0be84358fc0151 kernel-doc-2.6.32-642.4.2.el6.noarch.rpm 609b1081724287d046575cd63a1e7cb73300c6e7ee14c78d1ffc9ed2f5727e6c kernel-firmware-2.6.32-642.4.2.el6.noarch.rpm c3343b776cd3aeab4c9e6902484926a5d01512eca5aa382d07698acc075864a8 kernel-headers-2.6.32-642.4.2.el6.i686.rpm db467d475f5277fb46c1c12614da896e8bd0a86a8577991762ec7bba6b4c35c7 perf-2.6.32-642.4.2.el6.i686.rpm fed2a64b6163a61b4b43b0a671b7585379db095add209db0990f7f2606f69ced python-perf-2.6.32-642.4.2.el6.i686.rpm x86_64: 46934b3837275e20808bb0f68dc62e8f077d4fd245d634ccb19ee2591f7e0e39 kernel-2.6.32-642.4.2.el6.x86_64.rpm 25072df3d8420ac35312d69ce6fac6b78f438fd5ea2e1d97bb166f782dba3fe0 kernel-abi-whitelists-2.6.32-642.4.2.el6.noarch.rpm a0e24a0d9fcfb696c86d623aa577f703d33f507a2147de2f2ec18fe7cdfdaefc kernel-debug-2.6.32-642.4.2.el6.x86_64.rpm d0d83d507c6828bf029b64624fbc293346f3fe80413f5cfc043ca0ba47366954 kernel-debug-devel-2.6.32-642.4.2.el6.i686.rpm 06e06107d1c00061148ba10556c2b4656f8335e2220b617f484f422a1d4ae705 kernel-debug-devel-2.6.32-642.4.2.el6.x86_64.rpm 4773b929c8c3b19898fd9a415f531d0c8ec728a17b8f0de2afa8901137a89657 kernel-devel-2.6.32-642.4.2.el6.x86_64.rpm a2b8e7402c375a214974398310b3337e1b6bfd75732048436b0be84358fc0151 kernel-doc-2.6.32-642.4.2.el6.noarch.rpm 609b1081724287d046575cd63a1e7cb73300c6e7ee14c78d1ffc9ed2f5727e6c kernel-firmware-2.6.32-642.4.2.el6.noarch.rpm b25e359da5e1ec89789973d79ef80825fd8fbdfe0d805396a349960c0d96fa22 kernel-headers-2.6.32-642.4.2.el6.x86_64.rpm 01bc6d240b66222d09cd569783a4c637b4f6904a1c43b303da1bbe8e88b8f8d4 perf-2.6.32-642.4.2.el6.x86_64.rpm b2419fc1469f9e68d58f98c39863d4d9573ed89c7695017510ea1a5355a583ec python-perf-2.6.32-642.4.2.el6.x86_64.rpm Source: 585403d5df3ce9b229d474d9e8d5723afe036cc95fb1369d37150642ef42b478 kernel-2.6.32-642.4.2.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 138, Issue 8 ***********************************************

1 0

migrate openldap to centos 7 server..
by Jason Welsh 23 Aug '16

23 Aug '16

I hope this isnt terribly off-topic, but Im trying to migrate openldap from an old 32bit install of gentoo linux to 64bit centos 7. Ive searched and found all kinds of info on migrating, but none if it seems to work completely for me. It seems that the newer centos 7 opendlap config doesnt use the slapd.conf file any more. So It appears I need two ldif files. one for the config and one for the actual database? on the old server if I do (as root) slapcat -n 0 , i get the error slapcat: could not open database. but I was able to get a dump of the (non-config) database with slapcat -n 1, but I cant import that ldif on the new centos 7 server without the config part... anyone know what the right procedure for this would be ? regards, Jason

2 1

GRUB 2 dumps to grub prompt when installed on >4TB disk
by James A. Peltier 23 Aug '16

23 Aug '16

Hi All, I have a Dell R710 that has 6x1TB in a RAID-5 configuration. When installing CentOS 7 using the full disk capacity and booting in UEFI mode the machine dumps me into a GRUB rescue mode prompt. error: disk `,gpt2' not found Entering rescue mode... grub rescue> If I use the PERC RAID controller to make the disk smaller ROOTDISK volume of 100GB in size and then a DATA volume of the rest of the disk the system boots just fine so this seems like a GRUB2 issue. Any thoughts? -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 604-365-6432 Fax : 778-782-3045 E-Mail : jpeltier(a)sfu.ca Website : http://www.sfu.ca/itservices Twitter : @sfu_rcg Powering Engagement Through Technology

2 6

dm-0: WRITE SAME failed. Manually zeroing
by correomm 23 Aug '16

23 Aug '16

Hello In a VM with CentOS 7, kernel 3.10.0-327.28.3.el7.x86_64, the console root login shows "[ 72.776182] dm-0: WRITE SAME failed. Manually zeroing". What is wrong? Regards, MM

2 2

CentOS 7, memory hungry (2.5GB) without user and heavy services running
by correomm 23 Aug '16

23 Aug '16

Hello, The last weekend, the VM with CentOS 7 (kernel-3.10.0-327.28.2.el7.x86_64) was running with 2.5GB of used memory, but without users connected, and heavy services running. Three minutes after reboot, the o.s. is running with 114MB used. ¿Why the 62% of memory is used if the o.s. does not have an intensive load? top sorted by memory: top - 12:55:34 up 8 days, 21:41, 1 user, load average: 0.16, 0.74, 0.49 Tasks: 90 total, 1 running, 89 sleeping, 0 stopped, 0 zombie %Cpu0 : 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 3882816 total, 310948 free, 2639892 used, 931976 buff/cache KiB Swap: 7815164 total, 7815164 free, 0 used. 825004 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 579 root 20 0 323592 23168 6232 S 0.0 0.6 0:30.07 firewalld 1110 root 20 0 553052 18264 5624 S 0.0 0.5 3:29.65 tuned 720 polkitd 20 0 530364 10900 4736 S 0.0 0.3 0:12.84 polkitd 587 root 20 0 250252 8060 4800 S 0.7 0.2 20:48.88 vmtoolsd 692 root 20 0 436892 7988 6156 S 0.0 0.2 0:12.36 NetworkManager 1 root 20 0 273832 7128 3820 S 0.0 0.2 2:20.92 systemd 577 root 20 0 210456 5488 3708 S 0.0 0.1 0:03.85 abrtd 26833 root 20 0 143008 5436 4148 S 0.0 0.1 0:13.47 sshd 487 root 20 0 46424 5112 2652 S 0.0 0.1 0:02.26 systemd-udevd 592 root 20 0 207976 4480 3124 S 0.0 0.1 0:02.31 abrt-watch-log 1806 postfix 20 0 93512 4088 3028 S 0.0 0.1 0:02.80 qmgr 470 root 20 0 129132 3956 2456 S 0.0 0.1 0:00.02 lvmetad 580 root 20 0 445712 3888 3156 S 0.0 0.1 1:00.74 rsyslogd 26950 postfix 20 0 93328 3848 2840 S 0.0 0.1 0:00.11 pickup 1112 root 20 0 82560 3544 2688 S 0.0 0.1 1:02.99 sshd 26837 root 20 0 116160 2976 1732 S 0.0 0.1 0:01.94 bash 719 root 20 0 53064 2644 2052 S 0.0 0.1 0:00.25 wpa_supplicant 26783 root 20 0 178108 2448 1520 S 0.0 0.1 0:00.07 crond 578 root 20 0 130060 2184 1672 S 0.0 0.1 0:00.66 smartd 1801 root 20 0 93224 2168 1116 S 0.0 0.1 0:11.25 master 27041 root 20 0 157688 2128 1448 R 1.4 0.1 0:00.51 top 581 dbus 20 0 37112 2116 1392 S 0.0 0.1 0:28.27 dbus-daemon 26968 root 20 0 36820 2076 1812 S 0.0 0.1 0:00.69 systemd-journal 608 chrony 20 0 115844 1860 1448 S 0.0 0.0 0:14.59 chronyd 586 root 20 0 26448 1700 1348 S 0.0 0.0 0:46.24 systemd-logind 615 root 20 0 126336 1680 1028 S 0.0 0.0 0:21.39 crond 555 root 16 -4 116724 1604 1208 S 0.0 0.0 0:33.97 auditd 26787 root 20 0 113120 1404 1220 S 0.0 0.0 0:00.05 freshclam-sleep 620 root 20 0 25964 952 752 S 0.0 0.0 0:00.62 atd 18160 root 20 0 110036 816 692 S 0.0 0.0 0:00.18 agetty 601 libstor+ 20 0 8532 780 632 S 0.0 0.0 0:10.61 lsmd 26792 root 20 0 107896 620 528 S 0.0 0.0 0:00.00 sleep 2 root 20 0 0 0 0 S 0.0 0.0 0:00.24 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:06.40 ksoftirqd/0 # netstat -nao Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State Timer tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN off (0.00/0/0) tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN off (0.00/0/0) tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN off (0.00/0/0) tcp 0 64 ip.ad.dr.ess:22 my.ip.by.myisp:50470 ESTABLISHED on (0.26/0/0) tcp6 0 0 :::22 :::* LISTEN off (0.00/0/0) tcp6 0 0 ::1:25 :::* LISTEN off (0.00/0/0) udp 0 0 127.0.0.1:323 0.0.0.0:* off (0.00/0/0) udp6 0 0 ::1:323 :::* off (0.00/0/0) raw6 0 0 :::58 :::* 7 off (0.00/0/0) Active UNIX domain sockets (servers and established) Proto RefCnt Flags Type State I-Node Path unix 2 [ ACC ] STREAM LISTENING 9979 /run/lvm/lvmpolld.socket unix 2 [ ACC ] STREAM LISTENING 9988 /run/lvm/lvmetad.socket unix 2 [ ] DGRAM 6664 /run/systemd/notify unix 2 [ ACC ] STREAM LISTENING 17787 private/tlsmgr unix 2 [ ACC ] STREAM LISTENING 17790 private/rewrite unix 2 [ ACC ] STREAM LISTENING 17793 private/bounce unix 2 [ ACC ] STREAM LISTENING 6676 /run/systemd/journal/stdout unix 2 [ ACC ] STREAM LISTENING 17796 private/defer unix 2 [ ACC ] STREAM LISTENING 17799 private/trace unix 5 [ ] DGRAM 6679 /run/systemd/journal/socket unix 2 [ ACC ] STREAM LISTENING 17802 private/verify unix 11 [ ] DGRAM 6681 /dev/log unix 2 [ ACC ] STREAM LISTENING 17805 public/flush unix 2 [ ACC ] STREAM LISTENING 17808 private/proxymap unix 2 [ ACC ] STREAM LISTENING 17811 private/proxywrite unix 2 [ ACC ] STREAM LISTENING 17814 private/smtp

2 1

yum does not recognise new (updated) packages due to underscore in package name
by Felix Scheffler 23 Aug '16

23 Aug '16

Hi all, we are currently working on porting software from x86_64 to aarch64. We are working with the altarch aarch64 repos: http://mirror.centos.org/altarch/7/os/aarch64/Packages/ http://mirror.centos.org/altarch/7/extras/aarch64/Packages/ http://mirror.centos.org/altarch/7/updates/aarch64/Packages/ However, it seems that yum (and eventually rpm) has problems with identifying new packages, if you have packages named as: <name>-<version>-<release>.el7_x.y.<arch>.rpm <name>-<version>-<release>.el7.y.<arch>.rpm A concrete example is the package selinux-policy-3.13.1-60.el7.3.noarch.rpm in the os repo. It has an updated package (selinux-policy-3.13.1-60.el7_2.7.noarch.rpm) in the updates repo. However, the underscore seems to be interpreted as a dot and hence leads to the package located in the os repo to be considered as newer. Maybe, this was tried to be addressed by also copying a corresponding version selinux-policy-3.13.1-60.el7_2.3.noarch.rpm into the os repo. However, this of course is also regarded as older (for the same reason) and thus still leads to the initial package to have precedence. Do I miss out on something here? In addition, it might well be that this is not only an issue to the aarch64 repos, but also to other architectures. Is it a known issue and if yes, are there any attempts to correct this? As from what I can tell so far, it is not a problem of yum or rpm, but some inconsistencies in naming the packages in the centos repos. Other sources of information: http://superuser.com/questions/427065/what-comes-after-the-underscore-in-an… http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ https://fedoraproject.org/wiki/Archive:Tools/RPM/VersionComparison Thanks in advance for your help. Best regards Felix

1 0

GPG key issue for epel-release on ppc64le platform
by Manjunath A Kumatagi 23 Aug '16

23 Aug '16

Hi, I've installed centos 7 and updated the packages and trying to install the epel-release package and hit with following error: [root@localhost ~]# yum info epel-release Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Available Packages Name : epel-release Arch : noarch Version : 7 Release : 5 Size : 14 k Repo : extras/7/ppc64le Summary : Extra Packages for Enterprise Linux repository configuration URL : http://download.fedoraproject.org/pub/epel License : GPLv2 Description : This package contains the Extra Packages for Enterprise Linux : (EPEL) repository GPG key as well as configuration for yum. [root@localhost ~]# yum install epel-release Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package epel-release.noarch 0:7-5 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: epel-release noarch 7-5 extras 14 k Transaction Summary ================================================================================ Install 1 Package Total download size: 14 k Installed size: 24 k Is this ok [y/d/N]: y Downloading packages: warning: /var/cache/yum/ppc64le/7/extras/packages/epel-release-7-5.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY Public key for epel-release-7-5.noarch.rpm is not installed epel-release-7-5.noarch.rpm | 14 kB 00:00 Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-AltArch-7-ppc64le The GPG keys listed for the "CentOS-7 - Extras" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository. Failing package is: epel-release-7-5.noarch GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-AltArch-7-ppc64le [root@localhost ~]# Thanks, Manjunath.

1 0

Canon scanner LiDE 220
by J Martin Rushton 22 Aug '16

22 Aug '16

This scanner is supported according to the SANE page, but doesn't work on my up-to-date C7 system (updated 20 minutes ago). The Canon web site is as expected - as useful as a chocolate tea pot. Has anyone managed to get this to run, and if so can you share the secret please.

5 7

EPEL packages for CentOS 7 i686 AltArch distro
by Johnny Hughes 22 Aug '16

22 Aug '16

I have begun building the EPEL packages for the CentOS 7 i686 AltArch distribution. You can watch the progress here: http://buildlogs.centos.org/c7-epel/ Should have most of the packages built in the next couple days. Thanks, Johnny Hughes

3 3

Sound failure in CentOS 6.8
by j_post 21 Aug '16

21 Aug '16

Sound stopped working on my CentOS 6.8 system several months ago. I've tried everything I can to find out what's wrong. It is not the hardware; if I boot into a live dvd of 6.8 (or any other OS), the sound works perfectly. So something must have changed in my configuration. I've compared files on my system and another CentOS 6.8 system with working sound and I haven't found any differences relating to sound configuration. I've scoured the web for help, and found a few sites where people reported the same problem, but none of their "solutions" work. Many refer to sndconfig and system-config-soundcard which don't exit in 6.8. I've spent countless hours looking through alsa (and other) documentation for any hints that might help. Nothing. If I crank up the volume on the speakers, and set kmixer to max, I hear a low level of white noise coming from the speakers. This noise does not occur when I first boot up, but kicks in somewhere during the boot process, I'm guessing when the system is attempting to initialize the sound card. The only substantial info I have about the failure is the output from KInfoCenter -> Sound: -------------- Sound Driver:3.8.1a-980706 (ALSA v1.0.24 emulation code) Kernel: Linux 2.6.32-642.3.1.el6.x86_64 #1 SMP Tue Jul 12 18:30:56 UTC 2016 x86_64 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: HDA Intel PCH at 0xfbff8000 irq 33 HDA NVidia at 0xfaffc000 irq 17 Audio devices: NOT ENABLED IN CONFIG Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG Timers: 31:system timer Mixers: NOT ENABLED IN CONFIG --------------- I have no idea what "CONFIG" it's referring to. A gigantic "thank you" to anyone who can help resolve this problem. Jeff

2 5

running CGI scripts with SELinux=ENFORCING with priviledged commands ...
by Walter H. 21 Aug '16

21 Aug '16

Hello, how could it be achieved to run e.g. shutdown -h now from a CGI script on a system where SELinux is set to ENFORCING? Thanks Walter

3 3

Re: [CentOS] LSI SATA MegaRaid & Centos 7 build 1511
by Gordon Messmer 20 Aug '16

20 Aug '16

On 08/14/2016 03:59 AM, Fawzy Ibrhim wrote: > I have managed to install Centos 6.2 64bit with kernel > 2.6.32-220.el6.x86_64 and upgraded it to Centos 6.8 with kernel > 2.6.32-642.3.1.el6.x86_64. What about the output of "lsmod" and "modinfo dmraid"? Please reply on the list, rather than to my address directly, and if you could, please avoid sending HTML messages. Your font is so small I can barely read it.

5 10

CentOS-announce Digest, Vol 138, Issue 7
by centos-announce-request＠centos.org 20 Aug '16

20 Aug '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2016:1633 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sat, 20 Aug 2016 02:00:21 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1633 Important CentOS 7 kernel Security Update Message-ID: <20160820020021.GA56293(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1633 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1633.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4a43586d53bea13acb0a2bc8e2fe3fa09397d942ad718a4dee1e142e9e9380e8 kernel-3.10.0-327.28.3.el7.x86_64.rpm d969aa87c7d282f76f7acfee1aace918cf2ff6157072383cbb50c2c24a9f37e0 kernel-abi-whitelists-3.10.0-327.28.3.el7.noarch.rpm 897f672cd70164c77fcdd5afbce77f6e481ebca8bdafaab3a58eba2bf5e35364 kernel-debug-3.10.0-327.28.3.el7.x86_64.rpm 6cf6eb00c40c315cc736cf9525c711bd070ec62e0874148be94b9fb8c2879022 kernel-debug-devel-3.10.0-327.28.3.el7.x86_64.rpm 1851d0e886e22856b3c6b29f39e7929ce578d7108b32bacf05dbc59f9fe0de82 kernel-devel-3.10.0-327.28.3.el7.x86_64.rpm 9990858967dd7b9d71e1afb78a1447e4255c0805cdd34ef9456e803a86ba9f0e kernel-doc-3.10.0-327.28.3.el7.noarch.rpm b8b81ef90046f22134b84412758f687a143be2edcc6a208f81938fec2f44e5d7 kernel-headers-3.10.0-327.28.3.el7.x86_64.rpm 2c2f74547642ebf62fe2ff8aba681303c52358c3ab89e4a53f7717ed5eae91d4 kernel-tools-3.10.0-327.28.3.el7.x86_64.rpm 31d60421fce67ef936c1b589e5ae2208f1678043e48b6ae45d084d2d94024031 kernel-tools-libs-3.10.0-327.28.3.el7.x86_64.rpm d2a4a4340baa7cc0fa03772a08db6c13e4f343746c8c260fd89a804b5649bfbc kernel-tools-libs-devel-3.10.0-327.28.3.el7.x86_64.rpm c57adb2c9d31fb3b79c5b8c33d83ffc932a87d4dba4bb6e6360ba5aec593a901 perf-3.10.0-327.28.3.el7.x86_64.rpm 5b3202c66cf6db7238c408a105a05163eb5f6a4469d7069d1a84bab9945c7a81 python-perf-3.10.0-327.28.3.el7.x86_64.rpm Source: 7bdf741a077dfa14c49d861239eab449ba8813a47920f801079d8da7fc74c65c kernel-3.10.0-327.28.3.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 138, Issue 7 ***********************************************

1 0

explain strange behavior
by Dan Hyatt 19 Aug '16

19 Aug '16

In my bin directory, most of the binaries are linked to it. It is in my path. I have googled this and cannot find anything close. I am running bash on centos6.8 When I run "which command" most of the files in this custom bin directory show up. When I run "which file.jar" it cannot see it, but I can *ls* the file (soft link) as which only works on executables (according to man page), I created a dan.jar empty file and did a which on dan.tar and found it. can anyone explain what is happening and how I can soft link the jar files to my bin directory so which can see them? Dan

4 3

CentOS-announce Digest, Vol 138, Issue 6
by centos-announce-request＠centos.org 19 Aug '16

19 Aug '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2016:1626 Moderate CentOS 7 python Security Update (Johnny Hughes) 2. CESA-2016:1626 Moderate CentOS 6 python Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 18 Aug 2016 17:23:01 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1626 Moderate CentOS 7 python Security Update Message-ID: <20160818172301.GA16017(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1626 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1626.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4580fa3bd63f62fcb02e491b1ab0952f5c11d56dac42295d3f7917818790c28d python-2.7.5-38.el7_2.x86_64.rpm d65cd5414f4167267a8305c43b9828a19d6c0f02c4b9b046bcbc4ebfb9d898b9 python-debug-2.7.5-38.el7_2.x86_64.rpm 1d846ef07419a41e66c2423f07063dfc498f595bc8077bac36af8d3204a3e3fa python-devel-2.7.5-38.el7_2.x86_64.rpm 4225681bbc8bdc0a24dba05f6edd0b7536448a7d062a9ef0f921501c8bf3757e python-libs-2.7.5-38.el7_2.i686.rpm de6d8600d0d9a36c1cb22b6968224612ad7a06354d9cbd33da4bec17554837fe python-libs-2.7.5-38.el7_2.x86_64.rpm 01c3fecdcab99e8f853adcde3fb2080468c2eff91c5e29906a143541d494f4df python-test-2.7.5-38.el7_2.x86_64.rpm ca3d26aa3f2a10f399ab2f26577054fc0c443b099e2bbfba1b6d4785a4fce3f9 python-tools-2.7.5-38.el7_2.x86_64.rpm 95c26c4e3a57926bc59e80e8f2707011c5000a6a0d47875e823a4126cf15ea6b tkinter-2.7.5-38.el7_2.x86_64.rpm Source: 4470b36c08ba660c4317b4211b6aa2207288d4a9f438a998b92be3d62a958def python-2.7.5-38.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 18 Aug 2016 17:23:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1626 Moderate CentOS 6 python Security Update Message-ID: <20160818172323.GA16340(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1626 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1626.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d434ddba7ca4db22fb0a430f43961ecda1394f8e0c0c799855acf448a056b2f4 python-2.6.6-66.el6_8.i686.rpm 73a0c8b071682ee7cf2f44d1779ffc3302ad639fffe6ef3e528c887af609058b python-devel-2.6.6-66.el6_8.i686.rpm 48e1c9e73faeeed24011487a75915cdd67cdbdd0fb3aadfa6ea2a690220e6e0f python-libs-2.6.6-66.el6_8.i686.rpm fdfc3b56a5caa9bcf8b58737caa7337daf49532fca8a1e62e7c5f1edfcab0c91 python-test-2.6.6-66.el6_8.i686.rpm 069495e99bfd46b657c8622274cb0aca1921b374df5e43ec8ef7f88052b504c0 python-tools-2.6.6-66.el6_8.i686.rpm 6d267b6e09719e7cd17e7b05e736a4272f14d62dc3162616c65840a80bd90847 tkinter-2.6.6-66.el6_8.i686.rpm x86_64: 53c75a1756e5b4f6564c5229a37948c9b4561e0bf58076bd7dab7aff85a417f2 python-2.6.6-66.el6_8.x86_64.rpm 73a0c8b071682ee7cf2f44d1779ffc3302ad639fffe6ef3e528c887af609058b python-devel-2.6.6-66.el6_8.i686.rpm 5c9d6761d8d896b93ed92caa1ec61045aa1847c32d6cf860c2b4959b49d9de80 python-devel-2.6.6-66.el6_8.x86_64.rpm 48e1c9e73faeeed24011487a75915cdd67cdbdd0fb3aadfa6ea2a690220e6e0f python-libs-2.6.6-66.el6_8.i686.rpm ae6a523f79928c4fdb8c7d62f07279883b20b8b89d8703cb91030201c54e25e9 python-libs-2.6.6-66.el6_8.x86_64.rpm 61116f6ad9f288b23d0fd63fa2252ffd2fdc53e978a358aebda1654453145d4c python-test-2.6.6-66.el6_8.x86_64.rpm a88d7d03b236ac4938be140c230d2d8d645a82a39bcf647c7d5d55bc27106192 python-tools-2.6.6-66.el6_8.x86_64.rpm 7eb7c048610b47fd5c7918e5f12038c3869fe90f4a24d604fbc70a6220d460c2 tkinter-2.6.6-66.el6_8.x86_64.rpm Source: b56fb033143cf700283ef68914a9cec31a1f8a045e6849c3c1afd2e08d7a2b56 python-2.6.6-66.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 138, Issue 6 ***********************************************

1 0

BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
by correomm 18 Aug '16

18 Aug '16

This bug is reported only on the VM's with CentOS 7 running on on VMware ESXi 5.1. The vSphere performance graph shows high CPU consume and disk activity only on VM's with CentOS 7. Sometimes I can not connect remotely with ssh (timeout error). The details of last issues was reported to retrace.fedoraproject.org. ¿Do you have a hint? [root@vmguest ~]# abrt-cli list id c52b463b15cfa94af7a96f237e5f525332750dd3 reason: systemd-journald killed by SIGABRT time: Tue 16 Aug 2016 03:10:52 PM CLST cmdline: /usr/lib/systemd/systemd-journald package: systemd-219-19.el7_2.12 uid: 0 (root) count: 1 Directory: /var/spool/abrt/ccpp-2016-08-16-15:10:52-458 Reported: https://retrace.fedoraproject.org/faf/reports/bthash/d5f5d4f75b200eeab2f83c… id e6955aa621a0d296d4cdd05421523885e85a179b reason: BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0] time: Tue 09 Aug 2016 04:46:33 PM CLT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.28.2.el7.x86_64 root=/dev/mapper/centos_vmguest-root ro crashkernel=auto rd.lvm.lv=centos_vmguest/root rd.lvm.lv=centos_vmguest/swap rhgb quiet LANG=en_US.UTF-8 package: kernel uid: 0 (root) count: 1 Directory: /var/spool/abrt/oops-2016-08-09-16:46:33-3165-0 Reported: https://retrace.fedoraproject.org/faf/reports/bthash/4e231b49f72864c3487d89… id 402f22e7214ea6bddcb0db9a9315527be245f943 reason: systemd-logind killed by SIGABRT time: Wed 20 Jul 2016 06:10:55 AM CLT cmdline: /usr/lib/systemd/systemd-logind package: systemd-219-19.el7_2.9 uid: 0 (root) count: 3 Directory: /var/spool/abrt/ccpp-2016-07-20-06:10:55-32283 Reported: https://retrace.fedoraproject.org/faf/reports/bthash/307b26a77cc6d5005ce2fd… id 58a46f4a45699384ad74850f53e749c702ee7b0b reason: systemd-journald killed by SIGABRT time: Tue 02 Aug 2016 05:44:50 PM CLT cmdline: /usr/lib/systemd/systemd-journald package: systemd-219-19.el7_2.11 uid: 0 (root) count: 1 Directory: /var/spool/abrt/ccpp-2016-08-02-17:44:50-454 Reported: https://retrace.fedoraproject.org/faf/reports/bthash/1af5058d2b9650a1d91c67… id f4a35ca85a046e74bf4a4382c9f9a5c8dd8be149 reason: BUG: soft lockup - CPU#0 stuck for 24s! [vmtoolsd:579] time: Tue 02 Aug 2016 06:45:29 AM CLT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.22.2.el7.x86_64 root=/dev/mapper/centos_vmguest-root ro crashkernel=auto rd.lvm.lv=centos_vmguest/root rd.lvm.lv=centos_vmguest/swap rhgb quiet LANG=en_US.UTF-8 package: kernel uid: 0 (root) count: 1 Directory: /var/spool/abrt/oops-2016-08-02-06:45:29-11859-0 Reported: https://retrace.fedoraproject.org/faf/reports/bthash/87298dcaf6b7dea7a92b13… id edaec629ccce62943e9bdb514fe6e319ab320669 reason: BUG: soft lockup - CPU#0 stuck for 27s! [khugepaged:51] time: Tue 26 Jul 2016 06:00:13 PM CLT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.18.2.el7.x86_64 root=/dev/mapper/centos_vmguest-root ro crashkernel=auto rd.lvm.lv=centos_vmguest/root rd.lvm.lv=centos_vmguest/swap rhgb quiet LANG=en_US.UTF-8 package: kernel uid: 0 (root) count: 1 Directory: /var/spool/abrt/oops-2016-07-26-18:00:08-641-4 Reported: cannot be reported id b707fd06199e2e1edcb105878a46e238a50746f3 reason: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-journal:422] time: Tue 26 Jul 2016 06:00:10 PM CLT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.18.2.el7.x86_64 root=/dev/mapper/centos_vmguest-root ro crashkernel=auto rd.lvm.lv=centos_vmguest/root rd.lvm.lv=centos_vmguest/swap rhgb quiet LANG=en_US.UTF-8 package: kernel uid: 0 (root) count: 1 Directory: /var/spool/abrt/oops-2016-07-26-18:00:08-641-1 Reported: cannot be reported id a39eead9c9f75c2dc94df0852cd24260f414b80b reason: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] time: Tue 26 Jul 2016 06:00:08 PM CLT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.18.2.el7.x86_64 root=/dev/mapper/centos_vmguest-root ro crashkernel=auto rd.lvm.lv=centos_vmguest/root rd.lvm.lv=centos_vmguest/swap rhgb quiet LANG=en_US.UTF-8 package: kernel uid: 0 (root) count: 1 Directory: /var/spool/abrt/oops-2016-07-26-18:00:08-641-0 Reported: cannot be reported id fe7e2542e93848e41d9d702af5c4d12b1d833b72 reason: systemd-logind killed by SIGABRT time: Wed 20 Jul 2016 08:20:29 AM CLT cmdline: /usr/lib/systemd/systemd-logind package: systemd-219-19.el7_2.9 uid: 0 (root) count: 1 Directory: /var/spool/abrt/ccpp-2016-07-20-08:20:29-32660 id e58538a3aa1f01f384fe9bdd40a693f9d2f32889 reason: BUG: soft lockup - CPU#2 stuck for 24s! [kworker/2:0:31607] time: Mon 13 Jun 2016 04:48:05 PM CLT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.18.2.el7.x86_64 root=/dev/mapper/centos_vmguest-root ro crashkernel=auto rd.lvm.lv=centos_vmguest/root rd.lvm.lv=centos_vmguest/swap rhgb quiet LANG=en_US.UTF-8 package: kernel uid: 0 (root) count: 1 Directory: /var/spool/abrt/oops-2016-06-13-16:48:05-10215-0 id a4dd378d494c8eee43407b572e2b314f38f7c5b9 reason: systemd-journald killed by SIGABRT time: Sat 28 May 2016 06:24:40 PM CLT cmdline: /usr/lib/systemd/systemd-journald uid: 0 Directory: /var/spool/abrt/ccpp-2016-05-28-18:24:40-6058 Reported: cannot be reported

4 6

Error at sdhci-pci, kernel
by Walter H. 17 Aug '16

17 Aug '16

Hello, CentOS 6.8, kernel 2.6.32-642.3.1.el6.x86_64 sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pci 0000:00:10.0: SDHCI controller found [8086:2294] (rev 21) sdhci-pci 0000:00:10.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 sdhci-pci 0000:00:10.0: Invalid iomem size. You may experience problems. <-- sdhci-pci 0000:00:10.0: setting latency timer to 64 where can I either disable loading this driver at all or define a different value for io mem size? Thanks, Walter

1 0

Anaconda error on centos 7.2
by SUDHANSHU BHUTANI 17 Aug '16

17 Aug '16

Hi all, We are hitting an error in the centos 7 installation with our kickstart configuration. =============================================================================== An unknown error has occurred =============================================================================== anaconda 21.48.22.56-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 538, in lvactivate raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg)) File "/usr/lib/python2.7/site-packages/blivet/devices/lvm.py", line 690, in _setup lvm.lvactivate(self.vg.name, self._name) File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 413, in setup self._setup(orig=orig) File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 650, in execute self.device.setup(orig=True) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 377, in processActions action.execute(callbacks) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 374, in doIt self.devicetree.processActions(callbacks) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 224, in turnOnFilesystems storage.doIt(callbacks) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 186, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run threading.Thread.run(self, *args, **kwargs) LVMError: lvactivate failed for swap: running lvm lvchange -a y --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } redhat/swap failed Kickstart:- #version=RHEL7 # System authorization information auth --enableshadow --passalgo=sha512 # Use CDROM installation media cdrom # Run the Setup Agent on first boot firstboot --enable ignoredisk --only-use=vda # Keyboard layouts keyboard --vckeymap=us --xlayouts='us' network --device eth0 --bootproto static --ip 10.97.60.50 --netmask 255.255.255.0 --gateway 10.97.60.254 --nameserver 10.97.2.1 --noipv6 # System language lang en_US.UTF-8 # System timezone timezone America/Los_Angeles # Network information #network --bootproto=dhcp --device=eno1 --onboot=yes --ipv6=auto #network --bootproto=dhcp --device=eno2 --onboot=yes --ipv6=auto #network --bootproto=dhcp --device=enp4s0f0 --onboot=yes --ipv6=auto #network --bootproto=dhcp --device=enp4s0f1 --onboot=yes --ipv6=auto #network --bootproto=dhcp --device=enp4s0f2 --onboot=yes --ipv6=auto #network --bootproto=dhcp --device=enp4s0f3 --onboot=yes --ipv6=auto #network --bootproto=dhcp --device=enp7s0f0 --onboot=yes --ipv6=auto #network --bootproto=dhcp --device=enp7s0f1 --onboot=yes --ipv6=auto #network --hostname=localhost.localdomain # Reboot after installation reboot # Root password #rootpw --iscrypted $6$1VdyMsGywTam2QoF$h9G0RZJlZ8etF8LMvjT8LBuYoRkWfP3nXSP8UrNtW6gV/gHCjdUbnMDca.St2NVftNz5rJ5bZ/FgvLky2j2TG1 rootpw "root" # Create user admin user --groups=wheel --name=admin --password=$6$zVk6Jq/HtswVONHY$0frpMHx1IBOe302zYnhdo9xRQS6NOgBWgpXpH33k3dNYkHm1jCo6Cj.SXn9Ct/BugC.0iTkwBsX.NcpVtocc70 --iscrypted --shell=/sbin/nologin # Partitioning and System bootloader configuration bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=vda autopart --type=lvm clearpart --all --initlabel %packages <list of packages> %end Can somebody suggest a quick workaround for the above anaconda error. We feel that Red hat has acknowledged this issue, but not sure, when can we get the fix for this. https://access.redhat.com/solutions/2203631 Is there any workaround for this? Regards Sudhanshu bhutani

1 0

hfsplus on C7
by Jerry Geis 16 Aug '16

16 Aug '16

I followed the instructions (I thought) for hfsplus on C7. Installed elrepo Then installed hfsplus hfsplus-tools and kmod-hfsplus kmod-hfs rpm -qa | grep hfs clearly shows the items kmod-hfsplus-0.0-2.el7.elrepo.x86_64 hfsplus-tools-540.1.linux3-4.el7.x86_64 kmod-hfs-0.0-2.el7.elrepo.x86_64 When I do my mount command mount -t hfsplus -o loop Mac.dmg /mnt/mac mount: unknown filesystem type hfsplus What did I miss? Thanks, Jerry

4 11

firewalld and just a routing between local lans
by lejeczek 16 Aug '16

16 Aug '16

hi how much different iptables are in 7 from 6 I'm just learning, I expected that since IFs belong to the same zone traffic between them would pass, be forwarded without any extra settings/configuration but, I'm wrong it turns out. Am I missing something and there actually is a simple way, designed to make that routing between lans/interfaces just work - a one liner, one option/setting in that comprehensive(?) firewalld configuration? How does firewall make your centos a router of directly connected LANs? many thanks L.

1 0

local routing puzzle
by lejeczek 16 Aug '16

16 Aug '16

hi everyone I'm having a bit of a puzzle on one centos system, I have four interfaces: nm-team1 10.5.6.100 em1 192.168.2.17 em2 192.168.2.18 p3p3 172.25.12.222 I do: ping 10.5.6.17 -I em1 PING 10.5.6.17 (10.5.6.17) from 192.168.2.17 em1: 56(84) bytes of data. 64 bytes from 10.5.6.17: icmp_seq=1 ttl=64 time=0.367 ms the same for -I em2, for -I em1 and naturally for -I nm-team1 - all good. but: $ ping 10.5.6.17 -I p3p3 PING 10.5.6.17 (10.5.6.17) from 172.25.12.202 p3p3: 56(84) bytes of data. and nothing, ping waits and no reply, Ctrl+C with such a simple setup rules based routing should not be involved, kernel should figure it out, right? many thanks. L.

2 3

tcpdump loses lots of packets
by Anand Buddhdev 16 Aug '16

16 Aug '16

Hi folks, I've got a Dell R320 running CentOS 7, and a 10G NIC. I'm running a DNS server on it, for testing. As part of my testing, I'm attempting to capture all the DNS queries arriving on the server, using tcpdump. However, tcpdump's performance is abysmal, and it loses lots of the packets. Here's the output when I stop the capture: # tcpdump -nn -i p1p1 -w /dev/shm/queries.pcap -B 65536 dst host 193.0.14.129 tcpdump: listening on p1p1, link-type EN10MB (Ethernet), capture size 65535 bytes ^C4096558 packets captured 6882162 packets received by filter 2785604 packets dropped by kernel The number 6882162 is exactly the number of DNS queries I am sending from another server (the source). The filter is seeing them. However, not all of them make it into the pcap file. First I was writing to the disk, and thought it might be a bottleneck, so I tried to write to /dev/shm. You'll see I've also increased the buffer size with -B, but none of this helps. The packet rate is also not that high. From the sending side, this is what I have: # tcpreplay -i qtx:p1p1 5min.pcap Actual: 6882162 packets (620533334 bytes) sent in 317.08 seconds. Rated: 1951900.0 Bps, 15.61 Mbps, 21648.97 pps Flows: 4254416 flows, 13382.96 fps, 6882162 flow packets, 0 non-flow This is a very modest rate. Any ideas why tcpdump loses so many packets? And how to make it do better? Regards, Anand

5 5

vsftpd broken ?
by Günther J. Niederwimmer 15 Aug '16

15 Aug '16

Hello, CentOS 7.2 have any a workaround for this Error ? vsftpd Error:426 failure Reading Network STream after transfer I have a broken file on the ftp Server I mean I have found a newer Version 3.0.3 bot not for CentOS 7.2 but I cant say is this Problem corrected in 3.0.3? Any hint please ;-) -- mit freundlichen Grüßen / best regards, Günther J. Niederwimmer

2 4

postscreen and clamav on CentOS 6.8
by Jon LaBadie 15 Aug '16

15 Aug '16

A friend runs 6.8 but would like to add postscreen to his email server. It is provided with postfix version 2.8 and up. The newest postfix for 6.8 is 2.6.x. Any likelyhood it will be further updated? Or is there another source for newer postfix versions for CentOS 6.8? Similar query for the clamav db, now at 0.99.1 with 0.99.2 out for quite some time. Jon -- Jon H. LaBadie jon(a)jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)

6 6

Custom desktop menu entries: weird behavior with menu categories
by Nicolas Kovacs 15 Aug '16

15 Aug '16

Hi, For my client's desktops, I'm usually customizing the various Linux desktops I'm installing. I'm using custom icon themes (Elementary), custom system fonts (Droid Sans), and one of the things I also customize are desktop menu entries. Here's an example of what I do on a Slackware+Xfce-based desktop, so you get the idea. Once all applications are installed, I run the cleanmenu.sh script: http://www.microlinux.fr/microlinux/desktop-14.2-64bit/tools/ As you can see, this script replaces the various *.desktop files in /usr/share/applications and similar places with my own custom *.desktop files: http://www.microlinux.fr/microlinux/desktop-14.2-64bit/tools/desktop/ This solution has worked very well over the years. There are a few reasons I'm doing this. Most of my users come from a Windows-centric world, so it's better for them if the menu sports something like "Office>Presentation Software" instead of "LibreOffice Impress". Another reason is visual consistency. BTW, the "Elementary Xfce" icon theme is great not only for Xfce, but also for other desktops, and it fits great in corporate environments needing something sober and not too distracting. Last but not least, some menu entries are better organized in different categories. IMHO, the screenshot utility should default to "Graphics" and not to "Utility", and Brasero should be in "Utilities" and not in "Multimedia". Curiously enough, some menu entries stubbornly refuse to have their category redefined. 1. When I edit gnome-terminal.desktop and define "Categories=System;", it won't appear in "Outils systèmes" as expected but remains in "Utilitaires". 2. I have a category "Divers" (something like "Misc") with a single desktop entry for Printer Configuration. Now when I edit system-config-printer.desktop and define something like "Categories=System;", the "Divers" category remains there and the menu entry won't budge. Most of the menu entries can be redefined OK, and they appear in the new category. Why a handful of desktop entries would not work remains a mystery. This looks damn well like a bug, although I wouldn't even know how to call it. Any ideas? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

4 5

Single source repo, producing packages for CentOS 6 and 7, how?
by Martinx - ジェームズ 15 Aug '16

15 Aug '16

Guys, I have a source code here, that produces RPM packages for CentOS 6, that includes an Upstart Job and a ugly and minimal Init Script. Now, I have it running on CentOS 7, via systemd, looks good! However, my RPM package for CentOS 7 still includes the useless Upstart and Init Scripts... So, here is the question: How are you guys managing this? I mean, I would like to have 1 single source and 1 SPEC file for both CentOS 6 and 7, but no need to systemd service files on 6 / no need to upstart job files on 7. Cheers! Thiago

3 3

Locked out of the CentOS Fora
by Dan White 15 Aug '16

15 Aug '16

The username/email combo I give the "forgot password" option does not work and I cannot re-register as it says my email is in use. Suggestions ? Dan White | d_e_white(a)icloud.com ------------------------------------------------ “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” (Bill Waterson: Calvin & Hobbes)

2 2

Re: [CentOS] how to update from 5.8 to 5.latest?
by Kai Schaetzl 15 Aug '16

15 Aug '16

Eero Volotinen wrote on Mon, 15 Aug 2016 11:00:51 +0000: > Maybe your repodata cache was a bit old :) Yeah. I would have thought it checks the date of the file and tries to update it when it's that old. Anyway, clearing the whole yum cache was a good idea as I don't need the 5.8 rpms anymore. I just didn't think about that first, it's been long ... Thanks for the quick reply! It assured me that there was no special procedure necessary, so I thought again and remembered that. Kai

1 0

how to update from 5.8 to 5.latest?
by Kai Schaetzl 15 Aug '16

15 Aug '16

Hi! I revived an old disk with CentoS 5.8 on it and want to update it to 5.latest (=5.11). However, it insists on getting 5.8 files. From the past I remember I would get a major release jump from 5.n to 5.m automatically. Or do I remember this wrong? I googled a bit around, but couldn't really find something similar. How do I update now? The repo file looks exactly like on machines that are up to 5.11. Should I change it manually to 5.11 or just 5 paths? Does it still understand that this is then an upgrade to a another major version? Or should I do something different to make it upgrade to 5.11? Thanks! Kai

2 1

OT: Backup Question/Solution
by TE Dukes 14 Aug '16

14 Aug '16

Hello, I want to switch from DVDs as a backup medium to a usb flash drive. I have been using Mondo but get tired of feeding it DVD+RWs. I purchased a 128GB flash drive. I can't get Mondo to write to it. I want to be able to make this device bootable. Do I need it reformat it from a Windows file system to ext4? I never had to format a blank DVD previously. Is there a better solution for backing up a home system to some sort of external media? TIA

3 3

Duplicate *.desktop entries for GNOME in /usr/share/applications
by Nicolas Kovacs 14 Aug '16

14 Aug '16

Hi, Today I noticed something strange. There seem to be a series of duplicate desktop menu entries in /usr/share/applications. Example: gedit.desktop and org.gnome.gedit.desktop Other example: nautilus.desktop and org.gnome.Nautilus.desktop This is annoying, since I usually edit some custom menu entries for my users. Now, if I edit both files for a single application, I end up with duplicate menu entries. Any suggestions? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 2

Software RAID and GRUB on CentOS 7
by Nicolas Kovacs 13 Aug '16

13 Aug '16

Hi, When I perform a software RAID 1 or RAID 5 installation on a LAN server with several hard disks, I wonder if GRUB already gets installed on each individual MBR, or if I have to do that manually. On CentOS 5.x and 6.x, this had to be done like this: # grub grub> device (hd0) /dev/sda grub> device (hd1) /dev/sdb grub> root (hd0,0) grub> setup (hd0) grub> root (hd1,0) grub> setup (hd1) grub> quit I'd like my server to be able to boot a degraded software RAID after an eventual hard disk failure. Any suggestions? Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

5 5

centos 7 :: cannot update
by Adrian Sevcenco 13 Aug '16

13 Aug '16

Hi! I have a very strange problem with my centos 7 vm : i cannot update!! I have normal ingress/egress access but my yum update fills my screen with : [Errno 14] HTTP Error 404 - Not Found i already done "clean all" ... anyone seen this problem? any idea about the issue and workarounds? Thank you! Adrian

2 1

[CentOS6] Manually configured Firewall (WLAN-AP plus Router)
by Walter H. 13 Aug '16

13 Aug '16

Hello I've got this Mini-PC https://www.zotac.com/product/mini_pcs/zbox-ci323-nano everything is fine -> latest 6.8 kernel works; both Ethernet-Interfaces work and also the WLAN-Interface works; the two Ethernet-Interfaces are eth0 and eth1 the WLAN-Interface is wlan0 eth1 is connected on ISP side eth0 is connected on my LAN side to a switch; and wlan0 shall also be on my LAN side für wireless and work as an Access-Point (this works) I want both LAN interfaces (eth0 and wlan0) have the same IP subnet so I did this: http://www.microhowto.info/howto/persistently_bridge_traffic_between_two_or… also the DHCP works fine: both DHCP and DHCPv6; RADVd also works fine; in /etc/sysconfig/network-scripts/ I added ifcfg-sit1 with the configuration for my IPv6 tunnel at Hurricane Electric there is the following entry: IPV6TUNNELIPV4LOCAL=ipv4addr here the 1st question: does this have to be the IPv4 address of br0 (LAN) or the one of eth1 (WAN)? (before I had this on a virtual machine, there was only one interface, but here ...?) and now the bigger problem: here just the IP addresses for better troubleshooting; the ISP installed a box (NAT router), that is a medium converter (coaxial cable to ethernet twisted-pair cable), too; this box has on WAN side, my public IP an LAN side it has 192.168.0.1 this box which should be installed instead of my old NAT-router has the following IP addresses on device br0 192.168.1.100 (LAN) and on device eth1 (WAN) 192.168.0.127 the old router has on LAN side 192.168.1.254 and on WAN side 192.168.0.254 now both the new box and the old router are connected "parallel" which means, each is connected with its WAN interfaces to the built-in switch of ISP-box and with its LAN interfaces to my switch; on the old NAT-router I have defined the LAN-IP of the new box as DHCP relay; this works fine; (the new box is the only DHCP server in LAN) <begin /etc/sysconfig/iptables> # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] # ICMP: extra chain -N ALLOWED-ICMP -A ALLOWED-ICMP -p icmp -m limit --limit 1/sec --limit-burst 2 -j ACCEPT # Allow anything on the local link -A INPUT -i lo -j ACCEPT -A OUTPUT -o lo -j ACCEPT # Allow anything out on the localnet -A OUTPUT -o br0 -j ACCEPT # Allow established, related packets back in -A INPUT -i br0 -m state --state ESTABLISHED,RELATED -j ACCEPT # Enable DHCP -A INPUT -p udp -i br0 --dport 67:68 --sport 67:68 -j ACCEPT # Enable IPv6 -A INPUT -p ipv6 -i eth1 -s 216.66.80.30 -j ACCEPT # Allow SSH from LAN and redirected from internet # from WLAN there should be no SSH possible, so I used eth0 -A INPUT -i eth0 -m tcp -p tcp --dport 22 -m state --state NEW -j ACCEPT -A INPUT -i eth1 -d 192.168.0.127 -m tcp -p tcp --dport 22 -m state --state NEW -m recent --update --seconds 115 --hitcount 3 --name DEFAULT --rsource -j DROP -A INPUT -i eth1 -d 192.168.0.127 -m tcp -p tcp --dport 22 -m state --state NEW -m recent --set --name DEFAULT --rsource -A INPUT -i eth1 -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT # Allow anything out on the internet -A OUTPUT -o eth1 -j ACCEPT # Allow established, related packets back in -A INPUT -i eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT # Allow multicast -A INPUT -d 224.0.0.0/4 -j ACCEPT -A OUTPUT -d 224.0.0.0/4 -j ACCEPT # Allow Forwarding on LAN interfaces -A FORWARD -i br0 -o br0 -d 192.168.1.0/24 -j ACCEPT # Allow Forwarding to WAN interface -A FORWARD -i eth0 -o eth1 -s 192.168.1.0/24 -j ACCEPT -A FORWARD -i wlan0 -o eth1 -s 192.168.1.0/24 -j ACCEPT # Allow established, related packets back through -A FORWARD -i eth1 -o eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT -A FORWARD -i eth1 -o wlan0 -m state --state ESTABLISHED,RELATED -j ACCEPT -A FORWARD -i eth1 -o eth0 -j LOG --log-prefix "IP[FWD-Reply]: " --log-level 7 -A FORWARD -i eth1 -o wlan0 -j LOG --log-prefix "IP[FWD-Reply]: " --log-level 7 # Only pings with restricted icmp are allowed -A INPUT -i eth1 -p icmp -j ALLOWED-ICMP # Enable TRACEroute to me -I INPUT -i eth1 -p udp -d 192.168.0.127 --sport 32769:65535 --dport 33434:33523 -j ACCEPT # Enable SSH to me -I INPUT -i eth1 -p tcp -d 192.168.0.127 --dport 22 -j ACCEPT # Log all other -A INPUT -j LOG --log-prefix "IP[IN]: " --log-level 7 -A FORWARD -j LOG --log-prefix "IP[FWD]: " --log-level 7 -A OUTPUT -j LOG --log-prefix "IP[OUT]: " --log-level 7 COMMIT <end /etc/sysconfig/iptables> I have several virtual machines which have configured the old NAT-router als gateway; they all work fine; one virtual machine (OS = Win7) has the new box configured as gateway with IP address 192.168.1.6 I have a old notebook (OS = WinXP) that is "connected" via WLAN to the new box and this has 192.168.1.4 as IP address; both can ping each other the VM and this notebook; here the questions: should I use eth0 and wlan0 or br0 in the iptables and ip6tables roules? why is it possible to ping the VM or the notebook from the new box, but not the other way? Thanks for any help; Greetings, Walter

1 0

Re: [CentOS] LSI SATA MegaRaid & Centos 7 build 1511
by Gordon Messmer 13 Aug '16

13 Aug '16

On 08/13/2016 02:15 AM, Fawzy Ibrhim wrote: > I have double checked again and yes it's Fakeraid from LSI. > Also it's not shown in "lspci -nn" output. In your original message, you indicated that this was a PCI card, but it looks like this is just a firmware component of your motherboard. I think you should assume that this firmware is unsupported. Set your SATA mode to AHCI in the BIOS, and then use "dmraid -r -E" to remove the RAID metadata from those disks: https://bugs.centos.org/view.php?id=9813 You should be able to install using Linux software RAID.

1 0

Re: [CentOS] Linux TCP flaw
by Andrew Dent 12 Aug '16

12 Aug '16

Would a successful attack on the IP address of a VPS in a Plesk environment expose the VPS, the Virtual Host or both (and all other VPSs)? ------ Original Message ------ From: "Johnny Hughes" <johnny(a)centos.org> To: centos(a)centos.org Sent: 12/08/2016 9:08:23 PM Subject: Re: [CentOS] Linux TCP flaw >On 08/12/2016 05:58 AM, Andrew Dent wrote: >> Thanks for the info Peter. >> The VPS is running on a Plesk environment. >> > >Right, and in a Plesk environment there is only one kernel on the main >machine, and all the VPS machines use it. So the hosting provider has >to make all kernel mods. > >

2 1

Firefox crashing
by ken 12 Aug '16

12 Aug '16

This morning, the Firefox (45.3.0) installed (upgrade) just a few days ago has crashed already a half dozen times. Anyone else having the same problem?

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss