libteam August 2015

libteam@lists.fedorahosted.org

7 participants
11 discussions

Stange problems with CentOS 7 and roundrobin runner
by Ingo Brand 07 Sep '16

07 Sep '16

Hello, I am currently setting up a high available NFS server cluster with 2 nodes using pacemaker + corosync + drbd + flashcache. The two nodes (media1 and media2) have 4 1G copper nics each. I formed 2 teams: team0: LACP with em1 and em2 connected to a switch for NFS services team1: roundrobin with em3 and em4 and MTU 9000 directly connected with copper patch cables for drbd sync During my testing everything was working as expected. Then I started to tranfer about 20TB from an old server to the new cluster. The copy process was fine for about 32 hours. Then corosync and drbd started to report errors on the roundrobin team1 interface (see logs at the end of this email). The drbd sync and corosync started to flap between states for several hours on team1. I checked the error counters with ifconfig and found a huge amount off TX dropped packets on team1 of the drbd slave node media2. There were NO other error counters raising but team1 on media2. To make this a bit more clear: - team1 on media2 (the drbd slave) showed raising TX dropped packets - em3 and em4 on media2 (the physical interfaces of team1) did not show any raising error counters. - team1 on media1 (the drbd master) did not show any raising error counters. - em3 and em4 on media1 (the physical interfaces of team1) did not show any raising error counters. I then thought maybe one of the two patch cables between the two machines was not 100% ok. So I removed em4 from team1 on both machines: "teamdctl team1 port remove em4" The error counters stopped raising. I thought: "Yeah! That cable must be broken!" But just to make sure I really found the problem I re-enabled em4 on both nodes: "teamdctl team1 port add em4" Ok, now both team1 interfaces had 2 links up again and the error counter restarted to raise again. I then stopped em3 on both nodes to force all traffic through em4: "teamdctl team1 port remove em3" And guess what? The error counters on team1 stopped raising! So in short: If I remove either one of the two physical interfaces from team1 everything is working without any errors. As soon as I enable both physical interfaces the error counters start to raise. After these tests I rebooted the slave node (media2) and added both ports to team1 again (Have you tried turning it off and on again...). After doing this, I now see TX dropped packets on the not yet rebooted media1 team1 interface. Why do I only see these errors on the team1 interface and not on em3 and em4? Currently the copy process of 20TB is still running. I think that if I reboot media1 everything will work as expected again for some time because it worked during my initial tests. But I do think that I hit a bug in the teaming driver and the raising error counters will come back. Could anybody help? Kind regards Ingo This is the used network config of team1: media1: cat /etc/sysconfig/network-scripts/ifcfg-team1_slave_0 # Generated by parse-kickstart NAME=team1 slave 0 TEAM_MASTER=team1 DEVICETYPE=TeamPort DEVICE=em3 ONBOOT=yes UUID=b7026c5b-e9cd-457c-93d2-a2799361ed90 cat /etc/sysconfig/network-scripts/ifcfg-team1_slave_1 # Generated by parse-kickstart NAME=team1 slave 1 TEAM_MASTER=team1 DEVICETYPE=TeamPort DEVICE=em4 ONBOOT=yes UUID=fbe5bc56-95f5-4f9e-a5ea-ab6b6f5e5b50 cat /etc/sysconfig/network-scripts/ifcfg-team1 # Generated by parse-kickstart UUID=4e0090cd-32d3-4c5b-be23-9f53083da4dd NAME="Team connection team1" TEAM_CONFIG="{\"runner\": {\"name\": \"roundrobin\"}}" GATEWAY= IPV6_AUTOCONF=yes BOOTPROTO=none DEVICE=team1 MTU=9000 TYPE=Team ONBOOT=yes IPV6INIT=yes DEVICETYPE=Team IPADDR0=192.168.101.31 PREFIX0=24 DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_FAILURE_FATAL=no media2: cat /etc/sysconfig/network-scripts/ifcfg-team1_slave_0 # Generated by parse-kickstart NAME=team1 slave 0 TEAM_MASTER=team1 DEVICETYPE=TeamPort DEVICE=em3 ONBOOT=yes UUID=bfd8e77e-7eb8-47ea-ab7e-95286e073202 cat /etc/sysconfig/network-scripts/ifcfg-team1_slave_1 # Generated by parse-kickstart NAME=team1 slave 1 TEAM_MASTER=team1 DEVICETYPE=TeamPort DEVICE=em4 ONBOOT=yes UUID=93c5dfd8-3b81-4d1e-8ba9-c46f8daceb1a cat /etc/sysconfig/network-scripts/ifcfg-team1 # Generated by parse-kickstart UUID=79c843db-996c-41e4-9ee5-2a8f3da244ed NAME="Team connection team1" TEAM_CONFIG="{\"runner\": {\"name\": \"roundrobin\"}}" GATEWAY= IPV6_AUTOCONF=yes BOOTPROTO=none DEVICE=team1 MTU=9000 TYPE=Team ONBOOT=yes IPV6INIT=yes DEVICETYPE=Team IPADDR0=192.168.101.32 PREFIX0=24 DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_FAILURE_FATAL=no Here are some system logs from both machines: ============================================================ media1: ============================================================ Nov 6 02:31:27 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412041 iface 192.168.100.31 to [1 of 10] Nov 6 02:31:29 media1 corosync[3657]: [TOTEM ] ring 0 active with no faults Nov 6 02:31:29 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412047 iface 192.168.100.31 to [1 of 10] Nov 6 02:31:31 media1 corosync[3657]: [TOTEM ] ring 0 active with no faults Nov 6 02:32:51 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412315 iface 192.168.101.31 to [1 of 10] Nov 6 02:32:53 media1 corosync[3657]: [TOTEM ] ring 1 active with no faults Nov 6 02:32:53 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412319 iface 192.168.101.31 to [1 of 10] Nov 6 02:32:54 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412321 iface 192.168.101.31 to [2 of 10] Nov 6 02:32:55 media1 corosync[3657]: [TOTEM ] Decrementing problem counter for iface 192.168.101.31 to [1 of 10] Nov 6 02:32:56 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412325 iface 192.168.101.31 to [2 of 10] Nov 6 02:32:57 media1 corosync[3657]: [TOTEM ] Decrementing problem counter for iface 192.168.101.31 to [1 of 10] Nov 6 02:32:58 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412327 iface 192.168.101.31 to [2 of 10] Nov 6 02:32:59 media1 kernel: drbd r0: PingAck did not arrive in time. Nov 6 02:32:59 media1 kernel: drbd r0: peer( Secondary -> Unknown ) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown ) Nov 6 02:32:59 media1 kernel: block drbd0: new current UUID 0C0308FA4F94F811:59E43E5FD7B26A4F:1963884285B385E6:1962884285B385E6 Nov 6 02:32:59 media1 kernel: drbd r0: asender terminated Nov 6 02:32:59 media1 kernel: drbd r0: Terminating drbd_a_r0 Nov 6 02:32:59 media1 kernel: drbd r0: Connection closed Nov 6 02:32:59 media1 kernel: drbd r0: conn( NetworkFailure -> Unconnected ) Nov 6 02:32:59 media1 kernel: drbd r0: receiver terminated Nov 6 02:32:59 media1 kernel: drbd r0: Restarting receiver thread Nov 6 02:32:59 media1 kernel: drbd r0: receiver (re)started Nov 6 02:32:59 media1 kernel: drbd r0: conn( Unconnected -> WFConnection ) Nov 6 02:32:59 media1 corosync[3657]: [TOTEM ] Decrementing problem counter for iface 192.168.101.31 to [1 of 10] Nov 6 02:32:59 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412329 iface 192.168.101.31 to [2 of 10] Nov 6 02:33:01 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412333 iface 192.168.101.31 to [3 of 10] Nov 6 02:33:01 media1 corosync[3657]: [TOTEM ] Decrementing problem counter for iface 192.168.101.31 to [2 of 10] Nov 6 02:33:01 media1 crmd[4960]: notice: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL origin=abort_transition_graph ] Nov 6 02:33:01 media1 pengine[4959]: notice: unpack_config: On loss of CCM Quorum: Ignore Nov 6 02:33:01 media1 pengine[4959]: warning: unpack_rsc_op: Processing failed op monitor for res_nfsserver_mediafiles on media1: unknown error (1) Nov 6 02:33:01 media1 pengine[4959]: warning: unpack_rsc_op: Processing failed op monitor for res_nfsserver_mediafiles on media2: unknown error (1) Nov 6 02:33:01 media1 pengine[4959]: notice: process_pe_message: Calculated Transition 144: /var/lib/pacemaker/pengine/pe-input-227.bz2 Nov 6 02:33:01 media1 crmd[4960]: notice: run_graph: Transition 144 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-227.bz2): Complete Nov 6 02:33:01 media1 crmd[4960]: notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ] Nov 6 02:33:01 media1 kernel: drbd r0: Handshake successful: Agreed network protocol version 101 Nov 6 02:33:01 media1 kernel: drbd r0: Agreed to support TRIM on protocol level Nov 6 02:33:01 media1 kernel: drbd r0: Peer authenticated using 20 bytes HMAC Nov 6 02:33:01 media1 kernel: drbd r0: conn( WFConnection -> WFReportParams ) Nov 6 02:33:01 media1 kernel: drbd r0: Starting asender thread (from drbd_r_r0 [5999]) Nov 6 02:33:02 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412337 iface 192.168.101.31 to [3 of 10] Nov 6 02:33:02 media1 kernel: block drbd0: drbd_sync_handshake: Nov 6 02:33:02 media1 kernel: block drbd0: self 0C0308FA4F94F811:59E43E5FD7B26A4F:1963884285B385E6:1962884285B385E6 bits:192101 flags:0 Nov 6 02:33:02 media1 kernel: block drbd0: peer 59E43E5FD7B26A4E:0000000000000000:1963884285B385E6:1962884285B385E6 bits:0 flags:0 Nov 6 02:33:02 media1 kernel: block drbd0: uuid_compare()=1 by rule 70 Nov 6 02:33:02 media1 kernel: block drbd0: peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapS ) pdsk( DUnknown -> Consistent ) Nov 6 02:33:02 media1 kernel: block drbd0: send bitmap stats [Bytes(packets)]: plain 0(0), RLE 185(1), total 185; compression: 100.0% Nov 6 02:33:02 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412339 iface 192.168.101.31 to [4 of 10] Nov 6 02:33:03 media1 kernel: block drbd0: receive bitmap stats [Bytes(packets)]: plain 0(0), RLE 185(1), total 185; compression: 100.0% Nov 6 02:33:03 media1 kernel: block drbd0: helper command: /sbin/drbdadm before-resync-source minor-0 Nov 6 02:33:03 media1 kernel: block drbd0: helper command: /sbin/drbdadm before-resync-source minor-0 exit code 0 (0x0) Nov 6 02:33:03 media1 kernel: block drbd0: conn( WFBitMapS -> SyncSource ) pdsk( Consistent -> Inconsistent ) Nov 6 02:33:03 media1 kernel: block drbd0: Began resync as SyncSource (will sync 919244 KB [229811 bits set]). Nov 6 02:33:03 media1 kernel: block drbd0: updated sync UUID 0C0308FA4F94F811:59E53E5FD7B26A4F:59E43E5FD7B26A4F:1963884285B385E6 Nov 6 02:33:03 media1 corosync[3657]: [TOTEM ] Decrementing problem counter for iface 192.168.101.31 to [3 of 10] Nov 6 02:33:03 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412343 iface 192.168.101.31 to [4 of 10] Nov 6 02:33:04 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412345 iface 192.168.101.31 to [5 of 10] Nov 6 02:33:05 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412347 iface 192.168.101.31 to [6 of 10] Nov 6 02:33:05 media1 corosync[3657]: [TOTEM ] Decrementing problem counter for iface 192.168.101.31 to [5 of 10] Nov 6 02:33:05 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412349 iface 192.168.101.31 to [6 of 10] Nov 6 02:33:06 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412351 iface 192.168.101.31 to [7 of 10] Nov 6 02:33:07 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412355 iface 192.168.101.31 to [8 of 10] Nov 6 02:33:07 media1 corosync[3657]: [TOTEM ] Decrementing problem counter for iface 192.168.101.31 to [7 of 10] Nov 6 02:33:07 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412357 iface 192.168.101.31 to [8 of 10] Nov 6 02:33:08 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412361 iface 192.168.101.31 to [9 of 10] Nov 6 02:33:09 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412363 iface 192.168.101.31 to [10 of 10] Nov 6 02:33:09 media1 corosync[3657]: [TOTEM ] Marking seqid 412363 ringid 1 interface 192.168.101.31 FAULTY Nov 6 02:33:11 media1 crmd[4960]: notice: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL origin=abort_transition_graph ] Nov 6 02:33:11 media1 pengine[4959]: notice: unpack_config: On loss of CCM Quorum: Ignore Nov 6 02:33:11 media1 pengine[4959]: warning: unpack_rsc_op: Processing failed op monitor for res_nfsserver_mediafiles on media1: unknown error (1) Nov 6 02:33:11 media1 pengine[4959]: warning: unpack_rsc_op: Processing failed op monitor for res_nfsserver_mediafiles on media2: unknown error (1) Nov 6 02:33:11 media1 pengine[4959]: notice: process_pe_message: Calculated Transition 145: /var/lib/pacemaker/pengine/pe-input-228.bz2 Nov 6 02:33:11 media1 crmd[4960]: notice: run_graph: Transition 145 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-228.bz2): Complete Nov 6 02:33:11 media1 crmd[4960]: notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ] Nov 6 02:33:17 media1 corosync[3657]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:18 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412387 iface 192.168.101.31 to [1 of 10] Nov 6 02:33:20 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412389 iface 192.168.101.31 to [2 of 10] Nov 6 02:33:20 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412391 iface 192.168.101.31 to [3 of 10] Nov 6 02:33:21 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412393 iface 192.168.101.31 to [4 of 10] Nov 6 02:33:22 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412397 iface 192.168.101.31 to [5 of 10] Nov 6 02:33:22 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412399 iface 192.168.101.31 to [6 of 10] Nov 6 02:33:24 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412403 iface 192.168.101.31 to [7 of 10] Nov 6 02:33:31 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412421 iface 192.168.101.31 to [8 of 10] Nov 6 02:33:32 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412423 iface 192.168.101.31 to [9 of 10] Nov 6 02:33:34 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412429 iface 192.168.101.31 to [10 of 10] Nov 6 02:33:34 media1 corosync[3657]: [TOTEM ] Marking seqid 412429 ringid 1 interface 192.168.101.31 FAULTY Nov 6 02:33:36 media1 corosync[3657]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:39 media1 corosync[3657]: [TOTEM ] Incrementing problem counter for seqid 412437 iface 192.168.101.31 to [1 of 10] ============================================================ media2: ============================================================ Nov 6 02:32:59 media2 kernel: drbd r0: sock was shut down by peer Nov 6 02:32:59 media2 kernel: drbd r0: peer( Primary -> Unknown ) conn( Connected -> BrokenPipe ) pdsk( UpToDate -> DUnknown ) Nov 6 02:32:59 media2 kernel: drbd r0: short read (expected size 16) Nov 6 02:32:59 media2 kernel: drbd r0: asender terminated Nov 6 02:32:59 media2 kernel: drbd r0: Terminating drbd_a_r0 Nov 6 02:32:59 media2 kernel: drbd r0: Connection closed Nov 6 02:32:59 media2 kernel: drbd r0: conn( BrokenPipe -> Unconnected ) Nov 6 02:32:59 media2 kernel: drbd r0: receiver terminated Nov 6 02:32:59 media2 kernel: drbd r0: Restarting receiver thread Nov 6 02:32:59 media2 kernel: drbd r0: receiver (re)started Nov 6 02:32:59 media2 kernel: drbd r0: conn( Unconnected -> WFConnection ) Nov 6 02:33:01 media2 attrd[4940]: notice: attrd_trigger_update: Sending flush op to all hosts for: master-res_drbd_mediafiles (1000) Nov 6 02:33:01 media2 attrd[4940]: notice: attrd_perform_update: Sent update 16: master-res_drbd_mediafiles=1000 Nov 6 02:33:01 media2 kernel: drbd r0: Handshake successful: Agreed network protocol version 101 Nov 6 02:33:01 media2 kernel: drbd r0: Agreed to support TRIM on protocol level Nov 6 02:33:01 media2 kernel: drbd r0: Peer authenticated using 20 bytes HMAC Nov 6 02:33:01 media2 kernel: drbd r0: conn( WFConnection -> WFReportParams ) Nov 6 02:33:01 media2 kernel: drbd r0: Starting asender thread (from drbd_r_r0 [6367]) Nov 6 02:33:01 media2 kernel: block drbd0: drbd_sync_handshake: Nov 6 02:33:01 media2 kernel: block drbd0: self 59E43E5FD7B26A4E:0000000000000000:1963884285B385E6:1962884285B385E6 bits:0 flags:0 Nov 6 02:33:01 media2 kernel: block drbd0: peer 0C0308FA4F94F811:59E43E5FD7B26A4F:1963884285B385E6:1962884285B385E6 bits:192101 flags:0 Nov 6 02:33:01 media2 kernel: block drbd0: uuid_compare()=-1 by rule 50 Nov 6 02:33:01 media2 kernel: block drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) disk( UpToDate -> Outdated ) pdsk( DUnknown -> UpToDate ) Nov 6 02:33:02 media2 kernel: block drbd0: receive bitmap stats [Bytes(packets)]: plain 0(0), RLE 185(1), total 185; compression: 100.0% Nov 6 02:33:03 media2 kernel: block drbd0: send bitmap stats [Bytes(packets)]: plain 0(0), RLE 185(1), total 185; compression: 100.0% Nov 6 02:33:03 media2 kernel: block drbd0: conn( WFBitMapT -> WFSyncUUID ) Nov 6 02:33:03 media2 kernel: block drbd0: updated sync uuid 59E53E5FD7B26A4E:0000000000000000:1963884285B385E6:1962884285B385E6 Nov 6 02:33:03 media2 kernel: block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 Nov 6 02:33:03 media2 kernel: block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0) Nov 6 02:33:03 media2 kernel: block drbd0: conn( WFSyncUUID -> SyncTarget ) disk( Outdated -> Inconsistent ) Nov 6 02:33:03 media2 kernel: block drbd0: Began resync as SyncTarget (will sync 919244 KB [229811 bits set]). Nov 6 02:33:10 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412364 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:10 media2 corosync[3690]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:10 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412366 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:11 media2 corosync[3690]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:11 media2 attrd[4940]: notice: attrd_trigger_update: Sending flush op to all hosts for: master-res_drbd_mediafiles (10) Nov 6 02:33:11 media2 attrd[4940]: notice: attrd_perform_update: Sent update 18: master-res_drbd_mediafiles=10 Nov 6 02:33:11 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412368 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:12 media2 corosync[3690]: [TOTEM ] ring 1 active with no faults Nov 6 02:33:12 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412370 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:12 media2 corosync[3690]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:12 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412372 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:13 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412374 iface 192.168.101.32 to [2 of 10] Nov 6 02:33:14 media2 corosync[3690]: [TOTEM ] Decrementing problem counter for iface 192.168.101.32 to [1 of 10] Nov 6 02:33:14 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412376 iface 192.168.101.32 to [2 of 10] Nov 6 02:33:15 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412378 iface 192.168.101.32 to [3 of 10] Nov 6 02:33:15 media2 corosync[3690]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:15 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412380 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:16 media2 corosync[3690]: [TOTEM ] ring 1 active with no faults Nov 6 02:33:16 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412382 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:16 media2 corosync[3690]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:17 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412384 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:17 media2 corosync[3690]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:17 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412386 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:18 media2 corosync[3690]: [TOTEM ] ring 1 active with no faults Nov 6 02:33:19 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412388 iface 192.168.100.32 to [1 of 10] Nov 6 02:33:20 media2 corosync[3690]: [TOTEM ] ring 0 active with no faults Nov 6 02:33:35 media2 corosync[3690]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:36 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412430 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:36 media2 corosync[3690]: [TOTEM ] Automatically recovered ring 1 Nov 6 02:33:37 media2 corosync[3690]: [TOTEM ] Incrementing problem counter for seqid 412432 iface 192.168.101.32 to [1 of 10] Nov 6 02:33:38 media2 corosync[3690]: [TOTEM ] ring 1 active with no faults

