Discuss March 2017

discuss@lists.centos.org

125 participants
111 discussions

i686 packages for httpd and php
by Rajmohan Banavi 14 Mar '17

14 Mar '17

I do not see any i686 packages (32 bit) for httpd and php on the repositories for CentOS 7. Are they available somewhere? If not, is there a reasonably simple/quick way to build them myself? Thanks.

2 1

Hotel ethernet via nmcli
by Robert Moskowitz 14 Mar '17

14 Mar '17

Here I sit in my hotel room with my Cubie armv7 server with Centos7. They have an ethernet cable here, so most likely I will not need to resort to putting a WiFi USB dongle and trying to master nmcli. But I have to web authenticate to their portal with my personal information. Is that possible with a text web browser? I seem to recall that Centos has one. What to install? Of course, catch-22 here. How to install it to have the tool to authenticate! Going to have to go down to the conference ethernet cafe. Oh well. Have a fun night, all.

3 2

Problem getting ssh agent forwarding to work
by rainer＠ultra-secure.de 14 Mar '17

14 Mar '17

Hi, I need to get agent-forwarding working. I have: - a local OpenSUSE 42.1 box, where my key(s) reside (ssh agent running and working) - a remote FreeBSD 10.3 box, where I can login with my key (works) - from the FreeBSD box, I need to get to a CentOS 7 box (without entering a password - does not work) On the FreeBSD box, I can see my keys, when I type ssh-add -l I've enabled ssh agent forwarding locally and on the FreeBSD server (in sshd and ssh config). I've enabled ssh agent forwarding on the CentOS server [root@centos7-server ~]# grep Agent /etc/ssh/sshd_config AllowAgentForwarding yes My public key resides in the authorized_key file on the CentOS server. Still, I get a password-prompt. (I've disabled SELinux). I admit I never use agent-forwarding (I just don't need it). I set a password on the account and when I enter that password, I can login. So, it shouldn't a problem with the account per-se.

2 2

Strange behaviour of yum within %post in kickstart
by Ralph Angenendt 14 Mar '17

14 Mar '17

Hi, (This is happening on CentOS 6) during a machine's kickstart I install several yum repositories which are contained in an RPM. During the %post phase I install an RPM which has a dependency to nodejs. That package with all of its dependencies can be found in EPEL. On the other hand I have the Softwarecollections repository, which also contains nodejs with the same version. Now nodejs has a dependency on libuv: | root@devcma01 ~ # yum deplist nodejs -q --disableexcludes=all | […] | dependency: libuv.so.0.10()(64bit) | provider: nodejs010-libuv.x86_64 1:0.10.30-1.el6 | provider: libuv.x86_64 1:0.10.34-1.el6 | provider: libuv.x86_64 1:0.10.34-1.el6 As you can see, there are two packages satisfying the dependency. First strange behaviour: | root@devcma01 ~ # yum --disableexcludes=all -v -d9 install nodejs | […] | nodejs-0.10.48-3.el6.x86_64 requires: libuv.so.0.10()(64bit) | --> Processing Dependency: libuv.so.0.10()(64bit) for package: nodejs-0.10.48-3.el6.x86_64 | Searching pkgSack for dep: libuv.so.0.10()(64bit) | Building updates object | up:simple updates time: 0.010 | up:obs time: 0.014 | up:condense time: 0.000 | updates time: 1.059 | TSINFO: Marking 1:nodejs010-libuv-0.10.30-1.el6.x86_64 as install for nodejs-0.10.48-3.el6.x86_64 | […] Why is nodejs010-libuv winning over libuv? It has the longer name *and* an inferior version number. Does the amount of "requires" play a role here? | root@devcma01 ~ # repoquery --requires libuv | wc -l | 32 | root@devcma01 ~ # repoquery --requires nodejs010-libuv | wc -l | 15 The solution seems easy: Exclude nodejs010 from softwarecollections: | root@devcma01 /etc/yum.repos.d # grep exclude= * | python27.repo:exclude=nodejs010* Now comes the other strange behaviour. As said: I install that repository during kickstart and then a package gets installed (within %post) that needs nodejs. The installed repo file has the "exclude" line in it. But: | --> Processing Dependency: nodejs for package: is24-statsd-genuine-v0.7.2-677.noarch | ---> Package nodejs.x86_64 0:0.10.48-3.el6 will be installed | --> Processing Dependency: libuv.so.0.10()(64bit) for package: nodejs-0.10.48-3.el6.x86_64 | ---> Package nodejs010-libuv.x86_64 1:0.10.30-1.el6 will be installed It is as if the exclude line isn't even honoured within the %post section of kickstart. Any idea on why that is? Cheers, Ralph

1 0

How rc-local.service works?
by Yuri Kanivetsky 12 Mar '17

12 Mar '17

Hi, Let me cite the service file here: [Unit] Description=/etc/rc.d/rc.local Compatibility ConditionFileIsExecutable=/etc/rc.d/rc.local After=network.target [Service] Type=forking ExecStart=/etc/rc.d/rc.local start TimeoutSec=0 RemainAfterExit=yes I basically don't understand two things here: 1. What makes it run? Sure, when I make /etc/rc.d/rc.local executable, it runs. But for all I know, for it to run some other service must pull in it as a dependency. Am I wrong? 2. Why Type=forking? Thanks in advance. Regards, Yuri

2 2

kernel memory accounting
by Wensheng Deng 11 Mar '17

11 Mar '17

