[V13] Veeam Transport service fails due to missing /var/run/veeamtransport directory after reboot

[ashleyw]

hi,
We are running 2x Rocky9 self managed storage appliances
I applies some OS patches to them yesterday and rebooted them, and they went off line and it's taken me a few hours to trace what was going on.
Under managed servers the 2x managed servers show as offline.
I go into the UI in Veeam for managed servers and edit the server and then it fails.
I see from ssh'ing into our self managed storage appliances;

Code: Select all

tail /var/log/VeeamBackup/VeeamTransportSvc.log
[24.09.2025 09:15:59.467] <140445720534848>          |   User  : r: root(0) e: root(0) s: root(0)
[24.09.2025 09:15:59.467] <140445720534848>          |   Group : r: root(0) e: root(0) s: root(0)
[24.09.2025 09:15:59.467] <140445720534848>          | }
[24.09.2025 09:15:59.467] <140445720534848>          | ERR |Fatal error
[24.09.2025 09:15:59.467] <140445720534848>          | >>  |No such file or directory
[24.09.2025 09:15:59.467] <140445720534848>          | >>  |POSIX: Failed to create or open file [/var/run/veeamtransport/veeamtransport.pid].
[24.09.2025 09:15:59.467] <140445720534848>          | >>  |An exception was thrown from thread [140445720534848].

while its repeatedly failing in the managed server UI, I see that the directory /var/run/veeamtransport does not exist, so as a temporary hack after each reboot of the storage appliance I now have to do the following to stop the storage device going offline.

Code: Select all

mkdir /var/run/veeamtransport
chmod 755 /var/run/veeamtransport

So my guess is when the self managed linux server is added, then the addition process creates the directory, but when the services start after a reboot, then the the service isn't creating the directory again, causing the start up to fail, so perhaps its the "/opt/veeam/transport/veeamtransport" process which needs to be looked at to ensure starting it as a service corectly creates the directory under /var/run with the correct permissions.

Please can someone advise of a permanent fix as this is definitely going to catch others out.

thanks
Ashley

[Mildur]

Hi Ashley

Can you please report such bugs through the standard process with our customer support team? Our support team will investigate the issue and if necessary escalate it to our RnD teams which can provide you with the „permanent fix“.

Please remember that V13 is a fully supported release, which means we require a case number for any technical issue.

Thank you for understanding,
Fabian

[ashleyw]

Thanks Fabian,
I've logged a job and uploaded the logs. Case #07832243.

cheers
Ashley

[ashleyw]

For anyone stumbling across this. Shout out to Allan from Veeam support who was able to help me out.
The issue was that the repository had previously been used for Veeam12 and I attempted to use this for Veeam13 and this can cause an issue with the systemd startup process for Veeam.
So the solution was simply to remove the /etc/systemd/system/veeamtransport.service file and then to reconfirm the server under the managed server list and then things work perfectly after a reboot.

For any naysayers on Veeam Support, I have never had a single negative support experience with Veeam in the last 15 years we've been using their products - so keep up the great work team!

Code: Select all

# systemctl stop veeamtransport 
# cd /etc/systemd/system/ 
# mv veeamtransport.service veeamtransport.service.old
# reboot

* Veeamconsole>Backup Infrastructure>Managed servers>Linux, edit existing server, and reconfirm. 

cheers
Ashley

[ITP-Stan]

Looks like a great candidate for a KB support article.