Discuss

discuss@lists.centos.org

5 participants
34752 discussions

possible issue with nvidia and new patches?
by Zube 04 Jan '18

04 Jan '18

Twitter user stintel, in this thread: https://twitter.com/stintel/status/948499157282623488 mentions a possible problem with the new patches and the nvidia driver: "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" Also: https://twitter.com/tomasz_gwozdz/status/948590364679655429 https://twitter.com/BitsAndChipsEng/status/948578609761054721 Cheers, Zube

3 2

Issues with qt-creator from EPEL 7
by Toralf Lund 04 Jan '18

04 Jan '18

Hi, Is anyone here using the "EPEL" package for qt-creator on CentOS 7? I'm having a few issues with it, and I though I'd run them by the list before I try Qt Forums or whatever (since they could be specific to the above mentioned build.) Most notably, 1. If I click on an error message in the "Issues" list after compilation (to display source code related to the error), I sometimes get a "File not found" message *if the file in question is already open*. If I close the file and repeat, the same file opens just fine. 2. There is something slightly odd about the icons in the display. In particular, when I open the search panes, I sometimes get buttons with labels "Find Previous" and "Find Next", but at other times, those same buttons have arrow icons. Has anyone else seen something like this? - Toralf

1 0

Gtkcdlabel + cdlabelgen on CentOS 7 ?
by Nicolas Kovacs 03 Jan '18

03 Jan '18

Hi, I've been using the nifty little application Gtkcdlabel for making CD and DVD covers since 2005, if I remember correctly. Later versions are written in Python, and it's a graphical frontend to the cdlabelgen utility. The application doesn't look very well maintained, since the 1.15 release dates back to 2011. Nevertheless, I've been successfully running it on Slackware Linux until the latest 14.2 release. I'm currently trying to install it on CentOS 7, and I'm only having a partial success, with a showstopper. Here's what I could manage so far. The 'cdlabelgen' command line utility is available on EPEL, so I installed that. I downloaded Gtkcdlabel on the project site: http://gtkcdlabel.sourceforge.net/ The installation process takes you back 25 years, since it amounts to this: # tar xvjf gtkcdlabel-1.15.tar.bz2 -C / This installs the application in /usr/bin/gtkcdlabel.py along with a new desktop entry (and the ugliest icon on the planet). The application shows OK when running it, but PostScript file generation fails. I launched it from a terminal by invoking gtkcdlabel.py, filled out a few fields like Title and Subtitle and then clicked on Preview. Normally this is supposed to launch the PDF viewer (/usr/bin/evince in the default configuration). And it launches, except it gets stuck here, since nothing is generated. Under the hood, in my terminal, I get the following string of error messages: (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 I checked, and ghostscript as well as ghostscript-fonts are installed. Which leaves me clueless. Any help would be greatly appreciated, since I've been using this application for years on a daily basis. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

3 8

Identifying Official CentOS AWS AMIs
by Paul Heinlein 02 Jan '18

02 Jan '18

I'm trying to automate identification of CentOS AWS images. It appears that official CentOS AMIs have an OwnerID value of 410186602215, but I'm not sure if that value is transient or specific to one or more AWS regions. Is there a maintainer lurking here that can confirm or deny? Here's the base query I'm testing: aws ec2 describe-images \ --owners 410186602215 \ --output text \ --query 'reverse(sort_by(Images, &CreationDate))[?starts_with(Description, `CentOS Linux 7`)].[ImageId, CreationDate, Description]' -- Paul Heinlein heinlein(a)madboa.com 45°38' N, 122°6' W

1 0

DHCP timeout and mysteriously dropping IP address
by Jason Edgecombe 02 Jan '18

02 Jan '18

