Proxmox VE Systemlog settings

If errors or problems occur during the use of Proxmox VE, systemlogs support the analysis and identification of possible causes. This article explains the most important log sources and how to create them. Furthermore, you will find a script made and verified by the technical support of Thomas-Krenn.AG that automates the log collection.

Proxmox VE systemlogs

In the following, the important logs and commands are explained.

pvereport

The command pvereport creates an overview of the Proxmox configuration. The following is contained:

• package versions
• node information
• cluster state
• subscription state
• storage configuration (for example Ceph, ZFS)

Call

user@system:~$ pvereport

/var/log/syslog (only up to Proxmox VE 7.4)

The classic syslog contains notifications of the operating system, of its services as well as hardware events. Every line usually has a timestamp and a service assignment that simplifies troubleshooting.

Call

user@system:~$ less /var/log/syslog

logrotation

The size of log files is usually limited by the tool logrotate. Elder logs are stored in compressed form to safe storage space. The rotation is made automatically via cron-jobs and avoids a full file system.

Example of a typical rotation:

-rw-r----- 1 root adm  82484 2006-10-15 00:29 syslog 
-rw-r----- 1 root adm 163497 2006-10-14 13:06 syslog.0
-rw-r----- 1 root adm  23503 2006-10-13 01:30 syslog.1.gz
-rw-r----- 1 root adm  36587 2006-10-12 11:18 syslog.2.gz
...

journalctl (from Proxmox VE8.0)

Syslog has been replaced by systemd-journald from Debian 12 (Bookworm). The call is made via journalctl that enables structured and filtered log queries.

More information: Replacement of /var/log/syslog by journalctl in Debian 12

/var/log/apt/history.log

This log documentates the package changes via APT-package manager. In addition to installation and removal processes, package versions before and after updates are listed.

Call

user@system:~$ less /var/log/apt/history.log

dmesg

dmesg means "display message" and is a tool that can output the kernel messages (more specifically: the messages of the kernel ring buffer) on the screen. Under Linux, for example, dmesg reads /proc/kmsg by default and displays it as readable text. Dmesg specifies all messages of the boot process in chronological order, which are displayed in ascending order starting from zero.

Call

user@system:~$ dmesg

SMART values

SMART (Self-Monitoring, Analysis and Reporting Technology) provides information about the condition and reliability of data carriers. Warnings can indicate failures at an early stage.

Call

block devices:

user@system:~$ smartctl -a /dev/sdX

NVMe devices:

user@system:~$ nvme smart-log /dev/nvmeX

Support script

The Technical Support of Thomas-Krenn.AG provides a script that automatically collects the relevant logs and then merges them into a compressed archive. In addition, the serial numbers are determined and data is sorted by nodes.

Download: Thomas-Krenn PVE Systemlog Script

Once the script has been downloaded, the following procedure should be followed:

Usage

1. Establish a connection via SFTP (for example WinSCP or FileZilla) to the server.
2. Upload the file getpvelogs.sh to the server
3. Execute the script via shell ./getpvelogs.sh
4. Upon completion, a folder containing supportlogs.tar.gz will be created.
5. This archive can be downloaded and transmitted to the support.

After successful completion, the logs should be transmitted via the upload-address provided by the support.

• 
  Establish a connection to the server via SFTP (for example WinSCP or FileZilla).
• 
  Upload the file getpvelogs.sh to the server.
• 
  Execute the script via shell ./getpvelogs.sh
• 
  Upon completion, a folder named *.supportlogs.tar.gz will be created. This archive can then be downloaded and sent to the Support.

Author: Adrian Zillner Adrian Zillner has been working in Technical Service at Thomas-Krenn AG since May 2025. He is responsible for supporting customers and answering questions about technical issues.

Translator: Alina Ranzinger Alina has been working at Thomas-Krenn.AG since 2024. After her training as multilingual business assistant, she got her job as assistant of the Product Management and is responsible for the translation of texts and for the organisation of the department.