From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id EA70713838B for ; Tue, 23 Sep 2014 18:28:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 31F0BE097C; Tue, 23 Sep 2014 18:28:42 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2B243E07C7 for ; Tue, 23 Sep 2014 18:28:41 +0000 (UTC) Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com [209.85.213.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 891BA34011B for ; Tue, 23 Sep 2014 18:28:39 +0000 (UTC) Received: by mail-ig0-f180.google.com with SMTP id a13so5107686igq.1 for ; Tue, 23 Sep 2014 11:28:37 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.43.70.142 with SMTP id yg14mr2858646icb.94.1411496917604; Tue, 23 Sep 2014 11:28:37 -0700 (PDT) Received: by 10.64.111.135 with HTTP; Tue, 23 Sep 2014 11:28:37 -0700 (PDT) In-Reply-To: References: Date: Tue, 23 Sep 2014 14:28:37 -0400 Message-ID: Subject: Re: [gentoo-user] Re: journald refuses to put log files in /var/log/journal/ [NOT SOLVED] From: Mike Gilbert To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 7c5dc6b5-3453-4f7a-b835-aae8ea387e08 X-Archives-Hash: fec1cdad51006a1e3d06268a970a1f50 On Tue, Sep 23, 2014 at 1:40 PM, walt wrote: > On 09/23/2014 07:46 AM, Rich Freeman wrote: >> On Tue, Sep 23, 2014 at 10:27 AM, walt wrote: >>> >>> I used systemctl to stop and restart systemd-journald, thinking I might >>> see some useful error messages. But when systemd-journal started up >>> again the journal file was back in /var/log/journal where I want it :) >>> >>> No idea why rebooting the machine didn't do the same thing. >>> >> >> Are you sure that it is solved, and that the problem won't recur on >> the next reboot? > > After a reboot the journal file is back in /run/log/journal. > >> If it does, my next question (an educated guess, but a guess) would be >> whether you're using an initramfs, > > No, I never have. > >> I'd also look at anything >> that might be causing issues with /var/log/journal when journald is >> launched, such as that directory being on an unmounted filesystem and >> there not being some dependency that causes journald to notice. > > This particular machine has only root and swap partitions, so there's > nothing to remain unmounted during boot. > > Having reassured myself with that claim, I now spot this journal message > (which appears only on the 'broken' machine): > > Sep 23 07:40:46 a6 systemd[1]: Found ordering cycle on sysinit.target/start > Sep 23 07:40:46 a6 systemd[1]: Found dependency on local-fs.target/start > Sep 23 07:40:46 a6 systemd[1]: Found dependency on lvm.service/start > Sep 23 07:40:46 a6 systemd[1]: Found dependency on sysinit.target/start > Sep 23 07:40:46 a6 systemd[1]: Breaking ordering cycle by deleting job local-fs.target/start > Sep 23 07:40:46 a6 systemd[1]: Job local-fs.target/start deleted to break ordering cycle starting with sysinit.target/start > > I don't understand everything about that message, but it seems to imply > that systemd may think that the local filesystems are not mounted(?) > > Could this be causing my journald problem, maybe? Where is lvm.service coming from? I suspect it is causing the ordering cycle.