similar to: CentOS 7, systemd,, and message floods

On Wed, Apr 5, 2017 at 3:18 PM, <m.roth at 5-cent.us> wrote: > I've just updated a couple of servers, latest 7.3, and systemd is flooding > dmesg, journalctl with info level messages... or maybe debug level 1. > > Examples: > [ 478.258571] systemd[1]: Sent message type=signal sender=n/a > destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice >

On my Centos 7 update, into "journalctl -f" I have tons of this kind of message > feb 17 23:52:09 s-ispc.local systemd-logind[663]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=17152 reply_cookie=0 error=n/a > feb 17 23:52:09 s-ispc.local

Once upon a time, Brian Mathis <brian.mathis+centos at betteradmin.com> said: > if grep -q debug /proc/cmdline; then > echo "Kernel and systemd debugging was enabled as part of an errant > script during the yum update" > echo "See https://bugs.centos.org/view.php?id=12425 and > https://wiki.centos.org/HowTos/Grub2" > fi Assuming your GRUB

Dear Group members! Since I have set up a Samba PDC-Server (openSUSE 11.2-64bit with default package Samba 3.4.3) approx. 8 months ago, I have encountered 3 or 4 times a severe crash of Samba. What happens is that all over a sudden Samba floods /var/log/messages and /var/log/warn with the following message (cropped out date/time/servername, etc.): smbd[19724]:

Hi, I'm new to this list but not to Samba. I've recently been having problems with Samba that I have not encountered (ever). I cannot determine what the cause is but an hour or so into my dialup connection, my machine starts flooding the first dns server in /etc/resolv.conf with dns requests. I know it's samba responsible for the flooding because as soon as I kill both smbd and nmbd

Hi, We all know most people are reporting that Amazon hasn't been helpful at all. A few people say they've received answers, but most are getting smoke screen PR BS. You can vote this up on Slashdot, send the message: SIP Attacks From Amazon EC2 Going Unaddressed: http://bit.ly/bOkNNx Send this message out to Amazon, I am positive that once it reaches the right person, they will do the

Hello, I have bought Powerman Optima 500 Plus UPS. While this product might be unknown outside Russia, it is shipped with megatec software and obviously works with megatec driver in NUT. besides the following problems (I think they are caused by one reason): 1) megatac driver is able to load and detect UPS only on second or third run. On the first run it typically fails. Later if daemon is

Hello, Is there any reason why an IP-phone would pounder on port 5060 ? My firewall blocks the public IP because it thinks the remote IP is port scanning on port 5060. I think the phone is just registering but for some reason it does this repeatedly in a very short time. Oct 28 09:01:48 astserver kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:00:00

Hi there! I'm a n00b NUT user trying to get it running on RHEL5 and actually do something useful for me. Few questions: 1) I want it to notify me by email on power loss and power back events. I can't find any sample scripts for this purpose... Where shall I look for them? 2) So far, I've backported the package from Fedora and got my Ablerex running (previously used with Upsilon /

Am 03.12.2013 17:36, schrieb Stefan G. Weichinger: > > On a gentoo server with libvirt-1.1.3 I get problems with starting VMs. Additional logs: # journalctl -f lists Dec 03 18:19:31 jupiter systemd-machined[23995]: Failed to start machine scope: Method "StartTransientUnit" with signature "ssa(sv)" on interface "org.freedeskt...sn't exist Dec 03 18:19:31

On a gentoo server with libvirt-1.1.3 I get problems with starting VMs. When I do: # virsh start vm180 error: Failed to start domain vm180 error: Input/output error This happens with 1.1.3 and 1.1.4 (I rebuilt the packages and restarted the libvirtd.service). # journalctl -f -u libvirtd.service shows: Dec 03 17:32:56 jupiter libvirtd[24020]: Input/output error Dec 03 17:33:47 jupiter

Hello all, I am trying to use stepwise procedure to select covariates in Cox model and use bootstrap to repeat stepwise selection, then record how many times variables are chosen by step() in bootstrap replications. When I use step() (or stepAIC) to do model selection, I got errors. Here is the part of my code for (j in 1:mm){ #<--mm=10 for (b in 1:nrow(reg.bs)){ #<--bootstrap 10

We are seeing a problem that occurs ~5% of the time when rebooting CentOS 7.7 where systemd gets a 'Connection timed out' to D-Bus just after the D-Bus service starts - from 'journalctl -x' : ... Jan 21 16:09:59 linux7-7.mpc.local systemd[1]: Started D-Bus System Message Bus. -- Subject: Unit dbus.service has finished start-up -- Defined-By: systemd -- Support:

Simon Matter via CentOS wrote: > >> We are seeing a problem that occurs ~5% of the time when rebooting > > I see such issues on a quite large multi user system but when this > happens, after forced restarts for kernel updates, I usually don't have > the time to analyze and play doctor on it. My "solution" now is to simply > reboot the server again in such a

Hello all, I have a weird problem. We have several Windows 10 machines on our Network. All but one run older releases than 1709. We are using roaming profiles on those machines. The share is setup up as to allow different profiles depending on the machine used (see below). The %a is used as a legacy from times where WinXP and Win7 were used in parallel. The path then looks like this:

We are having one server machine (ubuntu 16.04 OS) with 10 VMs. When the server is rebooted, some VMs got failed to boot with systemd/dbus error messages. Rebooting the affected VMs resolves this issue. Jan 30 20:40:02 VM systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.DisplayManager': Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to subscribe

Hi all, I have a laptop in UEFI mode running CentOS 8.2. All works fine but when I enable Secure Boot, login via gdm is no longer possible. Console login is ok. I found some related discussions over on Ubuntu forums, suggesting that this could be related to 3rd-party kernel modules, such as nvidia. This laptop has only Intel builtin graphics, and every single module installed is part of the

I have a script that starts Icecast, waits a couple seconds, then starts ices. When I installed it all on Ubuntu 20.04, it just worked. Well, it still works now, but with a wrinkle. If I execute: /etc/init.d/icecast2 start I get: Starting icecast2 (via systemctl): icecast2.service==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ==== Authentication is required to start

On 19 Sep 2024, at 22:08, Steve Matzura wrote: > I have a script that starts Icecast, waits a couple seconds, then starts ices. When I installed it all on Ubuntu 20.04, it just worked. Well, it still works now, but with a wrinkle. If I execute: > > > /etc/init.d/icecast2 start > Hi, as far as I understand ?/etc/init.d/icecast2 start? on your system just dispatches to systemctl so

> We are seeing a problem that occurs ~5% of the time when rebooting I see such issues on a quite large multi user system but when this happens, after forced restarts for kernel updates, I usually don't have the time to analyze and play doctor on it. My "solution" now is to simply reboot the server again in such a case, AKA the systemd way :-) > CentOS 7.7 where systemd gets