April 2016 - Discuss - lists.centos.org

Re: [CentOS] KVM Virtualization Network VLAN CentOS7 (resolve)
by FrancisM 07 Apr '16

07 Apr '16

On Thu, Apr 7, 2016 at 4:20 PM, FrancisM <francis(a)mytechrepublic.com> wrote: > > > On Thu, Apr 7, 2016 at 1:51 PM, FrancisM <francis(a)mytechrepublic.com> > wrote: > >> >> >> On Thu, Apr 7, 2016 at 1:26 PM, Subscriber <ml-lists(a)agoris.net.ua> >> wrote: >> >>> Hello FrancisM, >>> >>> Thursday, April 7, 2016, 8:03:38 AM, you wrote: >>> >>> >>> > I tried last night and it seems like the vlans that I created is >>> failing to >>> > bring-up. So this is what Im doing >>> >>> > in my DATA trunk port at my HomeLab Im doing this >>> >>> > 2 port configured for teaming1 (set as link only port) -> Create Bridge >>> > (br0 port) on top of the teaming1 -> create slave vlan10,20,30,40 and >>> the >>> > parent is br0. Am I doing this correctly? Thanks >>> >>> not exactly. >>> >>> nmcli connection add con-name br10 ifname br10 type bridge stp no >>> nmcli connection down br10 >>> nmcli connection edit br10 >>> set ipv4.method disabled >>> set ipv6.method ignore >>> save >>> quit >>> nmcli connection up br10 >>> >>> nmcli connection add con-name vlan10 ifname vlan10 type vlan dev >>> teaming1 id 10 >>> nmcli connection down vlan10 >>> nmcli connection edit vlan10 >>> set connection.master br10 >>> set connection.slave-type bridge >>> verify fix >>> save >>> exit >>> nmcli connection up vlan10 >>> >>> similarly for br20+vlan20, br30+vlan30, br40+vlan40 >>> >>> _______________________________________________ >>> CentOS mailing list >>> CentOS(a)centos.org >>> https://lists.centos.org/mailman/listinfo/centos >>> >> >> Thanks for providing the command I will definitely try this method. >> >> > Hi, > > After trying the method using the 'nmcli' its the same error result as > what I encountered in using the 'nmtui' by the way after configuring then > check it in the nmtui its the same configuration as what I have done > earlier. > > [root@server network-scripts]# systemctl status network.service -l > ● network.service - LSB: Bring up/down networking > Loaded: loaded (/etc/rc.d/init.d/network) > Active: failed (Result: exit-code) since Tue 2015-04-07 17:19:00 SGT; > 1min 13s ago > Docs: man:systemd-sysv-generator(8) > Process: 48732 ExecStop=/etc/rc.d/init.d/network stop (code=exited, > status=0/SUCCESS) > Process: 49302 ExecStart=/etc/rc.d/init.d/network start (code=exited, > status=1/FAILURE) > > Apr 07 17:17:28 server network[49302]: [ OK ] > Apr 07 17:17:29 server network[49302]: Bringing up interface > team1_slave_enp5s0f1: Connection successfully activated (D-Bus active > path: /org/freedesktop/NetworkManager/ActiveConnection/69) > Apr 07 17:17:29 server network[49302]: [ OK ] > Apr 07 17:19:00 server network[49302]: *Bringing up interface vlan247: > Error: Timeout 90 sec expired.* > Apr 07 17:19:00 server network[49302]: *[FAILED]* > Apr 07 17:19:00 server network[49302]: Bringing up interface br247: [ > OK ] > Apr 07 17:19:00 server systemd[1]: network.service: control process > exited, code=exited status=1 > Apr 07 17:19:00 server systemd[1]: Failed to start LSB: Bring up/down > networking. > Apr 07 17:19:00 server systemd[1]: Unit network.service entered failed > state. > Apr 07 17:19:00 server systemd[1]: network.service failed. > [root@server network-scripts]# > > I will try to use other configuration on this bridge. Does it matter if I > use TEAMING and not BONDING on this bridging configuration because the two > nic card that is trunk is configured as TEAMING in my CentOS7 > Thanks all I already figure it out its due to the *ipv4.method link-only* it shoud be *ipv4.method disabled* in my teaming1 configuration

1 0

KVM Virtualization Network VLAN CentOS7
by Francis Mendoza 07 Apr '16

07 Apr '16

Im configuring my KVM and in my network configuration I have 4 Network lancard 2 nic = using teaming0 for management with access port configured in the switch side 2 nic = using teaming1 for guest VM DATA ports. and in the switch is configured for LACP with trunk allowing vlan 10,20,30,40,50 and configured in the CentOS7 the vlan 10, vlan 20,30,40,50 im sure its already working because I tried to use one vlan and ping was successful. my question is can I assigned directly the 'team1_vlan10, team1_vlan20.. and so on to directly use in my guest VM instead of bridging the network config in the VM.xml file? I tried to google and found only about bridging it first and could not find the direct connection in the DATA port Teaming1 Thank you in advance

5 12

CentOS 7, selinux issue
by m.roth＠5-cent.us 06 Apr '16

06 Apr '16

I'm seeing a lot of noise in the logs, to the effect of: setroubleshoot: SELinux is preventing /bin/ksh93 from write access on the directory /var/lib/ssh-x509-auth as well as others related to find, cat, etc on .pem's in that directory. Is this a policy bug, or just no policy covering this? mark

2 1

CentOS 7 annoyances
by m.roth＠5-cent.us 06 Apr '16

06 Apr '16

