[Linux-cluster] fence_ilo question

[Digimer]

On 11/07/2011 02:05 PM, Elena Ufimtseva wrote:
> Hello All
> 
> Anyone knows what is the latest version of fence_ilo or if fence_ilo
> (ILo3) should support timeout parameter? I try connecting to 
> ILO (its hp ilo v3) manually and it works fine. But fencing does not
> work in cluster.
> 
> Checking 
> 
> fence_ilo -l admin -p password -o status -a 172.28.84.33
> Unable to connect/login to fencing device
> 
> fence_ilo -V
> 2.0.115 (built Wed Aug 5 08:25:06 EDT 2009) Copyright (C) Red Hat, Inc.
> 2004 All rights reserved.
> 
> in strace output it looks like a timeout:
> 
> ioctl(3, TIOCGPTN, [6]) = 0 stat("/dev/pts/6", {st_mode=S_IFCHR|0620,
> st_rdev=makedev(136, 6), ...}) = 0 statfs("/dev/pts/6",
> {f_type="DEVPTS_SUPER_MAGIC", f_bsize=4096, f_blocks=0, f_bfree=0,
> f_bavail=0, f_files=0, f_ffree=0, ioctl(3, TIOCSPTLCK, [0]) = 0 ioctl(3,
> SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
> ioctl(3, TIOCGPTN, [6]) = 0 stat("/dev/pts/6", {st_mode=S_IFCHR|0620,
> st_rdev=makedev(136, 6), ...}) = 0 open("/dev/pts/6", O_RDWR|O_NOCTTY) =
> 4 clone(child_stack=0,
> flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
> child_tidptr=0x2acc82a54020) = 3120 close(4) = 0 select(0, NULL, NULL,
> NULL, {0, 50000}) = 0 (Timeout) write(3, "<?xml version=\"1.0\"?>\r\n",
> 23) = 23 wait4(3120, 0x7fffd7c58474, WNOHANG, NULL) = 0 wait4(3120,
> 0x7fffd7c58474, WNOHANG, NULL) = 0 select(4, [3], [], [], {10, 0}) = 1
> (in [3], left {10, 0}) read(3, "<?xml version=\"1.0\"?>\r\n\r\n", 2000)
> = 25 select(0, NULL, NULL, NULL, {0, 100}) = 0 (Timeout) wait4(3120,
> 0x7fffd7c58474, WNOHANG, NULL) = 0 wait4(3120, 0x7fffd7c58474, WNOHANG,
> NULL) = 0 select(4, [3], [], [], {9, 997862}) = 1 (in [3], left {6,
> 413000}) read(3, "HTTP/1.1 405 Method Not Allowed\r"..., 2000) = 132
> select(0, NULL, NULL, NULL, {0, 100}) = 0 (Timeout) wait4(3120,
> 0x7fffd7c58474, WNOHANG, NULL) = 0 wait4(3120, 0x7fffd7c58474, WNOHANG,
> NULL) = 0 select(4, [3], [], [], {6, 410183}) = 1 (in [3], left {6,
> 365000}) --- SIGCHLD (Child exited) @ 0 (0) --- read(3, 0x1108faa4,
> 2000) = -1 EIO (Input/output error) write(2, "Unable to connect/login to
> fenci"..., 42Unable to connect/login to fencing device ) = 42 close(3) =
> 0 select(0, NULL, NULL, NULL, {0, 100000}) = 0 (Timeout) wait4(3120,
> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 3120
> rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x39ec40e7c0},
> {0x39fdebc330, [], SA_RESTORER, 0x39ec40e7c0}, 8) = 0
> 
> That makes me think, that the default time out should be modified, but
> this version of fence_ilo
> doesn't have timeout option.
> 
> Does anyone knows if there is another version and if there is, where to
> get it.
> 
> 
> Thanks.
> 
> -- 
> Elena
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster

Looking at the cluster.rng, I see the follow options as being valid;

<attribute name="power_timeout" rha:description="Test X seconds for
status change after ON/OFF" />

<attribute name="shell_timeout" rha:description="Wait X seconds for cmd
prompt after issuing command" />

<attribute name="login_timeout" rha:description="Wait X seconds for cmd
prompt after login" />

<attribute name="power_wait" rha:description="Wait X seconds after
issuing ON/OFF" />

<attribute name="delay" rha:description="Wait X seconds before fencing
is started" />

To use these, try, for example, <fencedevice login_timeout="30" ...>

If this doesn't help, can you paste your cluster.conf file and the shell
call that works?

-- 
Digimer
E-Mail:              digimer at alteeve.com
Freenode handle:     digimer
Papers and Projects: http://alteeve.com
Node Assassin:       http://nodeassassin.org
"omg my singularity battery is dead again.
stupid hawking radiation." - epitron