similar to: From slashdot, systemd memory corruption bugs

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

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]

On Tue, Apr 26, 2016 at 3:01 PM, Chris Adams <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

On Wed, Apr 27, 2016 at 7:05 AM, Chris Adams <linux at cmadams.net> wrote: > Once upon a time, Chris Murphy <lists at colorremedies.com> said: >> On Tue, Apr 26, 2016 at 3:01 PM, Chris Adams <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

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 straight to rsyslogd?

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > On Tue, Apr 26, 2016 at 3:01 PM, Chris Adams <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

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

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

> * insure that when something is stopped, it's actually stopped. (If > you've ever managed an HPC cluster and had processes escape the > scheduler, you know this problem is real.) # systemctl list-units | grep -c abandoned 453 # uptime 15:53:58 up 11 days, 21:03, 1 user, load average, 0,01, 0,02, 0,05 > > * track process lifecycle, and restart (or take other

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 ...

On Oct 18, 2018, at 9:41 AM, mark <m.roth at 5-cent.us> wrote: > On 10/17/18 7:55 PM, Warren Young wrote: >>> Benno Rice is right: Lennart Poettering gets stuff done. > > Because he's funded. There are plenty of people with jobs that don?t get stuff done. > I strongly suspect that a lot of that funding > comes from M$'s interest in Upstream. Soooo?systemd

Hi. Another week, another experiment ;) I was trying to run systemd user session for non-root user, for example darek (uid=1000), operation failed with error: systemd[26]: pam_unix(systemd-user:session): session opened for user darek by (uid=0) systemd[1]: Started Login Service. systemd[26]: Failed to create root cgroup hierarchy: Permission denied systemd[26]: Failed to allocate manager

> Valeri Galtsev wrote: >> On 10/17/18 7:55 PM, Warren Young wrote: > <snip> >>> Benno Rice is right: Lennart Poettering gets stuff done. > > Because he's funded. And I strongly suspect that a lot of that funding > comes from M$'s interest in Upstream. > <snip> >> >> With all due respect, many people just stopped offering any

I have multiple VMs that are hanging on boot. Sometimes they'll boot fine after 5 mins and other times it'll take over an hour. The problem seems to be related to journald but I'd like to figure out how I can get more information. The VMs are running CentOS 7.1.1503. systemd and journald are both version 208. We are reluctant to upgrade to the newest CentOS because we found that

Hi all, Five minutes ago I heard a rumor that Lennart Poettering has rewritten rsync. My top urgency is to download the latest numbered version of rsync untouched by Lennart Poettering: I'll find out if the rumor is true or false later. I've downloaded rsync rsync-3.1.3.tar.gz and rsync-patches-3.1.3.tar.gz from https://download.samba.org/pub/rsync/ . Is the source code in both those

On 02/15/2017 07:41 AM, Johnny Hughes wrote: > On 02/15/2017 07:34 AM, Leroy Tennison wrote: >> Too much temptation to resist, I don't know which one of us is older but I have a feeling it's a "horse race". Like you, I still have a land line, WiFi is too slow and "WiFi security" seems to be an oxymoronic phrase. Why people text (or IM for that matter)

On Tue, Feb 28, 2017 at 08:39:07PM +0100, Lennart Poettering wrote: > On Tue, 28.02.17 19:28, Daniel P. Berrange (berrange at redhat.com) wrote: > > The problem with splitting these rules out into a separate project > > is that there's no other existing place that they would live. The > > "virtio people" as a group merely write specifications. The actual >

On Tue, Feb 28, 2017 at 08:39:07PM +0100, Lennart Poettering wrote: > On Tue, 28.02.17 19:28, Daniel P. Berrange (berrange at redhat.com) wrote: > > The problem with splitting these rules out into a separate project > > is that there's no other existing place that they would live. The > > "virtio people" as a group merely write specifications. The actual >

Valeri Galtsev wrote: > On 10/17/18 7:55 PM, Warren Young wrote: <snip> >> Benno Rice is right: Lennart Poettering gets stuff done. Because he's funded. And I strongly suspect that a lot of that funding comes from M$'s interest in Upstream. <snip> > > With all due respect, many people just stopped offering any argument > about systemd, and simply fled

On Tue, Jan 26, 2016 at 11:51:29AM +0000, Peter Duffy wrote: > I'm also still trying to figure out in what way systemd is supposed to > be "better". I've seen the following things claimed for it: Of the three things you list, hot-plug is certainly an important one. But, it's not the big deal. The big deal is that systemd is not just a fire-and-hope startup system, but