So, tell me folks, when you've got a system that isn't coming all the way up, and you get to the grub2? dracut? shell, and you tell it to reboot, and it responds by telling you I'm sorry, Dave, I can't do that, "target is destructive", what are you *expected* to do, other than power cycle the damn thing? mark

1 0

password
by Joe Smithian 06 Apr '16

06 Apr '16

3 3

systemd-run does not start scope in the specified slice
by Alexander Brand 06 Apr '16

06 Apr '16

It seems that systemd-run does not start the process in the specified slice when starting a transient scope instead of a service. I have created a test.slice, and started it: # systemctl status test.slice ● test.slice - Test slice Loaded: loaded (/usr/lib/systemd/system/test.slice; static; vendor preset: disabled) Active: active since Tue 2016-04-05 16:50:26 EDT; 2min 27s ago Memory: 0B Apr 05 16:50:26 abrand04 systemd[1]: Created slice Test slice. Apr 05 16:50:26 abrand04 systemd[1]: Starting Test slice. When running a process using systemd-run, # systemd-run --scope --slice=test --unit=test sleep 60 & [1] 52359 # Running scope as unit test.scope. the process is placed in the system.slice (see CGroup) instead of the test.slice as specified in the systemd-run command. # systemctl status test.scope ● test.scope - /usr/bin/sleep 60 Loaded: loaded (/run/systemd/system/test.scope; static; vendor preset: disabled) Drop-In: /run/systemd/system/test.scope.d └─50-Description.conf Active: active (running) since Tue 2016-04-05 16:56:04 EDT; 11s ago Memory: 92.0K CGroup: /system.slice/test.scope └─52359 /usr/bin/sleep 60 Apr 05 16:56:04 abrand04 systemd[1]: Started /usr/bin/sleep 60. Apr 05 16:56:04 abrand04 systemd[1]: Starting /usr/bin/sleep 60. CentOS Linux release 7.2.1511 (Core) systemd 219 Am I doing something wrong here? When starting the process as a service, and not a transient scope, the process is correctly placed in the specified slice.

1 0

Squid for CentOS 7 and available file descriptors
by Carlos A. Carnero Delgado 06 Apr '16

06 Apr '16

Hi, I'm installing a Squid instance for a large (ish) group of users. In the past I've had to increase the number of available file descriptors for the Squid process in order to avoid hitting the limits (and disrupting the service). It seems that the packaged Squid for CentOS 7 has a hardcoded value of 16386 maximum file descriptors <https://git.centos.org/blob/!rpms!squid.git/c6361861418913e2a375a3507da79ac…>. The relevant portion of that spec file is ⋮ --with-aio \ --with-default-user="squid" \ --with-filedescriptors=16384 \ --with-dl \ --with-openssl \ ⋮ Why this limit? Is there any merit to opening a bug or enhancement request somewhere? Other than that, what could I do next? A custom Squid build? Thanks a lot, Carlos.

1 0

CentOS-announce Digest, Vol 134, Issue 4
by centos-announce-request＠centos.org 06 Apr '16

