Discuss

discuss@lists.centos.org

11 participants
34746 discussions

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 29 Jul '17

29 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

ARM support from CentOS
by Jaytirth Khairatkar 28 Jul '17

28 Jul '17

Hello, I would like to know which ARM processors does CentOS support? Does it support Freescale/NXP? Thanks and regards Jay

3 2

CentOS-announce Digest, Vol 149, Issue 9
by centos-announce-request＠centos.org 28 Jul '17

28 Jul '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:1809 Important CentOS 7 tomcat Security Update (Johnny Hughes) 2. CEEA-2017:1805 CentOS 7 kmod-redhat-qed Enhancement Update (Johnny Hughes) 3. CEEA-2017:1805 CentOS 7 kmod-redhat-qede Enhancement Update (Johnny Hughes) 4. CEEA-2017:1805 CentOS 7 kmod-redhat-qedf Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 27 Jul 2017 15:49:22 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:1809 Important CentOS 7 tomcat Security Update Message-ID: <20170727154922.GA33880(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:1809 Important Upstream details at : https://access.redhat.com/errata/RHSA-2017:1809 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 43294259acd512850715ad15c50e7767bea30b2c123117f5f760eb4ad5d02e0b tomcat-7.0.69-12.el7_3.noarch.rpm e4605d5673e75ee3592faef8b59d1a2a8efa0da6e3cd8b04064380698586f9a3 tomcat-admin-webapps-7.0.69-12.el7_3.noarch.rpm 6330befc3bd1b7ab35b89ceca55174d94f7e0fe9cf2201166e18c399d48a1687 tomcat-docs-webapp-7.0.69-12.el7_3.noarch.rpm d89786225c6c877fc6134d8e45a85b7fc77169de14ffc543b26ab58299a36f6a tomcat-el-2.2-api-7.0.69-12.el7_3.noarch.rpm 38a4c3e437b1b8d3e4baa175b70a2bdc2681c175c5f7c8d12867100fb9c45134 tomcat-javadoc-7.0.69-12.el7_3.noarch.rpm 2a27c95ad8005bb879140c28deac8f2fac5d85ba225a0abed4ad99956b3231a6 tomcat-jsp-2.2-api-7.0.69-12.el7_3.noarch.rpm dd585fca98f9ff44e927c5820e8731b8604bd23c4c282883ff89501da5476274 tomcat-jsvc-7.0.69-12.el7_3.noarch.rpm 37f28d949569ca81df0b5934ee32116069f912a640e5704d53a6ee521cca4d89 tomcat-lib-7.0.69-12.el7_3.noarch.rpm 726d723713f270e4fb0fed6a2a59c2b224da4e2cf0b2b458a90cf5fcc90331b4 tomcat-servlet-3.0-api-7.0.69-12.el7_3.noarch.rpm 84766cc7724a0399ed3e9830ac5803249395cd4ddd5cab2bdb8730e9cca0a2f0 tomcat-webapps-7.0.69-12.el7_3.noarch.rpm Source: 209cc83cab3a92eaa48d20eb364e982722e639c29f1e3c984e2e03d45fcdbe73 tomcat-7.0.69-12.el7_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 27 Jul 2017 15:49:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:1805 CentOS 7 kmod-redhat-qed Enhancement Update Message-ID: <20170727154940.GA33951(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:1805 Upstream details at : https://access.redhat.com/errata/RHEA-2017:1805 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9c006c0b393981b70c0614c000afa915d5c93c625e760dfadfe95f75a053657d kmod-redhat-qed-8.10.10.21_dup7.3-2.el7_3.x86_64.rpm 0dfeb608ee3c79739743d12a3a1c7fa45d4158ad1780bb0768ac22333138bc05 kmod-redhat-qed-devel-8.10.10.21_dup7.3-2.el7_3.x86_64.rpm 1dc14cc4befdb6ce0986ff2b9cc490059453fdce294f42f88a600d9e8de15582 kmod-redhat-qed-firmware-8.15.3.0_dup7_3-2.el7_3.x86_64.rpm Source: b593624aee8832bf1a2cfaa204e2a1319c35eefff3e999859f6c2e2cfe08c7d8 kmod-redhat-qed-8.10.10.21_dup7.3-2.el7_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Thu, 27 Jul 2017 15:50:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:1805 CentOS 7 kmod-redhat-qede Enhancement Update Message-ID: <20170727155004.GA34014(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:1805 Upstream details at : https://access.redhat.com/errata/RHEA-2017:1805 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 2744e18793a8faff431b6d7921023e348a26bee67163f3fcf30e2f30fc5b97d1 kmod-redhat-qede-8.10.10.21_dup7.3-1.el7_3.x86_64.rpm c2abe7e9a94eee3327dde0ef4fdbf4c8fa5d981cc71cbc9e2b3195d44ab79c04 kmod-redhat-qede-devel-8.10.10.21_dup7.3-1.el7_3.x86_64.rpm Source: 2aa79cd8745dbe3a3f669361453fc4755569bc04b8b34c4ca8e3ab7d887f7c5c kmod-redhat-qede-8.10.10.21_dup7.3-1.el7_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Thu, 27 Jul 2017 15:50:45 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:1805 CentOS 7 kmod-redhat-qedf Enhancement Update Message-ID: <20170727155045.GA34077(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:1805 Upstream details at : https://access.redhat.com/errata/RHEA-2017:1805 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8510d1dc1501653018cdc937a4cb4328fabc0108083b0308cb55301b38414dba kmod-redhat-qedf-8.10.7.0_dup7.3-1.el7_3.x86_64.rpm Source: 1e5d5cc0b51055558df2538dc512777d8870cc9727b984776099e960af9e8c00 kmod-redhat-qedf-8.10.7.0_dup7.3-1.el7_3.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 149, Issue 9 ***********************************************

