Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Timemaster systemd
by Phil Manuel 02 Aug '17

02 Aug '17

Hi, If I run timemaster from systemd it fails with:- Aug 02 06:07:41 machinename timemaster[19230]: [1494069.352] process 19231 started: /usr/sbin/chronyd -u chrony -n -f /var/run/timemaster/chrony.conf Aug 02 06:07:41 machinename timemaster[19230]: [1494069.352] process 19232 started: /usr/sbin/ptp4l -l 5 -f /var/run/timemaster/ptp4l.0.conf -H -i eno1 Aug 02 06:07:41 machinename timemaster[19230]: [1494069.352] process 19233 started: /usr/sbin/phc2sys -l 5 -a -r -R 1.00 -z /var/run/timemaster/ptp4l.0.socket -n 0 -E ntpshm -M 0 Aug 02 06:07:41 machinename chronyd[19231]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH) Aug 02 06:07:41 machinename chronyd[19231]: Fatal error : shmget() failed Aug 02 06:07:41 machinename timemaster[19230]: [1494069.353] received signal 17 Aug 02 06:07:41 machinename timemaster[19230]: Fatal error : shmget() failed Aug 02 06:07:41 machinename timemaster[19230]: [1494069.354] process 19231 terminated with status 1 Aug 02 06:07:41 machinename ptp4l[19232]: [1494069.353] driver changed our HWTSTAMP options Aug 02 06:07:41 machinename ptp4l[19232]: [1494069.354] tx_type ?? 1 not 1 Aug 02 06:07:41 machinename ptp4l[19232]: [1494069.354] rx_filter 1 not 12 Aug 02 06:07:41 machinename ptp4l[19232]: [1494069.354] port 1: INITIALIZING to LISTENING on INITIALIZE Aug 02 06:07:41 machinename ptp4l[19232]: [1494069.354] port 0: INITIALIZING to LISTENING on INITIALIZE Aug 02 06:07:41 machinename timemaster[19230]: [1494069.354] process 19232 terminated with status 0 Aug 02 06:07:41 machinename timemaster[19230]: [1494069.354] process 19233 terminated abnormally Aug 02 06:07:41 machinename timemaster[19230]: [1494069.354] exiting Aug 02 06:07:41 machinename systemd[1]: timemaster.service: main process exited, code=exited, status=1/FAILURE Aug 02 06:07:41 machinename systemd[1]: Unit timemaster.service entered failed state. Aug 02 06:07:41 machinename systemd[1]: timemaster.service failed. The timemaster unit file is simple:- Unit] Description=Synchronize system clock to NTP and PTP time sources After=chronyd.service ntpd.service ntpdate.service sntp.service Conflicts=chronyd.service ntpd.service phc2sys.service ptp4l.service [Service] Type=simple ExecStart=/usr/sbin/timemaster -f /etc/timemaster.conf [Install] WantedBy=multi-user.target and If I run "/usr/sbin/timemaster -f /etc/timemaster.conf" all works perfectly. So it must be something related to sharedmemory and systemd. Anyone have any ideas ? Thanks Phil ~

1 0

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

list_add corruption problem
by Chris Beattie 01 Aug '17

01 Aug '17