06 Apr '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:0591 Moderate CentOS 6 nspr Security Update (Johnny Hughes) 2. CESA-2016:0591 Moderate CentOS 6 nss-util Security Update (Johnny Hughes) 3. CESA-2016:0591 Moderate CentOS 6 nss Security Update (Johnny Hughes) 4. CEEA-2016:0593 CentOS 7 libguestfs Enhancement Update (Johnny Hughes) 5. CESA-2016:0594 Important CentOS 7 graphite2 Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 5 Apr 2016 12:27:24 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0591 Moderate CentOS 6 nspr Security Update Message-ID: <20160405122724.GA26079(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0591 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0591.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3b223ca6b209603975d7067ca45911b0f61f445196fb4b87e8e30b881ba9c2e5 nspr-4.11.0-0.1.el6_7.i686.rpm e9f94771ef76b6bb895aaf2b196e90c1e9c3aafeb11177afc03a21d90be4ad34 nspr-devel-4.11.0-0.1.el6_7.i686.rpm x86_64: 3b223ca6b209603975d7067ca45911b0f61f445196fb4b87e8e30b881ba9c2e5 nspr-4.11.0-0.1.el6_7.i686.rpm 3d109fb2c496edf99f41fd9db08769239caef7758ea6abf118ffe72b1de57c94 nspr-4.11.0-0.1.el6_7.x86_64.rpm e9f94771ef76b6bb895aaf2b196e90c1e9c3aafeb11177afc03a21d90be4ad34 nspr-devel-4.11.0-0.1.el6_7.i686.rpm 14a47d3277db192096307cb88c8072df5b15257db7b352bf731fa54227a46c42 nspr-devel-4.11.0-0.1.el6_7.x86_64.rpm Source: 34bfff2b29fc9e980193a8cdc85aa65bae37e6c8e622de0882d0237365aa0c47 nspr-4.11.0-0.1.el6_7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 5 Apr 2016 12:33:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0591 Moderate CentOS 6 nss-util Security Update Message-ID: <20160405123302.GA26406(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0591 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0591.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: be545dfd2d5da2c62a77f9cc2b40987befdb5c5f669782af9c377f0b85484ff0 nss-util-3.21.0-0.3.el6_7.i686.rpm 56806dccf241355a1b9cba4e1595f54abbe5a5b1f92b9a4d4f5b7d8091bc7325 nss-util-devel-3.21.0-0.3.el6_7.i686.rpm x86_64: be545dfd2d5da2c62a77f9cc2b40987befdb5c5f669782af9c377f0b85484ff0 nss-util-3.21.0-0.3.el6_7.i686.rpm a7241304459acb2e2dca19fa7a61f516f2a38aa3e4440d1a2f001de413c54e1f nss-util-3.21.0-0.3.el6_7.x86_64.rpm 56806dccf241355a1b9cba4e1595f54abbe5a5b1f92b9a4d4f5b7d8091bc7325 nss-util-devel-3.21.0-0.3.el6_7.i686.rpm 7cb08f5c7d2c44566206fc7fb5c9dcb380b9ec3e036eecf3bc99ec764e95043e nss-util-devel-3.21.0-0.3.el6_7.x86_64.rpm Source: 3c391ab73bc502dc1a1aa74a1aeda1ddf08aee80c85ed02396808117d1a89ce5 nss-util-3.21.0-0.3.el6_7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 5 Apr 2016 14:21:27 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0591 Moderate CentOS 6 nss Security Update Message-ID: <20160405142127.GA28504(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0591 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0591.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5c8974b2d8730e2967751f835f4646bdf46fa968c29769748219ad426c5140d3 nss-3.21.0-0.3.el6_7.i686.rpm f3782c46dfadef016d7afe8d81015c92ca5062e738d225377bfb38904e70708d nss-devel-3.21.0-0.3.el6_7.i686.rpm 32b9c62453b3dd45c60985751e36ed30aba93ea2f024b4b08443b7b9438eb5a8 nss-pkcs11-devel-3.21.0-0.3.el6_7.i686.rpm 7ee7fb2e4107b38d7c03677abb588fdd59b28459fa01a67f1a0bfb159295c688 nss-sysinit-3.21.0-0.3.el6_7.i686.rpm a24d41eaadacaebcab9e7bf5490dc75028d7360e8484d9f4615b480067299539 nss-tools-3.21.0-0.3.el6_7.i686.rpm x86_64: 5c8974b2d8730e2967751f835f4646bdf46fa968c29769748219ad426c5140d3 nss-3.21.0-0.3.el6_7.i686.rpm 7242d7e199b316736c10a1e97629001a3f2ab4ba540f0e313730ae8a11358544 nss-3.21.0-0.3.el6_7.x86_64.rpm f3782c46dfadef016d7afe8d81015c92ca5062e738d225377bfb38904e70708d nss-devel-3.21.0-0.3.el6_7.i686.rpm 24a8bfae413d2a0ea8063fe0045615096d0cff4e8ddb483b625f32a20c403fb4 nss-devel-3.21.0-0.3.el6_7.x86_64.rpm 32b9c62453b3dd45c60985751e36ed30aba93ea2f024b4b08443b7b9438eb5a8 nss-pkcs11-devel-3.21.0-0.3.el6_7.i686.rpm dc1976aceb5f1e49dcb95308bc6ae80e9100d759141308f5fb786ac6d49e65b3 nss-pkcs11-devel-3.21.0-0.3.el6_7.x86_64.rpm 99a95ba3bfebf8d62f4033b0578ff4c0a604becc5e5255700d98ccf305e68cc9 nss-sysinit-3.21.0-0.3.el6_7.x86_64.rpm f1af7ca96a93c1ebeeab8051f137e92116d869ba0aa55c28bf7a6d0bcf7b49e7 nss-tools-3.21.0-0.3.el6_7.x86_64.rpm Source: ae57322f9c969f39ae79298247a6a8a795719d1e926d88077a92536b8332409c nss-3.21.0-0.3.el6_7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 5 Apr 2016 19:15:11 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2016:0593 CentOS 7 libguestfs Enhancement Update Message-ID: <20160405191511.GA54774(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2016:0593 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0593.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e41f1f0c1e04016bf837b5c5e32523d3cfb6fefa148c273f98a0d3906fd40fba libguestfs-1.28.1-1.55.el7.centos.2.x86_64.rpm 1de3c2f505fb7947ce4bf7a02aed54bb841af60c3b2520be629facd9b428aa87 libguestfs-bash-completion-1.28.1-1.55.el7.centos.2.noarch.rpm 25d7239057eb0e67658bd88e9cd1131adf7cc30dd7248830eb9ff6ad900ec9b0 libguestfs-devel-1.28.1-1.55.el7.centos.2.x86_64.rpm f1f49fd37bfe8e79472c85144cfa490f2b603529c590d1bce743cec54c9b4835 libguestfs-gfs2-1.28.1-1.55.el7.centos.2.x86_64.rpm 99736d954ddbe3cfd11e6a539d818b92a8d2c525fd22246bdba1d7d4cf48c084 libguestfs-gobject-1.28.1-1.55.el7.centos.2.x86_64.rpm 061eea52827be1f861a79d558bcf50e470de0b9480e2b26a91f0d34726c4fb70 libguestfs-gobject-devel-1.28.1-1.55.el7.centos.2.x86_64.rpm 124437fac47dfa1fcdf36dfc6f6329c360732dda2ba02c37c46bbabb8516e475 libguestfs-gobject-doc-1.28.1-1.55.el7.centos.2.noarch.rpm 4595763999e8fbc60b902282e6487175ec1dc0a1967075598ff78b3e54073a41 libguestfs-java-1.28.1-1.55.el7.centos.2.x86_64.rpm 395de464f35786d4a52e2d340992dc51af77441b862246156f58bd5ea45c942a libguestfs-java-devel-1.28.1-1.55.el7.centos.2.x86_64.rpm fe7d1c1f1018935bf163849aecdb53411556464b5bac0dcbb259c112701add1f libguestfs-javadoc-1.28.1-1.55.el7.centos.2.noarch.rpm 55dd3a16b965949628f1ee2a57f7ac3a059650066a7edc6eca681ffae2fbd3e6 libguestfs-man-pages-ja-1.28.1-1.55.el7.centos.2.noarch.rpm 16fc4d292e720a143f7558d9c831295698b15cb54a02c0ab0323d0756086d2e5 libguestfs-man-pages-uk-1.28.1-1.55.el7.centos.2.noarch.rpm 1f51f5079763f480e241bb3025b4b188b86c6b6f5c786ed5aee607308b00f01a libguestfs-rescue-1.28.1-1.55.el7.centos.2.x86_64.rpm 26e2e13368845dc9c5a87b0026b3d4553e92e4a41769a0f7699c39a000d13ea6 libguestfs-rsync-1.28.1-1.55.el7.centos.2.x86_64.rpm 0efaaec4a7d7ddc9d38c1b79c11a1c501db0696a16f158afd72d173ed08544c9 libguestfs-tools-1.28.1-1.55.el7.centos.2.noarch.rpm 16b577c6b8a7058a54afef6dae8080bf922721a2d82c74a105f3172621fe1f0a libguestfs-tools-c-1.28.1-1.55.el7.centos.2.x86_64.rpm 45a6688b5ed0f78fd2509e1ed738fe93df957fa0645719089ff2096699d20c65 libguestfs-xfs-1.28.1-1.55.el7.centos.2.x86_64.rpm b45d3ddccc275dc1ffc11b527c70b97cc6f1a6ded8c8fb3d36c1b77bedb99656 lua-guestfs-1.28.1-1.55.el7.centos.2.x86_64.rpm 522dab43977b5ffa55b3580d1b872b6c39d64f3a0647bcc3f610e94b6a4cf359 ocaml-libguestfs-1.28.1-1.55.el7.centos.2.x86_64.rpm c18daa1c6e22fa68e43fa4af67432775c4b85117fe8a602e73aa04a24129350c ocaml-libguestfs-devel-1.28.1-1.55.el7.centos.2.x86_64.rpm 4a2cf803a443ac25202b14edfd8793f082f108f085f4516cc92ae08979e7593f perl-Sys-Guestfs-1.28.1-1.55.el7.centos.2.x86_64.rpm 75b4ef7132a57003bcafca7da181be5a52893cfc57bdef249c2e7dcf217d7cb0 python-libguestfs-1.28.1-1.55.el7.centos.2.x86_64.rpm 986a65c4ff8627f2b5824ea053c34164a238c8f1b8d8de563be79360d22434da ruby-libguestfs-1.28.1-1.55.el7.centos.2.x86_64.rpm 24df4ea90173c3cfc1093235cf61d86fa76c19be7c11df650ad91d322f1c1d61 virt-v2v-1.28.1-1.55.el7.centos.2.x86_64.rpm Source: da1fc6d0671953604c8bf0c9f39a28ffad402fbd10d858f2119fcaa63335e454 libguestfs-1.28.1-1.55.el7.centos.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Tue, 5 Apr 2016 20:02:28 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0594 Important CentOS 7 graphite2 Security Update Message-ID: <20160405200228.GA55846(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0594 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0594.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 5833acac7b610ae47aaff9fff6976044184dcef52f724a1f94142e69e2215116 graphite2-1.3.6-1.el7_2.i686.rpm f14d09c338249719f5f75305ee0dc6c32829ad3e45c7bc62b9fa530d37bcd35f graphite2-1.3.6-1.el7_2.x86_64.rpm 2ba25e1c7cf6d499d2826dce52b463b1b41b653087a2b02b0a22f0a2ad8e8968 graphite2-devel-1.3.6-1.el7_2.i686.rpm 1ee921c206f47b305e00b9ead905655decd0c93334962dd6ed74112dc4be6db9 graphite2-devel-1.3.6-1.el7_2.x86_64.rpm Source: 24e94805fcb7de71ccd8fd1ecaf44cf56602da1a030a14c4d7862c3bcd87bbea graphite2-1.3.6-1.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 134, Issue 4 ***********************************************

