Startup messages in PROXMOX Server.

[ramses]

Hi everybody,

When I start the PROXMOX Server shows some errors during the startup process.

I am lookup the file that can contain these messages but I can't found.

In messages not appear, in syslog neither, etc...

Does PROXMOX loging this startup messages in any log file?


Regards,

Ramses

 

[mbaldini]

dmesg -H

 

[fireon]

systemctl --failed
journalctl -r -p3
journalctl -b

 

[ramses]

systemctl --failed
journalctl -r -p3
journalctl -b

fireon, very thanks by your answer.

During the startup appear some errors with modprobe module and the LV's of the VM / CT that not appear when I execute these commands.

Can I loging all startup messages in any file to review later?


Regards,

Ramses

 

[fireon]

This is "journalctl -b". You can also do some grep or -p3. Maybe an "journalctl -b > boot.log" should also work.

 

[ramses]

This is "journalctl -b". You can also do some grep or -p3. Maybe an "journalctl -b > boot.log" should also work.

fireon, the startup error messages that appear are like these:

-----------------------------------
/sbin/modprobe failed: 1

Can't process LV pve/data: thin-pool target support missing from kernel?

Can't process LV pve/vm-100-disk-1 thin target support missing from kernel?
-----------------------------------

When I use the journalctl -b or journalctl -p3 commands with grep, not appears nothing.

Where are saved these error messages and how could I see they?


Regards,

Ramses

 

[fireon]

Hmm, i remember... there is debug/maintenance mode for systemd, there you debug during the bootprocess on another shell in anohter tty. Sorry but i didn't remember the name. But what i know is that you must enable it with "systemctl enable ..." Search google about.

 

[fabian]

fireon, the startup error messages that appear are like these:

-----------------------------------
/sbin/modprobe failed: 1

Can't process LV pve/data: thin-pool target support missing from kernel?

Can't process LV pve/vm-100-disk-1 thin target support missing from kernel?
-----------------------------------

When I use the journalctl -b or journalctl -p3 commands with grep, not appears nothing.

Where are saved these error messages and how could I see they?


Regards,

Ramses

those can be ignored (they just state that in the initrd, you don't have LVM thin support. this does not matter, as you don't need your thin pools there). we might include the thin modules at some point, but it's not as straightforward as just copying the modules (you also need LVM userspace tools).

 

[ramses]

Fabian, very thanks.

But I am searching where saves PROXMOX, if it saves, all error messages that appear in Console when it starts.

I have googled a lot but I don't find where saves this errors messages or how to configure PROXMOX to save this messages.

Any idea...?


Best regards,

Ramses

 

[fabian]

Fabian, very thanks.

But I am searching where saves PROXMOX, if it saves, all error messages that appear in Console when it starts.

I have googled a lot but I don't find where saves this errors messages or how to configure PROXMOX to save this messages.

Any idea...?


Best regards,

Ramses

for the early boot, you need to set some debug on the kernel command line (not recommended for production use) if you want debug logs to go to /run. the rest is just regular dmesg/syslog/systemd-journald..

 

[bockhold]

All this is really good to know - I nearly had a heart attack seeing these messages running by...