Re: [Pacemaker] [libqb]Unlink of files bound to sockets

Thanks for the explanations. I will change the pull request as supposed. -Ursprüngliche Nachricht- Von: David Vossel [mailto:dvos...@redhat.com] Gesendet: Montag, 22. Dezember 2014 22:25 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] [libqb]Unlink of files bound to

Re: [Pacemaker] [libqb]Unlink of files bound to sockets

E.g. this 5 files are created for the sockets. srwxr-x--x 1 hacluster haclient 0 Dec 19 20:27 qb-cib_ro--13852-26-event srwxr-x--x 1 hacluster haclient 0 Dec 19 20:27 qb-cib_ro--13852-26-response -rw-rw 1 hacluster haclient 24 Dec 19 20:27

[Pacemaker] [libqb]Unlink of files bound to sockets

I sent yesterday this email to the mailing list of libq 'quarterback-de...@lists.fedorahosted.org'. But there is nearly no activity since august. I use the current trunk of libqb. In qb_ipcc_us_sock_close nd qb_ipcs_us_withdraw of lib/ipc_setup.c sockets are closed. Is there a reason why the

Re: [Pacemaker] Hawk and runtime environment

, Andreas (LGL Extern) Gesendet: Sonntag, 16. November 2014 21:27 An: 'The Pacemaker cluster resource manager' Betreff: Hawk and runtime environment I managed to get Hawk running on Solaris. I use as prefix /opt and not /usr. The last problem seems to be the runtime environment of the ruby application

[Pacemaker] Hawk and runtime environment

I managed to get Hawk running on Solaris. I use as prefix /opt and not /usr. The last problem seems to be the runtime environment of the ruby application. For testing purposes I started lighthhtpd in a shell in the foreground. In this shell crm works without any problem. If in hawk a function is

Re: [Pacemaker] Notes on pacemaker installation on OmniOS

I added heartbeat and corosync to have both available. Personally I use pacemaker/corosync. There is no need any more to run pacemaker as non-root with the newest version of pacemaker. The main problems with pacemaker are the changes in the last months especially in services_linux.c. As the

Re: [Pacemaker] Notes on pacemaker installation on OmniOS

: [Pacemaker] Notes on pacemaker installation on OmniOS On 13 Nov 2014, at 9:50 pm, Grüninger, Andreas (LGL Extern) andreas.gruenin...@lgl.bwl.de wrote: I added heartbeat and corosync to have both available. Personally I use pacemaker/corosync. There is no need any more to run pacemaker as non-root

Re: [Pacemaker] IPaddr resource agent on Illumos

Hi Vincenzo Add hacluster to the sudoers file with # visudo And add haclusterALL=(ALL) NOPASSWD: ALL at the very end. And of course use # sudo ifconfig… Regards Andreas Von: Vincenzo Pii [mailto:p...@zhaw.ch] Gesendet: Donnerstag, 23. Oktober 2014 17:51 An:

[Pacemaker] WG: Patches for Solaris/Illumos

During the last days I compiled the current trunk of pacemaker with gcc 4.4 in OpenIndiana. I checked the binaries with the current trunk of corosync and libqb. The change is compatible with Solaris and Illumos based OS like OpenIndiana, SmartOS, Nexenta, OmniOS. A pull request is waiting in

[Pacemaker] Compile error with OpenIndiana

Hi all I compiled the newest version of the complete Corosync/Pacemaker suite with OpenIndiana 151a7. Tests with libq run without error. All went well except a little problem with Pacemaker. I prepared two patches. They are waiting in this pull request

Re: [Pacemaker] solaris problem

With solaris/openindiana you should use this setting export PCMK_ipc_type=socket Andreas -Ursprüngliche Nachricht- Von: Andrei Belov [mailto:defana...@gmail.com] Gesendet: Montag, 25. März 2013 10:43 An: pacemaker@oss.clusterlabs.org Betreff: [Pacemaker] solaris problem Hi folks,

Re: [Pacemaker] Announce: pcs-0.9.26

Please see here: https://github.com/feist/pcs/issues Andreas -Ursprüngliche Nachricht- Von: Chris Feist [mailto:cfe...@redhat.com] Gesendet: Mittwoch, 17. Oktober 2012 02:03 An: The Pacemaker cluster resource manager Cc: linux clustering Betreff: Re: [Pacemaker] Announce: pcs-0.9.26

Re: [Pacemaker] Announce: pcs-0.9.26

