Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Re: [CentOS] Issue with "ExecStartPost" attribute in systemd daemon fail
by Gestió Servidors 22 Nov '19

22 Nov '19

Hi, it seems there is no difference in "systemctl status crond" :( El 22/11/2019 a las 13:00, centos-request(a)centos.org<mailto:centos-request@centos.org> escribió: Message: 3 Date: Thu, 21 Nov 2019 14:41:25 +0100 From: Leon Fauster <leonfauster(a)googlemail.com><mailto:leonfauster@googlemail.com> To: centos(a)centos.org<mailto:centos@centos.org> Subject: Re: [CentOS] Issue with "ExecStartPost" attribute in systemd daemon faile Message-ID: <b58a12c2-5e5c-f7ce-d69d-d464538f1972(a)gmail.com><mailto:b58a12c2-5e5c-f7ce-d69d-d464538f1972@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Am 21.11.19 um 14:28 schrieb Gesti? Servidors: Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email(a)%i.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=10s ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh" [Install] WantedBy=multi-user.target My "test.sh" is very simple: #!/bin/sh echo "CROND is restarting" | /usr/bin/mailx -s "crond failure notification" myemailaddress@mydomain As you can see, I have added lines "Restart=on-failure", "RestartSec=10s" and " ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh"" to the original crond.service daemon file. Then, I run "systemctl daemon-reconfigure" and, from one console, I run "kill -9 `pidof cron`" for restarting crond daemon. After it, I receive an email... But now, if I run again ""kill -9 `pidof cron`", I don't receive any mail... I have notice that if I run "systemctl daemon-reload" and then kill crond process, mail is sent perfectly... but if I don't run "systemctl daemon-reload", mail is sent ONLY first time... Why? What is "status" showing (systemctl status crond)? For both cases (first/second kill)? Any differences? -- Leon

1 0

CentOS-announce Digest, Vol 177, Issue 5
by centos-announce-request＠centos.org 22 Nov '19

22 Nov '19

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. CEBA-2019:3856 CentOS 6 udev BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 21 Nov 2019 17:00:13 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:3856 CentOS 6 udev BugFix Update Message-ID: <20191121170013.GA5573(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:3856 Upstream details at : https://access.redhat.com/errata/RHBA-2019:3856 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e238940087eba7a77b8e80ddc062fb8b27d1c2154e7216c14615c62a11bb1171 libgudev1-147-2.74.el6_10.i686.rpm fe383c264f0d1d887fbc3103bc78a9d379b7bdf0e54830d2be489b94ad969c42 libgudev1-devel-147-2.74.el6_10.i686.rpm 109fb20d3900b3997b0a5e9ffbdc0d6dfe2cc612921b81f58c50a9029f7fa9d9 libudev-147-2.74.el6_10.i686.rpm 763903775dc41c7e615ac6b81475c86a7fc021d7374d19fccbbb25af1d9c38b7 libudev-devel-147-2.74.el6_10.i686.rpm e6dc596d6e4b71fec1d61a1b97d79c980213c2bb181856b9c502808b32511deb udev-147-2.74.el6_10.i686.rpm x86_64: e238940087eba7a77b8e80ddc062fb8b27d1c2154e7216c14615c62a11bb1171 libgudev1-147-2.74.el6_10.i686.rpm a2084d7196fc5fadb1ade692409247fef882c86dda0fc019c6bd258d53493793 libgudev1-147-2.74.el6_10.x86_64.rpm fe383c264f0d1d887fbc3103bc78a9d379b7bdf0e54830d2be489b94ad969c42 libgudev1-devel-147-2.74.el6_10.i686.rpm ad3e6b2c8fc162981001985a3109cf11e4e61978bedc995a4425608cf5b6fdf9 libgudev1-devel-147-2.74.el6_10.x86_64.rpm 109fb20d3900b3997b0a5e9ffbdc0d6dfe2cc612921b81f58c50a9029f7fa9d9 libudev-147-2.74.el6_10.i686.rpm d2a3a49abcaf44923af02a46b3a33dd79325365f8560d7a570609b96286cdb4e libudev-147-2.74.el6_10.x86_64.rpm 763903775dc41c7e615ac6b81475c86a7fc021d7374d19fccbbb25af1d9c38b7 libudev-devel-147-2.74.el6_10.i686.rpm 4bbf43f5a02ec59527c1fd8909fb7f85ff5c47a9bb38bf81f3fbbc6ec282481b libudev-devel-147-2.74.el6_10.x86_64.rpm 226ab4ca0abe61cfe9b7b91ae9185087f39ddc4338aea7b22bf0f54717f5da31 udev-147-2.74.el6_10.x86_64.rpm Source: 43ceefd949dc838ce1fc222bb4e8b00f7198e4433277a6ac2e574479517e3ee2 udev-147-2.74.el6_10.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 177, Issue 5 ***********************************************

1 0

Issue with "ExecStartPost" attribute in systemd daemon faile
by Gestió Servidors 22 Nov '19

22 Nov '19

Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email(a)%i.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=10s ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh" [Install] WantedBy=multi-user.target My "test.sh" is very simple: #!/bin/sh echo "CROND is restarting" | /usr/bin/mailx -s "crond failure notification" myemailaddress@mydomain As you can see, I have added lines "Restart=on-failure", "RestartSec=10s" and " ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh"" to the original crond.service daemon file. Then, I run "systemctl daemon-reconfigure" and, from one console, I run "kill -9 `pidof cron`" for restarting crond daemon. After it, I receive an email... But now, if I run again ""kill -9 `pidof cron`", I don't receive any mail... I have notice that if I run "systemctl daemon-reload" and then kill crond process, mail is sent perfectly... but if I don't run "systemctl daemon-reload", mail is sent ONLY first time... Why? Thanks.

3 4

Is there an sshguard script for logwatch?
by Adrian van Bloois 21 Nov '19

21 Nov '19

Hi all, I wonder if there is a script to analyze logfiles for llogwatch and sshguard? Anyone knows? Adrian -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

3 2

can't login as subsequent FreeIPA users
by Carson Chittom 21 Nov '19

21 Nov '19

When I set up a machine with CentOS 8, I used the "Enterprise Login" in the initial setup wizard to authenticate against my FreeIPA server. This worked fine, and I have no issues logging in with that initial user. However, I am unable to use GDM or the console to login as any *other* valid user from FreeIPA. From GDM I get something like "Sorry, that didn't work" and "Permission denied" on the console. I've verified that the credentials are correct, and that I am able to manually get a ticket via kinit for one of those other users from this machine. With CentOS 7, I didn't have to do any additional configuration in this regard after the initial wizard. Not sure whether this is a CentOS configuration issue or a FreeIPA one, but I figured I'd start here. I'm also not terribly familiar with FreeIPA, so I could be missing something obvious; but this worked without issue when the machine in question ran CentOS 7. Can somebody point me in the right direction?

3 3

C8 and NetworkManager problem
by Alessandro Baggi 20 Nov '19

20 Nov '19

Hi list, I've installed C8 on my workstation. I configured my network devices (two bridges, two nics) using nmcli. Now that NM is the default I tried it. On C7 I always disabled it. I noticed some problem: 1) During the boot, also if NetworkManager-wait-online.service status is OK, I noticed that opening a terminal and ping some address it needs some time to perform ping and any operation on a network connection. So seems that in the first 30sec/1min there isn't an available network connection. After this time if I run a ping or whatever network is available. 2) Due to the problem 1, It cannot mount samba shares on boot saying "Not suitable address found". After the network is available I can mount samba shares. 3) I noticed that with NetworkManager a bridge must have an address. If I don't specify an address for the bridge, NM will try to assign some address, enable the connection forever (reporting errors in messages and on notification bar). 4) NetworkManager-wait-online slow down boot time and network availability. To solve this problem I installed network-scripts and disabled NetworkManager but I don't understand why NetworkManager need so much time to enable a connection. Can someone point me in the right direction? Thanks in advance.