Hi CentOS experts, I am using CentOS 7. Trying to disable kernel memory accounting: according to https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt, passing cgroup.memory=nokmem to the kernel at boot time, should be able to archive that. However it is not the case in my exercise. These are what I have now $ grep CONFIG_MEMCG_KMEM /boot/config-3.10.0-327.36.3.el7.x86_64 CONFIG_MEMCG_KMEM=y $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 root=UUID=56568066-5719-46d9-981d-278c7559689b ro quiet cgroup.memory=nokmem systemd.log_level=debug But kernel memory is still accounted in user's applications. Any suggestion on how to chase the issue is greatly appreciated! Thank you! Best Regards, Wensheng

3 5

Re: [CentOS] CentOS-6.8 fsck report Maximal Count
by James B. Byrne 11 Mar '17

11 Mar '17

On Thu, March 9, 2017 09:46, John Hodrien wrote: > On Thu, 9 Mar 2017, James B. Byrne wrote: > >> This indicated that a bad sector on the underlying disk system might >> be the source of the problem. The guests were all shutdown, a >> /forcefsck file was created on the host system, and the host system >> remotely restarted. > > fsck's not good at finding disk errors, it finds filesystem errors. If not fsck then what? > > If it was a real disk issue, you'd expect matching errors in the host > logs. Yes, there are: Mar 9 09:14:13 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063 Mar 9 09:14:30 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063 Mar 9 09:14:48 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063 I am running an extended SMART test on the drive at the moment. I suspect that the drive is probably at its EOL for practical purposes. So likely we will be looking at an equipment upgrade given the age of the rest of the equipment. In the meantime what steps, if any, should I take to remediate this problem? > >> /var/log/messages:Mar 9 08:34:48 vhost03 kernel: EXT4-fs (dm-6): >> warning: maximal mount count reached, running e2fsck is recommended > > Unmount it and run fsck on it, and that message would go away. But > I'd not > worry about that one. > > jh > > -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by 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

5 6

OT: hardware suggestions for video capture card for a server
by m.roth＠5-cent.us 10 Mar '17

10 Mar '17

We've got several secure rooms, with video surveillance 24x7. A few years ago, we got a couple of cards based on BT878 chips, which we use with the motion package. I've posted here about hardware issues... After a fair bit of testing, the cards just don't seem to be compatible with Dell rackmount server firmware. They work fine... on older Penguins, which are Supermicro. It's clearly not an o/s issue, it's hardware - having tried two Dells, and swapped cards between the old Penguin and the newer Dell, it's the Dell m/b. Does anyone have any suggestions, possibly for video capture cards, perhaps on newer chips? The two requirements are a) accept BNC connectors from the cameras, and b) must have *four* actual channels, not one multiplexed. Thanks in advance, folks. mark

1 0

CentOS-announce Digest, Vol 145, Issue 5
by centos-announce-request＠centos.org 10 Mar '17

10 Mar '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. Announcing the release for Gluster 3.10 on CentOS Linux 6 x86_64 (Niels de Vos) 2. Announcing the release for Gluster 3.10 on CentOS Linux 7 x86_64 (Niels de Vos) ---------------------------------------------------------------------- Message: 1 Date: Wed, 8 Mar 2017 22:44:15 +0100 From: Niels de Vos <ndevos(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing the release for Gluster 3.10 on CentOS Linux 6 x86_64 Message-ID: <20170308214415.GA1546(a)chromebook.lan.nixpanic.net> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 3.10 for CentOS 6 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 3.10 is a Long-Term-Maintenance release, and will receive updates for approximately 18 months. The difference between Long-Term-Maintenance and Short-Term-Maintenance releases is explained on the Gluster release schedule page: https://www.gluster.org/community/release-schedule/ Users of CentOS 6 can now simply install Gluster 3.10 with only these two commands: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster package is delivered via CentOS Extras repos. This contains all the metadata and dependency information, needed to install Gluster 3.10. The actual package that will get installed is centos-release-gluster310. Users of the now End-Of-Life Short-Term-Maintenance Gluster 3.9 will automatically get the update to Gluster 3.10, whereas users of Gluster 3.8 can stay on that Long-Term-Maintenance release for an other six months. We have a quickstart guide specifically built around the packages are available, it makes for a good introduction to Gluster and will help get you started in just a few simple steps, this quick start is available at https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart More details about the packages that the Gluster project provides in the Storage SIG is available in the documentation: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster The centos-release-gluster* repositories offer additional packages that enhance the usability of Gluster itself. Utilities and tools that were working with previous versions of Gluster are expected to stay working fine. If there are any problems, or requests for additional tools and applications to be provided, just send us an email with your suggestions. The current list of packages that is (planned to become) available can be found here: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster/Ecosystem-pkgs We welcome all feedback, comments and contributions. You can get in touch with the CentOS Storage SIG on the centos-devel mailing list ( [15]https://lists.centos.org ) and with the Gluster developer and user communities at [16]https://www.gluster.org/mailman/listinfo , we are also available on irc at #gluster on irc.freenode.net, and on twitter at @gluster . Cheers, Niels de Vos Storage SIG member & Gluster maintainer

1 0

CentOS-5 End of Life
by Johnny Hughes 09 Mar '17

09 Mar '17

Just a message to remind everyone that CentOS-5 has an End of Life date of March 31, 2017. This means that there will be no new security updates released by Red Hat for RHEL-5 after that date. Sometime in early April, the current 5.11 tree will be moved onto vault.centos.org (like CentOS-3 and CentOS-4 have been since their EOL). Thanks, Johnny Hughes

10 19

← Newer
1
...
5
6
7
8
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2017