Hi,

I'm new to the list. 
I have here a, AFAIK, uncommen setup. Sorry the whole explanation is a little 
bit long, but i want to give you all information in the hope of your help :-)

All servers are connected over a backend switch and a frontendswitch to the 
world.
The Backend Network use 10.1.1.0/24
None of the servers use iptabels or another filter mechanism.
Sofwareversions:
Heartbeat 2.0.7
DRBD 8.0.8

Servers:
mysql: 10.1.1.200
backup: 10.1.1.201
media: 10.1.1.202
fe1-fe4: 10.1.1.203-206

"media" server is a http server for image data and the main director for the 
fe? cluster.
"mysql" server is, as you will guess, the mysql server for fe1-4
"backup" server is the fallback for media AND mysql.

from media to backup runs a DRBD
from mysql to backup runs a DRBD

if media fails backup should kick in. (geting drbd primary, firing up external 
ip, firing up internal ip, starting ldirectord, firing up tinyhttpd)
if mysql fails backup should kick in. (geting drbd primary, starting mysql)

I hope this was understandble :-)

So the problems:
if either mysql or media fails i get
 orf-mysql heartbeat: [32004]: ERROR: Both machines own our resources!
 orf-mysql heartbeat: [32004]: ERROR: Both machines own foreign resources!
 orf-mysql heartbeat: [32004]: ERROR: Both machines own our resources!
 orf-mysql heartbeat: [32004]: ERROR: Both machines own foreign resources!

but the takeover still seems to work. Is my setup technicly possible ?

Another slight problem i have. in normal the backup and the media server dont 
have a own external ip. if media server is up heartbeat sets the external ip, 
but unfortunatly i can't get him to set the default gw also. Same case if 
backup server takes over. (currently i have 2 spare ips configured so i can 
set the gateway in the normal way, but this is not a permanent solution)

i dont want to make this mail longer as needed, so you can find all config 
files on http://iamjacks.net/cluster/

any help would be much aprecciated
TIA
Ludwig
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to