Discuss January 2017

discuss@lists.centos.org

125 participants
117 discussions

Re: [CentOS] time zone
by Richard 01 Feb '17

01 Feb '17

> Date: Tuesday, January 31, 2017 18:16:36 -0500 > From: TE Dukes <tdukes(a)palmettoshopper.com> > >> From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of >> Richard Sent: Tuesday, January 31, 2017 5:19 PM >> >> >> > Date: Tuesday, January 31, 2017 16:59:32 -0500 >> > From: TE Dukes <tdukes(a)palmettoshopper.com> >> >> > >> > From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of >> > Richard Sent: Tuesday, January 31, 2017 4:44 PM >> >> > >> >> Date: Tuesday, January 31, 2017 16:02:37 -0500 >> >> From: TE Dukes <tdukes(a)palmettoshopper.com> >> >> >> >> Today, I started getting this error when trying to login to >> >> zoneminder: >> >> >> >> ZoneMinder is not installed properly: php's date.timezone is >> >> not set to a valid timezone >> >> >> >> Zoneminder has been running since last Wednesday when I >> >> installed it. Today, I get this. >> >> >> >> In /etc/php.ini, I have date.timezone = America/New_York, which >> >> I added when zoneminder was installed. >> >> >> >> Output from date: Tue Jan 31 15:56:26 EST 2017 >> >> >> >> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25 >> >> 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York >> >> >> >> Been searching for hours for another file that may be overriding >> >> php.ini >> >> >> > >> > Put a simple php page on your/the server (where zoneminder is >> > running) with the "phpinfo()" function, and then look at the >> > timezone information in the "date" section of the output. >> > >> > If it isn't showing the correct value, check the location of the >> > php.ini that is being used in the "Loaded Configuration File" >> > value toward the top of that output. >> > >> > By default, php doesn't use the system's TZ, >> > >> > >> > Hello, >> > >> > I did, it shows the error about not being correctly set: >> > >> > Warning: phpinfo(): It is not safe to rely on the system's >> > timezone settings. You are *required* to use the date.timezone >> > setting or the date_default_timezone_set() function. In case you >> > used any of those methods and you are still getting this >> > warning, you most likely misspelled the timezone identifier. We >> > selected the timezone 'UTC' for now, but please set >> > date.timezone to select your timezone. in >> > /var/www/html/phpinfo.php on line 4 >> > >> > Why would it just start doing this? >> > >> >> Obviously can't answer that as we don't know enough about what >> changes you may have made to your system. The default php.ini >> doesn't have a TZ set, so will always give that message >> unless/until you add a TZ. >> >> However, to fix this: >> >> - check the location of the php.ini that is being referenced, >> as indicated above (generally /etc/php.ini). >> >> - edit that php.ini file to set a correct TZ following the >> "date.timezone =" entry. >> >> - be certain to uncomment that line. >> >> - you probably need to restart the apache server to get any >> change picked up. >> > > [Date] > ; Defines the default timezone used by the date functions > ; http://php.net/date.timezone > date.timezone = America/New_York > > Its set. Not sure why its not seeing it. The only changes I made to > php.ini was this last week when I installed 7.3 and zoneminder. > > Its been working up till about noon today. > You need to make certain that the php.ini where you have that setting is the one that is being referenced by the server. See above notes on checking that. The apache server needs to be restarted to load changes made to the php.ini. These things don't change "magically". If this worked until noon, I'd check various logs to see who/what made changes then - including looking to see if the apache server was restarted then and loaded changes made previously.

2 5

Mail issues
by TE Dukes 01 Feb '17

01 Feb '17

