You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Malcolm Crossley (JIRA)" <ji...@apache.org> on 2014/10/15 15:48:34 UTC

[jira] [Commented] (CLOUDSTACK-7527) XenServer heartbeat-script: make it reboot faster (when fencing)

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172370#comment-14172370 ] 

Malcolm Crossley commented on CLOUDSTACK-7527:
----------------------------------------------

Can you at least sync the disks before echoing "b" to /proc/sysrq-trigger

You can do this with a echo s > /proc/sysrq-trigger

Also if you want to capture some state of the host you could trigger a crash instead which will run the Xenserver crashdump analyser.  This will result in kernel dmesg ring and Xen dmesg ring being preserved. 

To trigger a crash: echo c > proc/sysrq-trigger

I would not trigger a crashdump by default because it won't be clear that Cloudstack initiated the crash.

> XenServer heartbeat-script: make it reboot faster (when fencing)
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7527
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7527
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.3.0, 4.4.0
>            Reporter: Remi Bergsma
>            Assignee: Daan Hoogland
>            Priority: Minor
>
> xenheartbeat.sh:
> I've seen the 'reboot' command hang, even though it has the force option specified (last line of the script). Wouldn't it be better to invoke it like this:
> echo b > /proc/sysrq-trigger
> Tested it, starts boot sequence immediately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)