1 0

NFS issue, C7
by m.roth＠5-cent.us 27 Jul '17

27 Jul '17

Actually, with C6, too. We've been fighting a problem with a server with a RAID appliance that's having issues. It's also serving /home/* and project directories for one team. What happens is when the issues happen, NFS on the other servers they use, of course, gags with timeouts. Now, my question is this: if we go to reboot one of the other servers where one or more home directories is being exported to, and is mounted by autofs, it hangs, and will *not* reboot, because it can't let go of the NFS-mounted directory, with the result that we have to physically go into the room and power cycle the box. Is there any way to configure NFS such that if a system is going down, NFS will wait a few minutes while it retries, then time out and let it reboot? mark

1 0

qemu-system-x86_64 does not support fw_cfg option
by Steve Rubie-Todd 26 Jul '17

26 Jul '17

Hi I am trying to run CoreOS (Container Linux) as a guest OS using KVM/QEMU. One of their suggestions is to pass config info into the VM using the "fw_cfg" option . When I try this I get the error "-fw_cfg invalid option". If I run the vm with the help option it does not list the fw_cfg option. However, according to the qemu documentation, see here <https://qemu.weilnetz.de/doc/qemu-doc.html#Debug_002fExpert-options>, they support this option. The command used to run the vm is: /usr/bin/qemu-system-x86_64 -name CL-IGN-1 -m 1024 \ -net nic,vlan=0,model=virtio \ -net user,vlan=0,hostfwd=tcp::2222-:22,hostname=CL-IGN-1 \ -drive if=virtio,file=./coreos_production_qemu_image.img \ -fw_cfg name=opt/com.coreos/config,file=./CL-IGN-1.ignconfig qemu-system-x86_64: -fw_cfg: invalid option I also tried using /usr/libexec/qemu-kvm but got the same error. I am running:: CentOS Linux release 7.3.1611 (Core) qemu-system-x86-2.0.0-1.el7.6.x86_64 qemu-kvm-1.5.3-126.el7.x86_64 Thanks.

2 2

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