I know I'm wearing you guys out. I thought I had mail working. It is but it isn't. Mail is stuck in /var/spool/mail. This is a fresh install of dovecot and postfix. I have uninstalled mailscanner as well until I can figure out what's wrong. I sent a test mail from root to tdukes but its not being delivered to ~/Maildir Here's the clip from maillog: Jan 30 18:40:42 ts130 postfix/pickup[4828]: 2DF2D82CA5B9: uid=0 from=<root> Jan 30 18:40:42 ts130 postfix/cleanup[6070]: 2DF2D82CA5B9: message-id=<20170130234042.2DF2D82CA5B9(a)ts130.palmettodomains.com> Jan 30 18:40:42 ts130 postfix/qmgr[4829]: 2DF2D82CA5B9: from=<root(a)ts130.palmettodomains.com>, size=480, nrcpt=1 (queue active) Jan 30 18:40:42 ts130 postfix/local[6071]: 2DF2D82CA5B9: to=<tdukes(a)ts130.palmettodomains.com>, orig_to=<tdukes>, relay=local, delay=0.1, delays=0.07/0.01/0/0.03, dsn=2.0.0, status=sent (delivered to mailbox) Jan 30 18:40:42 ts130 postfix/qmgr[4829]: 2DF2D82CA5B9: removed Jan 30 18:40:49 ts130 dovecot: imap-login: Login: user=<tdukes>, method=PLAIN, rip=::1, lip=::1, mpid=6078, secured, session=<iqNhWFhHcgAAAAAAAAAAAAAAAAAAAAAB> Jan 30 18:40:49 ts130 dovecot: imap(tdukes): Disconnected: Logged out in=82 out=495 Do I need to install additional packages that move mail to the user's /Maildir? TIA

5 8

Re: [CentOS] time zone
by Richard 31 Jan '17

31 Jan '17

> Date: Tuesday, January 31, 2017 16:02:37 -0500 > From: TE Dukes <tdukes(a)palmettoshopper.com> > > Today, I started getting this error when trying to login to > zoneminder: > > ZoneMinder is not installed properly: php's date.timezone is not > set to a valid timezone > > Zoneminder has been running since last Wednesday when I installed > it. Today, I get this. > > In /etc/php.ini, I have date.timezone = America/New_York, which I > added when zoneminder was installed. > > Output from date: Tue Jan 31 15:56:26 EST 2017 > > Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25 > 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York > > Been searching for hours for another file that may be overriding > php.ini > Put a simple php page on your/the server (where zoneminder is running) with the "phpinfo()" function, and then look at the timezone information in the "date" section of the output. If it isn't showing the correct value, check the location of the php.ini that is being used in the "Loaded Configuration File" value toward the top of that output. By default, php doesn't use the system's TZ,

2 3

multipath show config different in CentOS 7?
by Gianluca Cecchi 31 Jan '17

31 Jan '17

Hello, suppose I want to use a special configuration for my IBM/1814 storage array luns, then I put something like this in multipath.conf devices { device { vendor "IBM" product "^1814" product_blacklist "Universal Xport" path_grouping_policy "group_by_prio" path_checker "rdac" features "0" hardware_handler "1 rdac" prio "rdac" failback immediate rr_weight "uniform" no_path_retry "12" } } In CentOS 6.x when you restart multipathd or restart server, using multipathd -k multipathd> show config multipathd> exit in output you see your particular configuration instead than the default one for this particular device. In CentOS 7.3 instead I see it two times, the first one with the default built-in values (eg "no_path_retry fail") and at the end the customized one. So it is not clear what is the actual configuration that device mapper multipath is using... The last wins? Is this expected behaviour? In that case what command can I use to crosscheck it (apart from real testing that is anyway necessary to verify too)? Eg in CentOS 7.3 I'm using device-mapper-multipath-0.4.9-99.el7_3.1.x86_64 while on CentOS 6.8 I'm using device-mapper-multipath-0.4.9-93.el6.x86_64 Thanks in advance, Gianluca

2 1

time zone
by TE Dukes 31 Jan '17

31 Jan '17

Today, I started getting this error when trying to login to zoneminder: ZoneMinder is not installed properly: php's date.timezone is not set to a valid timezone Zoneminder has been running since last Wednesday when I installed it. Today, I get this. In /etc/php.ini, I have date.timezone = America/New_York, which I added when zoneminder was installed. Output from date: Tue Jan 31 15:56:26 EST 2017 Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York Been searching for hours for another file that may be overriding php.ini TIA

1 0

Question about 7.3
by TE Dukes 31 Jan '17

31 Jan '17

I haven't done a fresh install in years. I've always gone the upgrade route. Seemed to have always worked for me. I moved to 7.3 since it supports the latest versions of some programs I want to use to implement as a backup server/RAID/NAS for 3 machines here at home and a remote laptop at work. So, the question is, is there something different in 7.3 than the previous 7 versions? The reason I ask is I was running a lesser version of 7, I think 7.1, as a VM on 6.8. I remember I chose not to install the most recent version at the time. Never had these issues. Not really issues but everything just worked without a lot of expertise involved. One thing I could never figure out is that on 6.8, I have the zoneminder repo installed and when I did a yum update on the 7.1 VM, it was also accessing the zmrepo which wasn't installed. Just thought it was odd. Anyway, I really appreciate the help and keep paying it forward!!