Hi everyone, I'me having trouble with a CentOS 7 guest running on a Hyper-V host. For some reason, the CentOS guest randomly drops its IP address. Running "systemctl restart NetworkManager" on the console will restore IP connectivity without a reboot. I think that DHCP is timing out, but I'm not sure what to do about it. Is there a way to tell NetworkManager to keep trying after a timeout? Here are the versions of the kernel and NetworkManager: Kernel: 3.10.0-693.11.1.el7.x86_64 NetworkManager: 1.8.0-11.el7_4.x86_64 Here are some pertinent logs: Dec 23 03:30:26 myhost kernel: hv_utils: Using TimeSync version 3.0 Dec 23 03:30:27 myhost systemd: Time has been changed Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3750] device (eth0): link connected Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3762] device (eth0): DHCPv4 lease renewal requested Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3889] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7936 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3890] dhcp4 (eth0): state changed bound -> done Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3899] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.4487] dhcp4 (eth0): dhclient started with pid 33165 Dec 23 03:30:33 myhost dhclient[33165]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x5cb111f1) Dec 23 03:30:33 myhost dhclient[33165]: DHCPACK from xxx.xxx.36.1 (xid=0x5cb111f1) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5824] dhcp4 (eth0): address xxx.xxx.37.53 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5825] dhcp4 (eth0): plen 23 (255.255.254.0) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): gateway xxx.xxx.36.1 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): lease time 7200 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): nameserver 'xxx.xxx.0.20' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): nameserver 'xxx.xxx.0.30' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): domain name 'example.com' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp (eth0): domain search 'example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp (eth0): domain search 'foo.example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp (eth0): domain search 'dyn.example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp4 (eth0): state changed unknown -> bound Dec 23 03:30:33 myhost dhclient[33165]: bound to xxx.xxx.37.53 -- renewal in 3368 seconds. Dec 23 03:30:33 myhost dbus-daemon: dbus[726]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Dec 23 03:30:33 myhost dbus[726]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Dec 23 03:30:33 myhost systemd: Starting Network Manager Script Dispatcher Service... Dec 23 03:30:33 myhost dbus[726]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 23 03:30:33 myhost dbus-daemon: dbus[726]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 23 03:30:33 myhost systemd: Started Network Manager Script Dispatcher Service. Dec 23 03:30:33 myhost nm-dispatcher: req:1 'dhcp4-change' [eth0]: new request (4 scripts) Dec 23 03:30:33 myhost nm-dispatcher: req:1 'dhcp4-change' [eth0]: start running ordered scripts... Dec 23 03:40:42 myhost kernel: hv_utils: Using TimeSync version 3.0 Dec 23 03:40:43 myhost systemd: Time has been changed Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4566] device (eth0): link connected Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4583] device (eth0): DHCPv4 lease renewal requested Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4693] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 33165 Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4694] dhcp4 (eth0): state changed bound -> done Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4703] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4781] dhcp4 (eth0): dhclient started with pid 33440 Dec 23 03:40:49 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:40:52 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:40:57 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:41:02 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0xe5feb70) Dec 23 03:41:08 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0xe5feb70) Dec 23 03:41:18 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0xe5feb70) Dec 23 03:41:30 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 (xid=0xe5feb70) Dec 23 03:41:34 myhost NetworkManager[788]: <warn> [1514018494.9605] dhcp4 (eth0): request timed out Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9612] dhcp4 (eth0): state changed unknown -> timeout Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9713] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 33440 Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9714] dhcp4 (eth0): state changed timeout -> done Thanks, Jason --------------------------------------------------------------------------- Jason Edgecombe | Linux Administrator UNC Charlotte | The William States Lee College of Engineering 9201 University City Blvd. | Charlotte, NC 28223-0001 Phone: 704-687-1943 jwedgeco(a)uncc.edu | http://engr.uncc.edu | Facebook --------------------------------------------------------------------------- If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply e-mail or by telephone at 704-687-1943. Thank you.

1 0

Re: [CentOS] OpenVPN server and firewalld
by Gianluca Cecchi 30 Dec '17

30 Dec '17