Great. Of course I will test it. We are especially interested in the gui. Thanks Andreas -Ursprüngliche Nachricht- Von: Chris Feist [mailto:cfe...@redhat.com] Gesendet: Mittwoch, 17. Oktober 2012 21:22 An: The Pacemaker cluster resource manager Cc: Grüninger, Andreas (LGL Extern

Re: [Pacemaker] Announce: pcs-0.9.26

I checked the source code and found that the current version uses a mixture of fixed pathes for the binaries and calls without paths. E.g. cibadmin or /usr/sbin/crm_mon. Do you have plans to support installations where the software is installed in /opt/ha? This is the case when the option

[Pacemaker] [PATCH] Couldn't find src in NULL - missing null check

I found this in the logfile: Sep 29 19:14:29 [770]cib: notice: log_cib_diff: cib:diff: Diff: --- 0.11.3 Sep 29 19:14:29 [770]cib: notice: log_cib_diff: cib:diff: Diff: +++ 0.12.1 Sep 29 19:14:29 [776] crmd: notice: do_state_transition:State

Re: [Pacemaker] Exiting corosync-notifyd results in shutting downof pacemakerd

2012 01:09 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] Exiting corosync-notifyd results in shutting downof pacemakerd On Wed, Oct 3, 2012 at 2:51 AM, Grüninger, Andreas (LGL Extern) andreas.gruenin...@lgl.bwl.de wrote: I am currently investigating the monitoring

Re: [Pacemaker] Every line produced with ocf_log is written twice

(LGL Extern) andreas.gruenin...@lgl.bwl.de wrote: Pacemaker 1.1.8 (Build: bdd3f2e): ncurses libqb-logging libqb-ipc lha-fencing upstart systemd heartbeat corosync-native snmp libesmtp resource-agents 3.9.3.113-a796f3-dirty I use in a resource script the logging facility with ocf_log

[Pacemaker] Exiting corosync-notifyd results in shutting down of pacemakerd

I am currently investigating the monitoring of corosync/pacemaker with snmp. crm_mon used with the OCF resource ClusterMon works as it should. But corosync-notifyd can't be used in our case. I start corosync-notifyd in the foreground as follows corosync-notifyd -f -l -s -m 10.50.235.1 When I

Re: [Pacemaker] Logging in syslog daemon can't be stopped

: On Mon, Sep 24, 2012 at 4:08 PM, Andrew Beekhof and...@beekhof.net wrote: On Tue, Sep 25, 2012 at 6:00 AM, Grüninger, Andreas (LGL Extern) andreas.gruenin...@lgl.bwl.de wrote: When I use the corosync.conf attached below with logging to syslog disabled and loggong to file enabled all

[Pacemaker] Every line produced with ocf_log is written twice

Pacemaker 1.1.8 (Build: bdd3f2e): ncurses libqb-logging libqb-ipc lha-fencing upstart systemd heartbeat corosync-native snmp libesmtp resource-agents 3.9.3.113-a796f3-dirty I use in a resource script the logging facility with ocf_log. Every line produced with ocf_log is written twice. I

[Pacemaker] [PATCH] feature test for sighandler_t added and for ncurses improved

When pacemaker 1.1.8 is compiled with gcc 4.5.2 and ncurses 5.7 2 problems occur: - ncurses is errounesly detected as version 5.4 - sighandler_t is not defined in libglib-2.0 The feature test for ncurses uses another order for checking as the tests in lib/pengine/unpack.h. The test für ncurses

[Pacemaker] Logging in syslog daemon can't be stopped

When I use the corosync.conf attached below with logging to syslog disabled and loggong to file enabled all messages from corosync goes to the file. Pacemaker send the logging to both destinations and uses different formats. The messages sent to syslog are other messages than sent to the file.

Re: [Pacemaker] stdout reserved word

, 2012 at 3:20 AM, Grüninger, Andreas (LGL Extern) andreas.gruenin...@lgl.bwl.de wrote: Hello I compiled Pacemaker 1.1.7 with gcc 4.5 in Solaris 11 and with gcc 4.6 in OpenIndiana 151a6. I had to change the following: perl -pi -e 's#stdout#stdoutx#' include/crm/stonith-ng-internal.h perl

Re: [Pacemaker] stdout reserved word

reserved word Hmm, I ran the same commands with 4.7 and it works fine here. Is 4.7 available for solaris? It would be useful to know if it was a version issue or an platform one. On Fri, Aug 24, 2012 at 10:16 AM, Grüninger, Andreas (LGL Extern) andreas.gruenin...@lgl.bwl.de wrote: Making all

[Pacemaker] stdout reserved word

Hello I compiled Pacemaker 1.1.7 with gcc 4.5 in Solaris 11 and with gcc 4.6 in OpenIndiana 151a6. I had to change the following: perl -pi -e 's#stdout#stdoutx#' include/crm/stonith-ng-internal.h perl -pi -e 's#stdout#stdoutx#' lib/fencing/st_client.c perl -pi -e 's#stdout#stdoutx#'