January 2016 - Discuss - lists.centos.org

C7 postfix problem
by Rainer Traut 28 Jan '16

28 Jan '16

Hi all, topology: java/tomcat app mailing to the outside via a C7 postfix relay server. problem: java app submits mail to postfix but there is _nothing_ logged in the postfix maillog. This happen for 2/3 of all mail submitted. We cannot see any trace of this submitted mail either incoming/stored/outgoing. Log from java app (shortened): DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc] DEBUG SMTP: useEhlo true, useAuth true DEBUG SMTP: trying to connect to host "xxxxxxxx", port 25, isSSL false DEBUG SMTP: Attempt to authenticate AUTH LOGIN 235 2.7.0 Authentication successful DEBUG SMTP: use8bit false DEBUG SMTP: Verified Addresses DATA 354 End data with <CR><LF>.<CR><LF> ****message text*** 250 2.0.0 Ok: queued as 8D83AC2756DF QUIT 221 2.0.0 Bye Log from the postfix server: [root@xxx postfix]# grep 8D83AC2756DF /var/log/maillog [root@xxx postfix]# This happens for 2/3 of all messages send to this server. Any idea what is happening here? Thx Rainer

2 3

CentOS-announce Digest, Vol 131, Issue 10
by centos-announce-request＠centos.org 28 Jan '16

