#1 Global Leader in Data Protection & Ransomware Recovery

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
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

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

error icon

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"
[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&#x0A;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.
or
  • 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
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.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.