Discuss December 2015

discuss@lists.centos.org

131 participants
133 discussions

firewalld services
by Robert Moskowitz 29 Dec '15

29 Dec '15

I am familiar with using commands like: firewall-cmd --permanent --add-service=http To enable firewalld services. I am also aware that this is through xml 'scripts' in: /usr/lib/firewalld/services/ But what I find interesting is what services are there and which are not. I went a'lookin with: grep "port=" /usr/lib/firewalld/services/*|more And found some like: http, https, imaps, smtp, and pop3s What I do not find are others that I would think are 'standard' like: pop3 (110) and imap (143) I can understand 587 not being included, but imap? I can always just add them with: firewall-cmd --permanent --add-port=587/tcp But I want to use the standard files. Perhaps because they are there. Have I missed how some are handled? thanks

2 1

routing with 2 public ips
by Joey 28 Dec '15

28 Dec '15

Hello, i have a server with 2 public ips on 2 devices. I want that the request of incoming traffic dont use the default gateway. Incoming traffic sould be answered using the gateway of the incoming device Could i realize this with firewalld? Or directly iptables? Greeting J

5 9

Perl DBI 1.52 on el6
by Erick Ocrospoma 28 Dec '15

28 Dec '15

Hello guys, I was told by the client to install Perl DBI version 1.52 on a el6 box, by default el6 branch comes with DBI version 1.6x, this version is AFAIK not the desired one. First I tried installing DBI 1.52 from some rpm package [1], which had some dependencies, Perl 5.8.8 and dbd.4.4.x, this last package was also present el6, so it made conflict and it was not possible to install DBI 1.52 from a rpm. Then, I downloaded version 1.52 [2], and tried to compiled it, but it failed while doing the make test. I'm not sure if it is not a problem, because while doing make, it did not show error/failure messages. Finally, it seems I'd have to compile Perl 5.8.8 by hand, and then try to add DBI module also. Is this possible to install it safely and make it coexist with default Perl version (5.10.1) in el6 ? I'm also writing to DBI user list, about make test failure messages. But maybe, I guess, it is failing because it is not supported by Perl 5.10.1 and Perl 5.8.8 does. No clue about this, in my opinion it should compile with Perl 5.10.1 Regards. -- Erick. --- IRC : zerick Blog : http://zerick.me About : http://about.me/zerick Linux User ID : 549567

2 1

Fiber Channel target with CentOS 6.7?
by Joacim Melin 28 Dec '15

28 Dec '15

Hi all, I've been googling for this for a day now and I can't seem to find a coherent structured way to build a fiber channel storage box where CentOS 6.7 is used both at the fiber channel target and initiator ends. My Brocade HBA:s are installed and the driver loads just fine in both boxes. Any ideas, pointers or URL:s are more than welcome. Thanks, Joacim

1 0

CentOS 7 pcp-pmda-nvidia-gpu SELinux problems
by David O'Shea 28 Dec '15

28 Dec '15

