what version and arch of linux and solaris ? (eg, give a uname -mp for each)
what is the filename of the agent you are using for each ?
Linux: x86_64 x86_64
Solaris: sun4us sparc
I believe we run the following command under the covers to attempted to generate random data. You might want to try this manually to see what happens:
openssl rand 1024
On Linux, I believe we have also seen cases where disabling SELinux prior to agent installation and then re-enabling it, resolved the issue.
As Bill hinted at, we also see this when the wrong installer is used on the wrong platform e.g. x64 on x86 etc but that does not seem to be a problem here.
Hi John, This is the output I get running openssl,
. It also randomizes the title bar on my putty
Kg¯ûÓ¥ßÀgGúòÏ°. h\&HRÔXk ;!ãû
îÃ\p3Ê5Jîvmsteqlora5:~ # PuTTYPuTTY6cPuTTY
this happens on the solaris and the linux systems ?
which openssl is being run (which openssl) ?
Why do you try install RSCD83-SP1-SOL10-SPARC.sh in Sun4us sparc?
Although try with:
ln -s /var/spool/prngd/pool /dev/egd-pool
or similar, the not seeded message above goes away and openssh programs then work properly.
ok - so you are having the rng issues w/ both installers, on both oses ?
can you run the installer on one of the problem boxes/platforms and include the entire bladelogic_install file or stdout ?
also - in the 8.2 installer we added some debug settings - can you try 8.2 or 8.3 and set the 'BSA_DEBUG=true' env variable before running the installer ?
I recently had this issue on a server that didn't have the "file" package installed, and therefore no "file" command, which is used to determine the platform in the Install script. If anyone hits this on linux, and has the appropriate platform's installer, check to see if file is installed.