Discuss July 2017

discuss@lists.centos.org

108 participants
100 discussions

CentOS users: please try and provide feedback on Fedora Boltron
by Matthew Miller 05 Aug '17

05 Aug '17

Please take a look at http://www.itworld.com/article/3211046/linux/red-hats-boltron-snaps-togethe… and https://fedoramagazine.org/announcing-boltron/ which has a walkthrough questionnaire at the bottom. Your feedback very appreciated. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

11 46

ipa rpm conflicts
by lejeczek 04 Aug '17

04 Aug '17

does anybody see this: unning transaction Warning: RPMDB altered outside of yum. ** Found 8 pre-existing rpmdb problem(s), 'yum check' output follows: ipa-admintools-4.4.0-14.el7.centos.noarch has installed conflicts freeipa-admintools: ipa-admintools-4.4.0-14.el7.centos.noarch ipa-client-4.4.0-14.el7.centos.x86_64 has installed conflicts freeipa-client: ipa-client-4.4.0-14.el7.centos.x86_64 ipa-client-common-4.4.0-14.el7.centos.noarch has installed conflicts freeipa-client-common: ipa-client-common-4.4.0-14.el7.centos.noarch ipa-common-4.4.0-14.el7.centos.noarch has installed conflicts freeipa-common: ipa-common-4.4.0-14.el7.centos.noarch ipa-python-compat-4.4.0-14.el7.centos.noarch has installed conflicts freeipa-python-compat: ipa-python-compat-4.4.0-14.el7.centos.noarch ipa-server-4.4.0-14.el7.centos.x86_64 has installed conflicts freeipa-server: ipa-server-4.4.0-14.el7.centos.x86_64 ipa-server-common-4.4.0-14.el7.centos.noarch has installed conflicts freeipa-server-common: ipa-server-common-4.4.0-14.el7.centos.noarch ipa-server-dns-4.4.0-14.el7.centos.noarch has installed conflicts freeipa-server-dns: ipa-server-dns-4.4.0-14.el7.centos.noarch this in .rpm I guess and started appearing after upg to 7.3. *freeipa* is naming convention Fedora uses, right? Some remnants rebase did not take care of? regards, L.

4 3

CentOS SDR Support
by Chris Olson 02 Aug '17

02 Aug '17

Several weeks ago, we posted a message seeking information about time sources. There were many helpful and educational responses. An excerpt from one of the responses is included below. We have been following up with regard to how SDR capabilities might be used for obtaining time using SDR dongles as well as using the time source product referenced in that response. Our SDR investigation has yielded many sources of information, but not a source dedicated to CentOS support for SDR products. Is there a CentOS subgroup and mail list directly involved with SDR device or system support? The SDR information resulting from our search has many references to ADS-B and the P3. It is almost like one absolutely must have a P3 to make use of SDR products. One thing that we did not find was any reference at all to SDR products and software for monitoring the frequencies used by recreational Remote Controlled Aircraft. Thanks again for all the helpful system time responses.

5 5

claiming unsused space back
by Miguel González 01 Aug '17

01 Aug '17

Hi, I´m running a CentOS server in a VPS. Backups of the VPS take quite much space if I don´t claim unused space. Currently I´m using dd if=/dev/zero of=/mytempfile and remove that file to claim that unused space. Any automatic way of doing a similar thing in CentOS? I have googled for it but I have only found Debian commands. Thanks in advance! Miguel

7 14

Using GIMP on Centos-7, problem
by Fred Smith 31 Jul '17

31 Jul '17

Wondering if anyone here has ever tried installing this https://github.com/bootchk/resynthesizer as a gimp plugin in Centos-7, with gimp 2.8.16?? I find the installation instructions (for the binary tarball) are minimal and whatever I do, it doesn't seem to appear in the gimp menus, as it should. I've used an older version (0.14) from years ago in older versions of gimp, but how does one make this newer one work on C7? I also tried building the source, but even "autoconfig" spewed some errors that are greek to me, so I, for the moment, gave up on that. Advice will be appreciated, thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. ------------------------------- Romans 5:8 (niv) ------------------------------

2 1

firewalld and LISTEN
by 望月忠雄 31 Jul '17

31 Jul '17

On CentOS7 I have following firewalld setting. external (active) target: default icmp-block-inversion: no interfaces: eth0 sources: services: dns ftp http https imaps pop3s smtp ssh ports: 110/tcp 21/tcp 20000/tcp 106/tcp 53/tcp 990/tcp 5432/tcp 8447/tcp 113/tcp 143/tcp 3306/tcp 5224/tcp 22/tcp 465/tcp 995/tcp 25/tcp 10000/tcp 8443/tcp 993/tcp 443/tcp 8880/tcp 587/tcp 20/tcp 53/udp 12768/tcp protocols: masquerade: yes forward-ports: sourceports: icmp-blocks: rich rules: But by ss -nat, IPV4 443 is not listend. How can I fix? # ss -nat | grep LISTEN | grep 443 LISTEN 0 128 :::443 :::* Tadao

4 6

Headphones volume control not working in CentOS 7
by Bernard Lheureux 30 Jul '17

30 Jul '17

