Re: [CentOS] how to use intel-gpu-tools
This sort of email to the list is unacceptable, and the sender has been moderated. On 05/08/2017 07:24 AM, DR MW BAFFICO wrote: -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 147, Issue 2
Send CentOS-announce mailing list submissions to
centos-annou...@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-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CESA-2017:1202 Important CentOS 6 bind Security Update
(Johnny Hughes)
2. CESA-2017:1206 Important CentOS 6 qemu-kvmSecurity Update
(Johnny Hughes)
3. CESA-2017:1204 Moderate CentOS 6 java-1.7.0-openjdk Security
Update (Johnny Hughes)
4. CESA-2017:1201 Important CentOS 6 thunderbird Security Update
(Johnny Hughes)
5. CESA-2017:1201 Important CentOS 7 thunderbird Security Update
(Johnny Hughes)
6. CESA-2017:1204 Moderate CentOS 7 java-1.7.0-openjdk Security
Update (Johnny Hughes)
--
Message: 1
Date: Tue, 9 May 2017 16:58:21 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2017:1202 Important CentOS 6 bind
SecurityUpdate
Message-ID: <20170509165821.ga49...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2017:1202 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1202.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
c1b56581baba94701da450a96e6ab96f6ac4f083e5f421c3ebe7124aa3411179
bind-9.8.2-0.62.rc1.el6_9.2.i686.rpm
e033ff2999ee5094166f858629831f12caf926c10f2156d1bf92dd5fbc6c3a7b
bind-chroot-9.8.2-0.62.rc1.el6_9.2.i686.rpm
f3bd19a5c47a27ae24967a06b7bf37b09b27631556cd1873ac6b8b9f55b41b78
bind-devel-9.8.2-0.62.rc1.el6_9.2.i686.rpm
ec7c8ae880e8366214991ca56d02bed6043665ae34657aac5814c781e2e2b5af
bind-libs-9.8.2-0.62.rc1.el6_9.2.i686.rpm
2cecf3d6f6631711bc00d8c65a89c69f35caec84fd6a32aede440c6a3f7e0163
bind-sdb-9.8.2-0.62.rc1.el6_9.2.i686.rpm
37d38b81206240ff8562534ca327ac7fdbd4592ebcee0caaa637eccd3df8a8e9
bind-utils-9.8.2-0.62.rc1.el6_9.2.i686.rpm
x86_64:
7320440995c79fe2648545554f8fa76bd1467f8873df842002783d7e8c3d7e38
bind-9.8.2-0.62.rc1.el6_9.2.x86_64.rpm
9f589d84f1278d8c2c8595e2967fdee489478359a369f11a9f4c9a26f49fbccc
bind-chroot-9.8.2-0.62.rc1.el6_9.2.x86_64.rpm
f3bd19a5c47a27ae24967a06b7bf37b09b27631556cd1873ac6b8b9f55b41b78
bind-devel-9.8.2-0.62.rc1.el6_9.2.i686.rpm
0bc38d410990965648547b2fa605fcb177512b1488b192d6dbb060cfa018ee89
bind-devel-9.8.2-0.62.rc1.el6_9.2.x86_64.rpm
ec7c8ae880e8366214991ca56d02bed6043665ae34657aac5814c781e2e2b5af
bind-libs-9.8.2-0.62.rc1.el6_9.2.i686.rpm
949b45a95464c27e4093db800058df377fb9c5f7cf866655c3952c5f7c9c262d
bind-libs-9.8.2-0.62.rc1.el6_9.2.x86_64.rpm
5cbf42814270ca79b07de4864a56eb33dbc5c8e55cccdabbec816c8abcbd4655
bind-sdb-9.8.2-0.62.rc1.el6_9.2.x86_64.rpm
97e32251f12374180ecd20ac5bce16b7c904367f9a308b9b890c46f0da452f6c
bind-utils-9.8.2-0.62.rc1.el6_9.2.x86_64.rpm
Source:
6fd6c22a5158c38ff37918a7488a7ee579918c961464891d6f06b396c39df64f
bind-9.8.2-0.62.rc1.el6_9.2.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 2
Date: Tue, 9 May 2017 16:59:13 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2017:1206 Important CentOS 6 qemu-kvm
Security Update
Message-ID: <20170509165913.ga49...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2017:1206 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1206.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
1127cd30a8d85a38840172fb9dba9bf17948011904c3f7d815d9faa7682e1808
qemu-guest-agent-0.12.1.2-2.503.el6_9.3.i686.rpm
x86_64:
5f5ac3bcae2e27129b79f0d61344dbe4a536969210980986dd30e4bd1d6014cc
qemu-guest-agent-0.12.1.2-2.503.el6_9.3.x86_64.rpm
9893748998130ab9303f158dd41673c37285dd913b5f25772ba5c7000bc5d7d8
qemu-img-0.12.1.2-2.503.el6_9.3.x86_64.rpm
b4e189c5665d88b29f1f926ae6eb155138caf570efaea9a62fc352dbb14e1e0a
qemu-kvm-0.12.1.2-2.503.el6_9.3.x86_64.rpm
c205e403f4783d35ae6f2f71800f0da072eecd9186e540c621975e341a37e04c
qemu-kvm-tools-0.12.1.2-2.503.el6_9.3.x86_64.rpm
Source:
3f668573bbb95a3a79e82cc2d57fbb8213dedcff0c99b861754fc05fdbdfb513
qemu-kvm-0.12.1.2-2.503.el6_9.3.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 3
Date: Tue, 9 May 2017 16:59:58 +
From: John
Re: [CentOS] CentOS 7 selinux
Hi Larry, > If I make a change to /etc/sysconfig/selinux do I have to restart anything > for the change to take effect? It depends. If you are changing the SELinux mode from 'enforcing' to 'permissive' and vice versa, you can make that change active in the running system by issuing the 'setenforce 1' or 'setenforce 0' command, respectively. If you want to go to or from 'disabled' or change the SELinux policy you'll need to reboot to activate the change. Regards, Peter. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 selinux
On Tue, May 09, 2017 at 02:27:27PM -0600, Warren Young wrote: > Isn’t the correct answer “yes” for every single file under that > directory? > > If it were otherwise, you’d have services continually restarting to > look for updated settings. Then because of all the resulting > inadvertent lock-outs and other failures, you’d have big block > comments at the top of those files telling you not to save the file > until you’re sure you want those settings applied immediately. You say that, but NetworkManager's default setting used to be to monitor the files in /etc/sysconfig/network-scripts/ and restart the network interfaces when you changed the ifcfg-* files. Thankfully, now you need to set 'monitor-connection-files=true' in the NetworkManager.conf to get that 'feature'. Many times I'd change an IP in the file with vi, save out of muscle memory before I realize what I've done. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 selinux
On Wed, May 10, 2017 at 9:30 AM, Peter Eckel wrote: > Hi Larry, > > > If I make a change to /etc/sysconfig/selinux do I have to restart > anything > > for the change to take effect? > > It depends. > > If you are changing the SELinux mode from 'enforcing' to 'permissive' and > vice versa, you can make that change active in the running system by > issuing the 'setenforce 1' or 'setenforce 0' command, respectively. > > If you want to go to or from 'disabled' or change the SELinux policy > you'll need to reboot to activate the change. > Thanks! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] strange system outage
I have a CentOS 7 system that I run a home grown python daemon on. I run this same daemon on many other systems without any incident. On this one system the daemon seems to die or be killed every day around 3:30am. There is nothing it its log or any system logs that tell me why it dies. However in /var/log/messages every day I see something like this: May 10 03:35:58 localhost pure-ftpd: (t...@xx.xx.xx.xx) [NOTICE] /usrMay 10 03:57:57 localhost pure-ftpd: (t...@xx.xx.xx.xx) [NOTICE] /usr/local/motor/data//B31/today/Images/CP0982436.00C_T6PH8_M0-R_1/T6PH8_M0-RN_TT6PH8_M0-R_P4_M1_FX-1_FY4_RR1_TR1_Ver3.jpg uploaded (90666 bytes, 8322.34KB/sec) Notice how the message that was being printed at 03:35:58 is truncated mid-message and the next message is at 03:57:57 – there are always messages like around the time when the daemon dies. What could be going on here? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
Am 10.05.2017 um 20:40 schrieb Larry Martell: I have a CentOS 7 system that I run a home grown python daemon on. I run this same daemon on many other systems without any incident. On this one system the daemon seems to die or be killed every day around 3:30am. There is nothing it its log or any system logs that tell me why it dies. However in /var/log/messages every day I see something like this: May 10 03:35:58 localhost pure-ftpd: (t...@xx.xx.xx.xx) [NOTICE] /usrMay 10 03:57:57 localhost pure-ftpd: (t...@xx.xx.xx.xx) [NOTICE] /usr/local/motor/data//B31/today/Images/CP0982436.00C_T6PH8_M0-R_1/T6PH8_M0-RN_TT6PH8_M0-R_P4_M1_FX-1_FY4_RR1_TR1_Ver3.jpg uploaded (90666 bytes, 8322.34KB/sec) Notice how the message that was being printed at 03:35:58 is truncated mid-message and the next message is at 03:57:57 – there are always messages like around the time when the daemon dies. What could be going on here? Have you checked /etc/cron.daily/ for a cron job to restart the pure-ftpd service? /etc/cron.daily is called from /etc/anacrontab with some randomness so that the execution time varies. Alexander ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
On Wed, May 10, 2017 at 02:40:04PM -0400, Larry Martell wrote: > I have a CentOS 7 system that I run a home grown python daemon on. I > run this same daemon on many other systems without any incident. On > this one system the daemon seems to die or be killed every day around > 3:30am. There is nothing it its log or any system logs that tell me > why it dies. However in /var/log/messages every day I see something > like this: How are you starting this daemon? Can you check the journal? Perhaps you'll see more useful information than what you see in the syslogs? -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
On Wed, May 10, 2017 at 3:05 PM, Alexander Dalloz wrote: > Am 10.05.2017 um 20:40 schrieb Larry Martell: >> >> I have a CentOS 7 system that I run a home grown python daemon on. I >> run this same daemon on many other systems without any incident. On >> this one system the daemon seems to die or be killed every day around >> 3:30am. There is nothing it its log or any system logs that tell me >> why it dies. However in /var/log/messages every day I see something >> like this: >> >> May 10 03:35:58 localhost pure-ftpd: (t...@xx.xx.xx.xx) [NOTICE] >> /usrMay 10 03:57:57 localhost pure-ftpd: (t...@xx.xx.xx.xx) [NOTICE] >> >> /usr/local/motor/data//B31/today/Images/CP0982436.00C_T6PH8_M0-R_1/T6PH8_M0-RN_TT6PH8_M0-R_P4_M1_FX-1_FY4_RR1_TR1_Ver3.jpg >> uploaded (90666 bytes, 8322.34KB/sec) >> >> >> Notice how the message that was being printed at 03:35:58 is truncated >> mid-message and the next message is at 03:57:57 – there are always >> messages like around the time when the daemon dies. What could be >> going on here? > > > Have you checked /etc/cron.daily/ for a cron job to restart the pure-ftpd > service? /etc/cron.daily is called from /etc/anacrontab with some randomness > so that the execution time varies. I will check that, but the the pure-ftpd service is not my daemon that is getting killed - I was thinking the sudden stopping of the logging and subsequent time gap would be some sort of clue as to what is happing at that time. This is a system I do not have remote access to and it's in Japan so I have to ask someone there to do things for me. Such a pain. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
On Wed, May 10, 2017 at 3:07 PM, Jonathan Billings wrote: > On Wed, May 10, 2017 at 02:40:04PM -0400, Larry Martell wrote: >> I have a CentOS 7 system that I run a home grown python daemon on. I >> run this same daemon on many other systems without any incident. On >> this one system the daemon seems to die or be killed every day around >> 3:30am. There is nothing it its log or any system logs that tell me >> why it dies. However in /var/log/messages every day I see something >> like this: > > How are you starting this daemon? I am using code something like this: https://gist.github.com/slor/5946334. > Can you check the journal? Perhaps > you'll see more useful information than what you see in the syslogs? Thanks, I will do that. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
On Wed, May 10, 2017 at 03:19:05PM -0400, Larry Martell wrote: > > How are you starting this daemon? > > I am using code something like this: https://gist.github.com/slor/5946334. Oh, I was assuming that since you called it a daemon, it was actually something started automatically on boot, instead of something you manually started and it daemonized. If it is dying, are you logged in when its running? does it require you to be connected when its running? Maybe you should run it in a screen/tmux instead of daemonizing, so you can see stderr/stdout? -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
On Wed, May 10, 2017 at 4:18 PM, Jonathan Billings wrote: > On Wed, May 10, 2017 at 03:19:05PM -0400, Larry Martell wrote: >> > How are you starting this daemon? >> >> I am using code something like this: https://gist.github.com/slor/5946334. > > Oh, I was assuming that since you called it a daemon, it was actually > something started automatically on boot, instead of something you > manually started and it daemonized. So on all the other systems that this is deployed on it is started automatically at boot and it's controlled with service or systemctl. On this system because I do not have remote access and I do not have a very competent set of hands over there it was never set up to run as a service. So a user manually starts it by running the daemon script. This had been running on the machine like that for 8 months. The nightly crash just started on April 21 and has happened every day since. > If it is dying, are you logged in when its running? I am not 100% sure, but I think the user sus, starts the daemon process and then exits the su. > does it require you to be connected when its running? No. The underlying script polls dirs looking for files, and loads data into a db. > Maybe you should run it in a > screen/tmux instead of daemonizing, so you can see stderr/stdout? stdout and stderr are written to a file and when the daemon gets killed or dies or whatever happens to it, the output in the file abruptly stops, just like what I showed in the messages file. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
On Wed, May 10, 2017 at 3:11 PM, Larry Martell wrote: > On Wed, May 10, 2017 at 3:05 PM, Alexander Dalloz wrote: >> Am 10.05.2017 um 20:40 schrieb Larry Martell: >>> >>> I have a CentOS 7 system that I run a home grown python daemon on. I >>> run this same daemon on many other systems without any incident. On >>> this one system the daemon seems to die or be killed every day around >>> 3:30am. There is nothing it its log or any system logs that tell me >>> why it dies. However in /var/log/messages every day I see something >>> like this: >>> >>> May 10 03:35:58 localhost pure-ftpd: (t...@xx.xx.xx.xx) [NOTICE] >>> /usrMay 10 03:57:57 localhost pure-ftpd: (t...@xx.xx.xx.xx) [NOTICE] >>> >>> /usr/local/motor/data//B31/today/Images/CP0982436.00C_T6PH8_M0-R_1/T6PH8_M0-RN_TT6PH8_M0-R_P4_M1_FX-1_FY4_RR1_TR1_Ver3.jpg >>> uploaded (90666 bytes, 8322.34KB/sec) >>> >>> >>> Notice how the message that was being printed at 03:35:58 is truncated >>> mid-message and the next message is at 03:57:57 – there are always >>> messages like around the time when the daemon dies. What could be >>> going on here? >> >> >> Have you checked /etc/cron.daily/ for a cron job to restart the pure-ftpd >> service? /etc/cron.daily is called from /etc/anacrontab with some randomness >> so that the execution time varies. > > I will check that, but the the pure-ftpd service is not my daemon that > is getting killed - I was thinking the sudden stopping of the logging > and subsequent time gap would be some sort of clue as to what is > happing at that time. /etc/cron.daily has: 0yum-daily.cron logrotate man-db.cron mlocate ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Thunderbird Regression
Has anyone else noticed a 10X slowing of the time it takes Thunderbird to load an email that contains graphics on CentOS 6? The last Thunderbird update moved us from Thunderbird 45 to Thunderbird 52. While Thunderbird was loading the images the hard drive was busy cranking out seeks. I have all my local home accounts mounted on a software raid. I solved the problem with a downgrade to Thunderbird 45, but that's a poor solution not keeping Thunderbird up to date with the latest security patches. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
On Wed, May 10, 2017 at 04:35:07PM -0400, Larry Martell wrote: > On Wed, May 10, 2017 at 4:18 PM, Jonathan Billings > wrote: > > On Wed, May 10, 2017 at 03:19:05PM -0400, Larry Martell wrote: > >> > How are you starting this daemon? > >> > >> I am using code something like this: https://gist.github.com/slor/5946334. > > > > Oh, I was assuming that since you called it a daemon, it was actually > > something started automatically on boot, instead of something you > > manually started and it daemonized. > > So on all the other systems that this is deployed on it is started > automatically at boot and it's controlled with service or systemctl. > On this system because I do not have remote access and I do not have a > very competent set of hands over there it was never set up to run as a > service. So a user manually starts it by running the daemon script. > > This had been running on the machine like that for 8 months. The > nightly crash just started on April 21 and has happened every day > since. > > > If it is dying, are you logged in when its running? > > I am not 100% sure, but I think the user sus, starts the daemon > process and then exits the su. > > > does it require you to be connected when its running? > > No. The underlying script polls dirs looking for files, and loads data > into a db. > > > Maybe you should run it in a > > screen/tmux instead of daemonizing, so you can see stderr/stdout? > > stdout and stderr are written to a file and when the daemon gets > killed or dies or whatever happens to it, the output in the file > abruptly stops, just like what I showed in the messages file. Could you enable core dumps (ulimit -c unlimited) then after it has died, check for core files? -- Fred Smith -- fre...@fcshome.stoneham.ma.us - The eyes of the Lord are everywhere, keeping watch on the wicked and the good. - Proverbs 15:3 (niv) - ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
