https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2I0MTIxIiwiaGFzaCI6ImQ2OThlYjYxLWNmY2UtNDRkMi04NDg2LWY2ZDE0M2E2MzFkNCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Patching of Veeam Recovery Media version 5.0 fails with "ISO: FATAL ERROR:write_file: failed to create file /tmp/veeam/livecd-..., because Too many open files"

 

Challenge

The patching of the Veeam Recovery Media version 5.0 fails with the "ISO: FATAL ERROR:write_file: failed to create file /tmp/veeam/livecd-..., because Too many open files" error.

Cause

Veeam Agent reaches the limit of concurrently opened files during the ISO image unpacking that is performed by means of the unsquashfs utility.

Solution

Increase the limit of concurrently opened files for the Veeam Agent service. To do this, perform the following operations:

1. Open the service file for editing:

sudo systemctl edit veeamservice.service

2. Set the following values:

[Service]
LimitNOFILE=524288
LimitNOFILESoft=524288

3. Save changes:

sudo systemctl daemon-reload
sudo systemctl restart veeamservice.service
KB ID: 4121
Product: Veeam Agent for Linux 5.0
Published: 2021-03-02
Last Modified: 2021-03-03
Please rate how helpful this article was to you:
4.9 out of 5 based on 4 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.