[PLUG] question on looking at systemd log files

Russell Senior russell at personaltelco.net
Thu Jul 4 16:46:47 UTC 2019


I assume that a third person could read them in whatever format he read
them in, which would be dumped-to-text, possibly filtered out, maybe not.
When I don't know what might be happening, I usually err on the side of
more logs instead of less.

On Thu, Jul 4, 2019, 17:05 Ben Koenig <techkoenig at gmail.com> wrote:

> I ask this out of morbid curiosity...
>
> How does one read systemd logs on another system? My understanding is
> that it's a binary format, right? This sounds like it presents some
> problems for taking a "glance" at the logs in the way Randall is
> asking, since you have to run journalctl to access them.
>
> I'd like to offer my assistance... but unfortunately systemd isn't
> backwards compatible with existing infrastructure... so I can't
> actually help. Hmmmm.
>
>
>
> On Wed, Jul 3, 2019 at 4:37 PM logical american
> <website.reader3 at gmail.com> wrote:
> >
> > My openSuse linux computer, Leap 15.1 stalls while booting up. I enabled
> > the debug-shell.service under systemd to record the log files, but have
> > about 6 megs of logged data from one attempted boot up.
> >
> > Is there anyone in this group who can glance at the journalctl -b and
> > dmesg log files and pick out what might have gone wrong, for the system
> > stalling upon boot? Unfortunately the log files are long, about 27K
> > lines and 3 megs+ each.
> >
> > I would prefer to email you the log file(s) if possible.
> >
> > - Randall
> >
> >
> > _______________________________________________
> > PLUG mailing list
> > PLUG at pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
> _______________________________________________
> PLUG mailing list
> PLUG at pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>



More information about the PLUG mailing list