3 7

[jpirko/libteam] 336eb7: teamd: loadbalance mode lacks a .hwaddr_changed in...
by GitHub 31 Aug '15

31 Aug '15

Branch: refs/heads/master Home: https://github.com/jpirko/libteam Commit: 336eb7b92b9413a7598b5ac7c4a755ba258e697f https://github.com/jpirko/libteam/commit/336eb7b92b9413a7598b5ac7c4a755ba25… Author: Xin Long <lucien.xin(a)gmail.com> Date: 2015-08-31 (Mon, 31 Aug 2015) Changed paths: M teamd/teamd_runner_loadbalance.c Log Message: ----------- teamd: loadbalance mode lacks a .hwaddr_changed in teamd_event_watch_ops commit 01c1e7888cd9 ("teamd: do not change ctx->hwaddr pointer") make the first iface's mac is not same with the team: eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 26:29:fa:60:f0:ea txqueuelen 1000 (Ethernet) <--- eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:a4:f3:8c:47:d6 txqueuelen 1000 (Ethernet) team0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:a4:f3:8c:47:d6 txqueuelen 0 (Ethernet) <--- when we add the first iface to team0, three watch events will be triggerred in teamd: 1.teamd_event_watch_port_added. team0's mac will be updated with eth1's mac in teamd_hwaddr_check_change(), besides, ctx->hwaddr will not be update by this mac any more, it still keep the original team mac. 2.port_priv_change_handler_func. .port_added() of loadbalance will update eth1's mac with ctx->hwaddr. that's why eth1's mac is different from team0's. but for lacp and activebackup, they both has .hwaddr_changed(). when another watch event comes: 3. teamd_event_ifinf_hwaddr_changed: the eth1's mac will be update with team0's mac, now they have the same macs. for broadcast, roundrobin, and random, they don't have neither .port_added() nor .hwaddr_changed(), so the macs of team0 and eth1 are consistent. we can fix it by adding a .hwaddr_changed for loadbalance mode. Fixes: 01c1e7888cd9 ("teamd: do not change ctx->hwaddr pointer") Signed-off-by: Xin Long <lucien.xin(a)gmail.com> Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>

