Quantcast
Channel:
Viewing all articles
Browse latest Browse all 120649

Forum Post: New SG230 in Cluster - Slave always losing HA eth3 Link

$
0
0
Hello Community, we bought two SG230 - then i configured a Cluster ( HA LINK eth3) Now we always getting this mail from the UTM: The High Availability System is active and fully functional. You are receiving this message due to one of the following cases: * The HA System has been successfully initiated for the first time. * All HA nodes have returned into Active state again - after they had been Unlinked or - after they had been Dead and a reboot was forced or - after an Up2Date process has been successfully finished. We had two ASG 8 ( HA CLuster) befor and we never get this error. We tried new cable - new patchpanel. --> same error. HA LOG: 2016:02:23-05:45:47 UTM9CL-1 ha_daemon[4648]: id="38A3" severity="debug" sys="System" sub="ha" seq="M: 537 47.901" name="Netlink: Lost link beat on eth3!" 2016:02:23-05:45:47 UTM9CL-1 conntrack-tools[5179]: no dedicated links available! 2016:02:23-05:45:49 UTM9CL-1 ha_daemon[4648]: id="38C1" severity="error" sys="System" sub="ha" seq="M: 538 49.509" name="Node 2 is dead, received no heart beats" 2016:02:23-05:45:49 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 539 49.509" name="Executing (wait) /usr/local/bin/confd-setha mode master master_ip 198.19.250.1 slave_ip ''" 2016:02:23-05:45:49 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 540 49.587" name="Executing (nowait) /etc/init.d/ha_mode topology_changed" 2016:02:23-05:45:49 UTM9CL-1 ha_mode[10580]: calling topology_changed 2016:02:23-05:45:49 UTM9CL-1 ha_mode[10580]: topology_changed: waiting for last ha_mode done 2016:02:23-05:45:49 UTM9CL-1 ha_mode[10580]: daemonized... 2016:02:23-05:45:49 UTM9CL-1 repctl[10596]: [i] daemonize_check(1362): trying to signal daemon 2016:02:23-05:45:49 UTM9CL-1 ha_mode[10580]: topology_changed done (started at 05:45:49) 2016:02:23-05:45:49 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 541 49.845" name="Reading cluster configuration" 2016:02:23-05:45:50 UTM9CL-2 ha_daemon[4154]: id="38A3" severity="debug" sys="System" sub="ha" seq="S: 1019 50.838" name="Netlink: Found link beat on eth3 again!" 2016:02:23-05:45:51 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 542 51.327" name="Node 2 changed version! 0.000000 -> 9.351003" 2016:02:23-05:45:51 UTM9CL-1 ha_daemon[4648]: id="38A1" severity="warn" sys="System" sub="ha" seq="M: 543 51.327" name="Lost heartbeat message from node 2! Expected 8522690 but got 8522694" 2016:02:23-05:45:51 UTM9CL-1 ha_daemon[4648]: id="38C0" severity="info" sys="System" sub="ha" seq="M: 544 51.327" name="Node 2 is alive" 2016:02:23-05:45:51 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 545 51.327" name="Node 2 changed state: DEAD(2048) -> ACTIVE(0)" 2016:02:23-05:45:51 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 546 51.327" name="Node 2 changed role: DEAD -> SLAVE" 2016:02:23-05:45:51 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 547 51.327" name="Executing (wait) /usr/local/bin/confd-setha mode master master_ip 198.19.250.1 slave_ip 198.19.250.2" 2016:02:23-05:45:51 UTM9CL-2 ha_daemon[4154]: id="38A0" severity="info" sys="System" sub="ha" seq="S: 1020 51.557" name="Node 1 changed version! 0.000000 -> 9.351003" 2016:02:23-05:45:51 UTM9CL-2 ha_daemon[4154]: id="38A1" severity="warn" sys="System" sub="ha" seq="S: 1021 51.557" name="Lost heartbeat message from node 1! Expected 8919099 but got 8919103" 2016:02:23-05:45:51 UTM9CL-2 ha_daemon[4154]: id="38C0" severity="info" sys="System" sub="ha" seq="S: 1022 51.557" name="Node 1 is alive" 2016:02:23-05:45:51 UTM9CL-2 ha_daemon[4154]: id="38A0" severity="info" sys="System" sub="ha" seq="S: 1023 51.557" name="Node 1 changed state: DEAD(2048) -> ACTIVE(0)" 2016:02:23-05:45:51 UTM9CL-2 ha_daemon[4154]: id="38A0" severity="info" sys="System" sub="ha" seq="S: 0 51.557" name="Node 1 changed role: DEAD -> MASTER" 2016:02:23-05:45:51 UTM9CL-2 ha_daemon[4154]: id="38A0" severity="info" sys="System" sub="ha" seq="S: 1 51.557" name="Executing (nowait) /etc/init.d/ha_mode topology_changed" 2016:02:23-05:45:51 UTM9CL-2 ha_mode[26445]: calling topology_changed 2016:02:23-05:45:51 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 548 51.574" name="Executing (nowait) /etc/init.d/ha_mode topology_changed" 2016:02:23-05:45:51 UTM9CL-1 ha_mode[10725]: calling topology_changed 2016:02:23-05:45:51 UTM9CL-1 ha_mode[10725]: topology_changed: waiting for last ha_mode done 2016:02:23-05:45:51 UTM9CL-1 ha_mode[10725]: daemonized... 2016:02:23-05:45:51 UTM9CL-1 repctl[10751]: [i] daemonize_check(1362): trying to signal daemon 2016:02:23-05:45:51 UTM9CL-1 ha_mode[10725]: topology_changed done (started at 05:45:51) 2016:02:23-05:45:52 UTM9CL-1 ha_daemon[4648]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 549 52.391" name="Reading cluster configuration" 2016:02:23-05:45:52 UTM9CL-2 ha_mode[26435]: daemonized... 2016:02:23-05:45:52 UTM9CL-2 repctl[26471]: [i] daemonize_check(1362): trying to signal daemon 2016:02:23-05:45:52 UTM9CL-2 ha_mode[26435]: topology_changed done (started at 05:45:50) 2016:02:23-05:45:52 UTM9CL-2 ha_mode[26445]: topology_changed: waiting for last ha_mode done 2016:02:23-05:45:52 UTM9CL-2 ha_mode[26445]: daemonized... 2016:02:23-05:45:52 UTM9CL-2 repctl[26506]: [i] daemonize_check(1362): trying to signal daemon 2016:02:23-05:45:52 UTM9CL-2 ha_mode[26445]: topology_changed done (started at 05:45:51) any ideas ?

Viewing all articles
Browse latest Browse all 120649

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>