Hi all!
When create any resource, i have:
Dec 24 12:28:44 cluster1-node1 lrmd: [25907]: info: RA output:
(Public-IP:monitor:stderr) .: 44: 3: Too many open files
Dec 24 12:28:44 cluster1-node1 lrmd: [25907]: WARN: Managed Public-IP:monitor
process 30099 exited with return code 2.
Dec 24 12:28:
On Wed, Dec 23, 2009 at 8:34 AM, Dejan Muhamedagic wrote:
>
> > > > 3. Why the pingd attribute was not set immediately after pingd
> started
> > > > up, and was able to ping the ping node. After the pingd was started,
> then
> > > > it waited 60 seconds (the timeout value) to set the attribute so
Hi Guys,
I had a perfectly running system for about 3 weeks now but now on reboot I
see problems.
Looks like the processes are being spawned and respawned but a proper exec
is not happening.
Am I missing some permissions on directories.
I have a script which does the following for directories:
On Wed, Dec 16, 2009 at 12:52 PM, Frank DiMeo wrote:
> Hi All,
>
> Does anyone know the correct syntax for the crm_master command when used
> from a shell? I want to promote (and at some point demote) one of my
> multistate resources running on one of my nodes, but haven't found the
> correct syn
On Thu, Dec 17, 2009 at 8:23 AM, Frank DiMeo wrote:
> Hi,
>
>
>
> I need a way to inform the cluster of failures between monitor polls of my
> multistate resources, and I notice that I cannot use “crm_resource “ to
> inform the cluster of the failure of a master (multistate) resource, as it
> see
Hi,
On Wed, Dec 23, 2009 at 05:50:57PM +0100, Bernd Schubert wrote:
> On Wednesday 23 December 2009, Dejan Muhamedagic wrote:
> > Hi,
> >
> > On Tue, Dec 22, 2009 at 06:52:34PM +0100, Michael Schwartzkopff wrote:
> > > Hi,
> > >
> > > The Lustre Filesystem uses a feature called Multiple Mount Pro
