Problem in cluster reforming

[Massimo_20]

Hello Folks,
i made the reboot of a node of the cluster. When the server startup, the cluster did not reforming and in the syslog the messagges is:
Oct 31 15:53:18 rm_ip9 cmcld: Unable to read 64 bytes from /dev/urandom: No such file or directory.
Oct 31 15:53:18 rm_ip9 cmcld: Error, tried to create a cmcld secret key with 64 bytes and only generated 0 bytes.
Oct 31 15:53:18 rm_ip9 cmcld: Unable to initialize local communications. Could not write out the shared secret file.
Oct 31 15:53:48 rm_ip9 cmclconfd[7060]: The Serviceguard daemon, /usr/lbin/cmcld[7061], exited with a status of 1.

Can you help me?
Thanks in advanced.

[Calandrello]

Friend
Executes the command cmcheckconf - C xxxx.ascii will be informed the errors that estao occurring.

[Steven E. Protter]

Shalom,

It appears there may have been some critical files erased on this system or that mounting dit not happen as expected.

What dod you do to the system besides reboot it? Any software installed/removed?

SEP

[melvyn burnard]

What version of SG are you using?

Serviceguard A.11.16 and the latest patches for A.11.15 (PHSS_31067 and PHSS_31068) include functionality which uses the HP-UX Strong Random Number Generator on HP-UX 11i if this is loaded.

Unfortunately some versions of the HP-UX Strong Random Number Generator
prior to version B.11.11.07 have a defective startup script which can
result in the wrong major number for the random number device files
/dev/random and /dev/urandom. This can result in a number of different
symptoms which can be difficult to troubleshoot. Serviceguard commands
can hang, fail or take a very long time to work often with no apparent errors in syslog.log or other external symptoms.

Any Serviceguard clusters which have the HP-UX Strong Random Number Generator software loaded should ensure they have version B.11.11.07 or newer. This can be checked by looking at the version of the KRNG11i
bundle:

# swlist -l bundle | grep KRNG
KRNG11i B.11.11.09 HP-UX 11.11 Strong Random Number Generator

The latest version can be downloaded from software.hp.com.

If you have a cluster which is behaving erratically after installing
Serviceguard A.11.16 or the patches shown above and the HP-UX Strong Random Number Generator is loaded you should check that the /dev/urandom device file has the correct major number. The driver given by the major number should be the "rng" driver. This can be verified by checking the
devices files and the kernel major number:

# ls -l /dev/*random
cr--r--r-- 1 bin bin 62 0x000000 Nov 19 18:09 /dev/random
cr--r--r-- 1 bin bin 62 0x000001 Nov 19 18:09 /dev/urandom
# lsdev | grep 62
62 -1 rng pseudo

If the driver shown by lsdev grep'ing for the major number of the /dev/urandom device file is not "rng" then Serviceguard will not
function correctly. Note that the actual major number can vary since this number is dynamically allocated.

If the major number does not match, the device files should be corrected or deleted before Serviceguard is started until a newer version of the HP-UX Strong Random Number Generator is loaded. If /dev/urandom is not present Serviceguard uses an alternate mechanism for generating random
numbers.

[Massimo_20]

Thanks for the answers. Now, i try your solution...


Regards.

[Pratyush Paul_1]

hi - you randon # generator file /dev/urandom had been deleted. and you would be fine if you could copy this from the other node. This file is required to create keys for service guard to work.

Thanks

Pratyush