Howdy, I've got a CentOS 7 VM that occasionally becomes unresponsive. There's a "list_add corruption" entry in /var/log/messages, included below. This is on VMware. We have lots of other VMs which are running just fine. Only a few are CentOS 7 VMs, though, so I can't rule out some kind of environment issue. It's up-to-date on OS patches, and running kernel 3.10.0-514.26.2.el7.x86_64. When it locks up, there isn't any indication on its console, other than it looks like it's waiting at a login prompt. I did some Googling, which suggested similar issues have been around a while, but the results I found tended to be for CentOS 6 and older kernels. Can anyone help me understand what this means? Jul 31 16:58:15 den-nagios kernel: ------------[ cut here ]------------ Jul 31 16:58:15 den-nagios kernel: WARNING: at lib/list_debug.c:33 __list_add+0xac/0xc0() Jul 31 16:58:15 den-nagios kernel: list_add corruption. prev->next should be next (ffff880174795358), but was 64756f6c6373646e. (prev=ffff880806a44458). Jul 31 16:58:15 den-nagios kernel: Modules linked in: dell_rbu dcdbas ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_ mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter vmw_vsock_vmci_transport vsock vfat fat intel_power clamp coretemp iosf_mbi crc32_pclmul ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper ablk_helper cryptd ppdev vmw_balloon sg pcspkr vmw_vmci shpchp i2c_piix4 parport_pc parport ip_tables xfs libcrc32c sr_mod cdrom ata_generic pata_acpi sd_mod crc_t10dif crct10dif_gen eric Jul 31 16:58:15 den-nagios kernel: vmwgfx drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crct10dif_pclmul crct10dif_common ttm crc32c_intel ata_piix drm serio_raw libata vmxnet3 vmw_pvscsi i2c_core fjes dm_mirror dm_region_hash dm_log dm_mod Jul 31 16:58:15 den-nagios kernel: CPU: 6 PID: 127439 Comm: ssh Not tainted 3.10.0-514.26.2.el7.x86_64 #1 Jul 31 16:58:15 den-nagios kernel: Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.0.B64.1506250318 06/25/2015 Jul 31 16:58:15 den-nagios kernel: ffff880634f83c00 00000000ac63a691 ffff880634f83bb8 ffffffff81687133 Jul 31 16:58:15 den-nagios kernel: ffff880634f83bf0 ffffffff81085cb0 ffff880782e74210 ffff880174795358 Jul 31 16:58:15 den-nagios kernel: ffff880806a44458 ffff880174794000 0000000000000000 ffff880634f83c58 Jul 31 16:58:15 den-nagios kernel: Call Trace: Jul 31 16:58:15 den-nagios kernel: [<ffffffff81687133>] dump_stack+0x19/0x1b Jul 31 16:58:15 den-nagios kernel: [<ffffffff81085cb0>] warn_slowpath_common+0x70/0xb0 Jul 31 16:58:15 den-nagios kernel: [<ffffffff81085d4c>] warn_slowpath_fmt+0x5c/0x80 Jul 31 16:58:15 den-nagios kernel: [<ffffffff815b6410>] ? ip_fragment.constprop.54+0x90/0x90 Jul 31 16:58:15 den-nagios kernel: [<ffffffff8133399c>] __list_add+0xac/0xc0 Jul 31 16:58:15 den-nagios kernel: [<ffffffff81096c6b>] __internal_add_timer+0xab/0x130 Jul 31 16:58:15 den-nagios kernel: [<ffffffff81096d22>] internal_add_timer+0x32/0x70 Jul 31 16:58:15 den-nagios kernel: [<ffffffff810992ed>] mod_timer+0x13d/0x220 Jul 31 16:58:15 den-nagios kernel: [<ffffffff815591a8>] sk_reset_timer+0x18/0x30 Jul 31 16:58:15 den-nagios kernel: [<ffffffff815d0cae>] tcp_connect+0x74e/0x9f0 Jul 31 16:58:15 den-nagios kernel: [<ffffffff810eb045>] ? ktime_get_real+0x25/0x70 Jul 31 16:58:15 den-nagios kernel: [<ffffffff81568f99>] ? secure_tcp_sequence_number+0x69/0x90 Jul 31 16:58:15 den-nagios kernel: [<ffffffff815d5886>] tcp_v4_connect+0x376/0x4e0 Jul 31 16:58:15 den-nagios kernel: [<ffffffff815ec685>] __inet_stream_connect+0xb5/0x330 Jul 31 16:58:15 den-nagios kernel: [<ffffffff811b1461>] ? handle_mm_fault+0x6b1/0x1000 Jul 31 16:58:15 den-nagios kernel: [<ffffffff815ec938>] inet_stream_connect+0x38/0x50 Jul 31 16:58:15 den-nagios kernel: [<ffffffff81555f07>] SYSC_connect+0xe7/0x120 Jul 31 16:58:15 den-nagios kernel: [<ffffffff8121d72d>] ? set_close_on_exec+0x4d/0x70 Jul 31 16:58:15 den-nagios kernel: [<ffffffff81556d0e>] SyS_connect+0xe/0x10 Jul 31 16:58:15 den-nagios kernel: [<ffffffff81697809>] system_call_fastpath+0x16/0x1b Jul 31 16:58:15 den-nagios kernel: ---[ end trace 64494d91939a3eb0 ]--- Thanks, -Chris

1 0

Personal kernel, drivers mesa-test and winehq
by Andreas Benzler 01 Aug '17

01 Aug '17

Hello Guys, in the mean while i compiled and tested fallow http://centos.cms4all.org/repo/7/kernel/ Kernel 4.12.4, feels more stable as 4.12.0 (+ RadeonSI Flags) Drivers Libdrm 2.4.82, added a patch from git (intel and dri2) xorg-x11-drv-intel Added btrfs-progs 4.12. to my driver section, because fedora coopr doesn't compile i686 for centos. By the next release of intel drivers I rename back intel-vaapi-driver to be better backward compatible with other packages. Wine Update to wine-2.13 (Staging), allready tested with steam & WoW Mesa-Test I think that is the second time, when i try release candidate. But Why? Wanne know is is possible as i did it the last time: - Mesa 12.2.0-rc2 - against LLVM 5.0 RC1 And "Yes" :-) it do. After some simple refactoring LLVM 5.0 needs http://centos.cms4all.org/repo/7/drivers/ http://centos.cms4all.org/repo/7/llvm/ (because of cmake3.i686) Mesa Needs http://centos.cms4all.org/repo/7/drivers/ http://centos.cms4all.org/repo/7/mesa/ to compile, or you take my driver section and mesa-test as it is. Sincerely Andy

1 0

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss