Re: [systemd-devel] journald: no such file or directory
On Tue, 04.09.12 09:44, Christian Hesse (l...@eworm.de) wrote: > Hello everybody, > > a daemon flooded my syslog and rsyslog filled my log partition. After that > journald complains on startup: > > systemd-journald[260]: Failed to open > /var/log/journal/d1ba4a2d5fc8ab0c4c46f6f74b607fdd/fss: No such file or > directory > > How to fix that? > Everything seems to work without problems though. The two incidents are not related (as explained in the other mail). I have now fixed journald in git to not print that message anymore as it is quite pointless. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] journald: no such file or directory
Dave Reisner on Tue, 2012/09/04 06:03:
> On Tue, Sep 04, 2012 at 09:44:26AM +0200, Christian Hesse wrote:
> > Hello everybody,
> >
> > a daemon flooded my syslog and rsyslog filled my log partition. After that
> > journald complains on startup:
> >
> > systemd-journald[260]: Failed to open
> > /var/log/journal/d1ba4a2d5fc8ab0c4c46f6f74b607fdd/fss: No such file or
> > directory
> >
> > How to fix that?
> > Everything seems to work without problems though.
>
> These two events are unrelated. You've enabled persistent logs without
> setting up your sealing key.
>
> journalctl --setup-keys
Ah, some unrelated conditions made me think this is related. Thanks for the
hint!
--
main(a){char*c=/*Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/*Chris get my mail address:*/=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig*/b/42*2-3)*42);}
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] journald: no such file or directory
On Tue, Sep 04, 2012 at 09:44:26AM +0200, Christian Hesse wrote:
> Hello everybody,
>
> a daemon flooded my syslog and rsyslog filled my log partition. After that
> journald complains on startup:
>
> systemd-journald[260]: Failed to open
> /var/log/journal/d1ba4a2d5fc8ab0c4c46f6f74b607fdd/fss: No such file or
> directory
>
> How to fix that?
> Everything seems to work without problems though.
These two events are unrelated. You've enabled persistent logs without
setting up your sealing key.
journalctl --setup-keys
d
> --
> main(a){char*c=/*Schoene Gruesse */"B?IJj;MEH"
> "CX:;",b;for(a/*Chris get my mail address:*/=0;b=c[a++];)
> putchar(b-1/(/* gcc -o sig sig.c && ./sig*/b/42*2-3)*42);}
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] journald: no such file or directory
Hello everybody,
a daemon flooded my syslog and rsyslog filled my log partition. After that
journald complains on startup:
systemd-journald[260]: Failed to open
/var/log/journal/d1ba4a2d5fc8ab0c4c46f6f74b607fdd/fss: No such file or
directory
How to fix that?
Everything seems to work without problems though.
--
main(a){char*c=/*Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/*Chris get my mail address:*/=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig*/b/42*2-3)*42);}
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
