Problem creating ServiceGuard cluster with Linux

[Serviceguard for Linux]

Try limiting the cluster name to 8 characters.

[Serviceguard for Linux]

I actually meant limit the node name to 8 characters. You might want to try limiting all names to 8 characters and I can find out which is critical.

[Eric Taverny_1]

Hi,

I have changed the nodes' name to 8 characters.
Still have the problem. I have an kernel ioctl error message with the two primary ones :

Apr 27 10:52:59 clubdd01 kernel: ioctl32(cmlocklund:3936): Unknown cmd fd(5) cmd(0000ac01){00} arg(ffffa530) on /dev/rawctl
Apr 27 10:52:59 clubdd01 cmlocklund[3949]: Port number returned by locklund_setup: 32881
Apr 27 10:52:59 clubdd01 cmcld: Lock LUN resumed (port = 32881).
Apr 27 10:52:59 clubdd01 cmlocklund[3949]: Error setting raw device (Invalid argument)
Apr 27 10:52:59 clubdd01 cmlocklund[3949]: Error binding block device (/dev/sda1) to a char device.
Apr 27 10:52:59 clubdd01 cmcld: Service cmlocklund terminated due to an exit(1).
Apr 27 10:52:59 clubdd01 cmlocklund[3952]: Total allocated: 540672 bytes, used: 0 bytes, unused 540672 bytes
Apr 27 10:53:00 clubdd01 cmcld: Automatically restarted service cmlocklund for the 11th time after failure.

I have got this version of the QLogic drivers : hp_qla2x00src-7.05.00-9.

I will check the failover status ...

[melvyn burnard]

If this also fails, I strongly recommend you log a support call with your local HP Response Centre.

[Eric Taverny_1]

i all,

We had a 64-bit version of Redhat AS 3.0 (uptdate 3) for AMD64 and Intel EM64T installed on our HP Proliant DL 360 servers with HP MC Service Guard (i386 version).

We have installed the 32-bit version of Redhat AS 3.0 (update 4) and we are able now to start our cluster.

Thanks to all for helping me.

Regards,

Eric.