Hi all, I hope someone could enlighten me... How could I resolve the fact that the volume controls of all the headphones I try on CentOS 7 are not working, they are OK on CentOS 6 but impossible to make them work on my Thinkpad Laptop with an iPhone headphones or a Marshal Monitor plugged with a jack connector... Those 2 headphones work correctly in CentOS 6... What could I do to get the same behavior on CentOS 7 and this damned Gnome 3 ? Thanks for your help... -- (°- //\ Bernie v_/_ The Mad Axeman

4 4

Problems switching from RHEL 6 to Centos 6
by Alois Treindl 30 Jul '17

30 Jul '17

I am trying to migratean existing RHEL 6 machine to Centos 6. I followed the instructions in https://wiki.centos.org/HowTos/MigrationGuide I run into problems: when I run yum upgrade then yum tries to access a repository rhel-6-server-extras-rpms and then fails. What can I do that yum no longer tries to access this repository?

4 6

Getting started with mod_security
by Nicolas Kovacs 28 Jul '17

28 Jul '17

Hi, I'm currently fiddling with mod_security, and before going any further, I simply wanted to ask here for any recommended documentation/tutorials on the subject. There seems to be a lot of information about mod_security out there, and right now I have a bit of a hard time wrapping my head around it. I'm grateful for any suggestions. Cheers, Niki Kovacs -- 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

2 1

vncserver died
by Robert Moskowitz 28 Jul '17

28 Jul '17

I get back from two weeks on the road, and try to VNC to my server and it fails. I ssh in and see that, yes vncserver is dead. I tried restarting it and see below for the failure messages plus my systemd setup. Can someone point me to trouble shooting why it says about resources (if that is the problem); # systemctl -l status vncserver@:3.service ● vncserver@:3.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver@.service; enabled; vendor preset: disabled) Active: failed (Result: resources) since Fri 2017-07-28 13:31:15 EDT; 54s ago Process: 19173 ExecStart=/usr/sbin/runuser -l root -c /usr/bin/vncserver %i (code=exited, status=0/SUCCESS) Process: 19170 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Jul 28 13:31:12 homebase.home.htt systemd[1]: Starting Remote desktop service (VNC)... Jul 28 13:31:15 homebase.home.htt systemd[1]: PID file /home/root/.vnc/homebase.home.htt:3.pid not readable (yet?) after start. Jul 28 13:31:15 homebase.home.htt systemd[1]: Failed to start Remote desktop service (VNC). Jul 28 13:31:15 homebase.home.htt systemd[1]: Unit vncserver@:3.service entered failed state. Jul 28 13:31:15 homebase.home.htt systemd[1]: vncserver@:3.service failed. # cat /etc/systemd/system/vncserver@.service # The vncserver service unit file # # Quick HowTo: # 1. Copy this file to /etc/systemd/system/vncserver@.service # 2. Edit /etc/systemd/system/vncserver@.service, replacing <USER> # with the actual user name. Leave the remaining lines of the file unmodified # (ExecStart=/usr/sbin/runuser -l <USER> -c "/usr/bin/vncserver %i" # PIDFile=/home/<USER>/.vnc/%H%i.pid) # 3. Run `systemctl daemon-reload` # 4. Run `systemctl enable vncserver@:<display>.service` # # DO NOT RUN THIS SERVICE if your local area network is # untrusted! For a secure way of using VNC, you should # limit connections to the local host and then tunnel from # the machine you want to view VNC on (host A) to the machine # whose VNC output you want to view (host B) # # [user@hostA ~]$ ssh -v -C -L 590N:localhost:590M hostB # # this will open a connection on port 590N of your hostA to hostB's port 590M # (in fact, it ssh-connects to hostB and then connects to localhost (on hostB). # See the ssh man page for details on port forwarding) # # You can then point a VNC client on hostA at vncdisplay N of localhost and with # the help of ssh, you end up seeing what hostB makes available on port 590M # # Use "-nolisten tcp" to prevent X connections to your VNC server via TCP. # # Use "-localhost" to prevent remote VNC clients connecting except when # doing so through a secure tunnel. See the "-via" option in the # `man vncviewer' manual page. [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target [Service] Type=forking # Clean any existing files in /tmp/.X11-unix environment ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :' ExecStart=/usr/sbin/runuser -l root -c "/usr/bin/vncserver %i" PIDFile=/home/root/.vnc/%H%i.pid ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :' [Install] WantedBy=multi-user.target # cat /etc/systemd/system/multi-user.target.wants/vncserver@:3.service # The vncserver service unit file # # Quick HowTo: # 1. Copy this file to /etc/systemd/system/vncserver@.service # 2. Edit /etc/systemd/system/vncserver@.service, replacing <USER> # with the actual user name. Leave the remaining lines of the file unmodified # (ExecStart=/usr/sbin/runuser -l <USER> -c "/usr/bin/vncserver %i" # PIDFile=/home/<USER>/.vnc/%H%i.pid) # 3. Run `systemctl daemon-reload` # 4. Run `systemctl enable vncserver@:<display>.service` # # DO NOT RUN THIS SERVICE if your local area network is # untrusted! For a secure way of using VNC, you should # limit connections to the local host and then tunnel from # the machine you want to view VNC on (host A) to the machine # whose VNC output you want to view (host B) # # [user@hostA ~]$ ssh -v -C -L 590N:localhost:590M hostB # # this will open a connection on port 590N of your hostA to hostB's port 590M # (in fact, it ssh-connects to hostB and then connects to localhost (on hostB). # See the ssh man page for details on port forwarding) # # You can then point a VNC client on hostA at vncdisplay N of localhost and with # the help of ssh, you end up seeing what hostB makes available on port 590M # # Use "-nolisten tcp" to prevent X connections to your VNC server via TCP. # # Use "-localhost" to prevent remote VNC clients connecting except when # doing so through a secure tunnel. See the "-via" option in the # `man vncviewer' manual page. [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target [Service] Type=forking # Clean any existing files in /tmp/.X11-unix environment ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :' ExecStart=/usr/sbin/runuser -l root -c "/usr/bin/vncserver %i" PIDFile=/home/root/.vnc/%H%i.pid ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :' [Install] WantedBy=multi-user.target

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss July 2017