1 0

www.centos.org/forums/
by Steve Clark 06 Apr '16

06 Apr '16

Hi List, Does anyone know why the above URL is still using TLS V1.0. I can't connect to it unless I enable TLS V1.0 which I was under the impression that it should not be used anymore. Thanks for any enlightenment. Steve --

7 8

Re: [CentOS] [CentOS-announce] Notice of Service Outage and followup LON1/UK Facility
by Always Learning 06 Apr '16

06 Apr '16

On Wed, 2016-03-30 at 11:25 +0100, Karanbir Singh wrote: > On Wednesday February 24th, at 6pm UTC time, the DC hosting some of > the CentOS equipments used for various roles had suffered from > multiple electricity power outages. The facility was completely dark > for just under 2 hrs, and we were able to start recovering services by > 8pm UTC. By midnight we had most services restored, by 2:00AM UTC Feb > 25th we had all services restored. No emergency diesel generators ? I live in an area, having an unpublicised nationally strategic telecoms hub, with 9+ discrete data centres within 1.5 km of a power station (linked by dedicated underground cable to another power station) yet each data centre has at least one diesel generator. Resilience seems to be their motto. -- Regards, Paul. England, EU. England's place is in the European Union.

3 2

How to configure DNS server in RHEL 7 / CentOS 7
by Joe Smithian 05 Apr '16

05 Apr '16

