public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: journald refuses to put log files in /var/log/journal/ [NOT SOLVED]
Date: Tue, 23 Sep 2014 14:28:37 -0400	[thread overview]
Message-ID: <CAJ0EP433Tuu0m64+J4fQbvLqC3qY2=ZVCLFjx33pUh2wfUpOqg@mail.gmail.com> (raw)
In-Reply-To: <lvsban$hj8$1@ger.gmane.org>

On Tue, Sep 23, 2014 at 1:40 PM, walt <w41ter@gmail.com> wrote:
> On 09/23/2014 07:46 AM, Rich Freeman wrote:
>> On Tue, Sep 23, 2014 at 10:27 AM, walt <w41ter@gmail.com> 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?
>
> <sigh>  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.


  reply	other threads:[~2014-09-23 18:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  0:41 [gentoo-user] journald refuses to put log files in /var/log/journal/ walt
2014-09-23  0:52 ` Rich Freeman
2014-09-23  3:50 ` Canek Peláez Valdés
2014-09-23 14:27   ` [gentoo-user] Re: journald refuses to put log files in /var/log/journal/ [SOLVED] walt
2014-09-23 14:46     ` Rich Freeman
2014-09-23 17:40       ` [gentoo-user] Re: journald refuses to put log files in /var/log/journal/ [NOT SOLVED] walt
2014-09-23 18:28         ` Mike Gilbert [this message]
2014-09-23 18:42           ` Rich Freeman
2014-09-23 21:55           ` [gentoo-user] Re: journald refuses to put log files in /var/log/journal/ [REALLY SOLVED] walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ0EP433Tuu0m64+J4fQbvLqC3qY2=ZVCLFjx33pUh2wfUpOqg@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox