Graham, Simon wrote:
> Hi,
>
>
>
> I’m running with 2.1.0 right now and have noticed that when I turn up
> the debug level in my ha.cf, I get hangs during shutdown with the
> following as the last thing in the messages file:
>
>
>
> Jul 31 13:47:15 cheech heartbeat: [
> Jul 31 13:47:16 cheech heartbeat:
> Jul 31 13:47:16 cheech logd: [14076]: info: Waiting for pid=7474 to exit
>
>
>
> and this in ha.log:
>
>
>
> Jul 31 13:47:16 cheech logd: [7474]: debug: logd_term_action: received
> SIGTERM
>
> Jul 31 13:47:16 cheech logd: [7474]: debug: logd_term_action: waiting
> for 98 messages to be read for process heartbeat
>
>
>
> followed by a ton more logging (more than 98 lines for sure).
>
>
>
> I also note that the way the shutdown is done, the code will send a
> single SIGTERM and then wait forever for the process to go away – this
> is unlike other init.d scripts which send SIGTERM, then SIGKILL if the
> process is still running after a while and if the process continues to
> run, just continue to run, allowing the rest of the shutdown to make
> progress and the system to eventually shutdown or reboot.
>
> Is there any specific reason why the hb init script does not do this?
Because it's not a graceful shutdown. Things will be left in a bad
state. Any behavior like this is a bug.
Could you try 2.2.2 and see if this behavior persists?
--
Alan Robertson <[EMAIL PROTECTED]>
"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