Hi all, I installed Performance Co-Pilot 3 days ago, and installed the nVidia PMDA according to the instructions at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht… and was able to view metrics about my video card using pmchart. I then played around a little with the lmsensors PMDA (but it doesn't look too useful to me - it doesn't support my sensors, and I think it's for a 2.x kernel). After not looking at PCP at all for a few days, today I tried using pmchart to look at the nVidia metrics again but they were unavailable, and after checking /var/log/messages I found SELinux complaints. After a few iterations of the suggested 'grep pmdanvidia /var/log/audit/audit.log | audit2allow -M [...]', 'semodule -i [...].pp', restarting the PCP service, getting new SELinux errors, going back to step 1, I ended up with this content in the .te file: """ module doshea-selinux-pcp-pmda-nvidia-gpu 1.0; require { type xserver_misc_device_t; type pcp_pmcd_t; class capability sys_admin; class chr_file { read write ioctl open }; } #============= pcp_pmcd_t ============== allow pcp_pmcd_t self:capability sys_admin; #!!!! This avc is allowed in the current policy allow pcp_pmcd_t xserver_misc_device_t:chr_file { read write ioctl open }; """ I don't get why this worked 3 days ago and not today. I haven't installed many packages in the meantime. Should I file a bug somewhere about this? I don't know much about SELinux - I have a slight ability to edit those .te files and I think I remember what to do with them afterwards - but it seems like the sys_admin capability is pretty significant to be granting. Is there any way to work out why that's needed? Thanks in advance, David

1 1

Network services start before network is up since migrating to 7.2
by Sylvain CANOINE 28 Dec '15

28 Dec '15

Hello all, I updated two of my servers to CentOS 7.2 (1511) two days ago, and since, on one of them, the network services are started (and fail to start) before the network interfaces are online. Parts of "journalctl" after the last reboot : déc. 17 10:21:44 myserver kernel: NET: Registered protocol family 40 déc. 17 10:21:45 myserver sshd[700]: error: Bind to port 22 on 172.20.XX.XX failed: Cannot assign requested address. déc. 17 10:21:45 myserver sshd[700]: fatal: Cannot bind any address. déc. 17 10:21:45 myserver systemd[1]: sshd.service: main process exited, code=exited, status=255/n/a déc. 17 10:21:45 myserver systemd[1]: Unit sshd.service entered failed state. déc. 17 10:21:45 myserver systemd[1]: sshd.service failed. déc. 17 10:21:45 myserver sssd[729]: Starting up déc. 17 10:21:45 myserver kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max) déc. 17 10:21:34 myserver systemd[1]: Time has been changed déc. 17 10:21:35 myserver iptables.init[699]: iptables: Applying firewall rules: [ OK ] déc. 17 10:21:35 myserver systemd[1]: Started IPv4 firewall with iptables. déc. 17 10:21:35 myserver systemd[1]: Starting LSB: Bring up/down networking... déc. 17 10:21:35 myserver network[790]: Activation de l'interface loopback : [ OK ] déc. 17 10:21:36 myserver httpd[686]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address 172.19.XX.XX:443 déc. 17 10:21:36 myserver httpd[686]: no listening sockets available, shutting down déc. 17 10:21:36 myserver httpd[686]: AH00015: Unable to open logs déc. 17 10:21:36 myserver systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE déc. 17 10:21:36 myserver kernel: vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 2 vectors allocated déc. 17 10:21:36 myserver kernel: vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps déc. 17 10:21:36 myserver kill[924]: kill: cannot find process "" déc. 17 10:21:36 myserver systemd[1]: httpd.service: control process exited, code=exited status=1 déc. 17 10:21:36 myserver systemd[1]: Failed to start The Apache HTTP Server. déc. 17 10:21:36 myserver systemd[1]: Unit httpd.service entered failed state. déc. 17 10:21:36 myserver systemd[1]: httpd.service failed. déc. 17 10:21:36 myserver postfix/postfix-script[959]: starting the Postfix mail system déc. 17 10:21:36 myserver postfix/master[961]: daemon started -- version 2.10.1, configuration /etc/postfix déc. 17 10:21:36 myserver systemd[1]: Started Postfix Mail Transport Agent. déc. 17 10:21:36 myserver snmpd[704]: Turning on AgentX master support. déc. 17 10:21:36 myserver snmpd[704]: Error opening specified endpoint "udp:172.19.XX.XX:161" déc. 17 10:21:36 myserver snmpd[704]: Server Exiting with code 1 déc. 17 10:21:36 myserver systemd[1]: snmpd.service: main process exited, code=exited, status=1/FAILURE déc. 17 10:21:36 myserver systemd[1]: Failed to start Simple Network Management Protocol (SNMP) Daemon.. déc. 17 10:21:36 myserver systemd[1]: Unit snmpd.service entered failed state. déc. 17 10:21:36 myserver systemd[1]: snmpd.service failed. (...) déc. 17 10:21:38 myserver network[790]: Activation de l'interface ens160 : [ OK ] déc. 17 10:21:38 myserver kernel: vmxnet3 0000:0b:00.0 ens192: intr type 3, mode 0, 2 vectors allocated déc. 17 10:21:38 myserver kernel: vmxnet3 0000:0b:00.0 ens192: NIC Link is Up 10000 Mbps déc. 17 10:21:39 myserver ntpd[694]: Listen normally on 1 ens160 172.19.XX.XX UDP 123 déc. 17 10:21:39 myserver ntpd[694]: new interface(s) found: waking up resolver déc. 17 10:21:40 myserver ntpd[694]: 0.0.0.0 c61c 0c clock_step +11.002914 s déc. 17 10:21:51 myserver ntpd[694]: 0.0.0.0 c614 04 freq_mode déc. 17 10:21:51 myserver systemd[1]: Time has been changed déc. 17 10:21:51 myserver network[790]: Activation de l'interface ens192 : [ OK ] déc. 17 10:21:51 myserver systemd[1]: Started LSB: Bring up/down networking. déc. 17 10:21:51 myserver systemd[1]: Reached target Network is Online. déc. 17 10:21:51 myserver systemd[1]: Starting Network is Online. déc. 17 10:21:51 myserver systemd[1]: Reached target Multi-User System. déc. 17 10:21:51 myserver systemd[1]: Starting Multi-User System. déc. 17 10:21:51 myserver systemd[1]: Starting Update UTMP about System Runlevel Changes... déc. 17 10:21:51 myserver systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup. déc. 17 10:21:51 myserver systemd[1]: Started Update UTMP about System Runlevel Changes. déc. 17 10:21:51 myserver systemd[1]: Startup finished in 650ms (kernel) + 2.623s (initrd) + 13.647s (userspace) = 16.922s. I found a workaround, by replacing "After=network.target" by "After=network-online.target" is the failing services' units, but I want to understand what is the root problem, and what is the difference between my two servers... And by now, I found nothing. Got an idea ? Sylvain CANOINE. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