5 11

qemu-kvm
by Jerry Geis 20 Nov '19

20 Nov '19

I am running this command /usr/libexec/qemu-kvm -no-acpi -smp 4 -m 2048 -drive file=myimg.img,format=raw -vga std -device rtl8139 and expecting a window to open up for the console. It does not. This is on CentOS 8. Do I have something missing/not installed - or something wrong on the command line. Jerry

3 4

CentOS7 sometimes don't detect NIC after reboot
by Miroslav Geisselreiter 20 Nov '19

20 Nov '19

I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1) When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card. How can I avoid this problem with missing NIC? Can you help me, please? Miroslav Geisselreiter

4 10

Mirroring two screens for all users?
by James Pearson 20 Nov '19

20 Nov '19

We would like to have one workstation (CentOS7 with Gnome3) set up that has mirrored/cloned screens for all users that may login The workstation is using an Nvidia (proprietary) driver for the graphics card. We have set up xorg to use cloned screens, but gdm/Gnome3 appears to ignore these setting and only use what is set in ~/.config/monitors.xml We've set up /var/lib/gdm/.config/monitors.xml with mirrored/cloned settings for the login screen, but when a user logs in, the display switches to spanning both screens Is there any way we can force all user logins to use cloned displays on this one workstation (but not affect any settings they may use on other workstations - all users has NFS mounted home directories) ? Thanks James Pearson

1 0

Virtualizing on CentOS 8
by Jerry Geis 19 Nov '19

19 Nov '19

I am trying to get going with CentOS 8. In the past I would run qemu-system-x86_64 -hda myfile.img get a console and off we go. I dont with to use virt-manager and the gui and all - I just wish to have a similar command line to boot up and run my img. Is there something like that I'm not finding ? I have found virsh - but I dont see how to make it run with an image file from the command line. Perhaps I'm missing something. Thanks, Jerry

3 3

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