-
matteu
- Veeam Legend
- Posts: 1039
- Liked: 171 times
- Joined: May 11, 2018 8:42 am
- Contact:
VSA 13.1 warning log generation
Hello,
Since the upgrade from 13.0 to 13.1 on VSA when I try to generate log, I have this warning for the VBR server :
Logs export completed with warning : ''Failed to collect nginx logs: ensure that veeam-usr-transportsvc user has read and execute permissions for /var/log/nginx directory and all of its contents.'
I opened support ticket 08187815 and they help me to solve it.
However I could reproduce the same issue in a lab environment and I would like to know if other people have it too or not ?
Since the upgrade from 13.0 to 13.1 on VSA when I try to generate log, I have this warning for the VBR server :
Logs export completed with warning : ''Failed to collect nginx logs: ensure that veeam-usr-transportsvc user has read and execute permissions for /var/log/nginx directory and all of its contents.'
I opened support ticket 08187815 and they help me to solve it.
However I could reproduce the same issue in a lab environment and I would like to know if other people have it too or not ?
-
david.domask
- Product Manager
- Posts: 3857
- Liked: 936 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: VSA 13.1 warning log generation
Hi matteu,
I know on 13.0.x we had an issue with this previously, but it should have been resolved already on a 13.0.x build. I did see this though on my lab as well on 13.1, though I was still able to export logs (save the nginx logs)
Please continue with Support to get to root cause.
I know on 13.0.x we had an issue with this previously, but it should have been resolved already on a 13.0.x build. I did see this though on my lab as well on 13.1, though I was still able to export logs (save the nginx logs)
Please continue with Support to get to root cause.
David Domask | Product Management: Principal Analyst
-
matteu
- Veeam Legend
- Posts: 1039
- Liked: 171 times
- Joined: May 11, 2018 8:42 am
- Contact:
Re: VSA 13.1 warning log generation
Hello,
To be honest, I close the ticket because support provided me a manual fix with give correct permission.
Now when I create a new ticket, I have a warning with an other file so I will reopen it and ask them to find the root cause because I will not set ACL on the entire logs files
To be honest, I close the ticket because support provided me a manual fix with give correct permission.
Now when I create a new ticket, I have a warning with an other file so I will reopen it and ask them to find the root cause because I will not set ACL on the entire logs files
-
david.domask
- Product Manager
- Posts: 3857
- Liked: 936 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: VSA 13.1 warning log generation
Got it, please share the case number once you create it -- manually setting permissions undoubtedly gets you past the warning, but we need to fix it properly, there should be 0 reasons to go into shell on the Veeam Appliances.
David Domask | Product Management: Principal Analyst
-
matteu
- Veeam Legend
- Posts: 1039
- Liked: 171 times
- Joined: May 11, 2018 8:42 am
- Contact:
Re: VSA 13.1 warning log generation
Sure 
This is the new one : #08190792
This is the new one : #08190792
Who is online
Users browsing this forum: DatatoSecure, Google [Bot] and 351 guests