8 25

hostname service?
by Nicholas Geovanis 28 Dec '15

28 Dec '15

On CentOS 7, I find in /var/log/messages several times daily messages "localhost systemd: Started Hostname Service.". However I can't seem to find such a service using the systemctl command. What is the "Hostname Service", what does it do and why is it being restarted frequently? Many thanks....Nick

2 1

KDE Dying Overnight After Centos 7 Upgrade
by pro alias 27 Dec '15

27 Dec '15

On two blades both with Atom Processors but different Graphics chips (a Matrox WPCM450 on one, Intel 82945Gon the other). One machine had distorted video and required logging out of KDE and then back again. The other one had no video and required ssh from another box to restart X remotely (which I didn't think I should be able to do). Does anyone else see problems with KDE ( or X) after the upgrade? I'm not getting any obvious error messages, but my gut level says it is a problem with X rather than KDE. I haven't had the time to troubleshoot this properly, but when (if) it happens tomorrow I will see what I can find.

2 2

Re: [CentOS] Centos 7 Yum conflict libicalss
by david 26 Dec '15

26 Dec '15

At 09:28 PM 12/6/2015, david wrote: >To: CentOS mailing list <centos(a)centos.org>, centos(a)centos.org >From: david <david(a)daku.org> >Subject: Re: [CentOS] Centos 7 Yum conflict libicalss >In-Reply-To: <1449380359.16567.27.camel(a)gmail.com> >References: <201512060139.tB61d88R009873(a)telford.daku.org> ><1449380359.16567.27.camel(a)gmail.com> > >At 09:39 PM 12/5/2015, Earl Ramirez wrote: >>On Sat, 2015-12-05 at 17:39 -0800, david wrote: >> > Folks >> > >> > My Centos 7 systems are all failing to update because of >> > >> > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) >> > Requires: libicalss.so.0()(64bit) >> > Removing: libical-0.48-6.el7.x86_64 (@base) >> > libicalss.so.0()(64bit) >> > Updated By: libical-1.0.1-1.el7.x86_64 (cr) >> > ~libicalss.so.1()(64bit) >> > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) >> > Requires: libicalvcal.so.0()(64bit) >> > Removing: libical-0.48-6.el7.x86_64 (@base) >> > libicalvcal.so.0()(64bit) >> > Updated By: libical-1.0.1-1.el7.x86_64 (cr) >> > ~libicalvcal.so.1()(64bit) >> > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) >> > Requires: libical.so.0()(64bit) >> > Removing: libical-0.48-6.el7.x86_64 (@base) >> > libical.so.0()(64bit) >> > Updated By: libical-1.0.1-1.el7.x86_64 (cr) >> > ~libical.so.1()(64bit) >> > You could try using --skip-broken to work around the problem >> > You could try running: rpm -Va --nofiles --nodigest >> > >> > >> > Is there something I should (not) be doing? >> > The command was: >> > yum update >> > >> > >> >>Hello David, >> >>The conflict is caused by 'orage' from epel, I am not to familiar with >>that package, you can try and uninstall it and run 'yum clean all' and >>try to update your box again. Or you can exclude it from epel repo. >> >> >>_________________ > >Thanks for that. It appears to have solved the problem. I just >wonder if it should have been taken care of "automatically" without >my intervention, running nightly "yum -y update" commands. > >David Newest Information Having been unable to reproduce the fix, I managed to figure out that the offending package is the group Xfce. It was the only package in my system that wanted the earlier copies of libical*. By avoiding Xfce, the problem went away. David

1 0

Centos7 poblems with dnssec-keygen
by Robert Moskowitz 24 Dec '15

24 Dec '15

I am reading: https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-bind-rndc.html I have bind installed and default config running. I have not applied my customizations yet. The first step I am taking is getting rndc.key created. So reading the guide I am trying to run (while logged in as root, and in /etc): dnssec-keygen -a hmac-md5 -b 256 -n HOST rndc.key The system is just sitting there and doing nothing. I have sshed as another session and do not see any processing being done by dnssec-keygen. Has anyone else done this? Am I doing things in the right order? If it works for others, then there is something wrong with my setup...

2 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2015