Re: [ClusterLabs] Strange monitor return code log for LSB resource

2019-07-08 Thread Jan Pokorný
On 05/07/19 03:50 +, Harvey Shepherd wrote: > I was able to resolve an issue which caused these logs to disappear. > The problem was that the LSB script was named "logging" and the > daemon that it controlled was also called "logging". The init script > uses "start-stop-daemon --name" to start

Re: [ClusterLabs] Strange monitor return code log for LSB resource

2019-07-04 Thread Harvey Shepherd
rs@clusterlabs.org Subject: Re: EXTERNAL: Re: [ClusterLabs] Strange monitor return code log for LSB resource Thanks for your reply Andrei. There is no external monitoring software running. The logs that I posted are from the pacemaker log with debug enabled. The Linux hostname of the node is "

Re: [ClusterLabs] Strange monitor return code log for LSB resource

2019-07-04 Thread Jan Pokorný
Harvey, On 25/06/19 21:26 +, Harvey Shepherd wrote: > Thanks for your reply Andrei. There is no external monitoring > software running. The logs that I posted are from the pacemaker log > with debug enabled. that's exactly what's questionable here -- how can crm_resource invocation be at all

[ClusterLabs] Strange monitor return code log for LSB resource

2019-06-25 Thread Harvey Shepherd
Hi All, I have a 2 node cluster running under Pacemaker 2.0.2, with around 20 resources configured, the majority of which are LSB resources, but there are also a few OCF ones. One of the LSB resources is controlled via an init script called "logging" and runs only on the master node. The CIB