search for: journald

I have several recently-installed CentOS 7 servers that keep having systemd-journald corruption (which stops ALL logging, including syslog). Interestingly, they are all spam-scanning servers running amavisd-new (so could be some particular pattern is triggering it). Is there a "supported" way to just cut systemd-journald out of the picture and have log entries go straigh...

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: > > I have several recently-installed CentOS 7 servers that keep having > > systemd-journald corruption > > Determined with 'journalctl --verify' or another way? I get messages like this in dmesg: [4756650.489117] systemd-journald[21364]: Failed to write entry (21 items, 637 bytes), ignoring: Cannot assign requested address I'll check journalctl --verify when it happe...

On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: > I have several recently-installed CentOS 7 servers that keep having > systemd-journald corruption Determined with 'journalctl --verify' or another way? (which stops ALL logging, including syslog). > Interestingly, they are all spam-scanning servers running amavisd-new > (so could be some particular pattern is triggering it). > > Is there a "supported&quo...

Hi all, I have 5 CentOS 7 virtual guests installed (all fully patched to latest release) and i have the following error in all of them: systemd-journald[7779]: File /run/log/journal/b4a41f4214ca44f898638301891a6f2e/system.journal corrupted or uncleanly shut down, renaming and replacing. ?? .. And I don't understand why. I have configured "Storage=volatile" in journald.conf ... How can I debug this error? Is it possible to disable...

...# The imjournal module bellow is now used as a message source instead of imuxsock. $ModLoad imuxsock # provides support for local system logging (e.g. via logger command) $ModLoad imjournal # provides access to the systemd journal #$ModLoad imklog # reads kernel messages (the same are read from journald) #$ModLoad immark # provides --MARK-- message capability

...> wrote: > > Once upon a time, Chris Murphy <lists at colorremedies.com> said: > >> On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: > >> > I have several recently-installed CentOS 7 servers that keep having > >> > systemd-journald corruption > >> > >> Determined with 'journalctl --verify' or another way? One system did get into this state overnight, and that said: [root at spamscan3 ~]# journalctl --verify 15bd478: invalid object File corruption detected a...

...linux at cmadams.net> wrote: > Once upon a time, Chris Murphy <lists at colorremedies.com> said: >> On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: >> > I have several recently-installed CentOS 7 servers that keep having >> > systemd-journald corruption >> >> Determined with 'journalctl --verify' or another way? > > I get messages like this in dmesg: > > [4756650.489117] systemd-journald[21364]: Failed to write entry (21 items, 637 bytes), ignoring: Cannot assign requested address I haven't seen this...

...> > Once upon a time, Chris Murphy <lists at colorremedies.com> said: >> >> On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: >> >> > I have several recently-installed CentOS 7 servers that keep having >> >> > systemd-journald corruption >> >> >> >> Determined with 'journalctl --verify' or another way? > > One system did get into this state overnight, and that said: > > [root at spamscan3 ~]# journalctl --verify > 15bd478: invalid object > File corruption detected at /run...

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > Also I wonder if merely restarting the journal daemon solves it: > > systemctl restart systemd-journald > > What should happen is it realizes its own logs are corrupt and ignores > them, and starts working on new copies. And journalctl should still > try to read the old ones but skips the corrupt entries. I tried that and it didn't work (at least not every time). I had to actually...

...lete. >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> systemd 1 root 27u unix 0xffff880250ea0f00 0t0 1436 /dev/log >> systemd-j 263 root 5u unix 0xffff880250ea0f00 0t0 1436 /dev/log > > So, the obvious next step is to make sure journald isn't holding that > socket. That's outside my experience, but I'd imagine that you can: > > systemctl disable systemd-journald.service > systemctl stop systemd-journald.service > > Then you'll need to restart rsyslog and verify that it owns /dev/log. > >&gt...

