February 2017 - Discuss - lists.centos.org

CentOS-announce Digest, Vol 144, Issue 7
by centos-announce-request＠centos.org 23 Feb '17

23 Feb '17

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-2017:0190 Critical CentOS 5 firefox Security Update (Johnny Hughes) 2. CESA-2017:0190 Critical CentOS 6 firefox Security Update (Johnny Hughes) 3. CESA-2017:0190 Critical CentOS 7 firefox Security Update (Johnny Hughes) 4. CESA-2017:0293 Important CentOS 6 kernel Security Update (Johnny Hughes) 5. CESA-2017:0294 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 22 Feb 2017 13:18:10 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0190 Critical CentOS 5 firefox Security Update Message-ID: <20170222131810.GA7707(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0190 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0190.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4f351259abd6614da05b1ea8e9e4b83486631cadb9aa439996c7070f9eff8588 firefox-45.7.0-2.el5.centos.i386.rpm x86_64: 4f351259abd6614da05b1ea8e9e4b83486631cadb9aa439996c7070f9eff8588 firefox-45.7.0-2.el5.centos.i386.rpm 1e2b1680b6c395039fafb267db3426fde8c4f2c06b2ba9744f11e18736d2917f firefox-45.7.0-2.el5.centos.x86_64.rpm Source: fb33febf301919266593261c3e79a43af3957012b04083b99dc89b5053990019 firefox-45.7.0-2.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 22 Feb 2017 13:20:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0190 Critical CentOS 6 firefox Security Update Message-ID: <20170222132044.GA45572(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0190 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0190.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f34f42fb0d7c2d68da3493786c3ea6db8a5c3025ec23c4920f33739466aee8c5 firefox-45.7.0-2.el6.centos.i686.rpm x86_64: f34f42fb0d7c2d68da3493786c3ea6db8a5c3025ec23c4920f33739466aee8c5 firefox-45.7.0-2.el6.centos.i686.rpm b905dbe1aeb129fcf9dfcdae0476003f4d6f5e73615762346badf37e76c3a43d firefox-45.7.0-2.el6.centos.x86_64.rpm Source: 98283468cf9d1e539fc7dfbe25e79160d9b9c631dd30d1fd4cef84d1fd64b573 firefox-45.7.0-2.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 22 Feb 2017 13:44:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0190 Critical CentOS 7 firefox Security Update Message-ID: <20170222134406.GA58643(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0190 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0190.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 38bdd177d609902c6d514deae731df1f6778409730fa61dd213ad0937d54223c firefox-45.7.0-2.el7.centos.i686.rpm 4ce5659c46dee0b5a25d4e6583e9d498b2d146a9ba33565d1c35a2b983766942 firefox-45.7.0-2.el7.centos.x86_64.rpm Source: 7db60cb74cd564e32e8e9341c8b1c80e032afa31acfe7c155d0a725a2c80126b firefox-45.7.0-2.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Thu, 23 Feb 2017 04:21:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0293 Important CentOS 6 kernel Security Update Message-ID: <20170223042138.GA3656(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0293 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0293.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8e5db1418cf0c4cc98c3b3f75c73ae681e6d1af6e6af960bc03f96dd38c444c6 kernel-2.6.32-642.13.2.el6.i686.rpm 7b7c0130f6d949dbab08c622d33d3a965189992d9f790d2422ab847f7524266a kernel-abi-whitelists-2.6.32-642.13.2.el6.noarch.rpm d34bf5af966a9598fa12736e7cae72c3a02da76332774123b0e16905f88d4e95 kernel-debug-2.6.32-642.13.2.el6.i686.rpm bcef4faf1884b67f02e7b5a046bfc28ddb9f3c2f5009e86afefe00123a8d74e8 kernel-debug-devel-2.6.32-642.13.2.el6.i686.rpm 2b2ca285b26e3b90eee5ac182fcb8588532fb882632304f8a21c3e78dbb9c4a2 kernel-devel-2.6.32-642.13.2.el6.i686.rpm 83bc6d344aff521bc6b5766347fec8f2ccb482330be746661624d5e76624616a kernel-doc-2.6.32-642.13.2.el6.noarch.rpm ca77321a113b1a089c61a9d053efc06063476a0a6aeb08c257a3fb58591e8feb kernel-firmware-2.6.32-642.13.2.el6.noarch.rpm 60fb671174abdfa8ed467ff6cd71cf8ecae26f06ed94e6cd8aaca6b3820f29d5 kernel-headers-2.6.32-642.13.2.el6.i686.rpm e1ddc8fce78af40b1202267e7bdbefbb01f7b8ad9a75d68e0e88587dc68b7d4c perf-2.6.32-642.13.2.el6.i686.rpm 70bbabecf85895e3d7a1fb2d3cc6ffeccdcf0bc664bd3d994670a05cf7c6e7f7 python-perf-2.6.32-642.13.2.el6.i686.rpm x86_64: d42ff04a27c00197952bb3b84c66891022fadff49b2a907039061189e648820c kernel-2.6.32-642.13.2.el6.x86_64.rpm 7b7c0130f6d949dbab08c622d33d3a965189992d9f790d2422ab847f7524266a kernel-abi-whitelists-2.6.32-642.13.2.el6.noarch.rpm eebf181ae2c9217b4a65831903298e74454c11788ff3c4b66d66796f0d539736 kernel-debug-2.6.32-642.13.2.el6.x86_64.rpm bcef4faf1884b67f02e7b5a046bfc28ddb9f3c2f5009e86afefe00123a8d74e8 kernel-debug-devel-2.6.32-642.13.2.el6.i686.rpm 6224f08bbc8ec073385e4d9c6a4d18d1689e9914b44710214660d37a1725e4bf kernel-debug-devel-2.6.32-642.13.2.el6.x86_64.rpm af93fee2aa92ca20fc2b2a88415b9abeb1a4d8bb348f694216d7a3eaf07f7d61 kernel-devel-2.6.32-642.13.2.el6.x86_64.rpm 83bc6d344aff521bc6b5766347fec8f2ccb482330be746661624d5e76624616a kernel-doc-2.6.32-642.13.2.el6.noarch.rpm ca77321a113b1a089c61a9d053efc06063476a0a6aeb08c257a3fb58591e8feb kernel-firmware-2.6.32-642.13.2.el6.noarch.rpm 49e71d4eb8403a790910ad73529e72a52971ba0aebbe07dac25172946e94f200 kernel-headers-2.6.32-642.13.2.el6.x86_64.rpm 5b0d68de2c859691712276038c2640da96aeec17754b0aa5d0ffbd0fc2013261 perf-2.6.32-642.13.2.el6.x86_64.rpm 0455e0f63e3966926a1bbf0bd7882b90a67db437ad2e63b38800d8b6aa94c4be python-perf-2.6.32-642.13.2.el6.x86_64.rpm Source: 888ead19200985f6ad2a8f8fd53336e57b695ceb0ae47c026f82a28f67f70e7c kernel-2.6.32-642.13.2.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Thu, 23 Feb 2017 05:45:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0294 Important CentOS 7 kernel Security Update Message-ID: <20170223054533.GA18280(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0294 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0294.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 399d85490609511d4f57270f4db2ae22aff1e77dbfb9fa1735f3acd74a32b15d kernel-3.10.0-514.6.2.el7.x86_64.rpm ade938b455c925303441ff53433c55c4507501c34537a8dac3267f2027ac70a9 kernel-abi-whitelists-3.10.0-514.6.2.el7.noarch.rpm b9cbfd11d08961b8c9c78e82e669693b33063f7e5c5cd4835f17403e7a8adfd4 kernel-debug-3.10.0-514.6.2.el7.x86_64.rpm f845b17f3955c7e37c80ae44810c623e5e8679159395eb71374e3f081dbf8695 kernel-debug-devel-3.10.0-514.6.2.el7.x86_64.rpm b7fe4fc10de18db85e12d32dcb702229ed2fb3137e7cee784f5a15a2459f5db2 kernel-devel-3.10.0-514.6.2.el7.x86_64.rpm d2043d02d55f4189e3462149fbe80f8e281170d07acd5f4153636fdec89ab3c5 kernel-doc-3.10.0-514.6.2.el7.noarch.rpm 5849bd28663d4c8a112121b13c19b10b2f43decfc3a1bc3b4246227a3e255297 kernel-headers-3.10.0-514.6.2.el7.x86_64.rpm 640ba1792316b03339098f76f3bab13d2ca79a1f309122df21c3bf85ccba90e4 kernel-tools-3.10.0-514.6.2.el7.x86_64.rpm 8e9dd3262234c4d1cd6bb1cfe591111189bba8282e56cf284c5086c5977c7f96 kernel-tools-libs-3.10.0-514.6.2.el7.x86_64.rpm 35d8fee07d663665c297c3d6bd4dc623afc6fcae7bde1f09be88d4773a2837f9 kernel-tools-libs-devel-3.10.0-514.6.2.el7.x86_64.rpm c416658118df7791b9b8eb4fe9fbf941e1cb2005fd91b7f80b29232bf3b1aa7b perf-3.10.0-514.6.2.el7.x86_64.rpm 14c06f8de0921bd9a671feff1813b6af0c58a75fbe5f47ef92e4e6324c6c7249 python-perf-3.10.0-514.6.2.el7.x86_64.rpm Source: 19b33fba0c0c2c8eb838fcb65983c7dadc1c67b42c9b72e7dcd271d2c7b73572 kernel-3.10.0-514.6.2.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 144, Issue 7 ***********************************************

1 0

BOINC
by Alessandro Baggi 23 Feb '17

23 Feb '17

Hi list, I've installed boinc-client and boinc-manager from epel. After starting boinc-client with systemctl when I try to connect from boincmgr I get "Unable to connect to boinc client". I've added to unit file --allow_remote_gui_rpc and on netstat I get: tcp 0 0 0.0.0.0:31416 0.0.0.0:* LISTEN 4762/boinc_client On this machine there aren't iptables rules I've also added my current user to boinc group without success. I've tried also to run boincmgr from root without success. Reading from https://boinc.berkeley.edu/wiki/Client_configuration I've not found any usefull config parameters to save in /var/lib/boinc/cc_config.xml Selinux is Disabled. I've tried also to run from a root shell: /usr/bin/boinc_client Running the manager from root I can connect to the client but from simple user I cannot. So I don't understand where is the problem. What I can do to solve this problem? Thanks in advance.

2 3

Re: [CentOS] Network conections problems
by Rommel Rodriguez Toirac 23 Feb '17

23 Feb '17

El 21 de febrero de 2017 7:00:03 GMT-05:00, centos-request(a)centos.org escribió: >Send CentOS mailing list submissions to > centos(a)centos.org > > >From: Kahlil Hodgson <kahlil.hodgson(a)dp.exchange> >To: CentOS mailing list <centos(a)centos.org> >Subject: Re: [CentOS] Network conections problems > >First guess is that you may have two devices on the network with the >same ip address. > >Next time this happens, try doing > >1. 'arp -n' from a machine other than the db server >2. ping the other machine from the db server, then >3. 'arp -n' from the other machine > >Compare the outputs of the two invocations of arp. If the outputs show >different MAC addresses for 192.168.41.4 then you have two different >devices with the same IP address. > > I resolve the problem of network conection loose, but still a dude of how it happend and how it can be fixe. When I check with arping the MAC of sever change, for example rommel@p6:~$ arping 192.168.41.4 ARPING 192.168.41.4 from 192.168.41.6 enp3s0 Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.653ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.683ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.622ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.631ms ^CSent 3 probes (1 broadcast(s)) Received 4 response(s) The first answer is with a MAC diferent to the others one. But when I arping from the server inseft look the MAC associate to de IP address: [root@pgtm ] arping 192.168.41.4 -I eth1 ARPING 192.168.41.4 from 192.168.41.4 eth1 Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.658ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.654ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.654ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.662ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.655ms Sent 5 probes (1 broadcast(s)) Received 5 response(s) Looking in the config of network device I can not find the MAC 00:1D:09:FF:44:4B [root@pgtm ] ifconfig eth0 Link encap:Ethernet HWaddr 6C:92:BF:26:C7:02 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) Memory:c7220000-c723ffff eth1 Link encap:Ethernet HWaddr 6C:92:BF:26:C7:03 inet addr:192.168.41.4 Bcast:192.168.41.255 Mask:255.255.255.0 inet6 addr: fe80::6e92:bfff:fe26:c703/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:95819 errors:0 dropped:0 overruns:0 frame:0 TX packets:1924 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11728605 (11.1 MiB) TX bytes:263674 (257.4 KiB) Memory:c7200000-c721ffff eth2 Link encap:Ethernet HWaddr 00:E0:ED:33:4E:9C 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) Memory:c7120000-c713ffff eth3 Link encap:Ethernet HWaddr 00:E0:ED:33:4E:9D 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) Memory:c7100000-c711ffff 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:249609 errors:0 dropped:0 overruns:0 frame:0 TX packets:249609 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:52090343 (49.6 MiB) TX bytes:52090343 (49.6 MiB) The solution was another IP address to this network device and then everything work fine. Why this happend? How I can erase the link beteewn MAC 00:1D:09:FF:44:4B and IP 192.168.41.4? Where can be stored this link? Right now in the network is not assignet the IP address 192.168.41.4 to no one device (printserver, switch, router, workstation or server) and still whe I make arping have the answer: rommel@p6:~$ arping 192.168.41.4 ARPING 192.168.41.4 from 192.168.41.6 enp3s0 Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.631ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.623ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.623ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.691ms ^CSent 4 probes (1 broadcast(s)) Received 4 response(s) arping to the new server IP address look like this (this is the MAC of eth0, where a plug the network cable): rommel@p6:~$ arping 192.168.41.7 ARPING 192.168.41.7 from 192.168.41.6 enp3s0 Unicast reply from 192.168.41.7 [6C:92:BF:26:C7:02] 0.580ms Unicast reply from 192.168.41.7 [6C:92:BF:26:C7:02] 0.607ms Unicast reply from 192.168.41.7 [6C:92:BF:26:C7:02] 0.613ms Unicast reply from 192.168.41.7 [6C:92:BF:26:C7:02] 0.594ms ^CSent 4 probes (1 broadcast(s)) Received 4 response(s) Rommel Rodriguez Toirac rommelrt(a)nauta.cu

3 3

question about directory size in linux..
by Jason Welsh 23 Feb '17

23 Feb '17

on a CentOS release 6.8 (Final) I was looking around and noticed the following in a directory. [jason@server /app-vol/applications/]$ls -ld temp drwxr-xr-x 4 jason users 2899968 Feb 18 06:31 temp/ [jason@server /app-vol/applications/]$ How does the directory *itself* have a size of 2.8 megs? yes the contents in that temp directory add up to 2.8 megs, but.. umm. huh? when I run a stat on the temp directory, i get File: `temp' Size: 2899968 Blocks: 5672 IO Block: 4096 directory Device: fd02h/64770d Inode: 1836137 Links: 4 Access: (0755/drwxr-xr-x) Uid: ( 1022/ jason) Gid: ( 501/ users) Access: 2017-02-22 06:31:51.414190071 -0500 Modify: 2017-02-18 06:31:56.135448424 -0500 Change: 2017-02-18 06:31:56.135448424 -0500 on other "normal" directories, I see something like Size: 4096 Blocks: 8 IO Block: 4096 directory Jason

6 12

Re: [CentOS] Network conections problems
by Istimsak Abdulbasir 23 Feb '17

23 Feb '17

On Feb 20, 2017 2:42 PM, "Rommel Rodriguez Toirac" <rommelrt(a)nauta.cu> wrote: Hi; I have a CentOS 6.8 x86_64 server where just run Oracle 11g 64 bit data base server. Is happen that sometimes it loose all connections (no ping, I can not access via ssh, no TNSping of Oracle server have success). When this happend I make ping from this server to some IP address of my network and then everything work fine again. I check logs looking for some mistake or problem in the network device, but I do not find anything or maybe I not looking where must be. I check that from a workstation (Windows XP or Windows 7 or Windows 10) when I make ping to the server, after ~ 8 seconds in get answer and always the first one is loose. If you try again ping, everything work fine (no answers are loose) C:\Users\administrator>ping pgtm.gtm.gob.cu Haciendo ping a pgtm.gtm.gob.cu [192.168.41.4] con 32 bytes de datos: Tiempo de espera agotado para esta solicitud. Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Estadísticas de ping para 192.168.41.4: Paquetes: enviados = 4, recibidos = 3, perdidos = 1 (25% perdidos), Tiempos aproximados de ida y vuelta en milisegundos: Mínimo = 0ms, Máximo = 0ms, Media = 0ms This are some of the configs related with networks [root@pgtm ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 TYPE=Ethernet UUID=11dcddd4-6530-457a-8d3e-01a8339fb113 ONBOOT=yes NM_CONTROLLED=yes BOOTPROTO=none HWADDR=6C:92:BF:26:C7:02 IPADDR=192.168.41.4 PREFIX=24 GATEWAY=192.168.41.1 DNS1=192.168.41.17 DOMAIN=gtm.gob.cu DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth0" L I noticed from your ipcfg-eth0 file, the address 192.168.41.1 is assigned to eth0. When you typed the command "ifconfig", that same address was assigned to eth1. Try changing the name of this file to ipcfg-eth1 and restart networkmanager. As was stated earlier, check your gateway and see what other devices could be using that address. Put a block on that unknown MAC address if you can. cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.41.4 pgtm pgtm.gtm.gob.cu [root@pgtm ~]# cat /etc/resolv.conf # Generated by NetworkManager search gtm.gob.cu nameserver 192.168.41.17 [root@pgtm mail]# cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=pgtm.gtm.gob.cu GATEWAY=192.168.41.1 Someone that happend something like this, or some place for where keep looking to try to fix this loose of conection? Thank and sorry for my horryble English. Rommel Rodriguez Toirac rommelrt(a)nauta.cu _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] how to resize a partition of a disk define as a physical volume
by Istimsak Abdulbasir 22 Feb '17

22 Feb '17

On Feb 22, 2017 7:45 AM, "Bernard Fay" <bernard.fay(a)gmail.com> wrote: Hello, I have a CentOS VM with only one disk on a Xenserver. The disk has 2 partitions: /dev/xvda1 -> /boot /dev/xvda2 -> a physical volume for LVM I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I just have to do "pvresize /dev/xvda" to have the additional space added to the disk. But for some reason it does not work for this disk. [root ~]# pvresize /dev/xvda Failed to find physical volume "/dev/xvda". 0 physical volume(s) resized / 0 physical volume(s) not resized K Xvda does not seem to be read as an LVM volume. Xvda2 is handled by lvm so this can be resized. However xvda is just the harddrive itself. From what I have learned using lvm briefly, you can only resize lvm volumes or partitions created using lvm. [root ~]# pvresize /dev/xvda2 Physical volume "/dev/xvda2" changed 1 physical volume(s) resized / 0 physical volume(s) not resized Does someone have seen this problem before or could have an idea of the problem? Thanks, Bernard _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

how to resize a partition of a disk define as a physical volume
by Bernard Fay 22 Feb '17

22 Feb '17

Hello, I have a CentOS VM with only one disk on a Xenserver. The disk has 2 partitions: /dev/xvda1 -> /boot /dev/xvda2 -> a physical volume for LVM I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I just have to do "pvresize /dev/xvda" to have the additional space added to the disk. But for some reason it does not work for this disk. [root ~]# pvresize /dev/xvda Failed to find physical volume "/dev/xvda". 0 physical volume(s) resized / 0 physical volume(s) not resized [root ~]# pvresize /dev/xvda2 Physical volume "/dev/xvda2" changed 1 physical volume(s) resized / 0 physical volume(s) not resized Does someone have seen this problem before or could have an idea of the problem? Thanks, Bernard

6 8

Centos7 Postfixadmin with SELInux
by Robert Moskowitz 22 Feb '17

22 Feb '17

Anyone here running Postfixadmin on Centos7 with SELinux? The config.inc.php script has lots of warning comments about what you will have to do to get functions to work with SELinux, but does not supply any policy rules. I am still configuring, and so far I have only done: chcon -R -t httpd_sys_content_rw_t /usr/share/postfixadmin/templates_c (thanks Daniel) I suspect here are more so it can do things like create directories and files in the mail store (e.g. /home/vmail/). Oh my current server is running without SELinux (shutter) and that is one of the many reasons I want to upgrade. Bob

1 0

Problems with my simple write conf files method
by Robert Moskowitz 22 Feb '17

22 Feb '17

I have been creating conf files and similar with the following method that I picked up (I think from psotfix docs): cat <<EOF>>/etc/aliases || exit 1 root: youremail EOF See: http://medon.htt-consult.com/Centos7-armv7.html But with postfixadmin I stumbled onto a problem. The following: cat <<EOF>/usr/share/postfixadmin/config.local.php || exit 1 <?php $CONF['database_type'] = 'mysqli'; $CONF['database_user'] = 'postfix'; $CONF['database_password'] = 'xyz'; $CONF['database_name'] = 'postfix'; $CONF['configured'] = true; ?> EOF produces: cat <<EOF>/usr/share/postfixadmin/config.local.php || exit 1 <?php ['database_type'] = 'mysqli'; ['database_user'] = 'postfix'; ['database_password'] = 'xyz'; ['database_name'] = 'postfix'; ['configured'] = true; ?> That is the '$CONF' gets processed. What can I do to avoid this (and any other 'gotchas') or can someone provide an alternative? thanks

3 5

CentOS-announce Digest, Vol 144, Issue 6
by centos-announce-request＠centos.org 22 Feb '17

22 Feb '17

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-2017:0286 Moderate CentOS 6 openssl Security Update (Johnny Hughes) 2. CESA-2017:0286 Moderate CentOS 7 openssl Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 Feb 2017 11:44:42 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0286 Moderate CentOS 6 openssl Security Update Message-ID: <20170221114442.GA16750(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0286 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0286.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 168bc525c268d07b3fae14e4ba66dd7c6d9561f7789700feba0eeaf6951ff4e8 openssl-1.0.1e-48.el6_8.4.i686.rpm 765eff4b25e944dbadcd3523f89adb1b29f76337ff395cd5431c934dafd0cede openssl-devel-1.0.1e-48.el6_8.4.i686.rpm e5c04361a9531c903afde3b8876fe0dfb12520d70e5446f515750e98735aba7d openssl-perl-1.0.1e-48.el6_8.4.i686.rpm 57edfc2de0dbf1bf058e65898d500a725bd9c31cea6244a7e93af01c7776077d openssl-static-1.0.1e-48.el6_8.4.i686.rpm x86_64: 168bc525c268d07b3fae14e4ba66dd7c6d9561f7789700feba0eeaf6951ff4e8 openssl-1.0.1e-48.el6_8.4.i686.rpm f0b991e41e0a9d5d20ff60d1a7b5833a6f1cde6ed59bfdfab9a275d6d338b28e openssl-1.0.1e-48.el6_8.4.x86_64.rpm 765eff4b25e944dbadcd3523f89adb1b29f76337ff395cd5431c934dafd0cede openssl-devel-1.0.1e-48.el6_8.4.i686.rpm 6ebd15c228500784541fd778413348129c61c2af6249fd7043ef13c10c93bd60 openssl-devel-1.0.1e-48.el6_8.4.x86_64.rpm d9a31c566a6df0c15671c32e96abd64d8f0f906dc05ae995a2c57a64b70fa341 openssl-perl-1.0.1e-48.el6_8.4.x86_64.rpm 502e6c723c15b0aaf13bdb7a0faf6b647fcf953318e1782b6df3a2b2de323ff3 openssl-static-1.0.1e-48.el6_8.4.x86_64.rpm Source: dca305112f97f7c9a4c084e33901ffcd745bf260b8e1466fd9307eb819d388a9 openssl-1.0.1e-48.el6_8.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 21 Feb 2017 12:48:27 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0286 Moderate CentOS 7 openssl Security Update Message-ID: <20170221124827.GA30499(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0286 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0286.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 642eb35daa25ae290bd3922e7876ac5d61744cb56c0d3f7877e76320b99a8f59 openssl-1.0.1e-60.el7_3.1.x86_64.rpm 36fa878db932143ea4c107acb2deb34f78a9e7cb9159384b767f0932a27662d6 openssl-devel-1.0.1e-60.el7_3.1.i686.rpm 6d5b7f68f5cc4446092ab2c3502df813b0145a4186e654f22d241ca9a88f79c3 openssl-devel-1.0.1e-60.el7_3.1.x86_64.rpm 75afa599c87b32683162c976a3f7245767b1612b6fc1c1f935c41bcaaab71b8d openssl-libs-1.0.1e-60.el7_3.1.i686.rpm d3354df1c13897870b20407aed7b3eb1ee581b0e1f4af4bcd920fa57914202ca openssl-libs-1.0.1e-60.el7_3.1.x86_64.rpm 89aef81712ce7a139e59aa0e594db2c3bb03ba9f6bc2e161debb43705dee67a7 openssl-perl-1.0.1e-60.el7_3.1.x86_64.rpm a1af544918add7dbc76be337f395a816e1f3b0d7bae42fb0a6c812f8636c6f1d openssl-static-1.0.1e-60.el7_3.1.i686.rpm 8f7129a44f28934985e1b00ccec2a0c80271018a038afab49e23e22576c7d47c openssl-static-1.0.1e-60.el7_3.1.x86_64.rpm Source: 976eaf61e1cbe2ac4bf32a440a5697dc19be59fd1b275bb314fda8888c3340a4 openssl-1.0.1e-60.el7_3.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 144, Issue 6 ***********************************************

1 0

usermod under CentOS
by Beartooth 21 Feb '17

21 Feb '17

My wife's PC, running CentOS 6, suddenly quit connecting to the Net. Autodidact that I am, I fumbled with all the hard- and software I could find or dared try, but did no good. So we lugged it down to our favorite shop. While there, she bought a laptop, and asked them to install CentOS and copy all her files from the PC (including two books she's written and is trying to market). They called to ask whether I wanted to specify a username & password, or just use their default dummies. I chose the dummies -- and realized in the night that I've never changed a username before. I think, repeat think, I could hack it with mv and chown, but I had enough sense to try a few manuals and duckduckgo searches. Those eventually led me to usermod, and I took a look at 'man usermod'. It seems to be fairly powerful -- and therefore dangerous as well as apposite. So I ask here: are there caveats, gotchas, and/or other entities of their ilk that I need be wary of? -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is.

3 2

Centos7: Intel nuc/Linksys usb-ethernet
by johan.vermeulen7＠telenet.be 21 Feb '17

21 Feb '17

Hello All, I'm installing some DIY routers, composed of Intel nuc's ,Linksys usb-ethernet adapters and Centos7 On most machines I just plug in the usb device, install Centos7 and everything works. But on this one machine the network interface doesn't work. After installing ip addr shows: [root@clgmol ~]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether f4:4d:30:64:21:bb brd ff:ff:ff:ff:ff:ff inet 192.168.80.189/25 brd 192.168.80.255 scope global dynamic enp3s0 valid_lft 431sec preferred_lft 431sec inet6 fe80::f64d:30ff:fe64:21bb/64 scope link valid_lft forever preferred_lft forever 3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether b8:81:98:9f:8f:1c brd ff:ff:ff:ff:ff:ff 4: enp0s20u3c2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 14:91:82:3b:7b:b9 brd ff:ff:ff:ff:ff:ff [root@clgmol ~]# dmesg | tail -n15 [ 10.582462] Bluetooth: hci0: Intel device is already patched. patch num: 25 [ 10.770781] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd [ 10.782704] usb 2-3: New USB device found, idVendor=13b1, idProduct=0041 [ 10.782728] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 10.782745] usb 2-3: Product: Linksys USB3GIGV1 [ 10.782759] usb 2-3: Manufacturer: Linksys [ 10.782772] usb 2-3: SerialNumber: 000001000000 [ 10.787858] cdc_ether 2-3:2.0 eth0: register 'cdc_ether' at usb-0000:00:14.0-3, CDC Ethernet Device, 14:91:82:3b:7b:b9 [ 14.140292] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 14.175958] Netfilter messages via NETLINK v0.30. [ 14.178428] ctnetlink v0.93: registering with nfnetlink. [ 14.350689] ipt_ULOG: ULOG: fail to register logger. [ 15.192593] ipt_ULOG: ULOG: fail to register logger. I create /etc/sysconfig/network-scripts/ifcfg-enp0s20u3c2 using the hardware address from ip addr en uuid created with uuidgen but I don't understand why it's not created on install: TYPE=Ethernet BOOTPROTO=static DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=enp0s20u3c2 UUID=a728528c-0be7-49bc-9478-05743a285a7d DEVICE=enp0s20u3c2 ONBOOT=yes PEERDNS=yes PEERROUTES=yes NM_CONTROLLED=no HWADDR=14:91:82:3b:7b:b9 IPADDR=192.168.70.1 NETMASK=255.255.255.0 Next I cannot launch the network: [root@clgmol ~]# systemctl status network ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Active: failed (Result: exit-code) since di 2017-02-21 20:57:56 CET; 15s ago Docs: man:systemd-sysv-generator(8) Process: 2638 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) CGroup: /system.slice/network.service └─1076 /sbin/dhclient -H clgmol -1 -q -lf /var/lib/dhclient/dhclient-13b56b89-7b1d-42fa-aeb7-af96a38102ce-enp3s0.lease -pf /var/run/dhclient-enp3s0.pid en... feb 21 20:57:56 clgmol.router network[2638]: RTNETLINK answers: File exists feb 21 20:57:56 clgmol.router network[2638]: RTNETLINK answers: File exists feb 21 20:57:56 clgmol.router network[2638]: RTNETLINK answers: File exists feb 21 20:57:56 clgmol.router network[2638]: RTNETLINK answers: File exists feb 21 20:57:56 clgmol.router network[2638]: RTNETLINK answers: File exists feb 21 20:57:56 clgmol.router network[2638]: RTNETLINK answers: File exists feb 21 20:57:56 clgmol.router systemd[1]: network.service: control process exited, code=exited status=1 feb 21 20:57:56 clgmol.router systemd[1]: Failed to start LSB: Bring up/down networking. feb 21 20:57:56 clgmol.router systemd[1]: Unit network.service entered failed state. feb 21 20:57:56 clgmol.router systemd[1]: network.service failed. [root@clgmol ~]# ifup enp0s20u3c2 arping: recvfrom: Netwerk ligt plat RTNETLINK answers: Network is down I disabled NetworkManager I tried with another Linksys device and I reinstalled and started over. Why does it work with other devices and not with this one? Many thanks for any advise. Greetings, J

2 1

Centos 7 with Postfixadmin, what provides php5-mysql
by Robert Moskowitz 21 Feb '17

21 Feb '17

I am building a Centos7 mailserver to replace my Centos6 server. This means moving to Apache 2.4 and MariaDB, so I am finding a number of changes from my notes. I now have MariaDB running with the databases created and Apache running. I try accessing postfixadmin and get: DEBUG INFORMATION: MySQL 4.1 functions not available! (php5-mysqli installed?) database_type = 'mysqli' in config.inc.php, are you using a different database? Please check the documentation and website for more information. ================= mysqli is what the config.inc.php says to use for // mysqli = MySQL 4.1+ or MariaDB I installed httpd mod_ssl php mariadb-server Thanks for any help on this.

1 1

SELInux conflict with Postfixadmin
by Robert Moskowitz 21 Feb '17

21 Feb '17

postfixadmin setup.php is claiming: *Error: Smarty template compile directory templates_c is not writable.* *Please make it writable.* *If you are using SELinux or AppArmor, you might need to adjust their setup to allow write access.* This goes away with 'setenforce 0', so it is an SELinux issue. I have tried both: restorecon -Rv /usr/share/postfixadmin and chcon -R -t httpd_sys_content_t /usr/share/postfixadmin and they are not the problem. Googling this message doe snot produce any SELinux advice. Any ideas? thanks

3 5

movie player vs. mp3
by Michael Hennebry 21 Feb '17

21 Feb '17

I have movie player installed on centos 6. When I try to play an mp3 file, it complains about the lack of a codec, mpeg-1 something 3. google hasn't helped. What package do I need? Trying to install ffmpeg gets me a no such package message. I've dealt with codec issues before. Mostly what I remember is that before I was done, I wanted to kill something. -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

4 5

that ever puzzling special chars escaping + rdiff-backup
by lejeczek 21 Feb '17

21 Feb '17

hi everyone a good basher around here? I try in a script: _rdiffBack="rdiff-backup -v5 --tempdir /tmp/ --no-eas --exclude-other-filesystems --exclude-symbolic-links" _rdffiExclude="--exclude '**/~*' --exclude '**.tmp' --exclude-regexp '(.glusterfs|.trashcan|temp)'" _execCom=${!2} _sourceDir=${1} _backupTo=${3} __backMeUp() { for _sourceDir in ${_sourceDirs[@]}; do echo \$ ${_execCom} ${_rdffiExclude} ${_sourceDir}/ ${_backupTo} \> ${_logFile} | ${_copyToLog} ${_execCom} ${_rdffiExclude} ${_sourceDir}/ ${_backupTo} > ${_logFile} 2>&1 done } case ${1} in rdiffThis) declare -a _sourceDirs=( /0-ALL.DATA/rdiffThis ); __backMeUp ${@} ;; esac this is a snippet which may look obscure but obvious is: rdiff-backup some data, just that. And when I run it as a script ~]$ runme.sh rdiffThis _rdiffBack toHere I see: Fatal Error: Fatal Error: The file specification ''**' cannot match any files in the base directory You notice that the script echos what it is meant to execute, which suffice I copy&paste that echo in bash prompt... and it works!? No "Fatal Error" And the problem seems to specifically be a shell pattern for --exclude. Take two --exclude out, having: _rdffiExclude="--exclude-regexp '(.glusterfs|.trashcan|temp)'" and script works when invoked, fine! I've been fiddling around but failed to make rdiff-backup 1.2.8 play along. Must be something trivial, right? b.w. L

1 1

Latest CentOS-7 image on cloud.centos.org has incorrect checksum
by Jared Baker 21 Feb '17

21 Feb '17

Good day, I initially posted this issue on CentOS-mirror a week ago but did not receive any response. I'm looking for a resolution to a small issue with the cloud image repository for the latest CentOS-7 image. As far as I understand, the latest release of the CentOS-7 image should always be posted to http://cloud.centos.org/centos/7/images/CentOS-7-x86_ 64-GenericCloud.qcow2 The checksum of this file should match the highest numbered version of the cloud image listed in http://cloud.centos.org/centos/7/images/sha256sum.txt However, the actual checksum for CentOS-7-x86_64-GenericCloud.qcow2 is returning as b56ed1a3a489733d3ff91aca2011f8720c0540b9aa27e46dd0b4f575318dd1fa which matches for CentOS-7-x86_64-GenericCloud-1608.qcow2 but NOT CentOS-7-x86_64-GenericCloud-1612.qcow2. The latest image available should be CentOS-7-x86_64-GenericCloud-1612.qcow2 with a checksum of 559bebb4abb2fdf3bd88c917cc11ef b1975bfe4494e666d133a3148ec4e6225d. To further the confusion, the 'Last modified' image is CentOS-7-x86_64-GenericCloud-1611.qcow2 and not -1612. I picked up on this discrepancy because I have a script that monitors & updates our openstack images when new images become available for various distributions. If someone could please correct these inconsistencies it would be greatly appreciated. Thanks, Jared Baker

3 2

centos-openshift-origin
by Vedran.Bartonicek＠tieto.com 21 Feb '17

21 Feb '17

?Hi, Would someone know when to expect to have package origin-master.1.4.0 in repo centos-openshift-origin? Right now the package is available in centos-openshift-origin-testing. -Vedran

2 2

Network conections problems
by Rommel Rodriguez Toirac 20 Feb '17

20 Feb '17

Hi; I have a CentOS 6.8 x86_64 server where just run Oracle 11g 64 bit data base server. Is happen that sometimes it loose all connections (no ping, I can not access via ssh, no TNSping of Oracle server have success). When this happend I make ping from this server to some IP address of my network and then everything work fine again. I check logs looking for some mistake or problem in the network device, but I do not find anything or maybe I not looking where must be. I check that from a workstation (Windows XP or Windows 7 or Windows 10) when I make ping to the server, after ~ 8 seconds in get answer and always the first one is loose. If you try again ping, everything work fine (no answers are loose) C:\Users\administrator>ping pgtm.gtm.gob.cu Haciendo ping a pgtm.gtm.gob.cu [192.168.41.4] con 32 bytes de datos: Tiempo de espera agotado para esta solicitud. Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Estadísticas de ping para 192.168.41.4: Paquetes: enviados = 4, recibidos = 3, perdidos = 1 (25% perdidos), Tiempos aproximados de ida y vuelta en milisegundos: Mínimo = 0ms, Máximo = 0ms, Media = 0ms This are some of the configs related with networks [root@pgtm ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 TYPE=Ethernet UUID=11dcddd4-6530-457a-8d3e-01a8339fb113 ONBOOT=yes NM_CONTROLLED=yes BOOTPROTO=none HWADDR=6C:92:BF:26:C7:02 IPADDR=192.168.41.4 PREFIX=24 GATEWAY=192.168.41.1 DNS1=192.168.41.17 DOMAIN=gtm.gob.cu DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth0" cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.41.4 pgtm pgtm.gtm.gob.cu [root@pgtm ~]# cat /etc/resolv.conf # Generated by NetworkManager search gtm.gob.cu nameserver 192.168.41.17 [root@pgtm mail]# cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=pgtm.gtm.gob.cu GATEWAY=192.168.41.1 Someone that happend something like this, or some place for where keep looking to try to fix this loose of conection? Thank and sorry for my horryble English. Rommel Rodriguez Toirac rommelrt(a)nauta.cu

2 1

Re: [CentOS] usb drives & Orico ORICO 9548U3-BK
by tdukes＠palmettoshopper.com 20 Feb '17

20 Feb '17

> -----Original Message----- > From: CentOS [mailto:centos-bounces@centos.org] OnBehalf Of Gregory P. > Ennis > Sent: Sunday, February 19, 2017 12:31 PM > To: centos(a)centos.org > Subject: Re: [CentOS] usb drives & Orico ORICO9548U3-BK > > > > > > I decided to build an archive server for thepurpose of backing up > > other fedora/centos desktops at theoffice. I built a machine and > > have installed Centos 7.3 on it with all updatescurrent. I also > > purchased a 3.0 usb sata drive cabinet (OricoORICO 9548U3-BK) and > > installed two 5T black WDdrives. There was no problem installing > > the usb cabinet or the drives. Iformatted each drive with xfs as > > /dev/sdc and /dev/sdd, and then combined theminto a software mirrored > > raid with mdadm as /dev/md0. > > I've always thought that the perceived wisdom is tonot try and do software > raid across USB - especially when both drives are atthe other end of the > same USB cable. Sure USB 3 is faster and there's abetter chance it will appear > to work at a reasonable speed, but it's notsomething I would contemplate. > > > > > Everything was working perfectly until Iremoved the terminal, > > keyboard and mouse and tried to reboot themachine. It took a while > > to figure out, but when the mouse and keyboardwere removed the boot > > process assigns the usb drives differentlywhich makes /dev/md0 > > created by mdadm fail. > > Which means that the drive letters are explicitlymentioned in > /etc/mdadm.conf - you can change it to be wildcardedor leave mdadm to > figure it all out itself. See 'manmdadm.conf'. > > > > > My fstab file looks like : > > > > /dev/mapper/centos_poar-root / xfs defaults 0 > > 0 > > UUID=f915a354-28bf-4110-bec9-3767ef1fe52c/boot xfs defaults 0 > > 0 > >/dev/mapper/centos_poar-home /home xfs defaults 0 > > 0 > >/dev/mapper/centos_poar-u /u xfs defaults 0 > > 0 > >/dev/mapper/centos_poar-swap swap swap defaults 0 > > 0 > >/dev/sda /u0 btrfs defaults 0 > > 0 > > # entries below were combined into one mirroredraid system > #/dev/sdc > >/u1 xfs defaults 0 > > 0 > >#/dev/sdd /u2 xfs defaults 0 > > 0 > >/dev/md0 /u1 xfs defaults 0 > > 0 > > Another likely issue is that you explicitly mention/dev/sda in the fstab - if the > drives are re-ordered, then /dev/sda will not bewhat you think it is. It's a > much better idea to use UUIDs when mounting drives.You can find the UUID > with > > lsblk --fs /dev/sda > > BTW, are you really using partitionless disks - isit really /dev/sda and not > /dev/sda1 ? > > > > > > > This works perfectly when a usb mouse and a usbkeyboard are attached, > > but when I remove the mouse and keyboard thesystem will not boot > > because the usb drives are relabeled as/dev/sda and /dev/sdb. > > I would have thought that any SATA drives would havebeen processed > before the USB drives - certainly it looks that wayon my system. Try going > through the output of dmesg to see if you can seewhat is really happening > when in the boot sequence. > > > > > > > My thought is that if I could force the usbdrives to be labeled as > > /dev/sdc and /dev/sdd whether the mouse andkeyboard are attached or > > not, I might be able to fix the problem > > It's much easier to make sure you don't explicitlyuse drive letters - because, > as you've found out, they can change. Usefilesystem labels or UUIDs or disk > IDs. The disk IDs can be found in /dev/disk/by-idand they should remain the > same. > > P. > >----------------------------------------------------------------- > > Pete, > > Thank you for such excellent help; I appreciate yourwisdom and challenges. > The machine I am working on is still at the 'lab'stage so everything can be > changed at this point. I don't have the benefit of much 'perceivedwisdom' in > that most of my knowledge comes from mistakes I havemade or mistakes > others on this list have made that Ican learnfrom. So thanks again. > > Here are some of my thoughts... right or wrong. > > #1. 3.0 USB drives > I originally performed some testing on a small usbpassport 3T drive and was > amazed by the response and access times. I stumbled across the Orico > cabinet during a NewEgg search, and decided to giveit a try. I was even > more impressed with the response and accesstimes. I decided to attempt a > mdadm raid on the the Orico and everything hasworked better than > expected except for the problems I have had withdevice > assignments. I did have an electrical failure at my home related to > weather of which the ups powered down after 30minutes that caused one > of the raid 5T drives to become corrupted. I reformatted the drive and > rebuilt the raid with mdadm, and everything worked alot better than I > expected. Iwill only be using this system to store *.tar.gz backup files from > other systems. What should cause me to fear the USB 3.0 connection. > > #2. /etc/mdadm.conf > The tutorials I read about how to use mdadm did notinclude mdadm.conf, > and this was not created when I installedmdadm. I will take a look at the > man pages.... thank you. > > #3. UUID's > Thanks for the suggestion to use names instead ofdevice addresses and > how to get the names with lsblk --fs /dev/sda. Using this should fix > my problem of reassignment device names at boottime. Thanks much!!! > > #4. Partitionless disks > I orginally installed Centos 7.3 on an SSD, and theninstalled the hard drives > subsequently. I noticed that I gained quite a bit of disc space by not using a > partition. Since the files I will be storing on these discs are large and will only > be accessed for archive purposes I wanted > to use as much of the disk as possible. The original google searches > I made related to using a partitionless disk did notgive me compelling rational > to use a partition, however I would surely like tohear from you and others > about this. > > > Thanks again for your help, and instruction!!!!! > I kinda did the same thing as you. I bought a 4TB WDElements. Disabled the sleep timer. I use UrBackup to backup two local machines, one remote,to my CentOS server. The WD Elements is backing up the CentOS server as wespeak (since 9:00AM this morning). I use a rsync script I found,https://github.com/laurent22/rsync-time-backup I started with REAR, but it created a 1TB tar.gz file soI went with the rsync script. Had to remove the --one-file-system arg.

1 0

mdadm vs raidcheck
by Fred Smith 20 Feb '17

20 Feb '17

Hi all! I don't religiously follow everything that pops up in the selinux alerts, but now and then I go back and look at some of them. (I'm on an up to date Centos-7). Today I noted an error that seems to occur during a weekly raid check, from /etc/cron.d. the selinux alert is: SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless. so I go look at that file and find that it contains, down in the middle of commands run, a series of errors: 2017-02-19 01:30:03 Relax-and-Recover 1.17.2 / Git 2017-02-19 01:30:03 Command line options: /usr/sbin/rear checklayout 2017-02-19 01:30:03 Including /etc/rear/os.conf 2017-02-19 01:30:03 Including conf/Linux-i386.conf 2017-02-19 01:30:03 Including conf/GNU/Linux.conf 2017-02-19 01:30:04 Including /etc/rear/local.conf 2017-02-19 01:30:04 Running 'init' stage 2017-02-19 01:30:04 Including init/default/01_set_drlm_env.sh 2017-02-19 01:30:04 Finished running 'init' stage in 0 seconds 2017-02-19 01:30:04 Using build area '/tmp/rear.oaWHSvnwNFddStm' 2017-02-19 01:30:04 Running checklayout workflow 2017-02-19 01:30:04 Running 'layout/precompare' stage 2017-02-19 01:30:04 Including layout/precompare/default/11_check_layout_file.sh 2017-02-19 01:30:04 Finished running 'layout/precompare' stage in 0 seconds 2017-02-19 01:30:04 Running 'layout/save' stage 2017-02-19 01:30:04 Including layout/save/GNU/Linux/10_create_layout_file.sh 2017-02-19 01:30:04 Creating disk layout 2017-02-19 01:30:04 Preparing layout directory. 2017-02-19 01:30:04 Including layout/save/GNU/Linux/15_save_diskbyid_mappings.sh 2017-02-19 01:30:05 Saved diskbyid_mappings 2017-02-19 01:30:05 Including layout/save/GNU/Linux/20_partition_layout.sh 2017-02-19 01:30:06 Saving disk partitions. 2017-02-19 01:30:08 Including layout/save/GNU/Linux/21_raid_layout.sh 2017-02-19 01:30:08 Saving Software RAID configuration. /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 65: [: : integer expression expected /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 65: [: : integer expression expected /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 65: [: : integer expression expected /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 65: [: : integer expression expected 2017-02-19 01:30:09 Including layout/save/GNU/Linux/22_lvm_layout.sh 2017-02-19 01:30:09 Saving LVM layout. 2017-02-19 01:30:11 Including layout/save/GNU/Linux/23_filesystem_layout.sh 2017-02-19 01:30:11 Begin saving filesystem layout 2017-02-19 01:30:11 Saving filesystem layout (using the findmnt command). 2017-02-19 01:30:16 End saving filesystem layout 2017-02-19 01:30:16 Including layout/save/GNU/Linux/24_swaps_layout.sh 2017-02-19 01:30:16 Saving Swap information. 2017-02-19 01:30:16 Including layout/save/GNU/Linux/25_drbd_layout.sh 2017-02-19 01:30:16 Including layout/save/GNU/Linux/26_crypt_layout.sh 2017-02-19 01:30:16 Saving Encrypted volumes. 2017-02-19 01:30:16 Device Mapper name No not found in /dev/mapper. 2017-02-19 01:30:16 Including layout/save/GNU/Linux/27_hpraid_layout.sh 2017-02-19 01:30:16 Including layout/save/GNU/Linux/28_multipath_layout.sh 2017-02-19 01:30:16 Did not find multipath device No in the expected location. 2017-02-19 01:30:16 Including layout/save/default/30_list_dependencies.sh 2017-02-19 01:30:16 Including layout/save/default/31_autoexclude_usb.sh 2017-02-19 01:30:16 Including layout/save/default/31_include_exclude.sh 2017-02-19 01:30:16 Including layout/save/default/32_autoexclude.sh 2017-02-19 01:30:17 Disk /dev/sdb is not used by any mounted filesystem. Excluding. 2017-02-19 01:30:17 Disk /dev/sdc is not used by any mounted filesystem. Excluding. 2017-02-19 01:30:17 Including layout/save/default/33_remove_exclusions.sh 2017-02-19 01:30:17 Including layout/save/GNU/Linux/34_false_blacklisted.sh 2017-02-19 01:30:18 Including layout/save/default/34_generate_mountpoint_device.sh 2017-02-19 01:30:18 Including layout/save/GNU/Linux/35_copy_drbdtab.sh 2017-02-19 01:30:18 Including layout/save/default/40_check_backup_special_files.sh 2017-02-19 01:30:18 Including layout/save/default/45_check_bootloader_files.sh 2017-02-19 01:30:18 Including layout/save/default/45_check_network_files.sh 2017-02-19 01:30:18 Including layout/save/GNU/Linux/50_extract_vgcfg.sh 2017-02-19 01:30:18 Including layout/save/GNU/Linux/51_current_disk_usage.sh 2017-02-19 01:30:19 Including layout/save/default/60_snapshot_files.sh 2017-02-19 01:30:19 Finished running 'layout/save' stage in 15 seconds 2017-02-19 01:30:19 Running 'layout/compare' stage 2017-02-19 01:30:19 Including layout/compare/default/50_compare_layout.sh 2017-02-19 01:30:19 Disk layout is identical. 2017-02-19 01:30:19 Including layout/compare/default/51_compare_files.sh 2017-02-19 01:30:20 Finished running 'layout/compare' stage in 1 seconds 2017-02-19 01:30:20 Finished running checklayout workflow 2017-02-19 01:30:20 Running exit tasks. 2017-02-19 01:30:20 Finished in 18 seconds 2017-02-19 01:30:20 Removing build area /tmp/rear.oaWHSvnwNFddStm 2017-02-19 01:30:20 End of program reached selinux says it prevent writes to this file. but the file was clearly written to! Is selinux stupid enough to mistake shell errors as a failure to write? Also, in trying to figure out what those errors mean, I looked at the file specified in the errors, /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh, where I find line 44 and a couple above it read: ndevices=$( grep "Raid Devices" $TMP_DIR/mdraid | tr -d " " | cut -d ":" -f "2") totaldevices=$( grep "Total Devices" $TMP_DIR/mdraid | tr -d " " | cut -d ":" -f "2") let sparedevices=$totaldevices-$ndevices it appears that "ndevices" and "totaldevices" are both empty (not zero, but empty) because the error report above says "-" isn't valid, which would happen if those two variables were unpopulated. At this point I haven't yet found out where those values come from... (more to the point, I haven't yet figured out where TMP_DIR comes from) If any of you know more than I (I've never seen this code before) I'd appreciate a pointer, but I'll keep looking too. In the meantime, my software raid seems to keep chugging along. thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ---------------------------- Do you not know? Have you not heard? The LORD is the everlasting God, the Creator of the ends of the earth. He will not grow tired or weary, and his understanding no one can fathom. ----------------------------- Isaiah 40:28 (niv) -----------------------------

1 0

usb drives & Orico ORICO 9548U3-BK
by Gregory P. Ennis 19 Feb '17

19 Feb '17

Everyone, Is there a way to manually assign usb drives to a specified device label. Is there a way to force two usb drives to be labeled as /dev/sdc and /dev/sdd? I decided to build an archive server for the purpose of backing up other fedora/centos desktops at the office. I built a machine and have installed Centos 7.3 on it with all updates current. I also purchased a 3.0 usb sata drive cabinet (Orico ORICO 9548U3-BK) and installed two 5T black WD drives. There was no problem installing the usb cabinet or the drives. I formatted each drive with xfs as /dev/sdc and /dev/sdd, and then combined them into a software mirrored raid with mdadm as /dev/md0. Everything was working perfectly until I removed the terminal, keyboard and mouse and tried to reboot the machine. It took a while to figure out, but when the mouse and keyboard were removed the boot process assigns the usb drives differently which makes /dev/md0 created by mdadm fail. My fstab file looks like : /dev/mapper/centos_poar-root / xfs defaults 0 0 UUID=f915a354-28bf-4110-bec9-3767ef1fe52c /boot xfs defaults 0 0 /dev/mapper/centos_poar-home /home xfs defaults 0 0 /dev/mapper/centos_poar-u /u xfs defaults 0 0 /dev/mapper/centos_poar-swap swap swap defaults 0 0 /dev/sda /u0 btrfs defaults 0 0 # entries below were combined into one mirrored raid system #/dev/sdc /u1 xfs defaults 0 0 #/dev/sdd /u2 xfs defaults 0 0 /dev/md0 /u1 xfs defaults 0 0 This works perfectly when a usb mouse and a usb keyboard are attached, but when I remove the mouse and keyboard the system will not boot because the usb drives are relabeled as /dev/sda and /dev/sdb. The only way I have been able to make this archive server function is to keep a mouse and keyboard plugged in to the system, and even with the keyboard and mouse attached I can not do a software reboot, I am required to turn off the power supply for a couple of seconds and then turn it back on before I hit the power switch on the computer. I have played with the bios setting until my eyes are blurry, but have not been able to solve the problem. I am using a ASUS H110M-E/M.2 LGA 1151 Intel H110 HDMI SATA 6Gb/s USB 3.0 Micro ATX Motherboard. My thought is that if I could force the usb drives to be labeled as /dev/sdc and /dev/sdd whether the mouse and keyboard are attached or not, I might be able to fix the problem Anyone have any ideas? Thanks for your responses!!!! Greg Ennis

3 3

RAID questions
by tdukes＠palmettoshopper.com 19 Feb '17

19 Feb '17

Hello, Just a couple questions regarding RAID. Here's thesituation. I bought a 4TB drive before I upgraded from 6.8 to 7.3. I'm not too far into this that Ican't start over. I wanted disk space to backup 3 other machines. I way overestimated what I needed for full, incremental and image backups with UrBackup.I've used less than 1TB so far. I would like to add an additional drive to makeit a RAID server. I may use a PCIe SSD for the boot drive if I can find onecompatible with my old hardware. 1- Better to go with a hardware RAID (mainboardsupported) or software? 2 - Can an existing drive with data on it be used as aRAID drive without losing current data? 3 - Can additional drive(s) be added later with a changein RAID level without current data loss? TIA

8 11

Require option in Apache
by Robert Moskowitz 19 Feb '17

19 Feb '17

So I have read everything that my search foo can find on the require option. I want to specify IP addresses. The only examples I am finding are in: http://httpd.apache.org/docs/2.4/howto/auth.html And only IPv4 addresses and only dotted aggregation. No IPv6 examples and no CIDR aggregation examples. In fact, no IPv6 examples at all. So can anyone point me to some more information on specifying IP addresses with this new require option? thanks

1 1

getting files from a samsung flip phone
by Michael Hennebry 18 Feb '17

18 Feb '17

I'm trying to copy file from my samsung flip phone. google has informed me of libmtp and gvfs, but it doesn't seem to be helping. [root@localhost yum.repos.d]# mtp-detect libmtp version: 1.0.1 Listing raw device(s) No raw devices found. [root@localhost yum.repos.d]# In case it helps, I did a diff of ls -R from /dev before and after USB connection: [hennebry@localhost dev]$ diff /tmp/dev[12].txt | tee /tmp/dev.dif 89a90 > serial 166a168 > ttyACM0 257a260 > 011 330a334 > 166:0 336a341 > 189:138 577a583,592 > ./serial: > by-id > by-path > > ./serial/by-id: > usb-SAMSUNG_Electronics_Bo._Ltd._Samsung_SCH-u365-if00 > > ./serial/by-path: > pci-0000:00:1d.7-usb-0:2.4:1.0 > [hennebry@localhost dev]$ Any ideas? -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

3 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss February 2017