28 Jan '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:0071 Critical CentOS 6 firefox Security Update (Johnny Hughes) 2. CESA-2016:0073 Moderate CentOS 6 bind Security Update (Johnny Hughes) 3. CESA-2016:0071 Critical CentOS 7 firefox Security Update (Johnny Hughes) 4. CESA-2016:0073 Moderate CentOS 7 bind Security Update (Johnny Hughes) 5. CESA-2016:0074 Moderate CentOS 5 bind97 Security Update (Johnny Hughes) 6. CESA-2016:0071 Critical CentOS 5 firefox Security Update (Johnny Hughes) 7. CESA-2016:0073 Moderate CentOS 5 bind Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 27 Jan 2016 13:24:01 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0071 Critical CentOS 6 firefox Security Update Message-ID: <20160127132401.GA29873(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0071 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0071.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: c6d657f5507534819aeb712af8752230bbeb50253e45e7e440d4fdeded3c0760 firefox-38.6.0-1.el6.centos.i686.rpm x86_64: c6d657f5507534819aeb712af8752230bbeb50253e45e7e440d4fdeded3c0760 firefox-38.6.0-1.el6.centos.i686.rpm 685c98c6e6206b7336074554106ac415212bacdc6060a288ad66949c1346cd5d firefox-38.6.0-1.el6.centos.x86_64.rpm Source: 18d697b64f3b8817f71b83be1471b37167206f8547643dd26d0385cda53035fd firefox-38.6.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 27 Jan 2016 13:24:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0073 Moderate CentOS 6 bind Security Update Message-ID: <20160127132433.GA30191(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0073 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0073.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b6ed7e941878203bab5f445fdf02242ebc7ddb9e106d21448fa934567b6c9d69 bind-9.8.2-0.37.rc1.el6_7.6.i686.rpm ec4e913be997eb6ecb0adb463b3e048fd258abb50719d28e3bda699ba5564ac3 bind-chroot-9.8.2-0.37.rc1.el6_7.6.i686.rpm 6d0bc1d187e270721a840ff5b444ef71def121e3fcc3b0e3000be956ccefd2cb bind-devel-9.8.2-0.37.rc1.el6_7.6.i686.rpm e4b5938891980805d1f2b6cce9d3cf35d287c6fb23955966f5c33988011002d8 bind-libs-9.8.2-0.37.rc1.el6_7.6.i686.rpm 3219ce9865b0c077cec06304bd44e6093a94e2deb20131ac9eaf12be99390c85 bind-sdb-9.8.2-0.37.rc1.el6_7.6.i686.rpm fd0239cafda5baa254ce72b463032948de416ec28a52b13239efecaf16ed4672 bind-utils-9.8.2-0.37.rc1.el6_7.6.i686.rpm x86_64: 5c6dc609593f17d383c2d7c4c491b6b782453e11ac62770461eaa569f86971de bind-9.8.2-0.37.rc1.el6_7.6.x86_64.rpm fcac37ddb041c983721cec05d536513900a0726a106a39d8bd6a5635f0b8ad76 bind-chroot-9.8.2-0.37.rc1.el6_7.6.x86_64.rpm 6d0bc1d187e270721a840ff5b444ef71def121e3fcc3b0e3000be956ccefd2cb bind-devel-9.8.2-0.37.rc1.el6_7.6.i686.rpm a2b62f0e56767af74ecc39b32cff9bab02630d2ed828e1caa4cdc225f9cdf6b0 bind-devel-9.8.2-0.37.rc1.el6_7.6.x86_64.rpm e4b5938891980805d1f2b6cce9d3cf35d287c6fb23955966f5c33988011002d8 bind-libs-9.8.2-0.37.rc1.el6_7.6.i686.rpm bafaa0e1646245658301a2aec80915fd79a28b8cac54b0fbdd33a7aeb917cce0 bind-libs-9.8.2-0.37.rc1.el6_7.6.x86_64.rpm 72f64bdd0a6deaede7760d0728da752558913fe5f266ad39b383fcda390e541a bind-sdb-9.8.2-0.37.rc1.el6_7.6.x86_64.rpm 563fb6fe2028e188ec044091e79e415b067d2073b4fde07b7f179fee3f611e77 bind-utils-9.8.2-0.37.rc1.el6_7.6.x86_64.rpm Source: f6634e8e85939b9d204cb50d84fad0d31f095fc1c351ace5c20ee89cd522a984 bind-9.8.2-0.37.rc1.el6_7.6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 27 Jan 2016 13:25:49 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0071 Critical CentOS 7 firefox Security Update Message-ID: <20160127132549.GA33092(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0071 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0071.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: be34c367e10c7dc57ece2a1e963b78ea8528f6f6dd2900111945c4b9349bb66d firefox-38.6.0-1.el7.centos.i686.rpm 2742f3432b2ddf784c0e350d66c1488546c65cc3154b974cae43ae4e94d48655 firefox-38.6.0-1.el7.centos.x86_64.rpm Source: 7fc2d1a4212d902f469f0442a705d11065a8b1b3df348f8dbd4bc8668ef050a4 firefox-38.6.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 27 Jan 2016 13:26:10 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0073 Moderate CentOS 7 bind Security Update Message-ID: <20160127132610.GA33632(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0073 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0073.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 687d126e287b5261d66dfdefd6f2275667f6172810d437d89db00fe5b3699fd8 bind-9.9.4-29.el7_2.2.x86_64.rpm 85ec2b5256b2f7317eccb164514664a6d70ef259c88fe8fdb8420265fd35a656 bind-chroot-9.9.4-29.el7_2.2.x86_64.rpm 5c787513258b287757d732b1c64081bc3c5279a4302bfd4f290df16d142e33dd bind-devel-9.9.4-29.el7_2.2.i686.rpm e8864072298c6083b61945891ddd0084da8426527e380bbd9d40f199589d6055 bind-devel-9.9.4-29.el7_2.2.x86_64.rpm a8c318b3f3bfd258ba58125e638971ea58cc9be8489f42121bd16ac2c06c178b bind-libs-9.9.4-29.el7_2.2.i686.rpm e21275bf4758672beeb929263ef90eacbe35a4ae72394c6281ac7ba7b47f8627 bind-libs-9.9.4-29.el7_2.2.x86_64.rpm 73a32ba26598b5a23b99530fe699fb934a67f3f968e584e2374a99672780fed1 bind-libs-lite-9.9.4-29.el7_2.2.i686.rpm be4a8fec4ddf26a67053fcd4d7533564e032db6aa8f351c6953f1403917a5b64 bind-libs-lite-9.9.4-29.el7_2.2.x86_64.rpm 5e07d967ce3a00f18f5c78065b1dc3d6afd85447ebcb1c45772450f80479fc29 bind-license-9.9.4-29.el7_2.2.noarch.rpm 3c42a0bc47f6ddb9df1ad59adc9847ea78ad95c1bb0dbd5cd7ddd6b2423add9d bind-lite-devel-9.9.4-29.el7_2.2.i686.rpm ac5cb51ddb57e365c99fbe15e978662ae6a11b2fbf6e3e2ba33f147b9835e858 bind-lite-devel-9.9.4-29.el7_2.2.x86_64.rpm e92f2c1f37f67be2266c54dff8049dd9ddfbb4b8748ac1c899c5288f1125b055 bind-pkcs11-9.9.4-29.el7_2.2.x86_64.rpm 21c6d74ec37c375dd97f580f33a0b4ef9a03d4605ce385e30337712327c9e012 bind-pkcs11-devel-9.9.4-29.el7_2.2.i686.rpm 1b5db2d89b0ab1c0d576a5de73f08f4a6aaded98cdf40585cb90ff1ce9e2be11 bind-pkcs11-devel-9.9.4-29.el7_2.2.x86_64.rpm 6da046cfc1bed327100f00c18257e4db6163143027f688ce95093c92ab25d890 bind-pkcs11-libs-9.9.4-29.el7_2.2.i686.rpm 581c28fbae1ad38b9b969a8e4913e3d9cfd7bd8ca3bc8d816a43bec9d93722fb bind-pkcs11-libs-9.9.4-29.el7_2.2.x86_64.rpm 5368ad7cc0023a8b6764a935b207ca5f01e2eab4a7f68f35dc931d326f7d735f bind-pkcs11-utils-9.9.4-29.el7_2.2.x86_64.rpm f1b676334768c532e108a5b2e659495957a0c3c9a56ea0e15ff00c960d0a9997 bind-sdb-9.9.4-29.el7_2.2.x86_64.rpm dcec313d83c6b9027ac92c67b74cb79e3958cbacf3f5294128a1221722a79c09 bind-sdb-chroot-9.9.4-29.el7_2.2.x86_64.rpm 3094d168064b902abd356da286858c323d6d43b518701a9a9e163868adcdcd59 bind-utils-9.9.4-29.el7_2.2.x86_64.rpm Source: f7bf841e6e6c5aa5bb8f231eaf7f069272574987f3acf4d4d895db28259518c1 bind-9.9.4-29.el7_2.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Wed, 27 Jan 2016 13:29:51 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0074 Moderate CentOS 5 bind97 Security Update Message-ID: <20160127132951.GA7893(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0074 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0074.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1ac16b73eca063cb4f562733a64e35cff3ef7873209b22c48e6bbe1b5df936e6 bind97-9.7.0-21.P2.el5_11.5.i386.rpm d00a5209fd4a6c72783037af6b7909bcfa767a66385b245ad3b287ddfe48f4b7 bind97-chroot-9.7.0-21.P2.el5_11.5.i386.rpm 9ceb0ca912faefe419906fac778a83648ba1795a5c69f6382fda81df9a023fe1 bind97-devel-9.7.0-21.P2.el5_11.5.i386.rpm 8ffd71c8d09ac29cc9a9310c7d04c5249d34fab41559a918d504125386ddc441 bind97-libs-9.7.0-21.P2.el5_11.5.i386.rpm d924ae3b48500a8982a4ccb6249dd87bc9a5fe272abdee158e1eaa7935fdb58c bind97-utils-9.7.0-21.P2.el5_11.5.i386.rpm x86_64: b157e8406abe9110c9d40d4ae745d1136929de910986c82944f85240829ae42b bind97-9.7.0-21.P2.el5_11.5.x86_64.rpm 5418786b36f906420acc4c157d35a81d4e5e78acd42ce0cb477ae3043977f78e bind97-chroot-9.7.0-21.P2.el5_11.5.x86_64.rpm 9ceb0ca912faefe419906fac778a83648ba1795a5c69f6382fda81df9a023fe1 bind97-devel-9.7.0-21.P2.el5_11.5.i386.rpm c4da10547d26ffd16aa93e0ea69a9b1d7728c0a3f69d29e50339b1449305cf36 bind97-devel-9.7.0-21.P2.el5_11.5.x86_64.rpm 8ffd71c8d09ac29cc9a9310c7d04c5249d34fab41559a918d504125386ddc441 bind97-libs-9.7.0-21.P2.el5_11.5.i386.rpm df963d049822cfbf4832f0b7fcf9481b55252248a0f7ee4e1ad554350a811e32 bind97-libs-9.7.0-21.P2.el5_11.5.x86_64.rpm 7962f4a2e941a2de8da8f8729a17d7f42b5d90a5b9f544ccd9351811dc7a2963 bind97-utils-9.7.0-21.P2.el5_11.5.x86_64.rpm Source: 7a939bb5c6f9605c0b6798511dd7d5574fdaa2f24e325aaae0bc2ba2602de81d bind97-9.7.0-21.P2.el5_11.5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 6 Date: Wed, 27 Jan 2016 13:57:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0071 Critical CentOS 5 firefox Security Update Message-ID: <20160127135723.GA9383(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0071 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0071.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7857a7a7b41cb33bf15e4d44951a9769a41087a741ce2a46dd0a22e0ce92a7f4 firefox-38.6.0-1.el5.centos.i386.rpm x86_64: 7857a7a7b41cb33bf15e4d44951a9769a41087a741ce2a46dd0a22e0ce92a7f4 firefox-38.6.0-1.el5.centos.i386.rpm 218583469a900a71f38c9232ae3a6d099f1cf93e8ed841993521e76bd50991a7 firefox-38.6.0-1.el5.centos.x86_64.rpm Source: 11dbb60ec69d824094085cb320bddd37cd8cda1f7f658d5227c43701eb6d73bb firefox-38.6.0-1.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 7 Date: Wed, 27 Jan 2016 13:59:45 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0073 Moderate CentOS 5 bind Security Update Message-ID: <20160127135945.GA9546(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0073 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0073.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ddbfbbe93f13b2ad52daa56c2d188fdbd27ec99f8c2bb47bae45795b294d0d11 bind-9.3.6-25.P1.el5_11.6.i386.rpm 25a9c6953ff01c7b5d0cae31c4d9f472501de99084a2462c12f98710791f93a1 bind-chroot-9.3.6-25.P1.el5_11.6.i386.rpm 77b5271a5e8f4b3b196f2080a522885e1ac61934aae1aee555c4a006c9e94d72 bind-devel-9.3.6-25.P1.el5_11.6.i386.rpm 7d417af61cd259bbaeeaa785da1f0d3b81322e52484618aaf264384f3d1a9b6f bind-libbind-devel-9.3.6-25.P1.el5_11.6.i386.rpm b23b685f71e43193b5f44d8c1ec94c7d437722554783f4fe49c51877395f3c45 bind-libs-9.3.6-25.P1.el5_11.6.i386.rpm 517edaa050d9d1aac33caf9df8d7697be2257ac58a62ebc4347bdf2ced679a15 bind-sdb-9.3.6-25.P1.el5_11.6.i386.rpm 86df6e077ef4232cad3d00bcad67df95412628764b43cc0e20099cd6469fc283 bind-utils-9.3.6-25.P1.el5_11.6.i386.rpm a5b33baa5bcaad17b757a30b352281a6b7cfe23b820656c68f349ad54adb63f0 caching-nameserver-9.3.6-25.P1.el5_11.6.i386.rpm x86_64: 38c75d87815be4802e9b4b0eadd6ff7aaecc7ab390b63bfd324556953606997b bind-9.3.6-25.P1.el5_11.6.x86_64.rpm 439b61a89198405603239230a83d32baf2fd2f1654716c19310748cb1d1242eb bind-chroot-9.3.6-25.P1.el5_11.6.x86_64.rpm 77b5271a5e8f4b3b196f2080a522885e1ac61934aae1aee555c4a006c9e94d72 bind-devel-9.3.6-25.P1.el5_11.6.i386.rpm 96f45a79b9d6c1639484a8a2ca9ae210e46e8dd6b4e92285fc994a7bde0d45a9 bind-devel-9.3.6-25.P1.el5_11.6.x86_64.rpm 7d417af61cd259bbaeeaa785da1f0d3b81322e52484618aaf264384f3d1a9b6f bind-libbind-devel-9.3.6-25.P1.el5_11.6.i386.rpm a02c456ce0113de0dffd642ba5a1fd2983eeb4a91a9d02653139f3cdabbb20bf bind-libbind-devel-9.3.6-25.P1.el5_11.6.x86_64.rpm b23b685f71e43193b5f44d8c1ec94c7d437722554783f4fe49c51877395f3c45 bind-libs-9.3.6-25.P1.el5_11.6.i386.rpm 024c84269610726dae11e7e5ff02c03210984bbd87cb06af13bd095cc57bffe1 bind-libs-9.3.6-25.P1.el5_11.6.x86_64.rpm 5413c5a298327da426f17910082560b27ea64bfda8d25fad526e667557ec033e bind-sdb-9.3.6-25.P1.el5_11.6.x86_64.rpm 4609a64d0b10e1ff219a4d6ddcf225bb98486db32d476dac085ffd9c4cf8db60 bind-utils-9.3.6-25.P1.el5_11.6.x86_64.rpm 6e8d5003341a937e49e221ed5bca41f680bef0143669e8a36283f07b96eddc95 caching-nameserver-9.3.6-25.P1.el5_11.6.x86_64.rpm Source: 17b44d7032712e6a3542f01e2d58a31f5a0ee89f98616231d8810bd0798e0f3f bind-9.3.6-25.P1.el5_11.6.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 131, Issue 10 ************************************************

