| 1 |
On Tue, Sep 23, 2014 at 1:40 PM, walt <w41ter@×××××.com> wrote: |
| 2 |
> On 09/23/2014 07:46 AM, Rich Freeman wrote: |
| 3 |
>> On Tue, Sep 23, 2014 at 10:27 AM, walt <w41ter@×××××.com> wrote: |
| 4 |
>>> |
| 5 |
>>> I used systemctl to stop and restart systemd-journald, thinking I might |
| 6 |
>>> see some useful error messages. But when systemd-journal started up |
| 7 |
>>> again the journal file was back in /var/log/journal where I want it :) |
| 8 |
>>> |
| 9 |
>>> No idea why rebooting the machine didn't do the same thing. |
| 10 |
>>> |
| 11 |
>> |
| 12 |
>> Are you sure that it is solved, and that the problem won't recur on |
| 13 |
>> the next reboot? |
| 14 |
> |
| 15 |
> <sigh> After a reboot the journal file is back in /run/log/journal. |
| 16 |
> |
| 17 |
>> If it does, my next question (an educated guess, but a guess) would be |
| 18 |
>> whether you're using an initramfs, |
| 19 |
> |
| 20 |
> No, I never have. |
| 21 |
> |
| 22 |
>> I'd also look at anything |
| 23 |
>> that might be causing issues with /var/log/journal when journald is |
| 24 |
>> launched, such as that directory being on an unmounted filesystem and |
| 25 |
>> there not being some dependency that causes journald to notice. |
| 26 |
> |
| 27 |
> This particular machine has only root and swap partitions, so there's |
| 28 |
> nothing to remain unmounted during boot. |
| 29 |
> |
| 30 |
> Having reassured myself with that claim, I now spot this journal message |
| 31 |
> (which appears only on the 'broken' machine): |
| 32 |
> |
| 33 |
> Sep 23 07:40:46 a6 systemd[1]: Found ordering cycle on sysinit.target/start |
| 34 |
> Sep 23 07:40:46 a6 systemd[1]: Found dependency on local-fs.target/start |
| 35 |
> Sep 23 07:40:46 a6 systemd[1]: Found dependency on lvm.service/start |
| 36 |
> Sep 23 07:40:46 a6 systemd[1]: Found dependency on sysinit.target/start |
| 37 |
> Sep 23 07:40:46 a6 systemd[1]: Breaking ordering cycle by deleting job local-fs.target/start |
| 38 |
> Sep 23 07:40:46 a6 systemd[1]: Job local-fs.target/start deleted to break ordering cycle starting with sysinit.target/start |
| 39 |
> |
| 40 |
> I don't understand everything about that message, but it seems to imply |
| 41 |
> that systemd may think that the local filesystems are not mounted(?) |
| 42 |
> |
| 43 |
> Could this be causing my journald problem, maybe? |
| 44 |
|
| 45 |
Where is lvm.service coming from? I suspect it is causing the ordering cycle. |
Archives