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:
Last Modified:
2020-01-31

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

Rate the quality of this KB article: 
5 out of 5 based on 1 ratings

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:

Submit