[systemd-devel] I added the uuid to match a container to /var/log/journal

[Lennart Poettering]

On Fri, 16.11.12 09:20, Daniel J Walsh (dwalsh at redhat.com) wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
>  ls -l /var/log/journal/
> total 12
> drwxr-xr-x. 2 root root 12288 Nov 16 08:47 1b16d5a8cec649e7ba7d9f9f6ef8f393
> lrwxrwxrwx. 1 root root    52 Nov 13 15:24 1f9684eeed2d43d3bfee702a89f849d6 ->
> /var/lib/libvirt/filesystems/apache1/var/log/journal
> lrwxrwxrwx. 1 root root    48 Nov 13 15:29 99f38a5c9bfd46bab46cc8e2685bee65 ->
> /var/lib/libvirt/filesystems/dan/var/log/journal

The symlink should actually be from the machine ID to the machine ID,
i.e.e instead of:

/var/log/journal/1f9684eeed2d43d3bfee702a89f849d6 → /var/lib/libvirt/filesystems/apache1/var/log/journal

please create:

/var/log/journal/1f9684eeed2d43d3bfee702a89f849d6 → /var/lib/libvirt/filesystems/apache1/var/log/journal/1f9684eeed2d43d3bfee702a89f849d6

> How would I go about viewing the log file in journalctl?

As Zbigniew pointed out "journalctl -m" is what you want.

> Also in talks about containers, a discussion came up about using syslog to off
> load container logs to a centralized server.  Is there a way to collect the
> data from journald/containers into the host systems syslog?

Do you mean "BSD syslog" when you speak of syslog? If so, then one way
to implement this could be by hard linking/bind mounting the
/run/systemd/journal/syslog socket of the host into all containers at
the same place. That's where the syslog forwarding logic in journald
forwards all messages.

But honestly, I don't think this is really such a good idea since there
is no way how to discern container messages from others right now, since
SCM_CREDENTIALS does not include container IDs or anything.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.