libteam October 2015

libteam@lists.fedorahosted.org

8 participants
20 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

[PATCH libteam] dbus: don't do <deny send_interface="..." /> in dbus service file
by Lubomir Rintel 26 Oct '15

26 Oct '15

It does more than intended; apart from denying messages to that particular interface it also denies all messages non-qualified with an interface globally. >From the dbus-daemon manual: Be careful with send_interface/receive_interface, because the interface field in messages is optional. In particular, do NOT specify <deny send_interface="org.foo.Bar"/>! This will cause no-interface messages to be blocked for all services, which is almost certainly not what you intended. Always use rules of the form: <deny send_interface="org.foo.Bar" send_destination="org.foo.Service"/> We can just safely remove those rules, since we're sufficiently protected by the send_destination matches and method calls are disallowed by default anyway. Signed-off-by: Lubomir Rintel <lkundrak(a)v3.sk> --- teamd/dbus/teamd.conf | 1 - teamd/teamd.conf.in | 1 - 2 files changed, 2 deletions(-) diff --git a/teamd/dbus/teamd.conf b/teamd/dbus/teamd.conf index c395ea7..20366ea 100644 --- a/teamd/dbus/teamd.conf +++ b/teamd/dbus/teamd.conf @@ -8,6 +8,5 @@ </policy> <policy context="default"> <deny own_prefix="org.libteam.teamd"/> - <deny send_interface="org.libteam.teamd"/> </policy> </busconfig> diff --git a/teamd/teamd.conf.in b/teamd/teamd.conf.in index d1cb2a1..f4e3017 100644 --- a/teamd/teamd.conf.in +++ b/teamd/teamd.conf.in @@ -12,6 +12,5 @@ </policy> <policy context="default"> <deny own_prefix="org.libteam.teamd"/> - <deny send_interface="org.libteam.teamd"/> </policy> </busconfig> -- 2.4.3

2 1

[jpirko/libteam] cf24f9: dbus: don't do <deny send_interface="..." /> in db...
by GitHub 26 Oct '15

26 Oct '15

Branch: refs/heads/master Home: https://github.com/jpirko/libteam Commit: cf24f96afb338dcd223db5bfbefab66f4f9107d0 https://github.com/jpirko/libteam/commit/cf24f96afb338dcd223db5bfbefab66f4f… Author: Lubomir Rintel <lkundrak(a)v3.sk> Date: 2015-10-26 (Mon, 26 Oct 2015) Changed paths: M teamd/dbus/teamd.conf M teamd/teamd.conf.in Log Message: ----------- dbus: don't do <deny send_interface="..." /> in dbus service file It does more than intended; apart from denying messages to that particular interface it also denies all messages non-qualified with an interface globally. >From the dbus-daemon manual: Be careful with send_interface/receive_interface, because the interface field in messages is optional. In particular, do NOT specify <deny send_interface="org.foo.Bar"/>! This will cause no-interface messages to be blocked for all services, which is almost certainly not what you intended. Always use rules of the form: <deny send_interface="org.foo.Bar" send_destination="org.foo.Service"/> We can just safely remove those rules, since we're sufficiently protected by the send_destination matches and method calls are disallowed by default anyway. Signed-off-by: Lubomir Rintel <lkundrak(a)v3.sk> Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>

1 0

teaming daemon not starting after reboot
by Chris Card 19 Oct '15

19 Oct '15

