Hi,
On Wed, May 26, 2010 at 02:37:51PM +0200, Thomas Bätzler wrote:
> Hi,
>
> Am 26.05.2010 13:10, schrieb Dejan Muhamedagic:
> >
> >On Wed, May 26, 2010 at 10:32:23AM +0200, Thomas Bätzler wrote:
> >>Hi,
> >>
> >>Am 25.05.2010 16:05, schrieb Dejan Muhamedagic:
> >>
> >>>On Fri, May 21, 2010 at 0
Hi,
Am 26.05.2010 13:10, schrieb Dejan Muhamedagic:
>
On Wed, May 26, 2010 at 10:32:23AM +0200, Thomas Bätzler wrote:
Hi,
Am 25.05.2010 16:05, schrieb Dejan Muhamedagic:
On Fri, May 21, 2010 at 03:38:53PM +0200, Thomas Bätzler wrote:
[exporting nfs share for *]
This causes an incorrect "Ex
Hi,
On Wed, May 26, 2010 at 10:32:23AM +0200, Thomas Bätzler wrote:
> Hi,
>
> Am 25.05.2010 16:05, schrieb Dejan Muhamedagic:
>
> >On Fri, May 21, 2010 at 03:38:53PM +0200, Thomas Bätzler wrote:
> [exporting nfs share for *]
> >>This causes an incorrect "Export not reported by showmount -e" in
>
Hi,
Am 25.05.2010 16:05, schrieb Dejan Muhamedagic:
On Fri, May 21, 2010 at 03:38:53PM +0200, Thomas Bätzler wrote:
[exporting nfs share for *]
This causes an incorrect "Export not reported by showmount -e" in
exportfs_start().
I fixed this for myself by shortening
grep -E "^${OCF_RESKEY
Hi,
On Fri, May 21, 2010 at 03:38:53PM +0200, Thomas Bätzler wrote:
> Hello,
>
> Am 19.04.2010 17:28, schrieb Florian Haas:
> >After last week's resource-agents 1.0.3 release, I have merged the
> >exportfs resource agent, which has lived in its separate branch so far,
> >into the default branch.
Hello,
Am 19.04.2010 17:28, schrieb Florian Haas:
After last week's resource-agents 1.0.3 release, I have merged the
exportfs resource agent, which has lived in its separate branch so far,
into the default branch.
Thank you all for your work on this, it seems to be exactly what I have
been lo
Hi,
On Fri, Apr 23, 2010 at 03:05:31PM -0700, Sid Stuart wrote:
> This is a tricky problem. I think I have tracked it down, but am still
> working to confirm as I don't understand the steps pacemaker goes through to
> start a group.
>
> My understanding of how this works from the logs is,
>
> Pa
This is a tricky problem. I think I have tracked it down, but am still
working to confirm as I don't understand the steps pacemaker goes through to
start a group.
My understanding of how this works from the logs is,
Pacemaker calls "exportfs monitor" as part of an initialization process. It
does
Hi Florian,
I found the problem. The issue is with the RA-exportfs
*directory*parameter. If "/data" is configured as the directory it
works. If
"/data/shared" is configured, it fails. Since the Linux exportfs command
will accept "/data/shared" as a valid argument, this is either a bug in the
docu
Hi,
On Wed, Apr 21, 2010 at 01:31:44PM -0700, Sid Stuart wrote:
> The list server blocks mail with zipped attachments. I have sent the tar
> file directly to Florian. If someone else would like a copy of the
> hb_report, please let me know.
>
> The error that the other server returned was: 554 5
The ha-log.txt of that tarball contains a single instance of ERROR:
Apr 21 13:06:51 kong102.kongregate.com crmd: [11406]: ERROR:
verify_stopped: Resource shared_export was active at shutdown. You may
ignore this error if it is unmanaged.
That's a follow-up issue where Pacemaker has already decid
The list server blocks mail with zipped attachments. I have sent the tar
file directly to Florian. If someone else would like a copy of the
hb_report, please let me know.
The error that the other server returned was: 554 554 5.7.0 Reject, id=09291
- BANNED: multipart/mixed | application/x-bzip2,.
Hi,
thanks for testing! Can we get a full hb_report tarball please? That way
we'll have all the information we might possibly need.
Cheers,
Florian
signature.asc
Description: OpenPGP digital signature
___
Linux-HA-Dev: Linux-HA-Dev@lists.linu
Hi,
I am trying to configure two systems to use the exportfs resource agent, but
am running into a problem with the agent failing to start. The systems run
Centos 5.4 with Heartbeat 3.0.3-1.el5, Pacemaker 1.0.8-5.el5 and the
exportfs RA from the repository listed below. The CIB is provided at the
Hello,
After last week's resource-agents 1.0.3 release, I have merged the
exportfs resource agent, which has lived in its separate branch so far,
into the default branch.
exportfs was thankfully submitted by Ben Timby, and manages NFS exports
on a per-directory basis, without ever killing nfsd. T
15 matches
Mail list logo