3 2

CentOS-announce Digest, Vol 143, Issue 12
by centos-announce-request＠centos.org 31 Jan '17

31 Jan '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. Release for CentOS AltArch 7 (1611) on i386 Architecture (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 30 Jan 2017 07:24:20 -0600 From: Johnny Hughes <johnny(a)centos.org> To: CentOS-Announce <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS AltArch 7 (1611) on i386 Architecture Message-ID: <7a4903a6-8535-0cb4-a2ed-19c66b61ee87(a)centos.org> Content-Type: text/plain; charset="utf-8" The CentOS AltArch SIG is a group of people working to build alternative architecture support derived from CentOS Linux's sources. You can find more details about the AltArch group at: https://wiki.centos.org/SpecialInterestGroup/AltArch Including details on how to get involved and ways to get help for architecture specific issues. This is the release announcement for the i386 (Intel 32-bit) Architecture based on the source code released for CentOS-7 (1611). It includes all packages that build on x86 32-bit processors. The release notes for the normal CentOS-7 apply: https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 with the following notes that are specific to i386: https://wiki.centos.org/SpecialInterestGroup/AltArch/i386 If you already have a previous version of CentOS-7 i386 installed, just running 'yum update' will get you the latest packages installed. ISOs can be downloaded from: http://mirror.centos.org/altarch/7/isos/i386/ Here are the SHA256SUMS for the ISOs: CentOS-7-i386-DVD-1611.iso: 25eff443460d53155cb837983c947fb3d74f4c0a3077dc699c7d50e9fdb4c0f3 CentOS-7-i386-Everything-1611.iso 578a475248ecef427269357b7ff22b973a007f534988f39f365b8dded43fad72 CentOS-7-i386-LiveGNOME-1611.iso: 16a75041a77e4d98922d2f68c54abef35f50a1e8aa863f182ab84b443cb0fcd1 CentOS-7-i386-LiveKDE-1611.iso: f9651851adee59d646b509757186f038f2b453d285d92dce5b7b91c396d20d1a CentOS-7-i386-Minimal-1611.iso: bf0e17041aad294fbb3fa5c6fb100258ace4f62b94d5bf3356b40f9807a88805 CentOS-7-i386-NetInstall-1611.iso: 249c344d3e82f49be3195e06741276f409815b1d4785f1439fc47c342eb6dd7c =========================== The CentOS team will have a Dojo in Brussels, Belgium on Friday 3th February 2017: https://wiki.centos.org/Events/Dojo/Brussels2017 I will be at the Dojo to discuss the i386 distribution with those who are interested. I will also be at the CentOS Booth at FOSDEM 2017 ( https://fosdem.org/2017/ ) in Brussels, Belgium on February 4th and 5th, 2017. I will also attend the Config Management Camp EU ( http://cfgmgmtcamp.eu/ ) in Ghent, Belgium on the 6th of February, 2017. If you have any questions and will be at any of those locations, please look me up. Bug reports and feedback about specific packages should be filed at https://bugs.centos.org/ against the relevant package name, for project CentOS Linux 7, in the same manner as you would for x86_64. However, do mention the architecture as applicable. =========================== Johnny Hughes CentOS-7 i386 AltArch Maintainer Twitter: @JohnnyCentOS Freenode IRC: hughesjr

1 0

CentOS 6, flash-plugin crashing
by m.roth＠5-cent.us 31 Jan '17

31 Jan '17

Anyone else seeing this? I'm playing streaming media, and after about 10 or 15 min, flash-plugin crashes. I've had this happen today on streams from two separate radio stations. mark

2 1

tor and selinux
by Mark 30 Jan '17

30 Jan '17

