Mysteriously the problem is gone, so I guess I screwed up the installation at some point.<br><br><div class="gmail_quote">On Fri, Sep 14, 2012 at 12:32 PM, Borislav Borisov <span dir="ltr"><<a href="mailto:borislav.v.borisov@gmail.com" target="_blank">borislav.v.borisov@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all, Andrew,<br><br><br>I am performing tests against pacemaker from commit 7a9bf21cfc993530812ee43bde8c5af2653c1fa6 and for some reason it does not want to daemonize:<br>
<br>root@Cluster-Server-1:~/crmsh# pacemakerd -V<br>
Could not establish pacemakerd connection: Connection refused (111)<br> info: crm_ipc_connect: Could not establish pacemakerd connection: Connection refused (111)<br> info: config_find_next: Processing additional service options...<br>
info: get_config_opt: Found 'corosync_quorum' for option: name<br> info: config_find_next: Processing additional service options...<br> info: get_config_opt: Found 'corosync_cman' for option: name<br>
info: config_find_next: Processing additional service options...<br> info: get_config_opt: Found 'openais_clm' for option: name<br> info: config_find_next: Processing additional service options...<br>
info: get_config_opt: Found 'openais_evt' for option: name<br> info: config_find_next: Processing additional service options...<br> info: get_config_opt: Found 'openais_ckpt' for option: name<br>
info: config_find_next: Processing additional service options...<br> info: get_config_opt: Found 'openais_msg' for option: name<br> info: config_find_next: Processing additional service options...<br>
info: get_config_opt: Found 'openais_lck' for option: name<br> info: config_find_next: Processing additional service options...<br> info: get_config_opt: Found 'openais_tmr' for option: name<br>
info: config_find_next: No additional configuration supplied for: service<br> info: config_find_next: Processing additional quorum options...<br> info: get_config_opt: Found 'quorum_cman' for option: provider<br>
info: get_cluster_type: Detected an active 'cman' cluster<br> info: read_config: Reading configure for stack: cman<br> info: config_find_next: Processing additional logging options...<br> info: get_config_opt: Defaulting to 'off' for option: debug<br>
info: get_config_opt: Found '/var/log/cluster/corosync.log' for option: logfile<br> info: get_config_opt: Found 'yes' for option: to_logfile<br> info: get_config_opt: Found 'no' for option: to_syslog<br>
info: get_config_opt: Found 'daemon' for option: syslog_facility<br> notice: crm_add_logfile: Additional logging available in /var/log/cluster/corosync.log<br> info: read_config: User configured file based logging and explicitly disabled syslog.<br>
notice: main: Starting Pacemaker 1.1.7 (Build: 7a9bf21): ncurses libqb-logging libqb-ipc lha-fencing corosync-plugin cman<br> info: main: Maximum core file size is: 18446744073709551615<br> info: qb_ipcs_us_publish: server name: pacemakerd<br>
info: get_local_node_name: Using CMAN node name: Cluster-Server-1<br> notice: update_node_processes: 0xfe76d0 Node 1 now known as Cluster-Server-1, was: <br> info: start_child: Forked child 33591 for process cib<br>
info: start_child: Forked child 33592 for process stonith-ng<br> info: start_child: Forked child 33593 for process lrmd<br> info: start_child: Forked child 33594 for process attrd<br> info: start_child: Forked child 33595 for process pengine<br>
info: start_child: Forked child 33596 for process crmd<br> info: main: Starting mainloop<br> notice: update_node_processes: 0xfe8370 Node 2 now known as Cluster-Server-2, was: <br><br>It continues to work without any problem, just never goes into background.<br>
<br>Cheers,<br><br>Borislav<br>
</blockquote></div><br>