6
Im Linux Cluster läuft der 2.Server nicht ohne den ersten.
Linux Cluster funktioniert nicht richtig
Hallo,
Ich habe ein Problem und hoffe es kann mir da jemand weiterhelfen.
Ich habe ein Cluster aus 2 SLES10 SP3 DRBD und Heartbeat installiert. Das funktioniert eigendlich sehr gut.
Wenn ich nur den zweiten Server starte, sollte der doch sehen das der erste nicht läuft und sollte doch die Arbeit
als ersten Server übernehmen.
Vielleicht weis da jemand wo der Fehler liegt. Installiert ist das mit je 2Netzwerkkarten. Hier die Installation:
1. Rechnername ist: linux eth0=192.168.1.206 eth1 =10.0.0.1
2. Rechnername Ist: linux1 eth0=192.168.1.207 eth1=10.0.0.2
Hier meine drbd.conf
Und noch meine ha.cf von 1.Rechner
Und noch meine ha.cf von 2.Rechner
Und noch die haresource:
Als gemeinsame IP habe ich die 192.168.1.208
Hallo,
Ich habe ein Problem und hoffe es kann mir da jemand weiterhelfen.
Ich habe ein Cluster aus 2 SLES10 SP3 DRBD und Heartbeat installiert. Das funktioniert eigendlich sehr gut.
Wenn ich nur den zweiten Server starte, sollte der doch sehen das der erste nicht läuft und sollte doch die Arbeit
als ersten Server übernehmen.
Vielleicht weis da jemand wo der Fehler liegt. Installiert ist das mit je 2Netzwerkkarten. Hier die Installation:
1. Rechnername ist: linux eth0=192.168.1.206 eth1 =10.0.0.1
2. Rechnername Ist: linux1 eth0=192.168.1.207 eth1=10.0.0.2
Hier meine drbd.conf
resource r0 {
protocol C;
incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ; halt -f";
startup {
degr-wfc-timeout 120; # 2 minutes.
}
disk {
on-io-error detach;
}
net {
on-disconnect reconnect;
}
syncer {
rate 100M;
group 1;
al-extents 257;
}
on linux {
device /dev/drbd0;
disk /dev/hda3;
address 10.0.0.1:7788;
meta-disk internal;
}
on linux1 {
device /dev/drbd0;
disk /dev/hdc3;
address 10.0.0.2:7788;
meta-disk internal;
}debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility local0
keepalive 2
deadtime 10
warntime 3
initdead 120
udpport 694
ucast eth0 192.168.1.206
ucast eth0 192.168.1.207
bcast eth1 # Linux
auto_failback on
node linux
node linux1
ping 192.168.1.89
ping 192.168.1.1
respawn hacluster /usr/lib64/heartbeat/ipfaildebugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility local0
keepalive 2
deadtime 10
warntime 3
initdead 120
udpport 694
ucast eth0 192.168.1.206
ucast eth0 192.168.1.207
bcast eth1
auto_failback on
node linux
node linux1linux 192.168.1.208 drbddisk::r0 Filesystem::/dev/drbd0::/srv/r0::xfs
Auf Facebook teilen
Auf Twitter teilen
Auf Reddit teilen
Auf Linkedin teilenBitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 152510
Url: https://administrator.de/contentid/152510
Ausgedruckt am: 22.11.2024 um 06:11 Uhr
6 Kommentare
Neuester Kommentar
Moin,
schau dir mal diesen Link an. Dort wird der Aufbau und Konfiguration nochmals genauer beschrieben.
In den Logdateien /var/log/ha-log bzw. ha-debug stehen keine Meldungen die auf das Problem hinweisen?!
Grüße,
Dani
schau dir mal diesen Link an. Dort wird der Aufbau und Konfiguration nochmals genauer beschrieben.
In den Logdateien /var/log/ha-log bzw. ha-debug stehen keine Meldungen die auf das Problem hinweisen?!
Grüße,
Dani
Tausche mal in der ha.cfg für den zweiten Node die Reihenfolge der nodes. Also
in ha.cfg für Linux
node Linux
node Linux1
in ha.cfg für Linux1
node Linux1
node Linux
Das sollte helfen.
in ha.cfg für Linux
node Linux
node Linux1
in ha.cfg für Linux1
node Linux1
node Linux
Das sollte helfen.
Hallo,
Also jetzt hab ich das nochmal versucht und das geht nicht richtig.
Wenn ich beide Server nacheinander einschalte dann funktioniert das alles.
Wenn ich einen aus mache dann übernimmt der ander die Aufgabe des anderen.
Und wenn ich den wieder an mache dann über nimmt der das wieder, So wie
auch sein muß. Aber wenn ich nur einen allein Starte dann geht das nicht. Egal ob ich den
ersten oder den zweiten starte. Alleine laufen die nicht. Ich hab da mal die logs.
Ach ja, Wenn der Server hochgelaufen ist, dann kann ich Heartbeat manuell Starten, Also mit
/etc/init.d/heartbeat start dann läuft das und ich kann auf die ip 192.168.1.208 zugreifen und die Daten sind sichtbar.
Vielleicht sieht da jemand was.
ha-debug
heartbeat[5114]: 2010/10/07_22:21:17 info: Heartbeat shutdown in progress. (5114)
heartbeat[5948]: 2010/10/07_22:21:17 info: Giving up all HA resources.
ResourceManager[5961]: 2010/10/07_22:21:17 info: Releasing resource group: linux 192.168.1.208 drbddisk::r0 Filesystem::/dev/drbd0::/sr
v/r0::xfs
ResourceManager[5961]: 2010/10/07_22:21:17 info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop
ResourceManager[5961]: 2010/10/07_22:21:17 debug: Starting /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop
Filesystem[6068]: 2010/10/07_22:21:17 WARNING: Couldn't find device [/dev/drbd0]. Expected /dev/??? to exist
Filesystem[6068]: 2010/10/07_22:21:17 INFO: Running stop for /dev/drbd0 on /srv/r0
/dev/drbd0: No such file or directory
Filesystem[6050]: 2010/10/07_22:21:17 INFO: Success
INFO: Success
ResourceManager[5961]: 2010/10/07_22:21:17 debug: /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop done. RC=0
ResourceManager[5961]: 2010/10/07_22:21:17 info: Running /etc/ha.d/resource.d/drbddisk r0 stop
ResourceManager[5961]: 2010/10/07_22:21:17 debug: Starting /etc/ha.d/resource.d/drbddisk r0 stop
ResourceManager[5961]: 2010/10/07_22:21:17 debug: /etc/ha.d/resource.d/drbddisk r0 stop done. RC=0
ResourceManager[5961]: 2010/10/07_22:21:17 info: Running /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop
ResourceManager[5961]: 2010/10/07_22:21:17 debug: Starting /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop
In IP Stop
IPaddr[6195]: 2010/10/07_22:21:17 INFO: Success
INFO: Success
ResourceManager[5961]: 2010/10/07_22:21:17 debug: /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop done. RC=0
heartbeat[5948]: 2010/10/07_22:21:17 info: All HA resources relinquished.
heartbeat[5114]: 2010/10/07_22:21:18 info: killing /usr/lib64/heartbeat/ipfail process group 5222 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5170 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5171 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5172 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5173 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5174 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5175 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5176 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBFIFO process 5166 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5177 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5167 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5178 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5168 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5179 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5169 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5180 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5170 exited. 15 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5172 exited. 14 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5168 exited. 13 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5167 exited. 12 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5174 exited. 11 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5180 exited. 10 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5166 exited. 9 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5169 exited. 8 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5171 exited. 7 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5173 exited. 6 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5175 exited. 5 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5176 exited. 4 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5177 exited. 3 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5179 exited. 2 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5178 exited. 1 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: linux Heartbeat shutdown complete.
hb_standby[6431]: 2010/10/07_22:21:21 Going standby [foreign].
Also jetzt hab ich das nochmal versucht und das geht nicht richtig.
Wenn ich beide Server nacheinander einschalte dann funktioniert das alles.
Wenn ich einen aus mache dann übernimmt der ander die Aufgabe des anderen.
Und wenn ich den wieder an mache dann über nimmt der das wieder, So wie
auch sein muß. Aber wenn ich nur einen allein Starte dann geht das nicht. Egal ob ich den
ersten oder den zweiten starte. Alleine laufen die nicht. Ich hab da mal die logs.
Ach ja, Wenn der Server hochgelaufen ist, dann kann ich Heartbeat manuell Starten, Also mit
/etc/init.d/heartbeat start dann läuft das und ich kann auf die ip 192.168.1.208 zugreifen und die Daten sind sichtbar.
Vielleicht sieht da jemand was.
ha-debug
heartbeat[5114]: 2010/10/07_22:21:17 info: Heartbeat shutdown in progress. (5114)
heartbeat[5948]: 2010/10/07_22:21:17 info: Giving up all HA resources.
ResourceManager[5961]: 2010/10/07_22:21:17 info: Releasing resource group: linux 192.168.1.208 drbddisk::r0 Filesystem::/dev/drbd0::/sr
v/r0::xfs
ResourceManager[5961]: 2010/10/07_22:21:17 info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop
ResourceManager[5961]: 2010/10/07_22:21:17 debug: Starting /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop
Filesystem[6068]: 2010/10/07_22:21:17 WARNING: Couldn't find device [/dev/drbd0]. Expected /dev/??? to exist
Filesystem[6068]: 2010/10/07_22:21:17 INFO: Running stop for /dev/drbd0 on /srv/r0
/dev/drbd0: No such file or directory
Filesystem[6050]: 2010/10/07_22:21:17 INFO: Success
INFO: Success
ResourceManager[5961]: 2010/10/07_22:21:17 debug: /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop done. RC=0
ResourceManager[5961]: 2010/10/07_22:21:17 info: Running /etc/ha.d/resource.d/drbddisk r0 stop
ResourceManager[5961]: 2010/10/07_22:21:17 debug: Starting /etc/ha.d/resource.d/drbddisk r0 stop
ResourceManager[5961]: 2010/10/07_22:21:17 debug: /etc/ha.d/resource.d/drbddisk r0 stop done. RC=0
ResourceManager[5961]: 2010/10/07_22:21:17 info: Running /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop
ResourceManager[5961]: 2010/10/07_22:21:17 debug: Starting /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop
In IP Stop
IPaddr[6195]: 2010/10/07_22:21:17 INFO: Success
INFO: Success
ResourceManager[5961]: 2010/10/07_22:21:17 debug: /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop done. RC=0
heartbeat[5948]: 2010/10/07_22:21:17 info: All HA resources relinquished.
heartbeat[5114]: 2010/10/07_22:21:18 info: killing /usr/lib64/heartbeat/ipfail process group 5222 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5170 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5171 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5172 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5173 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5174 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5175 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5176 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBFIFO process 5166 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5177 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5167 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5178 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5168 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5179 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBWRITE process 5169 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: killing HBREAD process 5180 with signal 15
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5170 exited. 15 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5172 exited. 14 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5168 exited. 13 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5167 exited. 12 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5174 exited. 11 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5180 exited. 10 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5166 exited. 9 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5169 exited. 8 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5171 exited. 7 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5173 exited. 6 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5175 exited. 5 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5176 exited. 4 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5177 exited. 3 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5179 exited. 2 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: Core process 5178 exited. 1 remaining
heartbeat[5114]: 2010/10/07_22:21:19 info: linux Heartbeat shutdown complete.
hb_standby[6431]: 2010/10/07_22:21:21 Going standby [foreign].
Moin,
Das fällt mir so als erstes mal auf...
Ansonsten was stehe im Log "ha.log". Dort irgendwas ungewöhliches?
Grüße,
Dani
Filesystem[6068]: 2010/10/07_22:21:17 WARNING: Couldn't find device [/dev/drbd0]. Expected /dev/??? to exist
Filesystem[6068]: 2010/10/07_22:21:17 INFO: Running stop for /dev/drbd0 on /srv/r0
/dev/drbd0: No such file or directoryAnsonsten was stehe im Log "ha.log". Dort irgendwas ungewöhliches?
Grüße,
Dani
Hallo,
Kann das sein das der drbd Dienst noch nicht ganz gestartet ist wenn das Heartbeat startet?
Kann man da im Runlevel was ändern?
Gruß
Helmut
Kann das sein das der drbd Dienst noch nicht ganz gestartet ist wenn das Heartbeat startet?
Kann man da im Runlevel was ändern?
Gruß
Helmut
Hallo,
Jetzt hab ich das Heartbeat aus dem Runlevel herausgenommen und neu gestartet. Nach dem Start habe ich Heartbeat manuell mit
/etc/init.d/heartbeat start gestartet, und da gehts. Nach 2min Mountet er /srv/r0 und die IP ist auch erreichbar. Das log sieht jetzt so aus:
heartbeat[4182]: 2010/10/08_21:22:12 ERROR: glib: Unable to send bcast [-1] packet(len=182): No such device
heartbeat[4182]: 2010/10/08_21:22:12 ERROR: write_child: write failure on bcast eth1.: No such device
heartbeat[4184]: 2010/10/08_21:22:12 ERROR: glib: Unable to send [-1] ucast packet: No such device
heartbeat[4184]: 2010/10/08_21:22:12 ERROR: write_child: write failure on ucast eth0.: No such device
heartbeat[4186]: 2010/10/08_21:22:12 ERROR: glib: Unable to send [-1] ucast packet: No such device
heartbeat[4186]: 2010/10/08_21:22:12 ERROR: write_child: write failure on ucast eth0.: No such device
heartbeat[4188]: 2010/10/08_21:22:12 ERROR: glib: Error sending packet: Network is unreachable
heartbeat[4188]: 2010/10/08_21:22:12 info: glib: euid=0 egid=0
heartbeat[4188]: 2010/10/08_21:22:12 ERROR: write_child: write failure on ping 192.168.1.89.: Network is unreachable
heartbeat[4190]: 2010/10/08_21:22:12 ERROR: glib: Error sending packet: Network is unreachable
heartbeat[4190]: 2010/10/08_21:22:12 info: glib: euid=0 egid=0
heartbeat[4190]: 2010/10/08_21:22:12 ERROR: write_child: write failure on ping 192.168.1.1.: Network is unreachable
heartbeat[4179]: 2010/10/08_21:22:12 info: Heartbeat shutdown in progress. (4179)
heartbeat[5484]: 2010/10/08_21:22:12 info: Giving up all HA resources.
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4185 exited. 11 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4183 exited. 10 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4187 exited. 9 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4189 exited. 8 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4191 exited. 7 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4190 exited. 6 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4188 exited. 5 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4186 exited. 4 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4184 exited. 3 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4182 exited. 2 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4181 exited. 1 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: linux Heartbeat shutdown complete.
ResourceManager[5497]: 2010/10/08_21:22:12 info: Releasing resource group: linux 192.168.1.208 drbddisk::r0 Filesystem::/dev/drbd0::/srv/r0::xfs
ResourceManager[5497]: 2010/10/08_21:22:12 info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop
ResourceManager[5497]: 2010/10/08_21:22:12 debug: Starting /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop
Filesystem[5546]: 2010/10/08_21:22:12 INFO: Running stop for /dev/drbd0 on /srv/r0
Filesystem[5546]: 2010/10/08_21:22:12 INFO: Trying to unmount /srv/r0
Filesystem[5546]: 2010/10/08_21:22:12 INFO: unmounted /srv/r0 successfully
Filesystem[5535]: 2010/10/08_21:22:12 INFO: Success
INFO: Success
ResourceManager[5497]: 2010/10/08_21:22:12 debug: /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop done. RC=0
ResourceManager[5497]: 2010/10/08_21:22:12 info: Running /etc/ha.d/resource.d/drbddisk r0 stop
ResourceManager[5497]: 2010/10/08_21:22:12 debug: Starting /etc/ha.d/resource.d/drbddisk r0 stop
ResourceManager[5497]: 2010/10/08_21:22:12 debug: /etc/ha.d/resource.d/drbddisk r0 stop done. RC=0
ResourceManager[5497]: 2010/10/08_21:22:12 info: Running /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop
ResourceManager[5497]: 2010/10/08_21:22:12 debug: Starting /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop
In IP Stop
IPaddr[5663]: 2010/10/08_21:22:12 INFO: Success
INFO: Success
ResourceManager[5497]: 2010/10/08_21:22:12 debug: /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop done. RC=0
heartbeat[5484]: 2010/10/08_21:22:12 info: All HA resources relinquished.
heartbeat[4167]: 2010/10/08_21:29:16 WARN: Core dumps could be lost if multiple dumps occur.
heartbeat[4167]: 2010/10/08_21:29:16 WARN: Consider setting non-default value in /proc/sys/kernel/core_pattern (or equivalent) for maximum supportability
heartbeat[4167]: 2010/10/08_21:29:16 WARN: Consider setting /proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum supportability
heartbeat[4167]: 2010/10/08_21:29:16 info: Version 2 support: false
heartbeat[4167]: 2010/10/08_21:29:16 WARN: Logging daemon is disabled --enabling logging daemon is recommended
heartbeat[4167]: 2010/10/08_21:29:16 info: **
heartbeat[4167]: 2010/10/08_21:29:16 info: Configuration validated. Starting heartbeat 2.1.3
heartbeat[4168]: 2010/10/08_21:29:16 info: heartbeat: version 2.1.3
heartbeat[4168]: 2010/10/08_21:29:16 info: Heartbeat generation: 1285880012
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth1
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: UDP Broadcast heartbeat closed on port 694 interface eth1 - Status: 1
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: bound send socket to device: eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: bound receive socket to device: eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: started on port 694 interface eth0 to 192.168.1.206
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: bound send socket to device: eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: bound receive socket to device: eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: started on port 694 interface eth0 to 192.168.1.207
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ping heartbeat started.
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ping heartbeat started.
heartbeat[4168]: 2010/10/08_21:29:16 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat[4168]: 2010/10/08_21:29:16 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat[4168]: 2010/10/08_21:29:16 info: G_main_add_SignalHandler: Added signal handler for signal 17
heartbeat[4168]: 2010/10/08_21:29:16 info: Local status now set to: 'up'
heartbeat[4168]: 2010/10/08_21:29:18 info: Status update for node 192.168.1.1: status ping
heartbeat[4168]: 2010/10/08_21:29:18 info: Link 192.168.1.1:192.168.1.1 up.
heartbeat[4168]: 2010/10/08_21:29:18 info: Link 192.168.1.89:192.168.1.89 up.
heartbeat[4168]: 2010/10/08_21:29:18 info: Status update for node 192.168.1.89: status ping
heartbeat[4168]: 2010/10/08_21:29:18 info: Link linux:eth1 up.
heartbeat[4168]: 2010/10/08_21:31:17 WARN: node linux1: is dead
heartbeat[4168]: 2010/10/08_21:31:17 info: Comm_now_up(): updating status to active
heartbeat[4168]: 2010/10/08_21:31:17 info: Local status now set to: 'active'
heartbeat[4168]: 2010/10/08_21:31:17 info: Starting child client "/usr/lib64/heartbeat/ipfail" (90,90)
heartbeat[4168]: 2010/10/08_21:31:17 WARN: No STONITH device configured.
heartbeat[4214]: 2010/10/08_21:31:17 info: Starting "/usr/lib64/heartbeat/ipfail" as uid 90 gid 90 (pid 4214)
heartbeat[4168]: 2010/10/08_21:31:17 WARN: Shared disks are not protected.
heartbeat[4168]: 2010/10/08_21:31:17 info: Resources being acquired from linux1.
heartbeat[4215]: 2010/10/08_21:31:17 debug: notify_world: setting SIGCHLD Handler to SIG_DFL
ipfail[4214]: 2010/10/08_21:31:17 debug: PID=4214
ipfail[4214]: 2010/10/08_21:31:17 debug: Signing in with heartbeat
harc[4215]: 2010/10/08_21:31:17 info: Running /etc/ha.d/rc.d/status status
IPaddr[4276]: 2010/10/08_21:31:17 INFO: Resource is stopped
heartbeat[4216]: 2010/10/08_21:31:17 info: Local Resource acquisition completed.
heartbeat[4168]: 2010/10/08_21:31:17 debug: StartNextRemoteRscReq(): child count 2
heartbeat[4168]: 2010/10/08_21:31:17 debug: StartNextRemoteRscReq(): child count 1
ipfail[4214]: 2010/10/08_21:31:17 debug: [We are linux]
mach_down[4251]: 2010/10/08_21:31:17 info: /usr/share/heartbeat/mach_down: nice_failback: foreign resources acquired
mach_down[4251]: 2010/10/08_21:31:17 info: mach_down takeover complete for node linux1.
heartbeat[4168]: 2010/10/08_21:31:17 info: mach_down takeover complete.
heartbeat[4168]: 2010/10/08_21:31:17 info: Initial resource acquisition complete (mach_down)
ipfail[4214]: 2010/10/08_21:31:17 debug: auto_failback -> 1 (on)
heartbeat[4340]: 2010/10/08_21:31:17 debug: notify_world: setting SIGCHLD Handler to SIG_DFL
harc[4340]: 2010/10/08_21:31:17 info: Running /etc/ha.d/rc.d/ip-request-resp ip-request-resp
ip-request-resp[4340]: 2010/10/08_21:31:17 received ip-request-resp 192.168.1.208 OK yes
ResourceManager[4361]: 2010/10/08_21:31:17 info: Acquiring resource group: linux-ritter 192.168.1.208 drbddisk::r0 Filesystem::/dev/drbd0::/srv/r0::xfs
IPaddr[4388]: 2010/10/08_21:31:17 INFO: Resource is stopped
ipfail[4214]: 2010/10/08_21:31:17 debug: Setting message filter mode
ResourceManager[4361]: 2010/10/08_21:31:17 info: Running /etc/ha.d/resource.d/IPaddr 192.168.1.208 start
ResourceManager[4361]: 2010/10/08_21:31:17 debug: Starting /etc/ha.d/resource.d/IPaddr 192.168.1.208 start
IPaddr[4464]: 2010/10/08_21:31:18 INFO: Using calculated nic for 192.168.1.208: eth0
IPaddr[4464]: 2010/10/08_21:31:18 INFO: Using calculated netmask for 192.168.1.208: 255.255.255.0
IPaddr[4464]: 2010/10/08_21:31:18 DEBUG: Using calculated broadcast for 192.168.1.208: 192.168.1.255
ipfail[4214]: 2010/10/08_21:31:18 debug: Starting node walk
IPaddr[4464]: 2010/10/08_21:31:18 INFO: eval ifconfig eth0:0 192.168.1.208 netmask 255.255.255.0 broadcast 192.168.1.255
IPaddr[4464]: 2010/10/08_21:31:18 DEBUG: Sending Gratuitous Arp for 192.168.1.208 on eth0:0 [eth0]
IPaddr[4447]: 2010/10/08_21:31:18 INFO: Success
INFO: Success
ResourceManager[4361]: 2010/10/08_21:31:18 debug: /etc/ha.d/resource.d/IPaddr 192.168.1.208 start done. RC=0
ResourceManager[4361]: 2010/10/08_21:31:18 info: Running /etc/ha.d/resource.d/drbddisk r0 start
ResourceManager[4361]: 2010/10/08_21:31:18 debug: Starting /etc/ha.d/resource.d/drbddisk r0 start
ResourceManager[4361]: 2010/10/08_21:31:18 debug: /etc/ha.d/resource.d/drbddisk r0 start done. RC=0
Filesystem[4623]: 2010/10/08_21:31:18 INFO: Resource is stopped
ResourceManager[4361]: 2010/10/08_21:31:18 info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs start
ResourceManager[4361]: 2010/10/08_21:31:18 debug: Starting /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs start
Filesystem[4704]: 2010/10/08_21:31:18 INFO: Running start for /dev/drbd0 on /srv/r0
ipfail[4214]: 2010/10/08_21:31:18 debug: Cluster node: 192.168.1.1: status: ping
ipfail[4214]: 2010/10/08_21:31:18 debug: Cluster node: 192.168.1.89: status: ping
Filesystem[4693]: 2010/10/08_21:31:18 INFO: Success
INFO: Success
ResourceManager[4361]: 2010/10/08_21:31:18 debug: /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs start done. RC=0
ipfail[4214]: 2010/10/08_21:31:18 debug: Cluster node: linux1: status: dead
ipfail[4214]: 2010/10/08_21:31:19 debug: [They are linux1]
ipfail[4214]: 2010/10/08_21:31:19 debug: Cluster node: linux: status: active
ipfail[4214]: 2010/10/08_21:31:19 debug: Setting message signal
ipfail[4214]: 2010/10/08_21:31:19 debug: Waiting for messages...
heartbeat[4168]: 2010/10/08_21:31:28 info: Local Resource acquisition completed. (none)
heartbeat[4168]: 2010/10/08_21:31:28 info: local resource transition completed.
Was kann man da jetzt noch tun damit das auch Automatisch so startet?
Und was mich noch genauer interessiert:
Was sollte man nehmen bcast eth1 oder ucast eth0 und die ips ?
Was bedeutet das genau?
Danke.
Jetzt hab ich das Heartbeat aus dem Runlevel herausgenommen und neu gestartet. Nach dem Start habe ich Heartbeat manuell mit
/etc/init.d/heartbeat start gestartet, und da gehts. Nach 2min Mountet er /srv/r0 und die IP ist auch erreichbar. Das log sieht jetzt so aus:
heartbeat[4182]: 2010/10/08_21:22:12 ERROR: glib: Unable to send bcast [-1] packet(len=182): No such device
heartbeat[4182]: 2010/10/08_21:22:12 ERROR: write_child: write failure on bcast eth1.: No such device
heartbeat[4184]: 2010/10/08_21:22:12 ERROR: glib: Unable to send [-1] ucast packet: No such device
heartbeat[4184]: 2010/10/08_21:22:12 ERROR: write_child: write failure on ucast eth0.: No such device
heartbeat[4186]: 2010/10/08_21:22:12 ERROR: glib: Unable to send [-1] ucast packet: No such device
heartbeat[4186]: 2010/10/08_21:22:12 ERROR: write_child: write failure on ucast eth0.: No such device
heartbeat[4188]: 2010/10/08_21:22:12 ERROR: glib: Error sending packet: Network is unreachable
heartbeat[4188]: 2010/10/08_21:22:12 info: glib: euid=0 egid=0
heartbeat[4188]: 2010/10/08_21:22:12 ERROR: write_child: write failure on ping 192.168.1.89.: Network is unreachable
heartbeat[4190]: 2010/10/08_21:22:12 ERROR: glib: Error sending packet: Network is unreachable
heartbeat[4190]: 2010/10/08_21:22:12 info: glib: euid=0 egid=0
heartbeat[4190]: 2010/10/08_21:22:12 ERROR: write_child: write failure on ping 192.168.1.1.: Network is unreachable
heartbeat[4179]: 2010/10/08_21:22:12 info: Heartbeat shutdown in progress. (4179)
heartbeat[5484]: 2010/10/08_21:22:12 info: Giving up all HA resources.
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4185 exited. 11 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4183 exited. 10 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4187 exited. 9 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4189 exited. 8 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4191 exited. 7 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4190 exited. 6 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4188 exited. 5 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4186 exited. 4 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4184 exited. 3 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4182 exited. 2 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: Core process 4181 exited. 1 remaining
heartbeat[4179]: 2010/10/08_21:22:12 info: linux Heartbeat shutdown complete.
ResourceManager[5497]: 2010/10/08_21:22:12 info: Releasing resource group: linux 192.168.1.208 drbddisk::r0 Filesystem::/dev/drbd0::/srv/r0::xfs
ResourceManager[5497]: 2010/10/08_21:22:12 info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop
ResourceManager[5497]: 2010/10/08_21:22:12 debug: Starting /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop
Filesystem[5546]: 2010/10/08_21:22:12 INFO: Running stop for /dev/drbd0 on /srv/r0
Filesystem[5546]: 2010/10/08_21:22:12 INFO: Trying to unmount /srv/r0
Filesystem[5546]: 2010/10/08_21:22:12 INFO: unmounted /srv/r0 successfully
Filesystem[5535]: 2010/10/08_21:22:12 INFO: Success
INFO: Success
ResourceManager[5497]: 2010/10/08_21:22:12 debug: /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs stop done. RC=0
ResourceManager[5497]: 2010/10/08_21:22:12 info: Running /etc/ha.d/resource.d/drbddisk r0 stop
ResourceManager[5497]: 2010/10/08_21:22:12 debug: Starting /etc/ha.d/resource.d/drbddisk r0 stop
ResourceManager[5497]: 2010/10/08_21:22:12 debug: /etc/ha.d/resource.d/drbddisk r0 stop done. RC=0
ResourceManager[5497]: 2010/10/08_21:22:12 info: Running /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop
ResourceManager[5497]: 2010/10/08_21:22:12 debug: Starting /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop
In IP Stop
IPaddr[5663]: 2010/10/08_21:22:12 INFO: Success
INFO: Success
ResourceManager[5497]: 2010/10/08_21:22:12 debug: /etc/ha.d/resource.d/IPaddr 192.168.1.208 stop done. RC=0
heartbeat[5484]: 2010/10/08_21:22:12 info: All HA resources relinquished.
heartbeat[4167]: 2010/10/08_21:29:16 WARN: Core dumps could be lost if multiple dumps occur.
heartbeat[4167]: 2010/10/08_21:29:16 WARN: Consider setting non-default value in /proc/sys/kernel/core_pattern (or equivalent) for maximum supportability
heartbeat[4167]: 2010/10/08_21:29:16 WARN: Consider setting /proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum supportability
heartbeat[4167]: 2010/10/08_21:29:16 info: Version 2 support: false
heartbeat[4167]: 2010/10/08_21:29:16 WARN: Logging daemon is disabled --enabling logging daemon is recommended
heartbeat[4167]: 2010/10/08_21:29:16 info: **
heartbeat[4167]: 2010/10/08_21:29:16 info: Configuration validated. Starting heartbeat 2.1.3
heartbeat[4168]: 2010/10/08_21:29:16 info: heartbeat: version 2.1.3
heartbeat[4168]: 2010/10/08_21:29:16 info: Heartbeat generation: 1285880012
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth1
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: UDP Broadcast heartbeat closed on port 694 interface eth1 - Status: 1
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: bound send socket to device: eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: bound receive socket to device: eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: started on port 694 interface eth0 to 192.168.1.206
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: bound send socket to device: eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: bound receive socket to device: eth0
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ucast: started on port 694 interface eth0 to 192.168.1.207
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ping heartbeat started.
heartbeat[4168]: 2010/10/08_21:29:16 info: glib: ping heartbeat started.
heartbeat[4168]: 2010/10/08_21:29:16 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat[4168]: 2010/10/08_21:29:16 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat[4168]: 2010/10/08_21:29:16 info: G_main_add_SignalHandler: Added signal handler for signal 17
heartbeat[4168]: 2010/10/08_21:29:16 info: Local status now set to: 'up'
heartbeat[4168]: 2010/10/08_21:29:18 info: Status update for node 192.168.1.1: status ping
heartbeat[4168]: 2010/10/08_21:29:18 info: Link 192.168.1.1:192.168.1.1 up.
heartbeat[4168]: 2010/10/08_21:29:18 info: Link 192.168.1.89:192.168.1.89 up.
heartbeat[4168]: 2010/10/08_21:29:18 info: Status update for node 192.168.1.89: status ping
heartbeat[4168]: 2010/10/08_21:29:18 info: Link linux:eth1 up.
heartbeat[4168]: 2010/10/08_21:31:17 WARN: node linux1: is dead
heartbeat[4168]: 2010/10/08_21:31:17 info: Comm_now_up(): updating status to active
heartbeat[4168]: 2010/10/08_21:31:17 info: Local status now set to: 'active'
heartbeat[4168]: 2010/10/08_21:31:17 info: Starting child client "/usr/lib64/heartbeat/ipfail" (90,90)
heartbeat[4168]: 2010/10/08_21:31:17 WARN: No STONITH device configured.
heartbeat[4214]: 2010/10/08_21:31:17 info: Starting "/usr/lib64/heartbeat/ipfail" as uid 90 gid 90 (pid 4214)
heartbeat[4168]: 2010/10/08_21:31:17 WARN: Shared disks are not protected.
heartbeat[4168]: 2010/10/08_21:31:17 info: Resources being acquired from linux1.
heartbeat[4215]: 2010/10/08_21:31:17 debug: notify_world: setting SIGCHLD Handler to SIG_DFL
ipfail[4214]: 2010/10/08_21:31:17 debug: PID=4214
ipfail[4214]: 2010/10/08_21:31:17 debug: Signing in with heartbeat
harc[4215]: 2010/10/08_21:31:17 info: Running /etc/ha.d/rc.d/status status
IPaddr[4276]: 2010/10/08_21:31:17 INFO: Resource is stopped
heartbeat[4216]: 2010/10/08_21:31:17 info: Local Resource acquisition completed.
heartbeat[4168]: 2010/10/08_21:31:17 debug: StartNextRemoteRscReq(): child count 2
heartbeat[4168]: 2010/10/08_21:31:17 debug: StartNextRemoteRscReq(): child count 1
ipfail[4214]: 2010/10/08_21:31:17 debug: [We are linux]
mach_down[4251]: 2010/10/08_21:31:17 info: /usr/share/heartbeat/mach_down: nice_failback: foreign resources acquired
mach_down[4251]: 2010/10/08_21:31:17 info: mach_down takeover complete for node linux1.
heartbeat[4168]: 2010/10/08_21:31:17 info: mach_down takeover complete.
heartbeat[4168]: 2010/10/08_21:31:17 info: Initial resource acquisition complete (mach_down)
ipfail[4214]: 2010/10/08_21:31:17 debug: auto_failback -> 1 (on)
heartbeat[4340]: 2010/10/08_21:31:17 debug: notify_world: setting SIGCHLD Handler to SIG_DFL
harc[4340]: 2010/10/08_21:31:17 info: Running /etc/ha.d/rc.d/ip-request-resp ip-request-resp
ip-request-resp[4340]: 2010/10/08_21:31:17 received ip-request-resp 192.168.1.208 OK yes
ResourceManager[4361]: 2010/10/08_21:31:17 info: Acquiring resource group: linux-ritter 192.168.1.208 drbddisk::r0 Filesystem::/dev/drbd0::/srv/r0::xfs
IPaddr[4388]: 2010/10/08_21:31:17 INFO: Resource is stopped
ipfail[4214]: 2010/10/08_21:31:17 debug: Setting message filter mode
ResourceManager[4361]: 2010/10/08_21:31:17 info: Running /etc/ha.d/resource.d/IPaddr 192.168.1.208 start
ResourceManager[4361]: 2010/10/08_21:31:17 debug: Starting /etc/ha.d/resource.d/IPaddr 192.168.1.208 start
IPaddr[4464]: 2010/10/08_21:31:18 INFO: Using calculated nic for 192.168.1.208: eth0
IPaddr[4464]: 2010/10/08_21:31:18 INFO: Using calculated netmask for 192.168.1.208: 255.255.255.0
IPaddr[4464]: 2010/10/08_21:31:18 DEBUG: Using calculated broadcast for 192.168.1.208: 192.168.1.255
ipfail[4214]: 2010/10/08_21:31:18 debug: Starting node walk
IPaddr[4464]: 2010/10/08_21:31:18 INFO: eval ifconfig eth0:0 192.168.1.208 netmask 255.255.255.0 broadcast 192.168.1.255
IPaddr[4464]: 2010/10/08_21:31:18 DEBUG: Sending Gratuitous Arp for 192.168.1.208 on eth0:0 [eth0]
IPaddr[4447]: 2010/10/08_21:31:18 INFO: Success
INFO: Success
ResourceManager[4361]: 2010/10/08_21:31:18 debug: /etc/ha.d/resource.d/IPaddr 192.168.1.208 start done. RC=0
ResourceManager[4361]: 2010/10/08_21:31:18 info: Running /etc/ha.d/resource.d/drbddisk r0 start
ResourceManager[4361]: 2010/10/08_21:31:18 debug: Starting /etc/ha.d/resource.d/drbddisk r0 start
ResourceManager[4361]: 2010/10/08_21:31:18 debug: /etc/ha.d/resource.d/drbddisk r0 start done. RC=0
Filesystem[4623]: 2010/10/08_21:31:18 INFO: Resource is stopped
ResourceManager[4361]: 2010/10/08_21:31:18 info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs start
ResourceManager[4361]: 2010/10/08_21:31:18 debug: Starting /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs start
Filesystem[4704]: 2010/10/08_21:31:18 INFO: Running start for /dev/drbd0 on /srv/r0
ipfail[4214]: 2010/10/08_21:31:18 debug: Cluster node: 192.168.1.1: status: ping
ipfail[4214]: 2010/10/08_21:31:18 debug: Cluster node: 192.168.1.89: status: ping
Filesystem[4693]: 2010/10/08_21:31:18 INFO: Success
INFO: Success
ResourceManager[4361]: 2010/10/08_21:31:18 debug: /etc/ha.d/resource.d/Filesystem /dev/drbd0 /srv/r0 xfs start done. RC=0
ipfail[4214]: 2010/10/08_21:31:18 debug: Cluster node: linux1: status: dead
ipfail[4214]: 2010/10/08_21:31:19 debug: [They are linux1]
ipfail[4214]: 2010/10/08_21:31:19 debug: Cluster node: linux: status: active
ipfail[4214]: 2010/10/08_21:31:19 debug: Setting message signal
ipfail[4214]: 2010/10/08_21:31:19 debug: Waiting for messages...
heartbeat[4168]: 2010/10/08_21:31:28 info: Local Resource acquisition completed. (none)
heartbeat[4168]: 2010/10/08_21:31:28 info: local resource transition completed.
Was kann man da jetzt noch tun damit das auch Automatisch so startet?
Und was mich noch genauer interessiert:
Was sollte man nehmen bcast eth1 oder ucast eth0 und die ips ?
Was bedeutet das genau?
Danke.
