[Pacemaker] pacemakerd does not daemonize

[Borislav Borisov]

Mysteriously the problem is gone, so I guess I screwed up the installation
at some point.

On Fri, Sep 14, 2012 at 12:32 PM, Borislav Borisov <
borislav.v.borisov at gmail.com> wrote:

> Hello all, Andrew,
>
>
> I am performing tests against pacemaker from commit
> 7a9bf21cfc993530812ee43bde8c5af2653c1fa6 and for some reason it does not
> want to daemonize:
>
> root at Cluster-Server-1:~/crmsh# pacemakerd -V
> Could not establish pacemakerd connection: Connection refused (111)
>     info: crm_ipc_connect:      Could not establish pacemakerd connection:
> Connection refused (111)
>     info: config_find_next:     Processing additional service options...
>     info: get_config_opt:       Found 'corosync_quorum' for option: name
>     info: config_find_next:     Processing additional service options...
>     info: get_config_opt:       Found 'corosync_cman' for option: name
>     info: config_find_next:     Processing additional service options...
>     info: get_config_opt:       Found 'openais_clm' for option: name
>     info: config_find_next:     Processing additional service options...
>     info: get_config_opt:       Found 'openais_evt' for option: name
>     info: config_find_next:     Processing additional service options...
>     info: get_config_opt:       Found 'openais_ckpt' for option: name
>     info: config_find_next:     Processing additional service options...
>     info: get_config_opt:       Found 'openais_msg' for option: name
>     info: config_find_next:     Processing additional service options...
>     info: get_config_opt:       Found 'openais_lck' for option: name
>     info: config_find_next:     Processing additional service options...
>     info: get_config_opt:       Found 'openais_tmr' for option: name
>     info: config_find_next:     No additional configuration supplied for:
> service
>     info: config_find_next:     Processing additional quorum options...
>     info: get_config_opt:       Found 'quorum_cman' for option: provider
>     info: get_cluster_type:     Detected an active 'cman' cluster
>     info: read_config:  Reading configure for stack: cman
>     info: config_find_next:     Processing additional logging options...
>     info: get_config_opt:       Defaulting to 'off' for option: debug
>     info: get_config_opt:       Found '/var/log/cluster/corosync.log' for
> option: logfile
>     info: get_config_opt:       Found 'yes' for option: to_logfile
>     info: get_config_opt:       Found 'no' for option: to_syslog
>     info: get_config_opt:       Found 'daemon' for option: syslog_facility
>   notice: crm_add_logfile:      Additional logging available in
> /var/log/cluster/corosync.log
>     info: read_config:  User configured file based logging and explicitly
> disabled syslog.
>   notice: main:         Starting Pacemaker 1.1.7 (Build: 7a9bf21):
> ncurses libqb-logging libqb-ipc lha-fencing  corosync-plugin cman
>     info: main:         Maximum core file size is: 18446744073709551615
>     info: qb_ipcs_us_publish:   server name: pacemakerd
>     info: get_local_node_name:  Using CMAN node name: Cluster-Server-1
>   notice: update_node_processes:        0xfe76d0 Node 1 now known as
> Cluster-Server-1, was:
>     info: start_child:  Forked child 33591 for process cib
>     info: start_child:  Forked child 33592 for process stonith-ng
>     info: start_child:  Forked child 33593 for process lrmd
>     info: start_child:  Forked child 33594 for process attrd
>     info: start_child:  Forked child 33595 for process pengine
>     info: start_child:  Forked child 33596 for process crmd
>     info: main:         Starting mainloop
>   notice: update_node_processes:        0xfe8370 Node 2 now known as
> Cluster-Server-2, was:
>
> It continues to work without any problem, just never goes into background.
>
> Cheers,
>
> Borislav
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120914/f5719b6d/attachment.htm>