hi,
some of you might recall the bashism in external/rackpdu
which was discussed in [1] fixed in [2].
i today stumbled over this problem again and i think that the
stonith output is not fully captured via syslog:
calling stonith manually:
> # stonith -t external/rackpdu hostlist="AUTO" pduip="x" community="y" -T
> reset z2
> local: 280: l.i.a: bad variable name
^ please remember this line
> external/rackpdu[8264]: ERROR: Outlet number not found for node z2. Result:
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.1 = STRING: "z1"
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.2 = STRING: "b"
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.3 = STRING: "m2"
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.4 = STRING: "c1"
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.5 = STRING: "w1"
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.6 = STRING: "l.i.a"
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.7 = STRING: "w2"
...
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.24 = STRING: "abc"
> ** INFO: external_run_cmd: Calling '/usr/lib/stonith/plugins/external/rackpdu
> reset z2' returned 256
>
> ** (process:8241): CRITICAL **: external_reset_req: 'rackpdu reset' for host
> z2 failed with rc 256
when called by pacemaker/stonithd:
> Mar 29 18:26:26 z1 stonithd: [1628]: info: client tengine [pid: 1633]
> requests a STONITH operation RESET on node z2
> Mar 29 18:26:26 z1 stonithd: [1628]: info: stonith_operate_locally::2713:
> sending fencing op RESET for z2 to stonith:0 (external/rackpdu) (pid=3110)
...
> Mar 29 18:26:28 z1 external/rackpdu[3112]: [3146]: ERROR: Outlet number not
> found for node z2. Result: iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.1 = STRING: "z1"
> Mar 29 18:26:28 z1 external/rackpdu[3112]: [3146]:
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.2 = STRING: "b"
> Mar 29 18:26:28 z1 external/rackpdu[3112]: [3146]:
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.3 = STRING: "m2"
> Mar 29 18:26:28 z1 external/rackpdu[3112]: [3146]:
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.4 = STRING: "c1"
> Mar 29 18:26:28 z1 external/rackpdu[3112]: [3146]:
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.5 = STRING: "w1"
> Mar 29 18:26:28 z1 external/rackpdu[3112]: [3146]:
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.6 = STRING: "l.i.a"
> Mar 29 18:26:28 z1 external/rackpdu[3112]: [3146]:
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.7 = STRING: "w2"
...
> Mar 29 18:26:28 z1 external/rackpdu[3112]: [3146]:
> iso.3.6.1.4.1.318.1.1.12.3.3.1.1.2.24 = STRING: "abc"
> Mar 29 18:26:29 z1 stonithd: [3110]: info: external_run_cmd: Calling
> '/usr/lib/stonith/plugins/external/rackpdu reset z2' returned 256
> Mar 29 18:26:29 z1 stonithd: [3110]: CRIT: external_reset_req: 'rackpdu
> reset' for host z2 failed with rc 256
> Mar 29 18:26:29 z1 stonithd: [1628]: info: failed to STONITH node z2 with
> local device stonith:0 (exitcode 5), gonna try the next local device
> Mar 29 18:26:29 z1 stonithd: [1628]: info: we can't manage z2, broadcast
> request to other nodes
as you can see, "local: 280: l.i.a: bad variable name" isn't logged to
syslog.
my corosync logging section:
> logging {
> fileline: off
> to_stderr: yes
> to_logfile: no
> to_syslog: yes
> syslog_facility: daemon
> debug: off
> timestamp: on
> logger_subsys {
> subsys: AMF
> debug: off
> tags: enter|leave|trace1|trace2|trace3|trace4|trace6
> }
> }
is this a configuration or a cluster stack error?
thanks,
raoul
[1] http://www.gossamer-threads.com/lists/linuxha/dev/69168#69168
[2]
http://hg.linux-ha.org/glue/diff/400104f3d1d3/lib/plugins/stonith/external/rackpdu
--
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc. email. [email protected]
Technischer Leiter
IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at
Barawitzkagasse 10/2/2/11 email. [email protected]
1190 Wien tel. +43 1 3670030
FN 277995t HG Wien fax. +43 1 3670030 15
____________________________________________________________________
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
