Hi,
I know, no fencing configuration creates issue.
But the current scenario is due to fencing??
The syslog isn't revealing much about the same.
I would love to configure fencing but currently need some solution to
overcome the current scenario, if you say fencing is the only solution then
I migh
On 28/10/14 01:39 AM, kamal kishi wrote:
Hi all,
Facing a strange issue which I'm not able to resolve as I'm not
sure where what is going wrong as the logs is not giving away much to my
knowledge.
Issue -
Have configured 2 Node Clustering, have attached the configuration
file(New CRM con
> On 28 Oct 2014, at 3:36 pm, Neale Ferguson wrote:
>
> Thanks. I'll give it a try later this morning.
>
> BTW, do you know of a sample glusterfs configuration using
> ocf:glusterfs:{glusterfs, volume}?
Not personally, no
> I'm attempting to take a small systemd-based setup and place it und
Thanks. I'll give it a try later this morning.
BTW, do you know of a sample glusterfs configuration using
ocf:glusterfs:{glusterfs, volume}? I'm attempting to take a small systemd-based
setup and place it under control of Pacemaker and would like an example that I
could use as a template.
---
> On 24 Oct 2014, at 9:00 pm, Sékine Coulibaly wrote:
>
> Hi Andrew,
>
> Yep, forgot the attachments. I did reproduce the issue, please find
> the bz2 files attached. Please tell if you need hb_report being used.
Yep, I need the log files to put these into context
>
> Thank you !
>
>
> 201
Ok, I reproduced it and updated bugzilla.
Work-around:
rm -f /etc/httpd/conf.modules.d/00-systemd.conf
> On 28 Oct 2014, at 3:04 pm, Neale Ferguson wrote:
>
> I'm not near a terminal at the moment, but I believe you are correct.
>
>
> Original message
>
> It's also pos
I'm not near a terminal at the moment, but I believe you are correct.
Original message
It's also possible that httpd is defined as OCF resource instead of
systemd ...
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://o
> On 28 Oct 2014, at 2:47 pm, Andrei Borzenkov wrote:
>
> В Tue, 28 Oct 2014 14:31:17 +1100
> Andrew Beekhof пишет:
>
>>
>>> On 28 Oct 2014, at 7:36 am, Neale Ferguson wrote:
>>>
>>> I am getting loads of these types of messages in syslog:
>>>
>>> Oct 27 16:23:47 rh7cn1 systemd: pacemaker.
В Tue, 28 Oct 2014 14:31:17 +1100
Andrew Beekhof пишет:
>
> > On 28 Oct 2014, at 7:36 am, Neale Ferguson wrote:
> >
> > I am getting loads of these types of messages in syslog:
> >
> > Oct 27 16:23:47 rh7cn1 systemd: pacemaker.service: Got notification
> > message from PID 43007, but receptio
systemd-208-11.el7_0.2
RHEL 7 Kernel - 3.10.0-123.8.1
On 10/27/14, 11:39 PM, "Andrew Beekhof" wrote:
>
>Followup... what OS and systemd version do you have?
>I just tried with systemd-208-11.el7 and it seems to be working.
___
Pacemaker mailing list
> On 27 Oct 2014, at 6:05 pm, Sihan Goi wrote:
>
> Hi,
>
> That offending line is as follows:
> DocumentRoot "/var/www/html"
>
> I'm guessing it needs to be updated to the DRBD block device, but I'm not
> sure how to do that, or even what the block device is.
>
> fdisk -l shows the following
Thanks Andrew.
On 10/27/14, 11:31 PM, "Andrew Beekhof" wrote:
>
>So rephrasing:
>
> Got notification message from httpd, but reception only permitted for
>pacemakerd
>
>So it seems that systemd is calculating the wrong value for main_pid
___
Pacema
> On 28 Oct 2014, at 2:31 pm, Andrew Beekhof wrote:
>
>
>> On 28 Oct 2014, at 7:36 am, Neale Ferguson wrote:
>>
>> I am getting loads of these types of messages in syslog:
>>
>> Oct 27 16:23:47 rh7cn1 systemd: pacemaker.service: Got notification
>> message from PID 43007, but reception only
> On 28 Oct 2014, at 7:36 am, Neale Ferguson wrote:
>
> I am getting loads of these types of messages in syslog:
>
> Oct 27 16:23:47 rh7cn1 systemd: pacemaker.service: Got notification
> message from PID 43007, but reception only permitted for PID 17131
>
>
> PID 43007 refers to the https res
> On 27 Oct 2014, at 10:30 pm, Andrei Borzenkov wrote:
>
> On Mon, Oct 27, 2014 at 12:40 PM, Andrew Beekhof wrote:
>>
>>> On 27 Oct 2014, at 7:36 pm, Andrei Borzenkov wrote:
>>>
>>> On Wed, Oct 22, 2014 at 8:59 AM, Andrew Beekhof wrote:
> On 22 Oct 2014, at 4:34 pm, Andrei Borzenk
I am getting loads of these types of messages in syslog:
Oct 27 16:23:47 rh7cn1 systemd: pacemaker.service: Got notification
message from PID 43007, but reception only permitted for PID 17131
PID 43007 refers to the https resource and 17131 to pacemakerd.
A search on this type of message shows
27.10.2014 17:19, Ken Gaillot пишет:
On 10/25/2014 03:32 PM, Andrew wrote:
2) How to resolve split brain state? Is it enough just to wait for
failure, then - restart mysql by hand and clean row with dup index in
slave db, and then run resource again? Or there is some automation for
such cases?
On 10/25/2014 03:32 PM, Andrew wrote:
2) How to resolve split brain state? Is it enough just to wait for
failure, then - restart mysql by hand and clean row with dup index in
slave db, and then run resource again? Or there is some automation for
such cases?
Regarding mysql cleanup, it is usuall
On Mon, Oct 27, 2014 at 12:40 PM, Andrew Beekhof wrote:
>
>> On 27 Oct 2014, at 7:36 pm, Andrei Borzenkov wrote:
>>
>> On Wed, Oct 22, 2014 at 8:59 AM, Andrew Beekhof wrote:
>>>
On 22 Oct 2014, at 4:34 pm, Andrei Borzenkov wrote:
On Wed, Oct 22, 2014 at 8:01 AM, Andrew Beekhof w
> On 27 Oct 2014, at 6:42 pm, Andrew wrote:
>
> Nobody calls pacemakerd by hand/in script - maybe this is resource monitoring?
Oh I remember now, pgsql does it for some reason.
There was a thread on it a while back, I forget the reason but there is
probably a work-around
> Logging increased a
> On 27 Oct 2014, at 7:36 pm, Andrei Borzenkov wrote:
>
> On Wed, Oct 22, 2014 at 8:59 AM, Andrew Beekhof wrote:
>>
>>> On 22 Oct 2014, at 4:34 pm, Andrei Borzenkov wrote:
>>>
>>> On Wed, Oct 22, 2014 at 8:01 AM, Andrew Beekhof wrote:
> On 21 Oct 2014, at 11:15 pm, Andrei Borzenko
> On 27 Oct 2014, at 5:40 pm, Andrei Borzenkov wrote:
>
> On Mon, Oct 27, 2014 at 6:34 AM, Andrew Beekhof wrote:
>>
>>> On 27 Oct 2014, at 2:30 pm, Andrei Borzenkov wrote:
>>>
>>> В Mon, 27 Oct 2014 11:09:08 +1100
>>> Andrew Beekhof пишет:
>>>
> On 25 Oct 2014, at 12:38 am, Andre
On Wed, Oct 22, 2014 at 8:59 AM, Andrew Beekhof wrote:
>
>> On 22 Oct 2014, at 4:34 pm, Andrei Borzenkov wrote:
>>
>> On Wed, Oct 22, 2014 at 8:01 AM, Andrew Beekhof wrote:
>>>
On 21 Oct 2014, at 11:15 pm, Andrei Borzenkov wrote:
Pacemaker 1.1.11. I see in engine logs that it is
Nobody calls pacemakerd by hand/in script - maybe this is resource
monitoring?
Logging increased after update (and pacemakerd log ilines appeared);
nothing else was changed in config.
I'll try to reboot nodes (to finish system update) - maybe this'll
change something...
27.10.2014 02:08, And
Hi,
That offending line is as follows:
DocumentRoot "/var/www/html"
I'm guessing it needs to be updated to the DRBD block device, but I'm not
sure how to do that, or even what the block device is.
fdisk -l shows the following, which I'm guessing is the block device?
/dev/mapper/vg_node02-drbd--d
25 matches
Mail list logo
