« Validating Windows Providers | Main | Operations Manager and Unix/Linux Agents »

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

the "not enough entropy" is a good one, I had not seen that one yet.
there is a couple more of these errors and possible troubleshooting here:

http://technet.microsoft.com/en-us/library/dd891011.aspx

and here

http://technet.microsoft.com/en-us/library/dd891009.aspx

there is some more info about "not enough entropy" here
http://social.technet.microsoft.com/Forums/en-US/crossplatformsles/thread/f94ec905-23ac-4444-b9f8-644fec3ae357

Hi,

Thanks for this advice.

Your technique of remapping /dev/urandom onto /dev/random leaves /dev/random in a writable state:

# rm -rf /dev/random
# mknod /dev/random c 1 9
# ls -al /dev/random
crw-r--r-- 1 root root 1, 9 Aug 25 16:28 /dev/random

You might be better off running:
# mknod -m 0444 /dev/random c 1 9
# ls -al /dev/random
cr--r--r-- 1 root root 1, 9 Aug 25 16:31 /dev/random

After the installation, you should replace the existing /dev/random. I believe it is different from /dev/urandom for a reason.

Spelunker, you are correct the permissions should be set correctly if you are going to maintain the file. It should root writable though, so the commands would be:
mknod -m 644 /dev/random c 1 9
chown root:root /dev/random

To go back to the original state, you can use the commands:
mknod -m 644 /dev/random c 1 8
chown root:root /dev/random

I've updated the post to specify the new commands.

Thanks for pointing that out.

The comments to this entry are closed.