On Fri, Dec 29, 2017 at 10:32 AM, Kenneth Porter <shiva(a)sewingwitch.com> wrote: > How do I insert the iptables rule below using firewalld? > > I'm moving up from CentOS 6 to 7 on an office gateway and I'm trying to > get OpenVPN working to allow home workers to access PCs at the office. I've > got it all working but only by manually inserting an ACCEPT rule in the > FORWARD iptables chain: > > iptables -I FORWARD 3 -i tun+ -j ACCEPT > > This rule was extracted from my iptables firewall under CentOS6. The 3 > puts it after the accepts for established connections and loopback > connections, but before any firewalld sub-chains. With this I can connect > to an internal Windows 10 system with Remote Desktop. > > How can I inject this rule using firewalld, either as a direct rule or as > some more firewalld-approved kind of rule? > > Hello, in case your need is not covered by the "--add-service" and/or the "--add-port" you can still use a direct rule for it. I think it should be something like this to test: firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -i tun+ -j ACCEPT Manual page and some examples with man firewalld.direct The "iptables like" rule will be added into the pre-built chain named FORWARD_direct The 0 above means it is put at top of FORWARD_direct chain. In your example appears "3" and it is not clear what are lines 1 and 2. With iptables -L command you will see: # iptables -v -L FORWARD_direct Chain FORWARD_direct (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- tun+ any anywhere anywhere # With firewall-cmd you can see with # firewall-cmd --direct --get-all-rules ipv4 filter FORWARD 0 -i tun+ -j ACCEPT # If it works ok as expected, you can make it permanent with firewall-cmd --permanent --direct --add-rule ipv4 filter FORWARD 0 -i tun+ -j ACCEPT firewall-cmd --reload HIH digging into, Gianluca

2 1

CentOS 7 + KDE : post-installation script
by Nicolas Kovacs 29 Dec '17

29 Dec '17

Hi, I just spent two rainy days writing and fine-tuning a post-installation script for CentOS 7 and KDE. https://github.com/kikinovak/centos-7-desktop-kde I've just tested it on three different machines here, and it works quite nicely. Feel free to give it a spin and make some suggestions. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 3

Centos 7 and btrfs
by Matt 28 Dec '17

28 Dec '17

I am setting up a new test server. Doing a fresh install from CD onto a couple 4TB drives. Would like to try btrfs in a RAID 1 format. Are there any how to's on how to do that?

4 4

An rpmbuild spec question
by m.roth＠5-cent.us 28 Dec '17

28 Dec '17

I'm trying to build a package to create a directory and install some files. My rpmbuild keeps failing, unable to cd into the directory, "no such". Now, in the tmpfile, I *see* it cd'ing into BUILD/opt, and the source was unzipped and untared into BUILD/opt/smipmicfg-1.27.0. In the spec file, I've even added a cd $RPM_BUILD_ROOT/opt, and I see it cd to there... and then it says it fails cd'ing into the directory under it. I've been doing a lot of googling, but nothing seems to fix this. Anyone got a clue? mark

5 9

Can't see register value in crash vmcore
by wuzhouhui 28 Dec '17

28 Dec '17

OS: CentOS 6.5 Crash: crash-7.1.0-6.el6.x86_64 Kdump: kexec-tools-2.0.0-273.el6.x86_64 GDB: gdb-7.2-60.el6_4.1.x86_64 /etc/kdump.conf: core_collector makedumpfile -c --message-level 1 -d 31 Kernel crashed by panic("string"), but I can't see any register in vmcore: crash> bt PID: 53331 TASK: ffff880c523ed540 CPU: 2 COMMAND: "bw_sd-ar-7-0_2" #0 [ffff880c4f12f978] machine_kexec at ffffffff81038ed9 #1 [ffff880c4f12f9d8] crash_kexec at ffffffff810c5a82 #2 [ffff880c4f12faa8] panic at ffffffff815113b2 #3 [ffff880c4f12fb28] sd_submit_bio at ffffffffa0747a02 [sd] #4 [ffff880c4f12fb68] submit_clone_bio at ffffffffa0747d2b [sd] #5 [ffff880c4f12fb78] split_and_submit_bio_for_cbd at ffffffffa0747ec9 [sd] #6 [ffff880c4f12fbf8] sd_make_request at ffffffffa074c812 [sd] #7 [ffff880c4f12fc68] sdu_make_request at ffffffffa074ca41 [sd] #8 [ffff880c4f12fc88] generic_make_request at ffffffff81264d70 #9 [ffff880c4f12fd68] submit_bio at ffffffff81265140 #10 [ffff880c4f12fdb8] submit_area_bio at ffffffffa04ade20 [scst_vdisk] #11 [ffff880c4f12fde8] bwraid_submit_bio at ffffffffa04b03b2 [scst_vdisk] #12 [ffff880c4f12fe38] worker_thread at ffffffff81094c50 #13 [ffff880c4f12fee8] kthread at ffffffff8109ae26 #14 [ffff880c4f12ff48] kernel_thread at ffffffff8100c20a crash> Is it normal? Thanks.

1 0

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