[Pacemaker] Cluster Test Suite CTS Pacemaker 1.2 notdoinganything

Andrew Beekhof andrew at beekhof.net
Mon Feb 8 09:41:22 UTC 2010


On Fri, Feb 5, 2010 at 8:17 PM, Koch, Sebastian
<Sebastian.Koch at netzwerk.de> wrote:
> Thanks for your replay Mr. Beekhof
>
> Here ist he stack trace:
> ./CTSlab.py --nodes 'cluster01-node1 cluster01-node2' --benchmark --stack ais --logfile /var/log/messages --schema pacemaker-1.0 3
> Feb 05 20:16:40 Random seed is: 1265397400
> Feb 05 20:16:40 >>>>>>>>>>>>>>>> BEGINNING 3 TESTS
> Feb 05 20:16:40 System log files: /var/log/messages
> Feb 05 20:16:40 Stack:            openais (whitetank)
> Feb 05 20:16:40 Schema:           pacemaker-1.0
> Feb 05 20:16:40 Random Seed:      1265397400
> Feb 05 20:16:40 Enable Stonith:   1
> Feb 05 20:16:40 Enable Fencing:   1
> Feb 05 20:16:40 Enable Standby:   1
> Feb 05 20:16:40 Enable Resources: 0
> ^CTraceback (most recent call last):
>  File "./CTSlab.py", line 683, in <module>
>    cm.ns.WaitForAllNodesToComeUp(Environment["nodes"])
>  File "/root/download/cts/CTS.py", line 322, in WaitForAllNodesToComeUp
>    if not self.WaitForNodeToComeUp(node, timeout):
>  File "/root/download/cts/CTS.py", line 306, in WaitForNodeToComeUp
>    time.sleep(30)
> KeyboardInterrupt

Hmmm... I can only suggest adding some more print lines before and after.
Oh, and definitely remove the part that suppresses all the output
">/dev/null 2>&1", surely ping will print something relevant there for
us to look at.




More information about the Pacemaker mailing list