Your message dated Wed, 3 Apr 2019 00:25:02 +0200
with message-id <[email protected]>
and subject line Re: journalctl has lost a huge part
has caused the Debian Bug report #818358,
regarding journalctl has lost a huge part
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
818358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818358
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Package: systemd
Version: 215-17+deb8u3
I've seen it several times that the journal does not include the
very first steps at boot time. Sample:
# journalctl -b | head -20
- -- Logs begin at Wed 2016-03-16 07:48:02 CET, end at Wed 2016-03-16 11:42:09
CET. --
Mar 16 09:50:11 lxc05.example.com systemd-journal[79]: Runtime journal is using
8.0M (max allowed 3.1G, trying to leave 4.0G free of 31.4G available â
current limit 3.1G).
Mar 16 09:50:11 lxc05.example.com systemd-journal[79]: Runtime journal is using
8.0M (max allowed 3.1G, trying to leave 4.0G free of 31.4G available â
current limit 3.1G).
Mar 16 09:50:11 lxc05.example.com systemd-journal[79]: Journal started
Mar 16 09:50:11 lxc05.example.com anacron[60]: Anacron 2.3 started on 2016-03-16
Mar 16 09:50:11 lxc05.example.com anacron[60]: Normal exit (0 jobs run)
Mar 16 09:50:11 lxc05.example.com cron[65]: (CRON) INFO (pidfile fd = 3)
Mar 16 09:50:15 lxc05.example.com cron[65]: (CRON) INFO (Running @reboot jobs)
Mar 16 09:50:24 lxc05.example.com ntpd[81]: ntpd [email protected] Wed Oct 28
20:16:08 UTC 2015 (1)
Mar 16 09:50:25 lxc05.example.com systemd[1]: Started LSB: Start NTP daemon.
Mar 16 09:50:27 lxc05.example.com ntpd[83]: proto: precision = 0.218 usec
Mar 16 09:50:27 lxc05.example.com ntpd[83]: Listen and drop on 0 v4wildcard
0.0.0.0 UDP 123
Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen and drop on 1 v6wildcard ::
UDP 123
Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen normally on 2 lo 127.0.0.1
UDP 123
Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen normally on 3 lo ::1 UDP 123
Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen normally on 4 eth1
fe80::216:a8ff:fe3d:3edc UDP 123
Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen normally on 5 eth0
fe80::216:17ff:fe4b:d246 UDP 123
Mar 16 09:50:31 lxc05.example.com ntpd[83]: peers refreshed
Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listening on routing socket on fd
#22 for interface updates
Mar 16 09:50:31 lxc05.example.com ntpd[83]: authreadkeys: file /etc/ntp/keys:
No such file or directory
It should have shown something like this:
# journalctl -b | head -20
- -- Logs begin at Wed 2016-03-16 07:48:01 CET, end at Wed 2016-03-16 11:49:22
CET. --
Mar 16 09:49:33 lxc06.example.com systemd-journal[23]: Runtime journal is using
8.0M (max allowed 3.1G, trying to leave 4.0G free of 31.4G available â
current limit 3.1G).
Mar 16 09:49:33 lxc06.example.com systemd-journal[23]: Runtime journal is using
8.0M (max allowed 3.1G, trying to leave 4.0G free of 31.4G available â
current limit 3.1G).
Mar 16 09:49:33 lxc06.example.com systemd-journal[23]: Journal started
Mar 16 09:49:33 lxc06.example.com systemd[1]: Mounted Huge Pages File System.
Mar 16 09:49:33 lxc06.example.com systemd[1]: Mounted Debug File System.
Mar 16 09:49:33 lxc06.example.com systemd[1]: Mounted POSIX Message Queue File
System.
Mar 16 09:49:33 lxc06.example.com systemd[1]: Started Remount Root and Kernel
File Systems.
Mar 16 09:49:33 lxc06.example.com systemd[1]: Started Various fixups to make
systemd work better on Debian.
Mar 16 09:49:33 lxc06.example.com systemd[1]: Starting Load/Save Random Seed...
Mar 16 09:49:33 lxc06.example.com systemd[1]: Starting Local File Systems (Pre).
Mar 16 09:49:33 lxc06.example.com systemd[1]: Reached target Local File Systems
(Pre).
Mar 16 09:49:33 lxc06.example.com systemd[1]: Starting Local File Systems.
Mar 16 09:49:33 lxc06.example.com systemd[1]: Reached target Local File Systems.
Mar 16 09:49:33 lxc06.example.com systemd[1]: Starting Remote File Systems.
Mar 16 09:49:36 lxc06.example.com systemd-journal[23]: Permanent journal is
using 8.0M (max allowed 2.0G, trying to leave 4.0G free of 2.8T available â
current limit 2.0G).
Mar 16 09:49:56 lxc06.example.com systemd-journal[23]: Time spent on flushing
to /var is 19.210500s for 15 entries.
Mar 16 09:49:34 lxc06.example.com systemd[1]: Started Trigger Flushing of
Journal to Persistent Storage.
Mar 16 09:49:42 lxc06.example.com systemd[1]: Started Create Volatile Files and
Directories.
Mar 16 09:49:42 lxc06.example.com systemd[1]: Starting Update UTMP about System
Boot/Shutdown...
Both hosts are LXC container, identical setup, running on the same hardware
and booted in parallel.
Its essential to have a complete journal.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJW6TvpAAoJEAqeKp5m04HLTvgIAJdnKee8dDo0IBWvFGP4cuXw
RXWK3xj1gKbsSJE2evxOsoCmsJCSI/tun34UiKsAvhsu7FazOYGZJZfplGSbwU+U
uRfm9cafKARhJFNt+SP9J8zs6hcgIyj7/wX4Q0DLvn+Hl79KFjB7oKgnfpBeQyR+
uas21V+2K408OyFUQMvXQ1XBCB3f0Pe8fPHFxILWnL58RJpKL2Q6iOVgDged/T5A
87W2d2ovms6rdLounp6S7Ad4aMAp9kIkvs/W0OI0z7JkSx8L9tqxyE3nGBX47rWB
mztueupq5s6gZ4CGteKS3dAjvDaQnL3LBlRo7SW7b4ri7NmtNdbknTEO6HTcBLs=
=Pnbp
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Wed, 16 Mar 2016 11:56:41 +0100 Harald Dunkel <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Package: systemd
> Version: 215-17+deb8u3
>
> I've seen it several times that the journal does not include the
> very first steps at boot time. Sample:
>
> # journalctl -b | head -20
> - -- Logs begin at Wed 2016-03-16 07:48:02 CET, end at Wed 2016-03-16
> 11:42:09 CET. --
> Mar 16 09:50:11 lxc05.example.com systemd-journal[79]: Runtime journal is
> using 8.0M (max allowed 3.1G, trying to leave 4.0G free of 31.4G available
> â current limit 3.1G).
> Mar 16 09:50:11 lxc05.example.com systemd-journal[79]: Runtime journal is
> using 8.0M (max allowed 3.1G, trying to leave 4.0G free of 31.4G available
> â current limit 3.1G).
> Mar 16 09:50:11 lxc05.example.com systemd-journal[79]: Journal started
> Mar 16 09:50:11 lxc05.example.com anacron[60]: Anacron 2.3 started on
> 2016-03-16
> Mar 16 09:50:11 lxc05.example.com anacron[60]: Normal exit (0 jobs run)
> Mar 16 09:50:11 lxc05.example.com cron[65]: (CRON) INFO (pidfile fd = 3)
> Mar 16 09:50:15 lxc05.example.com cron[65]: (CRON) INFO (Running @reboot jobs)
> Mar 16 09:50:24 lxc05.example.com ntpd[81]: ntpd [email protected] Wed Oct 28
> 20:16:08 UTC 2015 (1)
> Mar 16 09:50:25 lxc05.example.com systemd[1]: Started LSB: Start NTP daemon.
> Mar 16 09:50:27 lxc05.example.com ntpd[83]: proto: precision = 0.218 usec
> Mar 16 09:50:27 lxc05.example.com ntpd[83]: Listen and drop on 0 v4wildcard
> 0.0.0.0 UDP 123
> Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen and drop on 1 v6wildcard
> :: UDP 123
> Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen normally on 2 lo 127.0.0.1
> UDP 123
> Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen normally on 3 lo ::1 UDP
> 123
> Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen normally on 4 eth1
> fe80::216:a8ff:fe3d:3edc UDP 123
> Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listen normally on 5 eth0
> fe80::216:17ff:fe4b:d246 UDP 123
> Mar 16 09:50:31 lxc05.example.com ntpd[83]: peers refreshed
> Mar 16 09:50:31 lxc05.example.com ntpd[83]: Listening on routing socket on fd
> #22 for interface updates
> Mar 16 09:50:31 lxc05.example.com ntpd[83]: authreadkeys: file /etc/ntp/keys:
> No such file or directory
>
>
> It should have shown something like this:
>
> # journalctl -b | head -20
> - -- Logs begin at Wed 2016-03-16 07:48:01 CET, end at Wed 2016-03-16
> 11:49:22 CET. --
> Mar 16 09:49:33 lxc06.example.com systemd-journal[23]: Runtime journal is
> using 8.0M (max allowed 3.1G, trying to leave 4.0G free of 31.4G available
> â current limit 3.1G).
> Mar 16 09:49:33 lxc06.example.com systemd-journal[23]: Runtime journal is
> using 8.0M (max allowed 3.1G, trying to leave 4.0G free of 31.4G available
> â current limit 3.1G).
> Mar 16 09:49:33 lxc06.example.com systemd-journal[23]: Journal started
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Mounted Huge Pages File System.
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Mounted Debug File System.
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Mounted POSIX Message Queue
> File System.
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Started Remount Root and Kernel
> File Systems.
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Started Various fixups to make
> systemd work better on Debian.
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Starting Load/Save Random
> Seed...
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Starting Local File Systems
> (Pre).
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Reached target Local File
> Systems (Pre).
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Starting Local File Systems.
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Reached target Local File
> Systems.
> Mar 16 09:49:33 lxc06.example.com systemd[1]: Starting Remote File Systems.
> Mar 16 09:49:36 lxc06.example.com systemd-journal[23]: Permanent journal is
> using 8.0M (max allowed 2.0G, trying to leave 4.0G free of 2.8T available â
> current limit 2.0G).
> Mar 16 09:49:56 lxc06.example.com systemd-journal[23]: Time spent on flushing
> to /var is 19.210500s for 15 entries.
> Mar 16 09:49:34 lxc06.example.com systemd[1]: Started Trigger Flushing of
> Journal to Persistent Storage.
> Mar 16 09:49:42 lxc06.example.com systemd[1]: Started Create Volatile Files
> and Directories.
> Mar 16 09:49:42 lxc06.example.com systemd[1]: Starting Update UTMP about
> System Boot/Shutdown...
>
>
> Both hosts are LXC container, identical setup, running on the same hardware
> and booted in parallel.
>
journald has matured a lot in the mean time, so let's close this old bug
report.
If you still have problems with a recent version of systemd, please let
us know, so we can re-open the bug report.
In that case, please attach the output of "reportbug --template systemd"
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
