similar to: Error "corrupted or uncleanly shut down, renaming and replacing" in CentOS 7 clean install

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

On Wed, Oct 14, 2015 at 09:24:00AM +0000, C.L. Martinez wrote: > On 10/13/2015 02:59 PM, Jonathan Billings wrote: > >How did you disable journald? > Changing Storage's option under /etc/systemd/journald.conf to none. While Storage=none is supposed to forward on messages to syslog, it might be worth checking to see what process owns /dev/log: # lsof /dev/log -- Jonathan Billings

Hey everyone, Thanks for the quick help resonses once again, We got some mail saying that RAM disks were not the way to go. So we re-installed, made several partitions to use, and rebuilt xen. However, we''re still having trouble mounting partitions when xeno-linux boots. We give a physical grant of one of our newly made paritions (/dev/hda14 in particular) to the domain. But when

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]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've compiled rsync 3.0.3 on OSX 10.4 PPC via the plain jane ./configure; make method (no patches). The resulting binary has then been moved to /usr/local/bin/rsync3 and copied to a OSX 10.5.4 Intel client machine as rsync3. I then run the following command: rsync3 -vvv -e ssh -avAX --progress --delete -

On 10/14/2015 06:42 PM, Gordon Messmer wrote: > On 10/14/2015 07:09 AM, C.L. Martinez wrote: >> Uhmm ... that is not what I expect: >> >> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >> /run/user/1000/gvfs >> Output information may be incomplete. >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> systemd

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 10/14/2015 07:09 AM, C.L. Martinez wrote: > Uhmm ... that is not what I expect: > > lsof: WARNING: can't stat() fuse.gvfsd-fuse file system > /run/user/1000/gvfs > Output information 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

I have been looking closely at using NUT with openSUSE 13.2. Here is a quick summary. 1. Like the alien plant in the Quatermass Experiment, systemd is reaching into every corner of the distribution. New systemd service units exist in /usr/lib/systemd/system: Power devices information server, nut-server.service, starts upsd Power devices monitor and shutdown controller, nut-monitor.service,

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

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

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?

This bug is reported only on the VM's with CentOS 7 running on on VMware ESXi 5.1. The vSphere performance graph shows high CPU consume and disk activity 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

On 27/09/17 16:49, m.roth at 5-cent.us wrote: > Hi, folks, > > Well, still more fun (for values of fun approaching zero): > > 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. > Even though I installed the 9 repo, all that I get is 8. I've > used their webform, and an waiting on a reply. > 2. I remove all nvidia packages.

Hi, folks, Well, still more fun (for values of fun approaching zero): 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. Even though I installed the 9 repo, all that I get is 8. I've used their webform, and an waiting on a reply. 2. I remove all nvidia packages. 3. It appears that the kmod-nvidia is what I need; that's what nvidia-detect

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

Hello, I search through but I didn't find a clear answer about it. I have a rh 6.2 based box where I made many steps of upgrades. Some of them, not being available the binary rpm glibc 2.1 based, I obtained using src.rpm from rh 7.2 and then runnig #rpm --rebuild package.src.rpm and then installing the generated binary: great sw rpm!!! My rpm version is 4.0.2-6x for both rpm, rpm-devel,

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 deletions(-) diff --git a/fish/fish.h b/fish/fish.h index df22e34..8ae6454