I'm experimenting with tor hidden services and got it to work nicely on my Centos7, with tor from epel. That is, until I booted the machine. Then SELinux kicked in and in the logs there's [warn] Directory /var/lib/tor/hidden_service/ cannot be read: Permission denied The permissions are drwx------. 2 toranon toranon 4096 Jan 28 23:39 hidden_service And SELinux gives the following SELinux is preventing /usr/bin/tor from using the dac_override capability. ***** Plugin dac_override (91.4 confidence) suggests ********************** If you want to help identify if domain needs this access or you have a file with the wrong permissions on your system Then turn on full auditing to get path information about the offending file and generate the error again. Do Turn on full auditing # auditctl -w /etc/shadow -p w Try to recreate AVC. Then execute # ausearch -m avc -ts recent If you see PATH record check ownership/permissions on file, and fix it, otherwise report as a bugzilla. ***** Plugin catchall (9.59 confidence) suggests ************************** If you believe that tor should have the dac_override capability by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'tor' --raw | audit2allow -M my-tor # semodule -i my-tor.pp Additional Information: Source Context system_u:system_r:tor_t:s0 Target Context system_u:system_r:tor_t:s0 Target Objects Unknown [ capability ] Source tor Source Path /usr/bin/tor Port <Unknown> Host <Unknown> Source RPM Packages tor-0.2.8.12-1.el7.x86_64 Target RPM Packages Policy RPM selinux-policy-3.13.1-102.el7_3.13.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name host Platform Linux host 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64 x86_64 Alert Count 5 First Seen 2017-01-29 22:42:46 EST Last Seen 2017-01-29 22:42:51 EST Local ID 51ceb58e-19cf-4f8f-ab1e-fe48265aaf1d Raw Audit Messages type=AVC msg=audit(1485747771.709:106): avc: denied { dac_override } for pid=2253 comm="tor" capability=1 scontext=system_u:system_r:tor_t:s0 tcontext=system_u:system_r:tor_t:s0 tclass=capability type=AVC msg=audit(1485747771.709:106): avc: denied { dac_read_search } for pid=2253 comm="tor" capability=2 scontext=system_u:system_r:tor_t:s0 tcontext=system_u:system_r:tor_t:s0 tclass=capability type=SYSCALL msg=audit(1485747771.709:106): arch=x86_64 syscall=open success=no exit=EACCES a0=7fcd2c12fe90 a1=20000 a2=0 a3=1 items=0 ppid=1 pid=2253 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=tor exe=/usr/bin/tor subj=system_u:system_r:tor_t:s0 key=(null) Hash: tor,tor_t,tor_t,capability,dac_override As I don't know what dac_override is I don't know if it's a good idea to give it to tor and the confidence seems quite low. Cheers Mark

2 3

Strange ABRT error when I try to switch to su
by Sean Son 30 Jan '17

30 Jan '17

Hello all One of my VMs, running RHEL 7, has been giving me the following ABRT error when I try to login as su Ive seen this error the past three times that Ive logged in. I know that the VM is using Red Hat,but seeing that RHEL/CentOS are pretty much the same thing, I figured I should ask the CentOS mailing list for help. Here is the error: $ su Password: ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1485781 # abrt-cli list --since 1485781 id b35dcbc9f05781fab04cdd9aca28bbe86a93eace reason: php-fpm killed by SIGSEGV time: Wed 25 Jan 2017 07:44:07 PM EST cmdline: 'php-fpm: pool www' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' package: rh-php56-php-fpm-5.6.5-9.el7 uid: 48 (apache) count: 4 Directory: /var/spool/abrt/ccpp-2017-01-25-19:44:07-47637 Run 'abrt-cli report /var/spool/abrt/ccpp-2017-01-25-19:44:07-47637' for creating a case in Red Hat Customer Portal id 27190e6535600b6fc4bc97de457b302a10698b95 reason: WARNING: at lib/vsprintf.c:1734 vsnprintf+0x691/0x6a0() time: Mon 01 Aug 2016 09:14:44 AM EDT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.22.2.el7.x86_64 root=/dev/mapper/VolGroup00-LogVol00 ro rd.lvm.lv=VolGroup00/LogVol00 vconsole.keymap=us vconsole.font=latarcyrheb-sun16 crashkernel=auto audit=1 rhgb quiet biosdevname=0 net.ifnames=0 LANG=en_US.UTF-8 package: kernel uid: 0 (root) count: 1 Directory: /var/spool/abrt/oops-2016-08-01-09:14:44-8775-0 Reported: cannot be reported What is this error trying to say and how do I fix the issue? All help is greatly appreciated! Thank you Sean

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2017