cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Flexnet Agent Error on installation of Sun SPARC

Jump to solution

Team

Any idea on below error

[Thu Sep 01 08:10:42 2022 (G, 0)] {27258} Uploading file 'system on ihees3 at 20220901T080825 (Full).ndi.gz' to 'https://fihe3flexbcn004.emea.nsn-net.net/ManageSoftDL/Inventories/'
[Thu Sep 01 08:10:42 2022 (N, 0)] {27258} Error 0xE0500027: Insufficient randomness for key generation: check /dev/random
[Thu Sep 01 08:10:42 2022 (N, 0)] {27258} Error 0xE050044D: Failed to create remote directory /ManageSoftDL
[Thu Sep 01 08:10:42 2022 (N, 0)] {27258} Error 0xE0690099: Specified remote directory is invalid, or could not be created
[Thu Sep 01 08:10:42 2022 (G, 0)] {27258} ERROR: Remote directory is invalid
[Thu Sep 01 08:10:42 2022 (G, 0)] {27258} Upload failed due to a server side issue. This server may be retried during this upload session.
[Thu Sep 01 08:10:42 2022 (G, 0)] {27258} WARNING: FlexNet Manager Platform has failed to upload a file to all configured upload servers; aborting attempt to upload these file(s)
[Thu Sep 01 08:10:42 2022 (G, 0)] {27258} Uploading finished
[Thu Sep 01 08:10:42 2022 (G, 0)] {27258} ************************************************************
[Thu Sep 01 08:10:42 2022 (G, 0)] {27258} Unable to upload inventory file(s)
[Thu Sep 01 08:10:42 2022 (U, 0)] {27258} ERROR: Error (s189m263)

0 Kudos
1 Solution

The missing /dev/random & /dev/urandom devices would likely explain what is going on here.

According to https://docs.oracle.com/cd/E88353_01/html/E37851/urandom-4d.html:

Support for /dev/random and /dev/urandom was [...] made available as a patch for Solaris 8.


So you may be able to get this going if you can find and install that patch on these servers.

Also note that the oldest Solaris version supported by current FlexNet inventory agent releases is version 10. That doesn't mean the agent won't work on earlier Solaris versions, but there may be some gotchas to watch out for.

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)

View solution in original post

0 Kudos
7 Replies
ChrisG
Community Manager Community Manager
Community Manager

The "Insufficient randomness for key generation" message is an unusual one! I can't find any record that this particular error has been reported ever before.

The error indicates that the RAND_status OpenSSL function has returned 0. As per https://www.openssl.org/docs/man1.1.1/man3/RAND_status.html:


RAND_status() indicates whether or not the random generator has been sufficiently seeded. If not, functions such as RAND_bytes(3) will fail.

And from https://www.openssl.org/docs/man1.0.2/man3/RAND_status.html:


On systems that provide /dev/urandom, the randomness device is used to seed the PRNG transparently.

I don't have any real insight into what might cause this. Maybe check that the /dev/random and /dev/urandom devices on this computer are working. For example, commands like the following should return a set of random bytes:

$ od -t x1 /dev/random | head -n 3
0000000 eb b2 2e 54 b3 b4 93 c6 fe a6 60 e5 28 98 86 e5
0000020 f0 79 86 b8 9f 7e 4b 02 c9 6e ae 61 45 d8 29 ef
0000040 3e c5 e1 c2 ad d1 08 23 cd 87 3a 2c d0 9e 76 b3

$ od -t x1 /dev/urandom | head -n 3
0000000 eb b2 2e 54 b3 b4 93 c6 fe a6 60 e5 28 98 86 e5
0000020 f0 79 86 b8 9f 7e 4b 02 c9 6e ae 61 45 d8 29 ef
0000040 3e c5 e1 c2 ad d1 08 23 cd 87 3a 2c d0 9e 76 b3

 

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
0 Kudos

Thanks Chris G. Can you confirm if its nothing related to flexera agent issue. As accordingly will ask unix admin to troubleshoot at OS layer.

0 Kudos

I don't have much insight into what the cause might be, but I'd certainly start with the suggestions I made earlier to see if that gives any hints about anything that might be wrong.

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
0 Kudos

Hi Chris G 

 

Checkd with Sun administrator & below is comment .

 

Looks like those servers does not have /dev/random or /dev/urandom configured. These Solaris 8 servers are very old.

0 Kudos

The missing /dev/random & /dev/urandom devices would likely explain what is going on here.

According to https://docs.oracle.com/cd/E88353_01/html/E37851/urandom-4d.html:

Support for /dev/random and /dev/urandom was [...] made available as a patch for Solaris 8.


So you may be able to get this going if you can find and install that patch on these servers.

Also note that the oldest Solaris version supported by current FlexNet inventory agent releases is version 10. That doesn't mean the agent won't work on earlier Solaris versions, but there may be some gotchas to watch out for.

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
0 Kudos

Thanks Chris. We will check with sun admin & update you.

0 Kudos

After Patch installation. Issue has resolved.

 

Thanks for your help & support as always.