On Sat, 2009-11-21 at 20:00 +0100, Nikola Ciprich wrote:
> Hi Guys,
> Finally I've found where the problem was! On my testing machines,
> the system was lacking separate /dev/shm tmpfs mount. While the /dev
> directory is also mounted as tmpfs, so it seemingly doesn't make any
> difference, there I
Hi Guys,
Finally I've found where the problem was! On my testing machines,
the system was lacking separate /dev/shm tmpfs mount. While the /dev
directory is also mounted as tmpfs, so it seemingly doesn't make any
difference, there IS one: /dev is mounted with mode=755 parameter,
while /dev/shm shou
On Nov 18, 2009, at 10:32 AM, Nikola Ciprich wrote:
ok, but then how do I set it for corosync?
just adding
aisexec {
user: root
group: root
}
The above is what I have.
if you run:
ps axfu | grep coro
do you get something like this:
root 29024 0.3 0.1 465000 4348
On Wed, Nov 18, 2009 at 9:16 AM, Nikola Ciprich wrote:
> Hi,
> well, I'm a bit confused now :)
> I have identical configuration working on my testing virtual machines, so it
> doesn't seem to be problem there. Furthermore, corosync.conf manpage doesn't
> mention any directives for setting user/g
Hi,
well, I'm a bit confused now :)
I have identical configuration working on my testing virtual machines, so it
doesn't seem to be problem there. Furthermore, corosync.conf manpage doesn't
mention any directives for setting user/group and "aisexec" directive is not
mentioned there either.
I tri
On Wed, Nov 18, 2009 at 8:22 AM, Nikola Ciprich wrote:
> Hi,
> sure, here it is. I also tried setting compatibility to none, but it did't
> help.
> cheers
> n.
I had a feeling that might be the problem.
You skipped a step :-)
Check out example D.3 of
http://clusterlabs.org/doc/en-US/Pacemaker/
Hi,
sure, here it is. I also tried setting compatibility to none, but it did't help.
cheers
n.
On Mon, Nov 16, 2009 at 03:08:23PM +0100, Andrew Beekhof wrote:
> On Tue, Nov 10, 2009 at 10:28 AM, Nikola Ciprich
> wrote:
> > Hello Andrew et al,
> > few days ago, I asked about pacemaker + corosync +
On Tue, Nov 10, 2009 at 10:28 AM, Nikola Ciprich
wrote:
> Hello Andrew et al,
> few days ago, I asked about pacemaker + corosync + clvmd etc. With Your
> advice, I got this working well.
> It was in testing virtual machines, I'm now trying to install similar setup
> on raw hardware but for some
Hi Steve,
I'm running CentOS5 based x86_64 system, 2.6.31.6 kernel, selinux is disabled,
corosync libraries seem to be properly installed, and I've got big enough
/dev/shm
ramdisk. libc should be OK as well.
I just tried rebuilding all packages from scratch and the problem persists :(
regards
nik
> Probably best to enable coredumps and to post the output of gdb.
Hi,
well, but that's exactly what I did... It's all in first post ;-)
regards
nik
>
> Thanks,
>
> Dejan
>
> >
> > Rasto
> >
> > --
> > : Dipl-Ing Rastislav Levrinc
> > : DRBD-MC http://www.drbd.org/mc/management-console/
> >
Nikola,
yet another possibility is your box doesn't have any/enough shared
memory available. Usually this is in the directory /dev/shm.
Unfortunately bad things happen and error handling around this condition
needs some work. Its hard to tell because the signal delivered to the
application on fa
One possibility is selinux is enabled and your selinux policies are out
dated.
Another possibility is you have improper coroipcc libraries (duplicates)
installed on your system.
Check your installed lib dir for coroipcc.so.4 and 4.0.0 and
coroipcc.so. They should all link to the same file.
Anot
Nikola,
Sorry, I don't have a solution, but I'm curious about your setup.
Which version of DLM are you using? Did you have to compile it
yourself?
Regards,
Mark
On Tue, Nov 10, 2009 at 7:28 AM, Nikola Ciprich wrote:
> Hello Andrew et al,
> few days ago, I asked about pacemaker + corosync + clvm
Hi,
On Tue, Nov 10, 2009 at 12:47:50PM +0100, Rasto Levrinc wrote:
>
> On Tue, November 10, 2009 11:54 am, Nikola Ciprich wrote:
> > nope, it really is crashing, it's visible in log: Nov 10 14:13:58 vbox3
> > stonithd: [4384]: info: G_main_add_SignalHandler: Added signal handler
> > for signal 17
On Tue, November 10, 2009 11:54 am, Nikola Ciprich wrote:
> nope, it really is crashing, it's visible in log: Nov 10 14:13:58 vbox3
> stonithd: [4384]: info: G_main_add_SignalHandler: Added signal handler
> for signal 17 Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] ERROR:
> pcmk_wait_dispatch:
nope, it really is crashing, it's visible in log:
Nov 10 14:13:58 vbox3 stonithd: [4384]: info: G_main_add_SignalHandler: Added
signal handler for signal 17
Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] ERROR: pcmk_wait_dispatch:
Child process cib terminated with signal 11 (pid=4385,
+core=fal
On Tue, November 10, 2009 10:28 am, Nikola Ciprich wrote:
> Nov 10 14:13:59 vbox3 cib: [4391]: WARN: retrieveCib: Cluster
> configuration not found: /var/lib/heartbeat/crm/cib.xml Nov 10 14:13:59
> vbox3 cib: [4391]: WARN: readCibXmlFile: Primary configuration corrupt or
> unusable, trying backup
Hello Andrew et al,
few days ago, I asked about pacemaker + corosync + clvmd etc. With Your advice,
I got this working well.
It was in testing virtual machines, I'm now trying to install similar setup on
raw hardware but for some
reasong attrd and cib seem to be crashing.
here's snippet from cor
18 matches
Mail list logo
