[SOLVED] Proxmox GUI doesn't show syslogs anymore?

kalasnikov

New Member
Jan 25, 2022
15
1
3
Not sure what happened or what I'm even supposed to look at. I have an old proxmox server that's not really doing anything. Its fully up to date. I was just poking around and noticed Syslog in the GUI isn't showing anything? But I can see it if I tail/cat it manually in the server.

Bellow is package versions.

Code:
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
 
But I can see it if I tail/cat it manually in the server.
Note that rsylog's /var/log/syslog isn't used for this purpose but rather systemd's journald, check with journalctl -b.

Besides that, does the time-range mode (vs. the default "live mode") also shows the same problems?
Can you open the web-developer console from your browser to check if anything times out (network view) or if some other error is logged in the console?

Could be also worth to check the journal/syslog on the server (for example, via ssh) for possibly related errors.
 
Both Live/Time-Range mode aren't showing anything. Below is my JournalD config perhaps I may have made an unsupported change?

Code:
[Journal]
Storage=persistent
SplitMode=none
RateLimitInterval=0
RateLimitIntervalSec=0
RateLimitBurst=0
ForwardToSyslog=no
ForwardToWall=yes
Seal=no
Compress=yes
SystemMaxUse=64M
RuntimeMaxUse=60M
MaxLevelStore=warning
MaxLevelSyslog=warning
MaxLevelKMsg=warning
MaxLevelConsole=notice
MaxLevelWall=crit
 
Was sure I wasn't going to get a response as it's a bit of a strange issue. For those who may run into this strange issue I'm not sure if this will fix it for you, but I fixed this by running
Code:
#apt reinstall gzip --purge