Unable to start heartbeat service

[Rahul Khengare]

Hi,

   I have two machine named puppetserver and db01 with CentOS-6.2(64-bit). 

   On db01: I am configuring pacemaker and heartbeat using puppet manifests present on puppetserver. I am also automating the network settings using puppet,

here i am adding the GATEWAY in "/etc/sysconfig/network" file using puppet manifests.

After deploying the respective manifests pacemaker and heartbeat working fine. 

But, after rebooting the machine, heartbeat service is unable to start (on db01).

Discription of error log:

-------------------------------- 

May 08 11:52:27 db01 heartbeat: [3423]: info: respawn directive: root /usr/lib64/heartbeat/ifcheckd

May 08 11:52:27 db01 heartbeat: [3423]: info: AUTH: i=1: key = 0x15b89b0, auth=0x7f5c36e15db0, authname=sha1

May 08 11:52:27 db01 heartbeat: [3423]: ERROR: Current node [db01] not in configuration!

May 08 11:52:27 db01 heartbeat: [3423]: info: By default, cluster nodes are named by `uname -n` and must be declared with a 'node' directive in the ha.cf file.

May 08 11:52:27 db01 heartbeat: [3423]: info: See also: http://linux-ha.org/wiki/Ha.cf#node_directive

May 08 11:52:27 db01 heartbeat: [3423]: WARN: Logging daemon is disabled --enabling logging daemon is recommended

May 08 11:52:27 db01 heartbeat: [3423]: ERROR: Configuration error, heartbeat not started.

If i add the GATEWAY parameter in the "/etc/sysconfig/network" file manually  then it works fine even after rebooting.

Queries:

----------

1. If i change the '/etc/sysconfig/network' file using puppet manifests the heartbeat service not start.

   Is there any problem if i change "/etc/sysconfig/network" file using puppet manifests.

2. Somebody faced similar or any other problem on editing or transferring '/etc/sysconfig/network' file using puppet manifests.

Any pointers or help!!!

Thanks and Regards,

Rahul Khengare

[Rahul Khengare]

HI,
There is no issue of puppet on editing /etc/sysconfig/network file.

Cause of problem :
Here, I edit template of "/etc/sysconfig/network" file in windows
machine so the line-feed character is of windows, on transferring that
template file on linux environment cause problem with network
configuration file because of mismatch of line-feed character.

Note : Avoid writing of template files for linux configuration on
windows machine and then copying on linux machine.

On 5/8/13, Rahul Khengare <rahul...@gmail.com> wrote:
> Hi,
> I have two machine named puppetserver and db01 with CentOS-6.2(64-bit).
>
> On db01: I am configuring pacemaker and heartbeat using puppet manifests
>
> present on puppetserver. I am also automating the network settings using
> puppet,

> here i am adding the GATEWAY in "*/etc/sysconfig/network*" file using

> puppet manifests.
>
> After deploying the respective manifests pacemaker and heartbeat working
> fine.

> *But, after rebooting the machine, heartbeat service is unable to start (on
>
> db01).*
>
> *Discription of error log:*

> --------------------------------
> May 08 11:52:27 db01 heartbeat: [3423]: info: respawn directive: root
> /usr/lib64/heartbeat/ifcheckd
> May 08 11:52:27 db01 heartbeat: [3423]: info: AUTH: i=1: key = 0x15b89b0,
> auth=0x7f5c36e15db0, authname=sha1
> May 08 11:52:27 db01 heartbeat: [3423]: ERROR: Current node [db01] not in
> configuration!
> May 08 11:52:27 db01 heartbeat: [3423]: info: By default, cluster nodes are
>
> named by `uname -n` and must be declared with a 'node' directive in the
> ha.cf file.
> May 08 11:52:27 db01 heartbeat: [3423]: info: See also:
> http://linux-ha.org/wiki/Ha.cf#node_directive
> May 08 11:52:27 db01 heartbeat: [3423]: WARN: Logging daemon is disabled
> --enabling logging daemon is recommended
> May 08 11:52:27 db01 heartbeat: [3423]: ERROR: Configuration error,
> heartbeat not started.
>

> If i add the GATEWAY parameter in the "/etc/sysconfig/network" file *
> manually* then it works fine even after rebooting.
>
> *Queries:*
> *----------*

> 1. If i change the '/etc/sysconfig/network' file using puppet manifests the
>
> heartbeat service not start.

> Is there any problem if i change "*/etc/sysconfig/network*" file using

> puppet manifests.
>
> 2. Somebody faced similar or any other problem on editing or transferring

> '*
> /etc/sysconfig/network*' file using puppet manifests.

>
> Any pointers or help!!!
>
> Thanks and Regards,
> Rahul Khengare
>

> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/AEp7IuPthLQ/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users...@googlegroups.com.
> To post to this group, send email to puppet...@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>