How to configure DNS server and search domain common for all network interfaces not per device? The only reliable way I found we can set DNS name server and search domain in CentOS 7 is using nmcli which adds DNS name server and search domain to *a specific interface*, e.g. nmcli con mod eth0 +ipv4.dns [IP_ADDRESS]. But I want to set them for all interfaces weather they are configure and connected or not. How can we do that? More back ground information: I am using NetworkManager and nmcli tool to configure multiple wired Ethernet interfaces on CentOS 7. I want to set common DNS name server and search domain for all interfaces. /etc/resolv.conf is generated by NetworkManger and we cannot manually modify it. Thanks, Joe

2 1

Disabling network service in CentOS 7
by Joe Smithian 05 Apr '16

05 Apr '16

Hi all, I've recently started using NetworkManger service and nmcli tool, I like it much better than the old network service and manually modifying network scripts. I've seen many online questions on how to disable NetworkManger but I have the opposite question! I am wondering if it be OK to disable network service altogether and just use NetworkManger for configuring and managing Ethernet interfaces. I care about wired Ethernet interfaces only. I disabled network service and rebooted my machine without any networking problem but I wanted to conform that that would be OK. Thanks, Joe On Mon, Apr 4, 2016 at 12:33 PM, Joe Smithian <joe.smithian(a)gmail.com> wrote: > Hi all, > I've recently started using NetworkManger service and nmcli tool, I like > it much better than the old network service and manually modifying network > scripts. I've seen many online questions on how to disable NetworkManger > but I have the opposite question! I am wondering if it be OK to disable > network service altogether and just use NetworkManger for configuring and > managing Ethernet interfaces. I care about wired Ethernet interfaces only. > > I disabled network service and rebooted my machine without any networking > problem but I wanted to conform that that would be OK. > > Thanks, > > Joe >

2 1

VPN suggestions centos 6, 7
by david 05 Apr '16

05 Apr '16

Folks I would like to have my windows 7 laptop communicate with my home server via a VPN, in such a way that it appears to be "inside" my home network. It should not only let me appear to be at home for any external query, but also let me access my computers inside my home. I already have this working using M$'s PPTP using my home Centos 6 gateway/router as the PoPToP server. However, I am concerned about the privacy/security of such a connection. I have seen discussions of OpenVPN, OpenSwan, LibreVPN, StrongSwan (and probably others I haven't noted). I'd be interested in hearing from anyone who wishes to comment about which to use, with the following requirements: 1) As noted, it should be secure (anti NSA?) 2) Works on Centos 6 and Centos 7 and Windows 7 (and for the future, Windows 10) 3) Can be set up on the server with command line interfaces only (no GUI) And, should not be a nightmare to set up. Any thoughts? David

13 19

virt-manager virtual USB disk unavailable option
by Roberto Cantalapiedra 05 Apr '16

05 Apr '16

Hi, I have installed virt-manager 1.3.2 and I want to create a virtual USB disk (not USB host passthrough) but unfortunately I don't see that option when I try to add a new storage hardware. I have another PC with virt-manager 0.9.5 and Linux Mint and I have that option and it is working perfectly. My CentOS version is: 7.2.1511 Thanks in advance <https://www.google.com/search?q=host+passthrough+usb&spell=1&sa=X&ved=0ahUK…>

1 0

CentOS-announce Digest, Vol 134, Issue 3
by centos-announce-request＠centos.org 05 Apr '16

05 Apr '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. Infra - CentOS forums migration (Fabian Arrotin) ---------------------------------------------------------------------- Message: 1 Date: Mon, 4 Apr 2016 17:33:17 +0200 From: Fabian Arrotin <arrfab(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] Infra - CentOS forums migration Message-ID: <5702893D.5090904(a)centos.org> Content-Type: text/plain; charset="utf-8" Just to inform you that we'll move some services to a new node, and so there will be a small impact for the following services : - https://www.centos.org (no real downtime, as it will just be redirected automatically) - https://www.centos.org/forums (see below) During that migration we'll also consolidate IPv6 and IPv4 connectivity and also we'll be able to implement higher protocol than TLS 1.0 (because we are/were still using a CentOS 5 based node in the previous setup) Migration is scheduled for """"Wednesday April 6th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2016-04-06 7:00 UTC') The expected "downtime" is estimated to ~30 minutes , time needed to update/propagate updated dns A/AAAA record[s] + last mysql dump/restore on the new node. Thanks for your comprehending and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

email
by gemma adlawan 05 Apr '16

05 Apr '16

1 0

How to install VPN server
by Chandran Manikandan 05 Apr '16

05 Apr '16

Hi All, I have running centos 6 server in my head quarters and branch offices. I need to access file server files in both location using VPN. How to setup vpn server in both location and how to access it. Could any one help me. -- *Thanks,* *Manikandan.C* *System Administrator*

2 1

EPEL - Clamav update?
by Rob Kampen 04 Apr '16

04 Apr '16

EPEL maintainers? I note messages in the log about updated version 0.99.1 of CLAMAV being available since Mar 5th. for CentOS 6 no update is available yet. I used to use rpmforge for this package but that languished for months before updates became available and eventually stopped altogether. Is there something I can do to assist in getting this package updated? I have no idea if this is a difficult package to compile with lots of dependancies or some otherwise complexities. In this era of constant SPAM and so many virus / trojan attempts to do harm to others, it is vital that we run this package to protect our users. Please let me know if / how I can assist. Kind regards Rob

5 4

Centos7: Mount problem (Unit mnt-bk\x2dbenvet\x2d01.mount is bound to inactive unit dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device. Stopping, too.
by Dario Lesca 03 Apr '16

03 Apr '16

On a server Centos 7.2 I insert my 1Tb usb disk and run sudo mount LABEL=bk-benvet-01 /mnt/bk-benvet-01 the command seem to work but nothing is mounted Into log I see this issue: > apr 01 13:49:06 s-virt.dom.loc kernel: XFS (sdb1): Mounting V4 Filesystem > apr 01 13:49:06 s-virt.dom.loc kernel: XFS (sdb1): Ending clean mount > apr 01 13:49:06 s-virt.dom.loc systemd[1]: Unit mnt-bk\x2dbenvet\x2d01.mount is bound to inactive unit dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device. Stopping, too. > apr 01 13:49:06 s-virt.dom.loc systemd[1]: Unmounting /mnt/bk-benvet-01... > apr 01 13:49:06 s-virt.dom.loc kernel: XFS (sdb1): Unmounting Filesystem > apr 01 13:49:06 s-virt.dom.loc systemd[1]: Unmounted /mnt/bk-benvet-01. I have try this: > [root@s-virt ~]# systemctl start dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device > Job for dev-disk-byx2dlabel-bkx2dbenvetx2d01.device timed out. > [root@s-virt ~]# systemctl status dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device > ● dev-disk-byx2dlabel-bkx2dbenvetx2d01.device > Loaded: loaded > Active: inactive (dead) > > apr 01 13:52:36 s-virt.vettorello.loc systemd[1]: Job dev-disk-byx2dlabel-bkx2dbenvetx2d01.device/start timed out. > apr 01 13:52:36 s-virt.vettorello.loc systemd[1]: Timed out waiting for device dev-disk-byx2dlabel-bkx2dbenvetx2d...ice. > apr 01 13:52:36 s-virt.vettorello.loc systemd[1]: Job dev-disk-byx2dlabel-bkx2dbenvetx2d01.device/start failed wi...ut'. > Hint: Some lines were ellipsized, use -l to show in full. > [root@s-virt ~]# systemctl status dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device -l > ● dev-disk-byx2dlabel-bkx2dbenvetx2d01.device > Loaded: loaded > Active: inactive (dead) But nothing is changed How to resolve this problem? Many thanks -- Dario Lesca (inviato dal mio Linux Fedora 23 Workstation)

2 4

Re: [CentOS] EPEL - Clamav update?
by Richard 03 Apr '16

03 Apr '16

> Date: Sunday, April 03, 2016 14:39:04 +1200 > From: Rob Kampen <rkampen(a)kampensonline.com> > > EPEL maintainers? > I note messages in the log about updated version 0.99.1 of CLAMAV > being available since Mar 5th. > for CentOS 6 no update is available yet. > I used to use rpmforge for this package but that languished for > months before updates became available and eventually stopped > altogether. > Is there something I can do to assist in getting this package > updated? > I have no idea if this is a difficult package to compile with lots > of dependancies or some otherwise complexities. > In this era of constant SPAM and so many virus / trojan attempts to > do harm to others, it is vital that we run this package to protect > our users. > Please let me know if / how I can assist. > Kind regards > Rob I'm seeing 0.99.1-1.el6 of the various (x86_64) bits in epel-testing, so you could get it from there and update to the fully tested version when it is released. In general I think it is most important to keep your signatures current. I don't get the sense that the changes between [sub-]point-releases are earth shattering (despite the ominous warning that you will see in your logs).

1 0

RHEL 7.3 wish-list
by Alice Wonder 02 Apr '16

02 Apr '16

CentOS tracks RHEL and there is something I think probably can only be done in a point release but I believe should be done. Update to nss and curl. The problem - the version of curl that ships with CentOS does not support ECC cryptography. A newer version would, but requires manual specification of the ciphers if the TLS/SSL library used (NSS on RHEL/Fedora) does not have the ECC ciphers enabled by default, and the NSS in RHEL/CentOS 7 does not. This causes a problem when using CentOS 7 for something like a CDN that needs to pull content from a server using modern ECC cryptography without support for the older cryptography methods, and some sensitive servers are starting to do just that to avoid being vulnerable to various 0 day exploits that pop up with older cryptography. I think the NSS library should be rebuilt to have ECC ciphers enabled by default (I don't think that requires a version update) and that curl should be updated, with a newer build, that includes a bump to the .so version. Thoughts on this? I'm out of town, I plan to try and file a bugzilla for this when I get back, but if this sounds idiotic to most then I won't. I can solve it on my system with a local build. Thank you for your time. -- -=- Sent my from my laptop, may not be able to respond timely

2 1

CentOS-announce Digest, Vol 134, Issue 2
by centos-announce-request＠centos.org 02 Apr '16

02 Apr '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. Notice of Service Outage and followup LON1/UK Facility (Karanbir Singh) 2. Announcing release for Developer Toolset 4 on CentOS Linux 6 x86_64 SCL (Honza Horak) 3. Announcing release for Developer Toolset 4 on CentOS Linux 7 x86_64 SCL (Honza Horak) ---------------------------------------------------------------------- Message: 1 Date: Wed, 30 Mar 2016 11:25:19 +0100 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] Notice of Service Outage and followup LON1/UK Facility Message-ID: <56FBA98F.6000102(a)centos.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 == What happened == On Wednesday February 24th, at 6pm UTC time, the DC hosting some of the CentOS equipments used for various roles had suffered from multiple electricity power outages. The facility was completely dark for just under 2 hrs, and we were able to start recovering services by 8pm UTC. By midnight we had most services restored, by 2:00AM UTC Feb 25th we had all services restored. That meant that the machines in those racks were running on batteries (ups in the racks) but finally went down in an uncontrolled way due to lack ot communication with that UPS. Subsequent on Monday March 14th, we suffered another power outage in the racks, this time due to a overload on the rack power circuits. == Services that were impacted == - severity critical : mirrorlist.centos.org node (IPv6) went down (while multiple mirrorlist.centos.org nodes for IPv4 nodes were still online). That means that machines with only IPV6 connectivity couldn't get yum to work to retrieve the list of nearest mirrors. - severity medium : Our main buildservices queue management services were down; note: this did not impact our ability to build, test and deliver updates. - severity medium : www.centos.org and www.centos.org/forums weren't reachable through IPv6 : at the moment, those services are natively reachable through IPv4, but proxied through nodes in that DC for IPv6 users. Most tested browsers were falling back to IPv4 during that period - severity medium : CentOS DevCloud (https://wiki.centos.org/DevCloud) : that means that CentOS Developers weren't able to instantiate new CentOS test VMs for their work, but also weren't able to reach the existing ones. - severity low : several publicly facing small services like http://planet.centos.org , http://seven.centos.org (not critical and could be restored quickly to other VMs elsewhere) - severity low : the server leading the armv7hl builds for the Plague build farm was also offline, meaning no armhfp build during that timeframe (but not updates were to be built, so mitigated issue) = Followup actions and notes Over the years, the baseline recovery model we've used and tried to enforce is one of 'restore in place', take a downtime hit if needed - and ensure we have service continuity for the user facing components ( the mirrorlist service, the centos update and content distribution services). For other resources, like the main website etc, we ensure there are good backups available in multiple places, usable to restore services should there be a need. This model has worked well for us over the years, and we've had very little, if any, service outages that had a user impact. The restore in place/restore outside HA also meant we were able to better utilise the exclusively sponsored machines we rely on. However, as the project grows, with a lot more infrastructure being consolidated into a few locations for non CDN services, our exposure to service downtime has dramatically increased. Its clear that we need to expand the scope of where we backup to, how we backup, how we anticipate failure and our ability to restore services in a timely manner should there be facilities outages. In the coming weeks, we are going to undertake a deep dive into our Infrastructure design and delivery and try to first come up with a consolidated set of risks we need to manage against, and then work towards reducing the risk, spreading the availability as needed. Our backend storage platform for the DevCloud and persistent storage for other nodes in the facility is run from a distributed, replicated Gluster setup. Inspite of the sudden loss of power, in a production environment with hundreds of running VMs and dozens of running data jobs, we were able to trivially recover our entire data set with minimum data loss. Some of the running VMs inside the DevCloud did see local filesystem issues, but we dont think that was a backing storage issue. This event has dramatically increased out confidence in the gluster technology stack and we will certainly be looking at extending deployments for it internally. == Comments about hosting facility == Their Status post about this http://status.uk2.net/2016/02/24/london-power-outage/ We have multiple racks at this facility, and have a long standing relationship with them going back to late Summer 2012. Over this period we have had a near perfect uptime record for our equipment there. And above all we have been consistently impressed with the speed of and the knowledgeable support we've recieved at the DC. In many cases, how the facility reacts to outage defines the real service value - and in this case, we can only commend the fantastic support we had through the outage hours. We do however feel there could be better monitoring and reporting of some of the facilities information and will be working with them to improve in those regards. Fabian Arrotin and Karanbir Singh The CentOS Project -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJW+6mPAAoJEI3Oi2Mx7xbtHo8IAI+RVIDjGwJOzgJ5Ry7mHwLe Zc+aBUQklDk5oRaDk7QZHsaGp1lclNsutBk3YujNlXwMC4hUKdPwkTVuX50usQ7s kd7qF1BlElNyfMPfFJGwchIQBDOZqZxkZP4uOrvQUnIZUYfyx6NnPnGS0uatBdnw hBJ6TbgP6i50h7U0fNWjHU2I8xe0zsx1jVrvNngDMlQcIHC0d1KMtpOgSMR5f9Bn bLwghfD4/yPyqJP1sc+021ANk1+a7uXs4KKG3MXpMlFyvYmv2ict0Q/sDtz0jzCx kbRgDGm/GF1TUUENciESkHPKy3kLWA1oCicOkiEhzNz2YwFQNdNpi9PqWEK/F5Q= =bDIN -----END PGP SIGNATURE----- ------------------------------ Message: 2 Date: Thu, 31 Mar 2016 17:38:07 +0200 From: Honza Horak <hhorak(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing release for Developer Toolset 4 on CentOS Linux 6 x86_64 SCL Message-ID: <56FD445F.8060304(a)redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed I am pleased to announce the immediate availability of Developer Toolset 4 on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-4-toolchain $ scl enable devtoolset-4 bash At this point you should be able to use gcc and other tools just as a normal application. Examples of commands run might be: $ gcc hello.c $ sudo yum install devtoolset-4-valgrind $ valgrind ./a.out $ gdb ./a.out In order to view the individual components included in this collection, including additional development tools, you can run: $ sudo yum list devtoolset-4\* About Software Collections -------------------------- Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. The collection devtoolset-4 delivers version 5.2.1 of the GNU Compiler Collection, GNU Debugger, and other development, debugging, and performance monitoring tools as RPMs. The SCLo SIG in CentOS ---------------------- The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Developer Toolset collection being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Ruby, Python and others. Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html You can learn more about Software Collections concepts at: http://softwarecollections.org You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. We meet every second Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar), for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. Enjoy! Honza SCLo SIG member ------------------------------ Message: 3 Date: Thu, 31 Mar 2016 17:38:11 +0200 From: Honza Horak <hhorak(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing release for Developer Toolset 4 on CentOS Linux 7 x86_64 SCL Message-ID: <56FD4463.3040800(a)redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed I am pleased to announce the immediate availability of Developer Toolset 4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-4-toolchain $ scl enable devtoolset-4 bash At this point you should be able to use gcc and other tools just as a normal application. Examples of commands run might be: $ gcc hello.c $ sudo yum install devtoolset-4-valgrind $ valgrind ./a.out $ gdb ./a.out In order to view the individual components included in this collection, including additional development tools, you can run: $ sudo yum list devtoolset-4\* About Software Collections -------------------------- Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. The collection devtoolset-4 delivers version 5.2.1 of the GNU Compiler Collection, GNU Debugger, Eclipse development platform, and other development, debugging, and performance monitoring tools as RPMs. The SCLo SIG in CentOS ---------------------- The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Developer Toolset collection being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Ruby, Python and others. Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html You can learn more about Software Collections concepts at: http://softwarecollections.org You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. We meet every second Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar), for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. Enjoy! Honza SCLo SIG member ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 134, Issue 2 ***********************************************

1 0

SSD disk and SMART errors
by Miguel Medalha 02 Apr '16

02 Apr '16

Two days ago I installed a brand new SSDNow E50 series (Enterprise) disk on a server. I intend to move the OS there. I just did the physical install and copied a few files to and from it just to see if it was OK. I left it there, waiting for an opportunity to configure it to do real work. Now I have looked at it with smartctl -a and it gives me the following info: 1 Raw_Read_Error_Rate 0x0033 104 104 050 Pre-fail Always - 9127078 5 Reallocated_Sector_Ct 0x0033 100 100 003 Pre-fail Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 55 (241 12 0) 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 7 13 Read_Soft_Error_Rate 0x0032 104 104 000 Old_age Always - 9127078 100 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 4 170 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 8480 171 Unknown_Attribute 0x000a 100 100 000 Old_age Always - 0 172 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 174 Unknown_Attribute 0x0030 000 000 000 Old_age Offline - 6 177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 0 181 Program_Fail_Cnt_Total 0x000a 100 100 000 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 090 Old_age Always - 0 187 Reported_Uncorrect 0x0012 100 100 000 Old_age Always - 0 194 Temperature_Celsius 0x0022 028 033 000 Old_age Always - 28 (Min/Max 20/33) 195 Hardware_ECC_Recovered 0x001c 120 120 000 Old_age Offline - 9127078 196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail Always - 0 198 Offline_Uncorrectable 0x0010 120 120 000 Old_age Offline - 75479755259904 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 201 Unknown_SSD_Attribute 0x001c 120 120 000 Old_age Offline - 9127078 204 Soft_ECC_Correction 0x001c 120 120 000 Old_age Offline - 9127078 230 Unknown_SSD_Attribute 0x0013 100 100 000 Pre-fail Always - 0 231 Temperature_Celsius 0x0000 100 100 011 Old_age Offline - 0 232 Available_Reservd_Space 0x0032 000 000 000 Old_age Always - 33 233 Media_Wearout_Indicator 0x0032 000 000 000 Old_age Always - 6 234 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 7 235 Unknown_Attribute 0x0033 100 100 002 Pre-fail Always - 0 241 Total_LBAs_Written 0x0032 000 000 000 Old_age Always - 7 242 Total_LBAs_Read 0x0032 000 000 000 Old_age Always - 5 Just look at the number under "198 Offline_Uncorrectable". Is this normal for this type of disk? Is smartctl misinterpreting the disk's features? The disk has been there essentially doing nothing and it presents such enormous numbers of errors. Why? This is under CentOS 7 (1511).

2 1

Is there a way to detect/validate DHCP static IP assignment?
by David Copperfield 01 Apr '16

01 Apr '16

Hi, We have tens of networks(VLANs) in data center with a central Linux DHCP server. each network has their router to do the DHCP relay. So, the DHCP server's configuration files has tens 'subnet' statements. Because PXE booting is standard in whole data center, there are also thousands of static MAC-IP mapping 'host' statements in dhcp configuration. The big challenge with a central dhcp server is how to detect typo in the thousands of MAC-IP 'host' statements? -- a single char/digit typo here will fail a PXE booting or download wrong post-installation snippets. Is there a tool to validate all 'host' statements from another Linux box? I tried nagios check-dhcp plugin, with a series of real MAC addresses(for hosts in other different networks). Surprisingly, the IP address came back were not the static IP addresses in 'host' statement, but dynamic addresses in the pool defined for this particular network (where I ran check-dhcp from). check_dhcp was run with the following arguments: /usr/lib64/nagios/plugins/check_dhcp --verbose --server=<my_dhcp_server> --interface=eth0 --mac=<real_Mac_for_servers_in_diff_networks> --unicast remove --unicast doesn't help but just see more DHCP replys. Interestingly, with a same MAC address, and the above same command, from two Centos boxes on different network there will be different dynamic IPs! instead the static IP defined with 'host' statement. So, how can we validate static IP assignment? Thanks. Best,David,

2 3

RHEL 5 EOL
by Tris Hoar 01 Apr '16

01 Apr '16

Hi List, As an FYI Red Hat have announced the 1 year EOL notice for RHEL 5. Anyone still using CentOS 5 would do well to start planning on upgrading to 6 or 7. Tris ************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmaster(a)bgfl.org The views expressed within this email are those of the individual, and not necessarily those of the organisation *************************************************************

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2016