Hi, We are seeing occasionally seeing issues with the teaming daemon not starting after a reboot on centos 7 VMs. Here is an example from last night (from /var/log/messages.minor): Oct 6 23:36:21 ****** ovs-ctl[623]: Starting ovsdb-server [ OK ] Oct 6 23:36:22 ****** ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait -- init -- set Open_vSwitch . db-version=7.6.2 Oct 6 23:36:22 ****** ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait set Open_vSwitch . ovs-version=2.3.1 "external-ids:system-id=\"47ff9309-5609-47e0-819c-b9055b25edbb\"" "system-type=\"CentOS\"" "system-version=\"7.1.1503-Core\"" Oct 6 23:36:22 ****** ovs-ctl[623]: Configuring Open vSwitch system IDs [ OK ] Oct 6 23:36:22 ****** network[733]: Bringing up loopback interface: [ OK ] Oct 6 23:36:22 ****** kernel: [ 6.158533] gre: GRE over IPv4 demultiplexor driver Oct 6 23:36:22 ****** systemd[1]: Starting system-teamd.slice. Oct 6 23:36:22 ****** systemd[1]: Created slice system-teamd.slice. Oct 6 23:36:22 ****** systemd[1]: Starting Team Daemon for device bond0... Oct 6 23:36:22 ****** kernel: [ 6.199635] openvswitch: Open vSwitch switching datapath Oct 6 23:36:22 ****** ovs-ctl[623]: Inserting openvswitch module [ OK ] Oct 6 23:36:22 ****** kernel: [ 6.338577] device ovs-system entered promiscuous mode Oct 6 23:36:22 ****** kernel: [ 6.340086] openvswitch: netlink: Unknown key attribute (type=62, max=21). Oct 6 23:36:22 ****** kernel: [ 6.385293] device br-ex entered promiscuous mode Oct 6 23:36:22 ****** kernel: [ 6.426511] device br-int entered promiscuous mode Oct 6 23:36:22 ****** teamd[857]: Failed to get interface information list. Oct 6 23:36:22 ****** teamd[857]: Failed to init interface information list. Oct 6 23:36:22 ****** teamd[857]: Team init failed. Oct 6 23:36:22 ****** teamd[857]: teamd_init() failed. Oct 6 23:36:22 ****** teamd[857]: Failed: Invalid argument Oct 6 23:36:22 ****** systemd[1]: teamd(a)bond0.service: main process exited, code=exited, status=1/FAILURE Oct 6 23:36:22 ****** network[733]: Bringing up interface bond0: Job for teamd(a)bond0.service failed. See 'systemctl status teamd(a)bond0.service' and 'journalctl -xn' for details. Oct 6 23:36:22 ****** kernel: [ 6.433515] device br-tun entered promiscuous mode Oct 6 23:36:22 ****** systemd[1]: Unit teamd(a)bond0.service entered failed state. Oct 6 23:36:22 ****** ovs-ctl[623]: Starting ovs-vswitchd [ OK ] Oct 6 23:36:22 ****** network[733]: [FAILED] Oct 6 23:36:22 ****** ovs-ctl[623]: Enabling remote OVSDB managers [ OK ] Is this a known issue? Chris

3 11

[PATCH] teamd: Fix member port state change on master team admin UP.
by Samudrala, Sridhar 12 Oct '15

12 Oct '15

commit beb831fdc19195aecb365c4b48b6d8451c59251c caused member ports state to be changed to CURRENT when master team device is brought UP. This is not correct as the partner may still be DOWN. Set it to EXPIRIED and let the state go CURRENT after receiving a LACPDU from the partner. Signed-off-by: Sridhar Samudrala <sridhar.samudrala(a)intel.com> --- teamd/teamd_runner_lacp.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/teamd/teamd_runner_lacp.c b/teamd/teamd_runner_lacp.c index 1cfef36..1af3b17 100644 --- a/teamd/teamd_runner_lacp.c +++ b/teamd/teamd_runner_lacp.c @@ -1314,12 +1314,13 @@ static int lacp_event_watch_admin_state_changed(struct teamd_context *ctx, bool admin_state; int err; + admin_state = team_get_ifinfo_admin_state(ctx->ifinfo); + teamd_for_each_tdport(tdport, ctx) { struct lacp_port *lacp_port = lacp_port_get(lacp, tdport); - admin_state = team_get_ifinfo_admin_state(ctx->ifinfo); err = lacp_port_set_state(lacp_port, - admin_state?PORT_STATE_CURRENT:PORT_STATE_DISABLED); + admin_state?PORT_STATE_EXPIRED:PORT_STATE_DISABLED); if (err) return err; } -- 2.1.0

2 1

[jpirko/libteam] 2a8cad: teamd: Fix member port state change on master team...
by GitHub 12 Oct '15

12 Oct '15

Branch: refs/heads/master Home: https://github.com/jpirko/libteam Commit: 2a8cadd5a72ae8c02a3637236fd92d57d2c484aa https://github.com/jpirko/libteam/commit/2a8cadd5a72ae8c02a3637236fd92d57d2… Author: Sridhar Samudrala <sridhar.samudrala(a)intel.com> Date: 2015-10-12 (Mon, 12 Oct 2015) Changed paths: M teamd/teamd_runner_lacp.c Log Message: ----------- teamd: Fix member port state change on master team admin UP. commit beb831fdc19195aecb365c4b48b6d8451c59251c caused member ports state to be changed to CURRENT when master team device is brought UP. This is not correct as the partner may still be DOWN. Set it to EXPIRIED and let the state go CURRENT after receiving a LACPDU from the partner. Fixes: 61fd9e61fd ("teamd: Fix member port state change on master team admin UP.") Signed-off-by: Sridhar Samudrala <sridhar.samudrala(a)intel.com> Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>

1 0

[jpirko/libteam] 49fa51: teamd: add CAP_NET_RAW capability for LACP packet ...
by GitHub 06 Oct '15

06 Oct '15