Once upon a time, Chris Adams <linux at cmadams.net> said: > So far, turning off the compression appears to have worked (but I'll > have to watch it for a day or two to really see). Just to follow up: turning off journald compression does appear to have fixed the corruption problem I was seeing. I'll watch for an updated systemd package. -- Chris Adams <linux at cmadams.net>

...;: "add", "values": [{"value": "group"}]}]}, "sAMAccountName": {"actions": [{"action": "add", "values": [{"value": "testgroup1"}]}]}}}} Added group testgroup1 But JSON debug to STDOUT, not journald. Why? [root at dc ~]# rpm -q samba samba-4.16.10-alt1.x86_64 -- Anton

On 10/13/2015 02:59 PM, Jonathan Billings wrote: > On Tue, Oct 13, 2015 at 02:39:24PM +0000, C. L. Martinez wrote: >> Nop, because binary logs (using journalctl) are disabled in this host >> ... But under /var/log/messages, there is no error ... > > How did you disable journald? > Changing Storage's option under /etc/systemd/journald.conf to none.

...rmation may be incomplete. > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > systemd 1 root 27u unix 0xffff880250ea0f00 0t0 1436 /dev/log > systemd-j 263 root 5u unix 0xffff880250ea0f00 0t0 1436 /dev/log So, the obvious next step is to make sure journald isn't holding that socket. That's outside my experience, but I'd imagine that you can: systemctl disable systemd-journald.service systemctl stop systemd-journald.service Then you'll need to restart rsyslog and verify that it owns /dev/log. > In theory, rsyslog is listenning...

...│ ├─systemd-logind.service │ │ │ └─17373 /usr/lib/systemd/systemd-logind │ │ ├─dbus.service │ │ │ └─17372 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation │ │ ├─sshd.service │ │ │ └─17379 /usr/sbin/sshd -D │ │ └─systemd-journald.service │ │ └─17348 /usr/lib/systemd/systemd-journald │ └─user.slice │ └─user-0.slice │ ├─session-c1.scope │ │ ├─17377 login -- root │ │ └─17413 -bash │ └─user@0.service │ └─17412 (sd-pam) Then I repeated the test, but I use...

...ivity only on VM's with CentOS 7. Sometimes I can not connect remotely with ssh (timeout error). The details of last issues was reported to retrace.fedoraproject.org. ?Do you have a hint? [root at vmguest ~]# abrt-cli list id c52b463b15cfa94af7a96f237e5f525332750dd3 reason: systemd-journald killed by SIGABRT time: Tue 16 Aug 2016 03:10:52 PM CLST cmdline: /usr/lib/systemd/systemd-journald package: systemd-219-19.el7_2.12 uid: 0 (root) count: 1 Directory: /var/spool/abrt/ccpp-2016-08-16-15:10:52-458 Reported: https://retrace.fedoraprojec...

...nto your log stream > > as Marcus Ranum said in his Artificial Ignorance writeup, the number > of times that an uninteresting thing happens can be interesting. > > If you see a big spike (or drop) is these attempts, it can indicate > cause for concern. I run Debian with systemd-journald instead of rsyslog. AFAIK journald does not support filtering of its ingress log messages. Only the output can be filtered with journalctl, but by then it's already too late in terms of log spam on disk. Regardless of which syslog solution is being used, I find it inconvenient to manually...

Lets user view journald log from VM in a similar format as journalctl uses. Fixes RFE: journal reader in guestfish (RHBZ#988100) --- fish/fish.h | 3 +++ generator/Makefile.am | 6 ++++-- generator/actions.ml | 22 ++++++++++++++++++++++ generator/main.ml | 3 +++ 4 files changed, 32 insertions(+), 2 d...

On 12/13/2015 12:45 PM, Valeri Galtsev wrote: > On Sun, December 13, 2015 11:36 am, Alice Wonder wrote: >> >> >> On 12/13/2015 08:39 AM, Timothy Murphy wrote: >>> Alice Wonder wrote: >>>> One of the benefits of systemd is the dependency based parallel > startup. >>>> The same speed can often be achieved with system V init by fine tuning >

On Jan 24, 2016, at 6:40 PM, Peter Duffy <peter at pwduffy.org.uk> wrote: > The thing which always gets me about systemd is not the thing itself, > but the way it was rolled out. When I first installed Red Hat 7, if a > window had appeared telling me about systemd and asking me if I wanted > to use it, or stick with the old init framework, I'd have opted for the > latter