Thanks Lars,
In the truth I do not know if my version is with service Pack. In my log
of cluster I found some lines, but very it is not detailed.
Jul 12 22:09:45 dcpr0190 pengine: [3475]: info: log_data_element:
create_fake_resource: Orphan resource </lrm_resource>
Jul 12 22:09:45 dcpr0190 pengine: [3475]: info: process_orphan_resource:
Making sure orphan Proxy is stopped
Jul 12 22:09:45 dcpr0190 pengine: [3475]: info: native_print: Proxy_VIP
(heartbeat::ocf:IPaddr2): Stopped
Jul 12 22:09:45 dcpr0190 pengine: [3475]: info: native_print: Virtual IP
(heartbeat::ocf:IPaddr): Stopped
Jul 12 22:09:45 dcpr0190 pengine: [3475]: info: native_print: Proxy
(heartbeat::ocf:IPaddr2): Stopped
Jul 12 22:09:45 dcpr0190 haclient: on_event: from message queue:
evt:cib_changed
Jul 12 22:09:45 dcpr0190 pengine: [3475]: WARN: native_color: Resource
Proxy_VIP cannot run anywhere
Jul 12 22:09:45 dcpr0190 pengine: [3475]: info: native_color: Stopping
orphan resource Virtual IP
Jul 12 22:09:45 dcpr0190 crmd: [3441]: info: do_state_transition: dcpr0190:
State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS
cause=C_IPC_MESSAGE origin=route_message ]
Jul 12 22:09:45 dcpr0190 pengine: [3475]: info: native_color: Stopping
orphan resource Proxy
Jul 12 22:09:45 dcpr0190 tengine: [3474]: info: unpack_graph: Unpacked
transition 18: 0 actions in 0 synapses
Jul 12 22:09:45 dcpr0190 tengine: [3474]: info: run_graph: Transition 18:
(Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0)
Jul 12 22:09:45 dcpr0190 crmd: [3441]: info: do_state_transition: dcpr0190:
State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS
cause=C_IPC_MESSAGE origin=route_message ]
It would have some suggestion?
___________________________
Claudemir Ferreira Franco
Analista Unix - Curitiba
Cyber DataCenter B2Br - BrT
41-3305-1657
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lars Marowsky-Bree
Sent: sexta-feira, 13 de julho de 2007 10:24
To: General Linux-HA mailing list
Subject: Re: [Linux-HA] /usr/lib/heartbeat/findif segmentation fault
On 2007-07-13T10:07:19, claudemirf <[EMAIL PROTECTED]> wrote:
> I have a new problem...(hehehe). Currently I installed heartbeat2 in my
box
> Suse Linux Enterprise Server 10, I configured a resource Virtual IP
> Address, but when I started my cluster, this resource isn?t running. I
was
> analyzing and and found a problem with the command findif. When I type
in
> the command line /usr/lib/heartbeat/findif, occurred segmentation fault.
> It will be that he is bug?
That is not the problem. findif doesn't segfault if called with the
proper parameters; while the error handling is "suboptimal", that isn't
your issue.
You need to read the logs as to what is wrong with your configuration.
Have you applied the SP1 updates yet?
If you have reason to believe that it is indeed a heartbeat bug, open a
support case with Novell.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
