[VHRISO] Veeam hardened repo - /var/log

[glen_uk]

Hello,

I want to try and get the /var/log files from our Veeam Hardened repo (Veeam ISO) to diagnose why it went offline last night. However, when I log in via console I get the locked down menu, when I start the SSH session, I can unprivileged credentials and cannot sudo to get access to the directory and I cannot ssh in with the vhradmin account.

Can anyone advise how I can get to those logs?

[Mildur]

Hi Glen

Welcome to the forum.

You could use the <Files Menu> in the backup console to download and open Log Files from a Hardened Repository.


Best,
Fabian

[gmajestix]

I'm guessing you are not the only one. I had four different hardened repos go down yesterday and also today.

[glen_uk]

Hi Mildur,

Thank you for that answer. I used that method to access /var/log/messages and received the following error:

"Permission denied POSIX: Failed to open [/var/log/messages] Failed to open file [/var/log/message] for reading. read: End of file"

Would you be able to advise?

[Mildur]

Hi Glen

I assume our service has no access permissions for some of the log files.
Another option is to boot into single user mode using a console. That should give you full access to the entire system inclusive log files.

Best,
Fabian

[glen_uk]

I'm guessing you are not the only one. I had four different hardened repos go down yesterday and also today.

It looks like their was an update to NetworkManager and the Kernel and since then it lost network... we've been fine since rebooting it.

[glen_uk]

Hi Glen

I assume our service has no access permissions for some of the log files.
Another option is to boot into single user mode using a console. That should give you full access to the entire system inclusive log files.

Best,
Fabian

That's fine... thank you very much for your help.

[HannesK]

Hello,
getting access to /var/log can be done via live boot or single user mode. And it would really help us if you could open a support case because we see similar issues also in this thread while we do not see them internally.

Best regards
Hannes

[ASG]

It looks like their was an update to NetworkManager and the Kernel and since then it lost network... we've been fine since rebooting it.

Our Hardened repo was pingable but only unavailble to VBR. Rescan did not bring it online. So it looks like network was not completetly down - but after a reboot and rescan it was fine. Went unavailable 07.07. somewhere between 05:00 and 13:00