On Tue, Sep 23, 2014 at 1:40 PM, walt <[email protected]> wrote:
> On 09/23/2014 07:46 AM, Rich Freeman wrote:
>> On Tue, Sep 23, 2014 at 10:27 AM, walt <[email protected]> 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 via email to