1 0

verify clean umount
by Robert Arkiletian 28 Jan '16

28 Jan '16

This is on a C6 systems. How can I verify that an ext4 data partition is being unmounted properly at (reboot/shutdown) on a sysV init system. I've looked at S01reboot and S01halt scripts in etc but what I'm concerned about is that I mounted my partition on a tmpfs dir mount point. So if those S01 scripts try to umount the tmpfs dir first they may get a "target busy" and then they will try a force umount. (I think that's not good) Basically I'm trying to verify that the partition (on reboot/shutdown) is being unmounted before its tmpfs mount point. Is there an easy way to verify this?

1 0

NTP Service Running on Local Host does not Sync System Time
by Traiano Welcome 27 Jan '16

27 Jan '16

Hi List I have ntp running as a service on a PC, with the expectation that it would keep time in synch to my ntp server. However, while I can manually update the time using "ntpdate -u ...", I find that if I manually force the wrong time, the ntpd service does not automatically re-synch the system time with the ntp server: - Current time: [admin@lol ~]# date Wed Jan 27 10:54:21 AST 2016 - Force wrong time: [admin@lol ~]# date -s 09:29 Wed Jan 27 09:29:00 AST 2016 - Restart ntp service: [admin@lol ~]# service ntpd restart Shutting down ntpd: [ OK ] Starting ntpd: [ OK ] - Time not synched (even after about 10 minutes) [admin@lol ~]# date Wed Jan 27 09:35:52 AST 2016 - use ntpdate -u to force synch: [admin@lol ~]# ntpdate -u time.lol.com 27 Jan 11:02:28 ntpdate[18570]: step time server 172.16.100.13 offset 5154.859809 sec [osadmin@test-till ~]# [admin@lol ~]# date Wed Jan 27 11:03:09 AST 2016 I'm not sure if this is a configuration issue with ntp (ntp.conf looks fine, as well as /etc/sysconfig/ntpd.conf (pasted below). /etc/ntp.conf: restrict default nomodify notrap nopeer noquery restrict 127.0.0.1 restrict ::1 server time.lol.com driftfile /var/lib/ntp/drift /etc/sysconfig/ntpd" # Drop root to id 'ntp:ntp' by default. OPTIONS="-x -u ntp:ntp -p /var/run/ntpd.pid" # Set to 'yes' to sync hw clock after successful ntpdate SYNC_HWCLOCK=yes # Additional options for ntpdate NTPDATE_OPTIONS="" --- Here are some diagnostic queries with ntpq: --- [admin@lol ~]# ntpq -pcrv remote refid st t when poll reach delay offset jitter ============================================================================== 10.1.0.111 xxx.xx.xx.x 2 u 26 64 1 3.618 6018473 0.001 associd=0 status=c012 leap_alarm, sync_unspec, 1 event, freq_set, version="ntpd 4.2.6p5(a)1.2349-o Sat Nov 23 18:20:11 UTC 2013 (1)", processor="i686", system="Linux/2.6.32-504.1.3.el6.i686", leap=11, stratum=16, precision=-20, rootdelay=0.000, rootdisp=0.405, refid=INIT, reftime=00000000.00000000 Thu, Feb 7 2036 9:28:16.000, clock=da52e461.90fabbc4 Wed, Jan 27 2016 9:38:25.566, peer=0, tc=3, mintc=3, offset=0.000, frequency=356.208, sys_jitter=0.000, clk_jitter=0.001, clk_wander=0.000 ---- What could be the issue? Any help would be appreciated. Here is the output from running the ntpd service in debug mode: --- [admin@lol ~]# ntpd -d ntpd 4.2.6p5(a)1.2349-o Sat Nov 23 18:20:11 UTC 2013 (1) 27 Jan 09:29:58 ntpd[18652]: proto: precision = 0.931 usec 27 Jan 09:29:58 ntpd[18652]: 0.0.0.0 c01d 0d kern kernel time sync enabled event at 0 0.0.0.0 c01d 0d kern kernel time sync enabled Finished Parsing!! 27 Jan 09:29:58 ntpd[18652]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 27 Jan 09:29:58 ntpd[18652]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 27 Jan 09:29:58 ntpd[18652]: Listen and drop on 1 v6wildcard :: UDP 123 27 Jan 09:29:58 ntpd[18652]: Listen normally on 2 lo 127.0.0.1 UDP 123 restrict: op 1 addr 127.0.0.1 mask 255.255.255.255 mflags 00003000 flags 00000001 27 Jan 09:29:58 ntpd[18652]: Listen normally on 3 eth 172.16.0.213 UDP 123 restrict: op 1 addr 172.16.0.213 mask 255.255.255.255 mflags 00003000 flags 00000001 27 Jan 09:29:58 ntpd[18652]: Listen normally on 4 lo ::1 UDP 123 restrict: op 1 addr ::1 mask ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff mflags 00003000 flags 00000001 27 Jan 09:29:58 ntpd[18652]: Listen normally on 5 eth fe80::3640:b5ff:fe90:104e UDP 123 restrict: op 1 addr fe80::3640:b5ff:fe90:104e mask ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff mflags 00003000 flags 00000001 27 Jan 09:29:58 ntpd[18652]: peers refreshed 27 Jan 09:29:58 ntpd[18652]: Listening on routing socket on fd #22 for interface updates restrict: op 1 addr 0.0.0.0 mask 0.0.0.0 mflags 00000000 flags 000001d0 restrict: op 1 addr :: mask 0.0.0.0 mflags 00000000 flags 000001d0 restrict: op 1 addr 127.0.0.1 mask 255.255.255.255 mflags 00000000 flags 00000000 restrict: op 1 addr ::1 mask ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff mflags 00000000 flags 00000000 key_expire: at 0 associd 17148 peer_clear: at 0 next 1 associd 17148 refid INIT event at 0 10.1.0.111 8011 81 mobilize assoc 17148 newpeer: 172.16.0.213->10.1.0.111 mode 3 vers 4 poll 6 10 flags 0x1 0x1 ttl 0 key 00000000 27 Jan 09:29:58 ntpd[18652]: 0.0.0.0 c016 06 restart event at 0 0.0.0.0 c016 06 restart 27 Jan 09:29:58 ntpd[18652]: 0.0.0.0 c012 02 freq_set kernel 356.208 PPM event at 0 0.0.0.0 c012 02 freq_set kernel 356.208 PPM transmit: at 1 172.16.0.213->10.1.0.111 mode 3 len 48 auth_agekeys: at 1 keys 1 expired 0 receive: at 1 172.16.0.213<-10.1.0.111 mode 4 len 48 event at 1 10.1.0.111 8024 84 reachable clock_filter: n 1 off 6018.651057 del 0.003849 dsp 7.945313 jit 0.000001 . . --- I'm tempted to stick an "ntpdate -u ..." in the crontab to force time-synch, but I don't see why that's needed if ntpd service should already be fulfilling that purpose. Many thanks in advance, Traiano

6 6

CentOS 7, man
by m.roth＠5-cent.us 27 Jan '16

27 Jan '16

This is... odd. >From my workstation, where I'm directly logged in, if I ssh to any CentOS 7 box, as myself, and try to run man, it fails. Example 1: man dd man: cannot write to /var/cache/man/cat1/dd.1.gz in catman mode dd. Example 2: man dd man: can't chmod (null): Bad address man: can't unlink (null): Bad address dd. In all cases, if I sudo -s to root, I have no trouble reading the manpage. In all cases I've tried, selinux is in permissive mode. >From one of these boxes: ls -laF /var/cache/man/ | more total 832 drwxr-xr-x. 38 root root 4096 Jan 27 07:52 ./ drwxr-xr-x. 9 root root 105 Dec 28 12:42 ../ -rw-r--r--. 1 root root 190 Dec 28 13:18 CACHEDIR.TAG drwxr-xr-x. 4 root root 62 Jan 27 07:52 ca/ drwxr-xr-x. 2 root root 20 Jan 27 11:27 cat1/ <...> But it's the same in CentOS 6. Clues? mark

2 2

Re: [CentOS] Intel Xorg driver for Intel HD graphics
by Jerry Geis 27 Jan '16

27 Jan '16

> i915.preliminary_hw_support=1 Adding this to the boot - does not make it work on straight 7.2 I saw information about this - but it is mentioned on the page I included that this was no longer needed with the files listed in the link. The kernel 4.4 installs and runs fine on the NUC5C. Its the xorg-server package that is is my issue. Everything else ran fine. The problem I'm trying to solve is getting the NUC 5C to run X on 7.2. I "realize" that is all newer hardware - but if its possible it's beneficial. I just need to figure out how to compile the X server it was giving an error. Thanks, Jerry

2 1

CD-Mount on CentOS-6.7
by James B. Byrne 27 Jan '16

27 Jan '16

When I load a blank cd into the optical drive on my CentOS-6.7 workstation I am not getting any window or visible mount action on my Gnome desktop. Formerly, when I mounted a writeable media in this drive on this host I would see a nautilus style file browser window open with inducements to add files. When I visit /mnt I see nothing: ll /mnt total 0 My fstab does not seem to have much to say either: cat /etc/fstab # # /etc/fstab # Created by anaconda on Mon Sep 24 12:57:28 2012 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/vg_vhost04-lv_root / ext4 defaults 1 1 UUID=a9a7cc59-bd0c-4362-9ab6-f721e25df2f8 /boot ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_home /home ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_tmp /tmp ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_log /var/log ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_spool /var/spool ext4 defaults 1 2 /dev/mapper/vg_vhost04-lv_swap swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/vg_vhost04/lv_data_disk_images /var/data/disk_images ext4 defaults 00 /dev/vg_vhost04/lv_home_byrnejb /home/byrnejb ext4 defaults 0 0 /dev/vg_vhost04/lv_var /var_new ext3 defaults 0 0 The hardware seems to be there: lshw . . . *-cdrom description: DVD-RAM writer product: DVD-RAM GH22NS30 vendor: HL-DT-ST physical id: 1 bus info: scsi@3:0.0.0 logical name: /dev/cdrom logical name: /dev/cdrw logical name: /dev/dvd logical name: /dev/dvdrw logical name: /dev/scd0 logical name: /dev/sr0 version: 1.01 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram configuration: ansiversion=5 status=nodisc *-serial UNCLAIMED description: SMBus product: 82801JI (ICH10 Family) SMBus Controller vendor: Intel Corporation physical id: 1f.3 bus info: pci@0000:00:1f.3 version: 00 width: 64 bits clock: 33MHz configuration: latency=0 resources: memory:d0825800-d08258ff ioport:1180(size=32) . . . Now, I have not played with any of this stuff in quite some time and I used it late last year to cut CentOS-7 ISOs. So my question is: What has changed to cause this behaviour? Any ideas? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

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

27 Jan '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:0067 Important CentOS 6 java-1.6.0-openjdk Security Update (Johnny Hughes) 2. CESA-2016:0067 Important CentOS 5 java-1.6.0-openjdk Security Update (Johnny Hughes) 3. CESA-2016:0067 Important CentOS 7 java-1.6.0-openjdk Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 26 Jan 2016 13:28:19 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0067 Important CentOS 6 java-1.6.0-openjdk Security Update Message-ID: <20160126132819.GA55163(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0067 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0067.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8df06a899e26a7520bdeb3b4db31a8fe4c4686e10b2fefde977664de9c7fb658 java-1.6.0-openjdk-1.6.0.38-1.13.10.0.el6_7.i686.rpm b645b00280c6b2df08eff4b3ea35f7c5dadffd5c261cfab385aaf9b1b9f37c39 java-1.6.0-openjdk-demo-1.6.0.38-1.13.10.0.el6_7.i686.rpm 1a3a289f87f54ac2e0b351171f969e10c18f2b7f9068b37ffb962ecf3e5f2480 java-1.6.0-openjdk-devel-1.6.0.38-1.13.10.0.el6_7.i686.rpm bcae5c7e8520c7462c383d629d5e74047e2ce5991b7ac22f36ac035f0fc33000 java-1.6.0-openjdk-javadoc-1.6.0.38-1.13.10.0.el6_7.i686.rpm 30a96ce89d2188f1ee96309dfd9ba72f37c77d3d8cc924baf3dcd25ae786d5f7 java-1.6.0-openjdk-src-1.6.0.38-1.13.10.0.el6_7.i686.rpm x86_64: dc86666020c01029080793f7a80ee11ff7b8aa692ee3e5d27b36281d54f5e1a3 java-1.6.0-openjdk-1.6.0.38-1.13.10.0.el6_7.x86_64.rpm 8090ed5219f8f569c4fb0dc94242b0fcfe62415de1089b1a99ade591102ba088 java-1.6.0-openjdk-demo-1.6.0.38-1.13.10.0.el6_7.x86_64.rpm 7f3c15ee1836066bad87abca524b4af50cc449f51f7ef5a248f4f3db2b2d62af java-1.6.0-openjdk-devel-1.6.0.38-1.13.10.0.el6_7.x86_64.rpm 4ac324c5649d25af27d90af2b6310924c029ac7063f922a43e946969051cc92b java-1.6.0-openjdk-javadoc-1.6.0.38-1.13.10.0.el6_7.x86_64.rpm 0b05e4b8e47cf5c7e6d7daf23c9eb8ab620ac85840dbc6d4d50bf5c4a4aa9743 java-1.6.0-openjdk-src-1.6.0.38-1.13.10.0.el6_7.x86_64.rpm Source: 5caca590014371e8066406ef364651473a52b86e7fc56f33acbef9d9b9aa2d80 java-1.6.0-openjdk-1.6.0.38-1.13.10.0.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, 26 Jan 2016 13:50:52 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0067 Important CentOS 5 java-1.6.0-openjdk Security Update Message-ID: <20160126135052.GA6567(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0067 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0067.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a564cd9490be5ab97d050c1a1cee2090f315dc6e8993c3bb57fac0c732c6a3d3 java-1.6.0-openjdk-1.6.0.38-1.13.10.0.el5_11.i386.rpm 1e6e6102a88e6f8d1d99ba513f5d5bd27445c08ac35606126330dcb7eb309d8b java-1.6.0-openjdk-demo-1.6.0.38-1.13.10.0.el5_11.i386.rpm 5c5f8fed0f9e6ea7f009fa5db9f1d8517160a68470d5fa42d3b5964c730e1e12 java-1.6.0-openjdk-devel-1.6.0.38-1.13.10.0.el5_11.i386.rpm e3a65df6870d94b0be2553dabb647892d44564fc25ce7f091a50e711fb1bb6a3 java-1.6.0-openjdk-javadoc-1.6.0.38-1.13.10.0.el5_11.i386.rpm 7596230198a5fc3d7149f94becde9cccccc1166f03b7d664500df33bae23ea67 java-1.6.0-openjdk-src-1.6.0.38-1.13.10.0.el5_11.i386.rpm x86_64: 65e34e63b9a6d16a8019e1e7027d41438ae81722373d5847c94a0ee879a5478b java-1.6.0-openjdk-1.6.0.38-1.13.10.0.el5_11.x86_64.rpm 3018d3ea3b1a291928891409ac60be0120863848ded1f271cc2b6a332a45b102 java-1.6.0-openjdk-demo-1.6.0.38-1.13.10.0.el5_11.x86_64.rpm 276a82950dbe20324ce1322cf2cd781466b8a0b8a155b6d7f7f46a0bce2e76d9 java-1.6.0-openjdk-devel-1.6.0.38-1.13.10.0.el5_11.x86_64.rpm dc3173332668d4a3a75894c73ed938cf558592d49cc3e18c86e03a92ad776ba8 java-1.6.0-openjdk-javadoc-1.6.0.38-1.13.10.0.el5_11.x86_64.rpm e14622d70222762fad88e2f2238e6ae27c8f630e0ed29dbd78c19e0d2d0fb329 java-1.6.0-openjdk-src-1.6.0.38-1.13.10.0.el5_11.x86_64.rpm Source: 67daf7f23cfdf1dc5aecdd9d6e1fdaedf77d3863445da21200f52628ec412953 java-1.6.0-openjdk-1.6.0.38-1.13.10.0.el5_11.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 26 Jan 2016 14:24:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0067 Important CentOS 7 java-1.6.0-openjdk Security Update Message-ID: <20160126142406.GA5978(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0067 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0067.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6d2a9fcd8c0047fbf75850d6f87916da874d826cd045fd282624d4e2c9027e2a java-1.6.0-openjdk-1.6.0.38-1.13.10.0.el7_2.x86_64.rpm fc340ba9fdf41498a57f1e855c5ef4d914b1bf02dda5c3532efecdb721fbb64b java-1.6.0-openjdk-demo-1.6.0.38-1.13.10.0.el7_2.x86_64.rpm d20b7ecea5d222dd53a8795dd24ef962e6fea3e12169dabaa09408fb99c6f96f java-1.6.0-openjdk-devel-1.6.0.38-1.13.10.0.el7_2.x86_64.rpm 88daac1696331dc127050b86ead11f1e1311b630f2e8cb0105e09c54293b2a22 java-1.6.0-openjdk-javadoc-1.6.0.38-1.13.10.0.el7_2.x86_64.rpm a2e0e4314c57c089bd5a0269b43dd4f90225f689c3cf31ade4445959c8d44c72 java-1.6.0-openjdk-src-1.6.0.38-1.13.10.0.el7_2.x86_64.rpm Source: 93a4207025786c507681644aeb2d0b477bc7ff567c95a7275df008576d8a61dc java-1.6.0-openjdk-1.6.0.38-1.13.10.0.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 131, Issue 9 ***********************************************

1 0

system refuses to install monit.
by Jason Welsh 26 Jan '16

26 Jan '16

_**_So I have epel enabled on this centos 6 server, but yum -y install monit will not install monit. yum search monit does not show monit as available to be installed. [root@lb1 ~]# yum install monit Loaded plugins: fastestmirror, presto Setting up Install Process Loading mirror speeds from cached hostfile * base: mirror-centos.hostingswift.com * epel: reflector.westga.edu * extras: mirrors.usinternet.com * updates: mirrors.usinternet.com No package monit available. Error: Nothing to do If I download the rpm manually and try to localinstall it, it will not install.. [root@mb1 ~]# cat /etc/centos-release CentOS release 6.7 (Final) [root@lb1 ~]# rpm -qa | grep monit [root@lb1 ~]# uname -m x86_64 [root@lb1 ~]# ls -al monit-5.14-1.el6.x86_64.rpm -rw-r--r-- 1 root root 267556 Sep 13 13:45 monit-5.14-1.el6.x86_64.rpm [root@lb1 ~]# yum -v localinstall monit-5.14-1.el6.x86_64.rpm Loading "fastestmirror" plugin Loading "presto" plugin Config time: 0.036 Yum Version: 3.2.29 Setting up Local Package Process rpmdb time: 0.000 Examining monit-5.14-1.el6.x86_64.rpm: monit-5.14-1.el6.x86_64 Excluding monit-5.14-1.el6.x86_64 Nothing to do [root@lb1 ~]# ???!?!?!!!! I did a rpm -i of the file and that seems to install the file.. but why will it not install with yum? Jason

2 2

Enable_extended_ACL_support_in_smb.conf
by Henry McLaughlin 26 Jan '16

26 Jan '16

I am not 100% clear as to when the following is required in smb.conf on a member server: vfs objects = acl_xattr map acl inherit = yes store dos attributes = yes https://wiki.samba.org/index.php/Shares_with_Windows_ACLs#Enable_extended_A… I have confirmed Samba is compiled with ACL support: [root@centos7member ~]# smbd -b | grep HAVE_LIBACL HAVE_LIBACL [root@centos7member ~]#

1 1

bash: Samba: command not found
by Henry McLaughlin 26 Jan '16

26 Jan '16

I have installed Sernet Samba however after installation I cannot confirm the version: samba -V bash: samba: command not found

6 5

Re: [CentOS] Hylafax without modems - SIP?
by James B. Byrne 26 Jan '16

26 Jan '16

On Tue, January 26, 2016 04:57, Gary Stainburn wrote: > I've just had to replace my Hylafax server as the cooling fan in the > rack case has died and could not be replaced. > > My box runs three fax modems, one for each of the original 3 fax > machines that got skipped years ago. > > This means that I now have 3 lots of: > > USB to seral converter (new box doesn't have any COM ports. > 9pin->25-pin serial cable > Modem > power supply > phone line > analogue port on our Mitel 3300 controller > > I was wondering if there a better way? > > I've done lots of Googling and there is a lot of conflicting - and > mostly very old - information out there. > > Does anyone have any more up-to-date opinions or advice on doing this? > > Most of the concerns about reliability were based on IP latency, > but my fax server and my Mitel controller are both on the same > Procurv Gigabit switch so hopefully that would be quick enough > > We run Hylafax+ and use a Digium TDM800P analogue card in a Atom based Supermicro 1u running Asterisk to connect to our fax lines using standard RJ11 plugs. On the Asterisk host we run iaxmodem to listen to the analogue ports. Hylafax+ talks to the iaxmodem instances. This can be a network connection so it is not necessary to have Hylafax running on the host with the FXO connection. We have been running this setup with Avantfax as the UI since summer 2013 without problems. The load on the fax host is trivial. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

Re: [CentOS] What to do when you've been hacked?
by James B. Byrne 26 Jan '16

26 Jan '16

On Mon, January 25, 2016 19:12, Benjamin Smith wrote: > > Which I'd consider "best practices" and we do them. > They are specifically asking about what to do *after* a > breach. Despite all the best practices in > place, there's *still* some risk. > If someone wants in to your network then they will get in. There is no point in deluding yourself or your clients on that point. The first thing that you must do after a breach is detected, or even suspected, is to notify all affected parties. There is an institutional bias against revelation of security incidents because of the fear of embarrassment. This is often couched in terms using the word 'premature'. Failure to disclose at the earliest opportunity is unethical and ultimately self-defeating. You will never regain trust thereafter. The second thing to do, concurrently with the first, is to isolate the affected systems from the rest of your network. If that means physically pulling wires and putting the things on their own switch and LAN segment blocked from the rest of your networks then do it. If it means shutting down the affected hosts then do it. If if means disconnecting from the network at your gateway then do it. They are in and they are looking for ways to expand their foothold. Delaying containment is pointless. The third thing to do is to involve the authorities. Unauthorised computer access is an indictable offence in Canada and the UK. It is a federal felony in the U.S.A. If you have an incident then report it. That means you should have computer emergency response contact information and reporting protocols already in place. Now, with your clients and the authorities notified and the suspect systems isolated, you begin to map out your recovery strategy. The basic bones of which you have already written down and implemented in your backup and disaster recovery plan. A security breach is a disaster. You need to start with that point clearly in mind and proceed on that basis. Once corporate and client services are restored on clean hosts and reconnected to the Internet then begin your investigation. Use your AIDE and syslog records to determine the point of entry, the length of compromise and the extent of penetration. If possible identify the nature of the attackers and their target. Where possible keep the compromised hosts' disk drives unaltered for further technical analysis. Where warranted bring in forensic investigators to examine them. It will likely prove impossible to positively identify them but you should be able to glean some inkling if this was a targeted breach or an opportunistic one. If the former then they will be back and you will need to consider how to deal with the next assault. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

kernel update does not update grub boot list ...
by lejeczek 26 Jan '16

26 Jan '16

.. in that expected way where newly installed kernel is set to boot as default. would you suggest where to look, what to check? many thanks.

2 2

CentOS-announce Digest, Vol 131, Issue 8
by centos-announce-request＠centos.org 26 Jan '16

26 Jan '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:0063 Important CentOS 6 ntp Security Update (Johnny Hughes) 2. CESA-2016:0063 Important CentOS 7 ntp Security Update (Johnny Hughes) 3. CESA-2016:0064 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Jan 2016 14:27:37 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0063 Important CentOS 6 ntp Security Update Message-ID: <20160125142737.GA16278(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0063 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0063.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b172e4c9936ba6db7e7df9a611f2ba305b0682bb0545c03ba23bc501ae7833f8 ntp-4.2.6p5-5.el6.centos.4.i686.rpm 0cbe654866db67e07ba4dbea484f6eea8136a0a23e5123dfebf1ac097162dfb4 ntpdate-4.2.6p5-5.el6.centos.4.i686.rpm 9a0cbc08c20ee5b43fd8518a2ccd0a13a274b0464a688fef4cc10b940c848993 ntp-doc-4.2.6p5-5.el6.centos.4.noarch.rpm 4fdf6a42d2a1178394d328832e70284d631a0b14535af97ffa94d659b545d4b8 ntp-perl-4.2.6p5-5.el6.centos.4.i686.rpm x86_64: c9bcbc789b84223a297f54197d407520f56d0d4d4775787dd0f746426d2e8866 ntp-4.2.6p5-5.el6.centos.4.x86_64.rpm 07fcdccf4e98b884fc6e99bf568fb037547d7340083ba913d598d0b53cc162d7 ntpdate-4.2.6p5-5.el6.centos.4.x86_64.rpm 9a0cbc08c20ee5b43fd8518a2ccd0a13a274b0464a688fef4cc10b940c848993 ntp-doc-4.2.6p5-5.el6.centos.4.noarch.rpm c2069c233875863df714450ba095380586746768fab379e7fe737c915e27721f ntp-perl-4.2.6p5-5.el6.centos.4.x86_64.rpm Source: 7a3f04e3f4c7402309a5a7cbf9a7997778298cd1dbac24efd2ca98b9d75eacec ntp-4.2.6p5-5.el6.centos.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 25 Jan 2016 15:08:59 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0063 Important CentOS 7 ntp Security Update Message-ID: <20160125150859.GA31510(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0063 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0063.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4b606ea94878f359cc016e2fb3545c87af50b77cab65c21ca7daa534c5a49252 ntp-4.2.6p5-22.el7.centos.1.x86_64.rpm 4a320e7a12cf9b0e662e05a5371df9fe3b8fe3881f8b489ec02fc97769ac8628 ntpdate-4.2.6p5-22.el7.centos.1.x86_64.rpm 37c9092a5fc997a11dd02bd4748024584c305f691437e4546418e453cec19c7e ntp-doc-4.2.6p5-22.el7.centos.1.noarch.rpm b71ff70a1dfd7ed80ad43c76d651b821b5cdc3cd4360b87f244b4aff154d5387 ntp-perl-4.2.6p5-22.el7.centos.1.noarch.rpm 71e36f16c2b105c208284bdfc4d08b1e93b0822fa7f08a569043c4cefdccf4f8 sntp-4.2.6p5-22.el7.centos.1.x86_64.rpm Source: 207b221dcadaa5ce149bd47258f23eafe973686dfe31030d689850dfe6b4d9ed ntp-4.2.6p5-22.el7.centos.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 26 Jan 2016 02:08:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0064 Important CentOS 7 kernel Security Update Message-ID: <20160126020806.GA42992(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0064 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0064.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 29350967bf2d01358deaf9a99e1520eeb0af7bedae1d1cde8fdc73bf80731d4c kernel-3.10.0-327.4.5.el7.x86_64.rpm 674d565da50e81500b2b7fc49fc5a8005e2819b07acbd1d405078e7bc605036a kernel-abi-whitelists-3.10.0-327.4.5.el7.noarch.rpm 3c412b021fdab6881f46d0d7a09e9a2f2e3ffb33a93fb4f365f508e8e35b5b2d kernel-debug-3.10.0-327.4.5.el7.x86_64.rpm 21b228926c50ffcf49e55ed47bab7012d7cb55b495e84934138089cc1595933b kernel-debug-devel-3.10.0-327.4.5.el7.x86_64.rpm 0e2b4c67a11169566fa3d14818dbfa96454a1ddf204d574e102d4f340cbb415c kernel-devel-3.10.0-327.4.5.el7.x86_64.rpm 1d345ee1527bdbf3aacbf97b39ce22fba2c9ba0c76e511970090b7a52c45b246 kernel-doc-3.10.0-327.4.5.el7.noarch.rpm ad1cdc0d750914db690dfd58b0b58a16b09d0cadbd68281c26bbf4a31ef06f85 kernel-headers-3.10.0-327.4.5.el7.x86_64.rpm 128d4dec4b6fd338ad2974140d4ac1e79737539324669c2d9135dd338817a653 kernel-tools-3.10.0-327.4.5.el7.x86_64.rpm 6210ac1a8f1f0d783b8ea0ce617475eb124ce1163f51d5aba6988be8319e4bd7 kernel-tools-libs-3.10.0-327.4.5.el7.x86_64.rpm d826d7458ffed75e9fcb1b3ec86977c1593044a9b54336819d5caf507be8f8e1 kernel-tools-libs-devel-3.10.0-327.4.5.el7.x86_64.rpm 8fa80deb6de526b395a35c4d49e2c9ac669397a954452bf454f87a0b182ba20d perf-3.10.0-327.4.5.el7.x86_64.rpm 4d65609eec974b3172035c5a0eacf470c565145cda94d6c6d4399766714d9ea6 python-perf-3.10.0-327.4.5.el7.x86_64.rpm Source: ad702b51357600291eededf7c8d8b83bbfca93c106fcb0515aa3040110a4199c kernel-3.10.0-327.4.5.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 131, Issue 8 ***********************************************

1 0

Hylafax without modems - SIP?
by Gary Stainburn 26 Jan '16

26 Jan '16

I've just had to replace my Hylafax server as the cooling fan in the rack case has died and could not be replaced. My box runs three fax modems, one for each of the original 3 fax machines that got skipped years ago. This means that I now have 3 lots of: USB to seral converter (new box doesn't have any COM ports. 9pin->25-pin serial cable Modem power supply phone line analogue port on our Mitel 3300 controller I was wondering if there a better way? I've done lots of Googling and there is a lot of conflicting - and mostly very old - information out there. Does anyone have any more up-to-date opinions or advice on doing this? Most of the concerns about reliability were based on IP latency, but my fax server and my Mitel controller are both on the same Procurv Gigabit switch so hopefully that would be quick enough

1 0

What to do when you've been hacked?
by Benjamin Smith 26 Jan '16

26 Jan '16

No, we haven't been hacked. ;) We have a prospective client who is asking us what our policy is in the event of unauthorized access. Obviously you fix the system(s) that have been compromised, but what steps do you take to mitigate the effects of a breach? What is industry best practice? So far, searches haven't produced anything that looks consistent, except maybe identity monitoring for financial data. (EG: Target breach) We host a significant amount of educational data, but no financial information. How would we even respond to this question? I've also posted this question at https://www.reddit.com/r/linuxadmin/comments/42mi1r/what_to_do_when_youve_b… Thanks, Ben

3 4

Re: [CentOS] Just need to vent
by James B. Byrne 25 Jan '16

25 Jan '16

On Sun, January 24, 2016 11:45, Peter Duffy wrote: > > Trouble is that when you go from 6 to 7, you also have the delights of > systemd and grub 2 to contend with. > . . . > Similarly with others who have commented, I simply cannot > understand why the maintainers of crucial components in > linux have this thing about making vast changes which impact > (usually adversely) on users and admins, without (apparently) > any general discussion or review of the proposed changes. > What happened to RFCs? Maybe it's a power thing - we > can do it, so we're gonna do it, and if ya don't like it, tough! > Part of it is marketing. Most of it is ego. > It would be very interesting to know how many other users are > still on CentOS/Red Hat 6 as a result of reluctance to enjoy > all the - erm - improvements in 7. Maybe it's time to fork > CentOS 6 and make it look and behave like 7 without systemd > (or even better, with some way of selecting the init methodology > at install-time and afterwards), and with gnome2 (or a clear > choice between 2 and 3). Call it DeCentOS. > Depending on how the systemd drama plays out CentOS-6 may well be our last RH derivative, and perhaps our last Linux. At the moment we are withholding any judgement on the matter for want of clear empirical evidence respecting systemd's benefits and risks. On our test CentOS-7 systems we eventually switched to Mate. That in itself sorted out most of the most visceral negativity to RHEL7. But systemd, rightly or wrongly, remains a controversial issue here. And, being more interested in stability than features we will await further developments on that front. Maybe someone could convince Linus to embed an init processor into the kernel in a manner similar to how KVM made its way. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

Re: [CentOS] Intel Xorg driver for Intel HD graphics
by Earl A Ramirez 24 Jan '16

24 Jan '16

What happen if you append i915.preliminary_hw_support=1 to the kernel argument?

1 0

Intel Xorg driver for Intel HD graphics
by Jerry Geis 24 Jan '16

24 Jan '16

I found this page: https://01.org/linuxgraphics/downloads/2015q4-intel-graphics-stack-release I have an Intel NUC5C with "Intel HD" graphics and I'm trying to use CentOS 7.2 I downloaded the files suggested: cairo-1.14.4.tar.xz libva-1.6.2.tar.bz2 mesa-11.0.4.tar.xz intel-gpu-tools-1.13.tar.bz2 libva-intel-driver-1.6.2.tar.bz2 xf86-video-intel-2.99.917.tar.gz libdrm-2.4.65.tar.gz xorg-server-1.18.0.tar.bz2 and compiled, then installed them. All are working except the final one xorg-server-1.18 On the configure I get these errors: configure: error: Package requirements (fixesproto >= 5.0 damageproto >= 1.1 xcmiscproto >= 1.2.0 xtrans >= 1.3.5 bigreqsproto >= 1.1.0 xproto >= 7.0.28 randrproto >= 1.5.0 renderproto >= 0.11 xextproto >= 7.2.99.901 inputproto >= 2.3 kbproto >= 1.0.3 fontsproto >= 2.1.3 pixman-1 >= 0.27.2 videoproto compositeproto >= 0.4 recordproto >= 1.13.99.1 scrnsaverproto >= 1.1 resourceproto >= 1.2.0 xf86driproto >= 2.1.0 glproto >= 1.4.17 dri >= 7.8.0 presentproto >= 1.0 xineramaproto xkbfile pixman-1 >= 0.27.2 xfont >= 1.4.2 xau libsystemd-daemon xshmfence >= 1.1) were not met: Requested 'xproto >= 7.0.28' but version of Xproto is 7.0.26 Requested 'randrproto >= 1.5.0' but version of RandrProto is 1.4.0 I'm not sure what to do with these errors. The "proto" packags are nothing that I can install -devel packages for as these packages are not even present on the Packages directory that I see. Any thoughts how I might get the Xorg server running on the "Intel HD" graphics of the NUC5C? Thanks, Jerry

3 2

cups-1.3.7-32.el5_11.x86_64 may have a problem
by Greg Ennis 24 Jan '16

24 Jan '16

Everyone, I have a problem I have been chasing for about three weeks and only occurred after cups was updated with cups-1.6.3-22.el7. I would be interested as to whether any one else has had this problem, and would entertain suggestions as to how I can debug the problem. My Centos 5 server is a gateway as well as a cups print server that has been in place for 8 years and has continued to perform exceptionally well. My Centos 7 server is a mail server and archive file server that is in the same network as my Centos 5 server described above. I have cups active on this server, which communicates to the Centos 5 server described above as well as another remote Centos 5 cups print server and another remote Centos 6 cups print server. Each of the latter two print servers are on different networks than the Centos 7 server that has the problem. The problem that has been occurring for the last three weeks appears to be related to the Centos 7 server or communication failure between it and the Centos 5 print server in the same network. What happens is that when the Centos 7 archive server receives a command to print an archived file on one of the printers inside its own network it appears to send several print commands to the Centos 5 server which causes the file to be printed several times. What happens is that the users eventually turn off the printer to keep the file from being printed dozens of times, and eventually the cups print queue on the Centos 5 server becomes full and all the printers in that network become unreachable with print commands. It is interesting that the remote print servers appear to function normally during this time. The only way I have figured out to remedy the problem is the use the "cancel -u user" command on the Centos 5 server to get rid of the command on the Centos 5 server and to use cancel lpt2-xxxxx on the Centso 7 server to get rid of the command on the archive server. When I evaluate the logs, I am either blind to the problem or am not seeing much I can piece together. Both machines have all updates and are listed as : Gateway and Cups Print Server : CentOS release 5.11 (Final) with 2.6.18-407.el5.centos.plusxen kernel with cups-1.3.7-32.el5_11.x86_64 Mail server and Archive File server : CentOS Linux release 7.2.1511 (Core) with 3.10.0-327.4.4.el7.x86_64 kernel with cups-1.6.3-22.el7.x86_64 If any of you have ideas, would sure appreciate your help. Greg Ennis

2 2

How does Live CD find OS's?
by Timothy Murphy 24 Jan '16

24 Jan '16

If I boot into CentOS on my home server from a Live CD or USB stick and go to Troubleshoot, it lists OS's it finds on the machine. How does it find these OS's? Presumably it looks through all the partitions on all the hard disks for something that looks like an OS? But how exactly does it identify an OS? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

3 4

HDD badblocks
by Alessandro Baggi 23 Jan '16

23 Jan '16

Hi list, I've a notebook with C7 (1511). This notebook has 2 disk (640 GB) and I've configured them with MD at level 1. Some days ago I've noticed some critical slowdown while opening applications. First of all I've disabled acpi on disks. I've checked disk for badblocks 4 consecutive times for disk sda and sdb and I've noticed a strange behaviour. On sdb there are not problem but with sda: 1) First run badblocks reports 28 badblocks on disk 2) Second run badblocks reports 32 badblocks 3) Third reports 102 badblocks 4) Last run reports 92 badblocks. Running smartctl after the last badblocks check I've noticed that Current_Pending_Sector was 32 (not 92 as badblocks found). To force sector reallocation I've filled the disk up to 100%, runned again badblocks and 0 badblocks found. Running again smartctl, Current_Pending_Sector 0 but Reallocated_Event Count = 0. Why each consecutive run of badblocks reports different results? Why smartctl does not update Reallocated_Event_Count? Badblocks found on sda increase/decrease without a clean reason. This behaviuor can be related with raid (if a disk had badblocks this badblock can be replicated on second disk?)? What other test I can perform to verify disks problems? Thanks in advance.

12 27

Re: [CentOS] How to get UEFI setting by shell?
by wk 23 Jan '16

23 Jan '16

Hi, another question.With secure boot on, I make a kernel module test.ko Then insmod test.ko: [root@localhost linux]# insmod test.ko insmod: ERROR: could not insert module test.ko: Required key not available How can I sign my test.ko for CentOS7.1? If I set secure boot off, insmod test.ko will be successful. w.k. ------------------ Original ------------------ From: "我自己的邮箱";<304702903(a)qq.com>; Date: Fri, Jan 22, 2016 03:07 PM To: "eero.volotinen"<eero.volotinen(a)iki.fi>; "gordon.messmer"<gordon.messmer(a)gmail.com>; Cc: "centos"<centos(a)centos.org>; Subject: Re: [CentOS] How to get UEFI setting by shell? volotinen and gordon.messmer: thank you for your answers. w.k. ------------------ Original ------------------ From: "Gordon Messmer";<gordon.messmer(a)gmail.com>; Date: Fri, Jan 22, 2016 02:13 PM To: "CentOS mailing list"<centos(a)centos.org>; Subject: Re: [CentOS] How to get UEFI setting by shell? On 01/21/2016 09:47 PM, wk wrote: > How to check/get UEFI information by shell/bash terminal ? example:if UEFI is enabled? if secure boot is enabled? Systems that boot via UEFI will have /sys/firmware/efi. You may have access to your secure boot setting in /sys/firmware/efi/efivars/, or in the output of "bootctl --path /boot/efi status" _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

5 15

How to get UEFI setting by shell?
by wk 22 Jan '16

22 Jan '16

Hi, CentOS7.1, Dell PowerEdge R730xd. How to check/get UEFI information by shell/bash terminal ? example:if UEFI is enabled? if secure boot is enabled? Thanks.

4 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2016