1 0

[PATCH libteam] teamd: loadbalance mode lacks a .hwaddr_changed in teamd_event_watch_ops
by Xin Long 31 Aug '15

31 Aug '15

From: root <root(a)dhcp12-119.nay.redhat.com> commit 01c1e7888cd9 ("teamd: do not change ctx->hwaddr pointer") make the first iface's mac is not same with the team: eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 26:29:fa:60:f0:ea txqueuelen 1000 (Ethernet) <--- eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:a4:f3:8c:47:d6 txqueuelen 1000 (Ethernet) team0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:a4:f3:8c:47:d6 txqueuelen 0 (Ethernet) <--- when we add the first iface to team0, three watch events will be triggerred in teamd: 1.teamd_event_watch_port_added. team0's mac will be updated with eth1's mac in teamd_hwaddr_check_change(), besides, ctx->hwaddr will not be update by this mac any more, it still keep the original team mac. 2.port_priv_change_handler_func. .port_added() of loadbalance will update eth1's mac with ctx->hwaddr. that's why eth1's mac is different from team0's. but for lacp and activebackup, they both has .hwaddr_changed(). when another watch event comes: 3. teamd_event_ifinf_hwaddr_changed: the eth1's mac will be update with team0's mac, now they have the same macs. for broadcast, roundrobin, and random, they don't have neither .port_added() nor .hwaddr_changed(), so the macs of team0 and eth1 are consistent. we can fix it by adding a .hwaddr_changed for loadbalance mode. Fixes: Commit 01c1e7888cd9 ("teamd: do not change ctx->hwaddr pointer") Signed-off-by: Xin Long <lucien.xin(a)gmail.com> --- teamd/teamd_runner_loadbalance.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/teamd/teamd_runner_loadbalance.c b/teamd/teamd_runner_loadbalance.c index f98c0fe..43b07af 100644 --- a/teamd/teamd_runner_loadbalance.c +++ b/teamd/teamd_runner_loadbalance.c @@ -60,7 +60,26 @@ static int lb_event_watch_port_link_changed(struct teamd_context *ctx, return teamd_port_check_enable(ctx, tdport, port_up, !port_up); } +static int lb_event_watch_hwaddr_changed(struct teamd_context *ctx, void *priv) +{ + struct teamd_port *tdport; + int err; + + teamd_for_each_tdport(tdport, ctx) { + err = team_hwaddr_set(ctx->th, tdport->ifindex, ctx->hwaddr, + ctx->hwaddr_len); + if (err) { + teamd_log_err("%s: Failed to set port hardware address.", + tdport->ifname); + return err; + } + } + + return 0; +} + static const struct teamd_event_watch_ops lb_port_watch_ops = { + .hwaddr_changed = lb_event_watch_hwaddr_changed, .port_added = lb_event_watch_port_added, .port_removed = lb_event_watch_port_removed, .port_link_changed = lb_event_watch_port_link_changed, -- 2.1.0

2 1

LACP frames sent even when 'team' down
by Samudrala, Sridhar 30 Aug '15

30 Aug '15

I am seeing that LACP frames are sent even when the master 'team' device is down, but the member ports are UP. Is this a bug or expected behavior? Thanks Sridhar

2 3

[patch libteam] libteamdctl: fix timeval value for select
by Marcelo Ricardo Leitner 28 Aug '15

28 Aug '15

timeval.tv_usec shouldn't be bigger than 10^6, as then it overlaps .tv_sec. The fix is to normalize the fields regarding their resolutions. Fixes: 7824c18d65ab ("libteamdctl: increase usock timeout to 5secs") Reported-by: Vitezslav Humpa <vhumpa(a)redhat.com> Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner(a)gmail.com> --- libteamdctl/cli_usock.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/libteamdctl/cli_usock.c b/libteamdctl/cli_usock.c index 0136d6909ea620584b6ee9f42917481f642f7761..0dc97ae53f89931a7854a5218d9f6cbdd9e84495 100644 --- a/libteamdctl/cli_usock.c +++ b/libteamdctl/cli_usock.c @@ -79,7 +79,8 @@ static int cli_usock_send(int sock, char *msg) return 0; } -#define WAIT_USEC (TEAMDCTL_REPLY_TIMEOUT * 1000) +#define WAIT_SEC (TEAMDCTL_REPLY_TIMEOUT / 1000) +#define WAIT_USEC (TEAMDCTL_REPLY_TIMEOUT % 1000 * 1000) static int cli_usock_wait_recv(int sock) { @@ -88,7 +89,7 @@ static int cli_usock_wait_recv(int sock) int ret; struct timeval tv; - tv.tv_sec = 0; + tv.tv_sec = WAIT_SEC; tv.tv_usec = WAIT_USEC; FD_ZERO(&rfds); FD_SET(sock, &rfds); -- 2.4.3

3 2

[jpirko/libteam] 5b538c: libteamdctl: fix timeval value for select
by GitHub 28 Aug '15

28 Aug '15

Branch: refs/heads/master Home: https://github.com/jpirko/libteam Commit: 5b538c0ef22dd9e42513bf2c137e3efca24e807c https://github.com/jpirko/libteam/commit/5b538c0ef22dd9e42513bf2c137e3efca2… Author: Marcelo Ricardo Leitner <marcelo.leitner(a)gmail.com> Date: 2015-08-28 (Fri, 28 Aug 2015) Changed paths: M libteamdctl/cli_usock.c Log Message: ----------- libteamdctl: fix timeval value for select timeval.tv_usec shouldn't be bigger than 10^6, as then it overlaps .tv_sec. The fix is to normalize the fields regarding their resolutions. Fixes: 7824c18d65ab ("libteamdctl: increase usock timeout to 5secs") Reported-by: Vitezslav Humpa <vhumpa(a)redhat.com> Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner(a)gmail.com> Acked-by: Flavio Leitner <fbl(a)sysclose.org> Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>

1 0

[jpirko/libteam] 42fc89: add v1.18 tarball
by GitHub 21 Aug '15

21 Aug '15

Branch: refs/heads/gh-pages Home: https://github.com/jpirko/libteam Commit: 42fc89ca4c33c73114725e541a0e555d7c25b6bd https://github.com/jpirko/libteam/commit/42fc89ca4c33c73114725e541a0e555d7c… Author: Jiri Pirko <jiri(a)resnulli.us> Date: 2015-08-21 (Fri, 21 Aug 2015) Changed paths: A files/libteam-1.18.tar.gz M files/libteam-latest.tar.gz M index.html Log Message: ----------- add v1.18 tarball Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>

1 0

[jpirko/libteam]
by GitHub 21 Aug '15

21 Aug '15

Branch: refs/tags/v1.18 Home: https://github.com/jpirko/libteam

1 0

[jpirko/libteam] 5fbefd: 1.18 release
by GitHub 21 Aug '15

21 Aug '15

Branch: refs/heads/master Home: https://github.com/jpirko/libteam Commit: 5fbefdd17831a4ae54cbc8a777786c331660988c https://github.com/jpirko/libteam/commit/5fbefdd17831a4ae54cbc8a777786c3316… Author: Jiri Pirko <jiri(a)resnulli.us> Date: 2015-08-21 (Fri, 21 Aug 2015) Changed paths: M configure.ac Log Message: ----------- 1.18 release Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>

1 0

[jpirko/libteam] 4f58d7: teamd: lacp: change actor system value on team mac...
by GitHub 21 Aug '15

21 Aug '15

Branch: refs/heads/master Home: https://github.com/jpirko/libteam Commit: 4f58d76ea4956feec009002f5faba9f9d8391fee https://github.com/jpirko/libteam/commit/4f58d76ea4956feec009002f5faba9f9d8… Author: Jiri Pirko <jiri(a)resnulli.us> Date: 2015-08-15 (Sat, 15 Aug 2015) Changed paths: M teamd/teamd_runner_lacp.c Log Message: ----------- teamd: lacp: change actor system value on team mac change It is needed to reflect mac address change of team device on the actor->system values of ports. Also, on the way, fix couple of whitespace issues and use lacp_port_set_mac for port mac change. Reported-by: Amit Supugade <asupugad(a)redhat.com> Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

libteam August 2015