I've been going through many operations but each time there is a
failure I am only presented with very vague information like,
crm_resource: [8001]: ERROR: unpack_rsc_op: Hard error - drbd_start_0
failed with rc=5:
Is there a way to set a more verbose output and specify a separate log
file beside
On Mon, Dec 28, 2009 at 8:50 AM, Michael Schwartzkopff
wrote:
> Am Montag, 28. Dezember 2009 14:43:25 schrieb Christopher Deneen:
>> acpid atop bootlogd
>> bootmisc.sh checkfs.sh checkroot.sh
>&
On Mon, Dec 28, 2009 at 8:43 AM, Christopher Deneen wrote:
> acpid atop bootlogd
> bootmisc.sh checkfs.sh checkroot.sh
> console-screen.sh corosync cron
> dbus
Am Montag, 28. Dezember 2009 14:13:27 schrieb Christopher Deneen:
>> Are there any guides that show how to work with the resources like
>> nfslock , when i listed the classes in crm I didn't see any of the
>> mentioned resources except for nfs_kernel_server
>>
&g
schrieb Christopher Deneen:
>> I'm trying to setup a cluster of 2 servers that provide a network boot
>> service (using drbl). Are there any problems I may run into when a
>> server is using an nfs share as root and there is a failover, i'm
>> still in the early stag
I'm trying to setup a cluster of 2 servers that provide a network boot
service (using drbl). Are there any problems I may run into when a
server is using an nfs share as root and there is a failover, i'm
still in the early stages of setting it up and notice that with a
manual failure the network bo
Thank you I did not see the faq
-- Sent from my Palm Prē
Michael Schwartzkopff wrote:
Am Montag, 28. Dezember 2009 07:37:05 schrieb Christopher Deneen:
> I followed the lenny guide very carefully and setup a 2 node cluster
> with just ip failover. The only issue I had was installing g
I followed the lenny guide very carefully and setup a 2 node cluster
with just ip failover. The only issue I had was installing gawk to get
it to even start the resource. Currently I am unable to get the
failover to work properly if I restart the computer, I am however able
to put nodes in standby