Branch: refs/heads/master Home: https://github.com/jpirko/libteam Commit: 49fa51c1e486a7b998840fd90e45926029c2a607 https://github.com/jpirko/libteam/commit/49fa51c1e486a7b998840fd90e45926029… Author: Pawel Wieczorkiewicz <pwieczorkiewicz(a)suse.de> Date: 2015-10-06 (Tue, 06 Oct 2015) Changed paths: M teamd/teamd.c Log Message: ----------- teamd: add CAP_NET_RAW capability for LACP packet sockets The CAP_NET_RAW capability is needed in order to facilitate socket(PF_PACKET...) calls (see: packet(7)), which are used within teamd_packet_sock_open() function. Without the CAP_NET_RAW capability, teamd running as non-root user is unable to add lacp ports. Signed-off-by: Pawel Wieczorkiewicz <pwieczorkiewicz(a)suse.de> Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>

1 0

[PATCH] teamd: add CAP_NET_RAW capability for LACP packet sockets
by Pawel Wieczorkiewicz 06 Oct '15

06 Oct '15

The CAP_NET_RAW capability is needed in order to facilitate socket(PF_PACKET...) calls (see: packet(7)), which are used within teamd_packet_sock_open() function. Without the CAP_NET_RAW capability, teamd running as non-root user is unable to add lacp ports. Signed-off-by: Pawel Wieczorkiewicz <pwieczorkiewicz(a)suse.de> --- teamd/teamd.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/teamd/teamd.c b/teamd/teamd.c index 391b981..aac2511 100644 --- a/teamd/teamd.c +++ b/teamd/teamd.c @@ -1681,7 +1681,7 @@ static void teamd_context_fini(struct teamd_context *ctx) static int teamd_drop_privileges() { - cap_value_t cv[] = {CAP_NET_ADMIN, CAP_NET_BIND_SERVICE}; + cap_value_t cv[] = {CAP_NET_ADMIN, CAP_NET_BIND_SERVICE, CAP_NET_RAW}; cap_t my_caps; struct passwd *pw = NULL; struct group *grpent = NULL; @@ -1731,9 +1731,9 @@ static int teamd_drop_privileges() if ((my_caps = cap_init()) == NULL) goto error; - if (cap_set_flag(my_caps, CAP_EFFECTIVE, 2, cv, CAP_SET) < 0) + if (cap_set_flag(my_caps, CAP_EFFECTIVE, ARRAY_SIZE(cv), cv, CAP_SET) < 0) goto error; - if (cap_set_flag(my_caps, CAP_PERMITTED, 2, cv, CAP_SET) < 0) + if (cap_set_flag(my_caps, CAP_PERMITTED, ARRAY_SIZE(cv), cv, CAP_SET) < 0) goto error; if (cap_set_proc(my_caps) < 0) goto error; -- 2.1.4

2 1

[PATCH] teamd: add CAP_NET_RAW capability for LACP packet sockets
by Pawel Wieczorkiewicz 06 Oct '15

06 Oct '15

Signed-off-by: Pawel Wieczorkiewicz <pwieczorkiewicz(a)suse.de> --- teamd/teamd.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/teamd/teamd.c b/teamd/teamd.c index 391b981..aac2511 100644 --- a/teamd/teamd.c +++ b/teamd/teamd.c @@ -1681,7 +1681,7 @@ static void teamd_context_fini(struct teamd_context *ctx) static int teamd_drop_privileges() { - cap_value_t cv[] = {CAP_NET_ADMIN, CAP_NET_BIND_SERVICE}; + cap_value_t cv[] = {CAP_NET_ADMIN, CAP_NET_BIND_SERVICE, CAP_NET_RAW}; cap_t my_caps; struct passwd *pw = NULL; struct group *grpent = NULL; @@ -1731,9 +1731,9 @@ static int teamd_drop_privileges() if ((my_caps = cap_init()) == NULL) goto error; - if (cap_set_flag(my_caps, CAP_EFFECTIVE, 2, cv, CAP_SET) < 0) + if (cap_set_flag(my_caps, CAP_EFFECTIVE, ARRAY_SIZE(cv), cv, CAP_SET) < 0) goto error; - if (cap_set_flag(my_caps, CAP_PERMITTED, 2, cv, CAP_SET) < 0) + if (cap_set_flag(my_caps, CAP_PERMITTED, ARRAY_SIZE(cv), cv, CAP_SET) < 0) goto error; if (cap_set_proc(my_caps) < 0) goto error; -- 2.1.4

2 3

[jpirko/libteam] e18689: add teamd.conf.in to EXTRA_DIST
by GitHub 05 Oct '15

05 Oct '15

Branch: refs/heads/master Home: https://github.com/jpirko/libteam Commit: e18689c59f5143be07ff47189f27d7cddac76046 https://github.com/jpirko/libteam/commit/e18689c59f5143be07ff47189f27d7cdda… Author: Pawel Wieczorkiewicz <pwieczorkiewicz(a)suse.de> Date: 2015-10-05 (Mon, 05 Oct 2015) Changed paths: M teamd/Makefile.am Log Message: ----------- add teamd.conf.in to EXTRA_DIST Signed-off-by: Pawel Wieczorkiewicz <pwieczorkiewicz(a)suse.de> 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 October 2015