2015-01-27 17:58 GMT+01:00 Dejan Muhamedagic :
> On Tue, Jan 27, 2015 at 03:18:13PM +0100, Oscar Salvador wrote:
> > Hi,
> >
> > I've checked the resource graphs I have, and the resources were fine, so
> I
> > think it's not a problem due to a high use of memory or something like
> that.
> > And
On Tue, Jan 27, 2015 at 03:18:13PM +0100, Oscar Salvador wrote:
> Hi,
>
> I've checked the resource graphs I have, and the resources were fine, so I
> think it's not a problem due to a high use of memory or something like that.
> And unfortunately I don't have a core dump to analize(I'll enable i
Hi,
I've checked the resource graphs I have, and the resources were fine, so I
think it's not a problem due to a high use of memory or something like that.
And unfortunately I don't have a core dump to analize(I'll enable it for a
future case) so the only thing I have are the logs.
For the line
Hi,
On Mon, Jan 26, 2015 at 06:20:35PM +0100, Oscar Salvador wrote:
> Hi!
>
> I'm writing here because two days ago I experienced a strange problem in my
> Pacemaker Cluster.
> Everything was working fine, till suddenly a Segfault in Nginx monitor
> resource happened:
>
> Jan 25 03:55:24 lb02 cr
maybe you can use sar for checking if your server was tight of resources?
Jan 25 04:10:30 lb02 lrmd: [9972]: info: RA output:
(Nginx-rsc:monitor:stderr) Killed
/usr/lib/ocf/resource.d//heartbeat/nginx: 910:
/usr/lib/ocf/resource.d//heartbeat/nginx: Cannot fork
2015-01-26 18:22 GMT+01:00 Oscar Sa
Oh, I forgot some important details:
root# (S) crm status
Last updated: Mon Jan 26 18:21:35 2015
Last change: Sun Jan 25 05:19:13 2015 via crm_resource on lb01
Stack: Heartbeat
Current DC: lb01 (43b2c5a1-9552-4438-962b-6e98a2dd67c7) - partition with
quorum
Version: 1.1.7-ee0730e13d124
