TOPIC:

Please find attached log

The first part of the log is when master goes away, then slave reboots.
The log has both parts in it.
Thank you.

Your slave is self fencing. Once it reboots it enters a suspended HA mode. This mode is forced intentionally since the slave failed to fence the master OR failed to reach your heuristic IP address.

A portion of your log file is missing. If you could run your test again and make sure to grab all the log file lines up until the slave reboots. It will tell us exactly why it is happening.

Before running your test, make sure to remove the HA-suspended state from the slave.

Thank you.
I am attaching everything from the /var/log/messages from the time of the master going down to slave rebooting.
btw: after the slave comes back up ha-cfg status hangs with no response ...

Based on the previous log file that was posted, the slave entered into suspended HA state after it rebooted. The log lines for that are missing in this log file. Can you rerun the test capturing all logs? Only HA-lizard logs are needed (iscsi-ha not required).

Given that you are running your test environment on top of virtualbox, it could be that virtualbox is caching disk writes to the XS VM (/var/log/messages) which are then lost when the host hard reboots.

Try your test again, this time capturing the shell output directly rather than relying on /var/log/messages.

try "ha-cfg log" and watch/capture the output.

Thanks SC.
this is what I got:

Actually this probably has what you need: