Successful boots which crashed somehow and sometime afterwards, will
show the same "until" value ("still running" or timestamp) as the next
following boot(s). The most recent boot from such a sequence of
duplicated "until" lines, has not been crashed or not yet.Example output where only the boot from 16:25:41 crashed: reboot system boot 6.5.11-7-pve Thu Apr 11 16:31:24 2024 still running reboot system boot 6.5.11-7-pve Thu Apr 11 16:29:17 2024 - Thu Apr 11 16:31:12 2024 (00:01) reboot system boot 6.5.11-7-pve Thu Apr 11 16:25:41 2024 - Thu Apr 11 16:31:12 2024 (00:05) ... Furthermore, it shows the booted/crashed/problematic kernel version. `last` is also used since currently `journalctl --list-boots` can take 10 seconds or even longer on some systems, with no option to limit the amount of reported boot lines. Signed-off-by: Alexander Zeidler <a.zeid...@proxmox.com> --- v3: * place the cmd after pveversion due to priority reasons v2: https://lists.proxmox.com/pipermail/pve-devel/2024-April/063286.html * move away from dmesg base * list also recent (5) boot timestamps with additional information v1: https://lists.proxmox.com/pipermail/pve-devel/2024-March/062342.html PVE/Report.pm | 1 + 1 file changed, 1 insertion(+) diff --git a/PVE/Report.pm b/PVE/Report.pm index 73f14744..9a8eaa4b 100644 --- a/PVE/Report.pm +++ b/PVE/Report.pm @@ -33,6 +33,7 @@ my $init_report_cmds = sub { 'date -R', 'cat /proc/cmdline', 'pveversion --verbose', + 'last reboot -F -n5', 'cat /etc/hosts', 'pvesubscription get', 'cat /etc/apt/sources.list', -- 2.39.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
