- Veeam Support Knowledge Base
- Scale-out Backup Repository offload job to Quantum DXI used as S3 storage fails with "Failed to retrieve SSL certificate. Underlying error: PRNG not seeded" error
Scale-out Backup Repository offload job to Quantum DXI used as S3 storage fails with "Failed to retrieve SSL certificate. Underlying error: PRNG not seeded" error
| KB ID: | 3094 |
| Product: | Veeam Backup & Replication |
| Version: | 9.5.4.2866 |
| Published: | 2020-01-31 |
| Last Modified: | 2020-08-13 |
Get weekly article updates
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
Veeam Backup & Replication fails to perform an S3 offload task if targeted to Quantum DXI storage.
The error retrieved in UI says: "Failed to retrieve SSL certificate. Underlying error: PRNG not seeded"
The error retrieved in UI says: "Failed to retrieve SSL certificate. Underlying error: PRNG not seeded"
[06.01.2020 13:38:21] <18> Info [PublicCloudCertificateLoader] Loading certificate for 'https://<IP ADDRESS>:9000/'
[06.01.2020 13:38:21] <18> Info [AP] (6891) command: 'Invoke: Network.RetrieveSslCertificate { (EString) HostName = <IP ADDRESS>; (EInt32) Port = 9000; }'
[06.01.2020 13:38:21] <11> Info [AP] (5c63) output: <VCPCommandArgs />
[06.01.2020 13:38:21] <11> Info [AP] (5c63) output: >
[06.01.2020 13:38:26] <28> Info [AP] (6891) output: <VCPCommandResult result="false" exception="Failed to retrieve SSL certificate. Underlying error: PRNG not seeded
Agent failed to process method {Network.RetrieveSslCertificate}." />
[06.01.2020 13:38:26] <05> Info [AP] (6891) output: >
Cause
Quantum DXI series storage with firmware version prior to 4.0.3 lacks several default devices that exist in typical Linux kernels. The devices below are required by Veeam Backup & Replication, and lack of them generates the error:
- /dev/null
- /dev/zero
- /dev/random
- /dev/urandom
- /dev/tty
Solution
To resolve the issue, perform either of the following operations:
- Upgrade Quantum DXI firmware to version 4.0.3.
- Manually add required devices through Quantum DXi-Series CLI
For example:
sudo /bin/mknod -m 0666 /dev/random c 1 8 sudo /bin/mknod -m 0666 /dev/urandom c 1 9
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.