Discuss

discuss@lists.centos.org

2 participants
34758 discussions

CentOS 7: changes to php.ini
by Nicolas Kovacs 22 Sep '17

22 Sep '17

Hi, I'm hosting a few web apps like OwnCloud, Wordpress and Dolibarr on CentOS 7 that require a handful of changes to php.ini. I have to define some custom values for post_max_size, upload_max_filesize, etc. I don't know if I'm supposed to edit /etc/php.ini directly or if changes should be put in a configuration file stub in /etc/php.d. For example, I followed the recommendations of a fellow CentOS user and defined date.timezone by edit /etc/php.d/date.ini like this. [Date] ; Defines the default timezone used by the date functions ; http://php.net/date.timezone date.timezone = Europe/Paris Am I supposed to do something similar for other PHP variables? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

5 6

Strange issue with CentOS7 on XenServer
by Todor Petkov 21 Sep '17

21 Sep '17

Hello, I stumbled upon a strange problem with CentOS upgrade on XenServer environment, and I would like to ask if someone has this issue as well: XenServer 7.1, the VM is CentOS7, with kernel 3.10.0-514.26.2.el7.x86_64 running in PV mode When I upgrade the kernel (running with yum update kernel), after reboot in the VM console it says "dracut-pre-udev[212]: modprobe: ERROR: could not insert 'dm-mod': Cannot allocate memory" and after a while it drops to dracut shell If I boot from from an old kernel with the updated kexec-tools/dracut, it's fine. Anyone experiencing this issue? Regards,

2 2

CentOS 7 yum Issue
by Chris Olson 21 Sep '17

21 Sep '17

We have been following the email list discussion regarding recent problems with yum and the upgrade to the most current CentOS 7. We have also tried some of the remedies suggested or recommended. None of these measures has yielded success, and it is not totally clear whether or not our most recent yum issues have the same root cause as those experienced by others. Fortunately, our yum execution after the most recent updates came available was on one of our virtual machines. This is a CentOS 7 system running on VirtualBox and hosted on a Windows 7 system. It is typically used for verifying system updates and applications before they are introduced to regular Intel-based systems. This virtual CentOS 7 system has also been faithfully updated for over a year by using yum and accepting all updates when they become available. The truly remarkable thing is that yum does not finish with any identifiable errors. In fact it does not finish at all and seems to be in a continuous loop of some kind that has run up to ten minutes, so far. Information scrolling by seems to repeat every few seconds with the names of a set of packages repeating over and over. Many of the messages indicate package conflicts or a dependency problem of some kind. This "loop" never allows progress to the point where one would answer yes or no the to the updates. With no end in sight, we chose to kill the yum process. Shut down and restart of the current CentOS system yields a system that appears to work well with no issues related to killing the yum process. Four separate yum update sessions have been attempted, and all have been killed. All data has been backed up properly and our application reload plan is in place, with the exception of some from epel which have caused previous problems, that others have noticed recently also. Our current plan is to remove the current CentOS 7 virtual system and install the newest CentOS 7 available. We have no plans to run yum update on any other CentOS 7 systems.

2 1

CentOS-announce Digest, Vol 151, Issue 5
by centos-announce-request＠centos.org 21 Sep '17

21 Sep '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2017:2771 Important CentOS 7 emacs Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 20 Sep 2017 12:06:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2771 Important CentOS 7 emacs Security Update Message-ID: <20170920120623.GA19904(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2771 Important Upstream details at : https://access.redhat.com/errata/RHSA-2017:2771 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 47619da497682c1d399f3e839774d98a579db4c15f1f0295cfd6cdcae070e408 emacs-24.3-20.el7_4.x86_64.rpm 31638172ec33046d69beebdbde23d7e5f5521c6fe3df1ca063a4f11900d38b65 emacs-common-24.3-20.el7_4.x86_64.rpm a494e7928ca31b88142e2762f88a934c94e8c8bc526d3a78bc58ab706f650c08 emacs-el-24.3-20.el7_4.noarch.rpm 2184386790f816e052c59b814ba9c5acb898161ad3cf12b5d3523536dc021bd0 emacs-filesystem-24.3-20.el7_4.noarch.rpm 1c43a83bfa035a29d4c04958292253931172a07d910972fcdf07fcec9b59b658 emacs-nox-24.3-20.el7_4.x86_64.rpm 2a974431e4ae960ddd2c31f9183a22b926ebcbefbb31e51f250687e8545a01ed emacs-terminal-24.3-20.el7_4.noarch.rpm Source: 6d52969eb35bae9d613ab2297b900c6241a96f4e8fd3a67225e6d94c69cb8b3c emacs-24.3-20.el7_4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 151, Issue 5 ***********************************************

1 0

Public mirror synchronization failing
by Unsub Shafiq 21 Sep '17

21 Sep '17

Hello, Our CentOS public mirror synchronization is failing since yesterday, with the log files showing the following "Permission denied" messages. It seems that my server is not able to access some of the files; any leads on to how to resolve it? rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.3PYmPD" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.7ryULv" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.8K1cYn" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.KoVhZw" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.NihJX5" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.O44pIw" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.O6PlFu" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.PFLTdf" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.PuBBXM" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.W4ppDL" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.brAhov" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.cuN3VQ" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.fAEi2g" (in centos): Permission denied (13) -- *Unsub Shafiq* Inara Technologies (Pvt) Ltd.

2 1

weird wordpress/php/pecl/ssh problem
by John R Pierce 21 Sep '17

21 Sep '17

So I'm running a centos 6 server which among other things hosts a website using wordpress. I'm using php56u from IUS on C6's native apache, and pecl + ssh because php-ssh2 is kinda broken. I ran smack dab into this exact problem: https://core.trac.wordpress.org/ticket/39746 In my case, wordpress 4.7.6 auto updated, and I notied that 4.8.2 was available, so I chose my standard update method of ssh2.sftp via the web interface, and it errored "couldn't find wordpress directories". error_log showed a php error: PHP Warning: file_put_contents(ssh2.sftp://Resource id #834/.maintenance): failed to open stream ... this had worked for me for several years of updates prior to this. if I understand what that guy posted on the wordpress TRAC, there's an upstream error in php 5.6.29+ (I was on .30 and now .31) and pecl ssh2. the wordpress folks on that thread think that its a php ssh problem and don't want to address it, while the poster thinks they could easily work around it. now, I realize none of this is directly a centos problem as its the IUS (Rackspace?) version of php I'm running, and pecl is way out of your bounds, but I'm wondering. anyone here at all plugged into the pecl world and familiar with the ssh extension want to comment ? or am I way out of bounds. the wordpress folks I've talked with say just don't USE the ssh2.sftp update method, use FTP (ugh!) or use 'direct' (php directly writes the .php files to update the app, eek). they think I should contain php in php-fpm, something thing I've not looked at before. -- john r pierce, recycling bits in santa cruz

1 0

KeePassX replacement
by H 21 Sep '17

21 Sep '17

I have been using the KeePassX password manager on CentOS 6 and 7 for some time and it works pretty well. On my Windows machine I use KeePass which offers a number of features missing from KeePassX, I also sync the database between several machines, including Android units where I use keepass2android. Database compatibility is thus required. KeePassX, however, does not seem to be maintained any more, the last update was just a bit less than a year ago. It also has some annoying bugs, including where switching keyboards on the computer corrupts the username and the password if they include any character outside the ASCII range. There seems to be a community fork called KeePassXC and I would like to ask if anyone is using this password manager? It is not in EPEL, nor in any other standard repository, only through an unofficial repository at https://copr.fedorainfracloud.org/coprs/bugzy/keepassxc/,

11 22

xfs not getting it right?
by hw 20 Sep '17

20 Sep '17

Hi, xfs is supposed to detect the layout of a md-RAID devices when creating the file system, but it doesn´t seem to do that: # cat /proc/mdstat Personalities : [raid1] md10 : active raid1 sde[1] sdd[0] 499976512 blocks super 1.2 [2/2] [UU] bitmap: 0/4 pages [0KB], 65536KB chunk # mkfs.xfs /dev/md10p2 meta-data=/dev/md10p2 isize=512 agcount=4, agsize=30199892 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=0, sparse=0 data = bsize=4096 blocks=120799568, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=58984, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 # mkfs.xfs -f -d su=64m,sw=2 /dev/md10p2 meta-data=/dev/md10p2 isize=512 agcount=16, agsize=7553024 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=0, sparse=0 data = bsize=4096 blocks=120799568, imaxpct=25 = sunit=16384 swidth=32768 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=58984, version=2 = sectsz=512 sunit=8 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 The 64MB chunk size was picked my mdadm automatically. The device is made from two disks, and xfs either doesn´t figure that out, or it decided to ignore the layout of the underlying RAID. Am I doing something wrong here, or is xfs in Centos somehow different? Do, or must, we always specify the apporpriate values for su and sw or did xfs ignore them because what it picked is better?

5 8

Join us at CERN, October 20th, 2017
by Rich Bowen 20 Sep '17

20 Sep '17

Please join us, one month from today, in Meyrin, Switzerland, at the amazing CERN facility, for a day of learning and sharing. http://cern.ch/centos Details, schedule, and registration are at the above link. While the event is free, you *must* register in order to gain access to the facility, due to security requirements. See you at CERN! -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

1 0

update to 7.4
by Jerry Geis 20 Sep '17

20 Sep '17

I was doing an update to 7.4 and somewhere in middle the machine died. If I drop back to a previous kernel the machine is alive. So how do I say "forget the previous yum update" and start all over and do it again. Booting into the new kernel I get a kernel fault. So going back one level on teh boot screen solves that - I just need to start the update again. How is that? Thanks, Jerry

6 8

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss