On 07/15/2011 04:01 PM, Sebastian Kaps wrote:
> Hi!
>
> I'm looking for a way to run a certain subset of cronjobs only on the
> active node of our cluster. It seems, the best way to achieve this would
> be to use different crontab files and to switch them depending on the
> node's state (i.e. acti
Hi!
I'm looking for a way to run a certain subset of cronjobs only on the
active node of our cluster. It seems, the best way to achieve this
would
be to use different crontab files and to switch them depending on the
node's state (i.e. active/standby).
I've found an announcement for a "cronjob
Hello all.
I found what I using corosync with pacemaker "ver:0" with installed
pacemaker 1.1.5 - eg without start a pacemakerd.
Sounds wrong. :-)
So I try to upgrade.
I shutdown one node. Change 0 to 1 on service.d/pcmk
Start corosync and then start pacemakerd via init script.
But this node s
Dear community,
I am running on Debian Lenny, a cluster with corosync. I have :
One DRBD partition and 4 resources :
fs-data(ocf::heartbeat:Filesystem):
mda-ip (ocf::heartbeat:IPaddr2):
postfix(ocf::heartbeat:postfix):
apache (ocf::heartbeat:apache):
Last night something happens
> On 2011-07-15 10:17, Michael Schwartzkopff wrote:
> >> As for other ideas, please post your "mount" output on the NFSv4 client
> >> so we can get an idea of the default NFS mount options in effect on your
> >> system.
> >
> > 192.168.10.16:/home on /mnt/home type nfs4
> > (rw,udp,clientaddr=192.
> On 2011-07-15 10:17, Michael Schwartzkopff wrote:
> >> As for other ideas, please post your "mount" output on the NFSv4 client
> >> so we can get an idea of the default NFS mount options in effect on your
> >> system.
> >
> > 192.168.10.16:/home on /mnt/home type nfs4
> > (rw,udp,clientaddr=192.
On 2011-07-15 10:17, Michael Schwartzkopff wrote:
>> As for other ideas, please post your "mount" output on the NFSv4 client
>> so we can get an idea of the default NFS mount options in effect on your
>> system.
>
> 192.168.10.16:/home on /mnt/home type nfs4
> (rw,udp,clientaddr=192.168.10.133,ad
> On 07/14/2011 09:46 PM, Michael Schwartzkopff wrote:
> >> On 2011-07-13 23:08, Michael Schwartzkopff wrote:
> >>> Hi,
> >>>
> >>> I am trying to set up a NFSv4 server cluster. After failover my client
> >>> has to wait 90 sec to be able to access the data agin.
> >>>
> >>> I already set /proc/f
On 2011-07-15 09:44, Florian Haas wrote:
> exportfs is designed such that you don't need to use nfsserver.
I should clarify: ... such that you don't need ocf:heartbeat:nfsserver,
which is essentially a wrapper around an LSB init script. Using the LSB
resource directly will do fine.
Cheers,
Floria
On 2011-07-15 08:44, E. Kuemmerle wrote:
> Hi,
>
> you could try
>
> group groupNFS resFilesystem resIP resNFScommon resNFSserver
> resExportRoot resExportHome
>
> instead of
>
> group groupNFS resFilesystem resNFScommon resNFSserver resExportRoot
> resExportHome resIP
Nope, quite the contrary
On 07/14/2011 09:46 PM, Michael Schwartzkopff wrote:
>> On 2011-07-13 23:08, Michael Schwartzkopff wrote:
>>> Hi,
>>>
>>> I am trying to set up a NFSv4 server cluster. After failover my client
>>> has to wait 90 sec to be able to access the data agin.
>>>
>>> I already set /proc/fs/nfsd/nfsv4leaset
Hi, Andrew
(2011/07/15 15:09), Andrew Beekhof wrote:
On Fri, Jul 15, 2011 at 3:16 PM, Gao,Yan wrote:
On 07/15/11 10:55, Andrew Beekhof wrote:
On Thu, Jul 14, 2011 at 4:28 PM, Gao,Yan wrote:
Hi,
Sorry for the delay. I've been thinking about it...
On 07/14/11 12:21, Andrew Beekhof wrote:
Th
12 matches
Mail list logo
