Re: f32:: teamd process takes 100% cput - libteam bug, solved in 1.31

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/11/20 1:43 PM, Ed Greshko wrote:
On 11/11/2020 19:10, Adrian Sevcenco wrote:
On 11/11/20 10:22 AM, Adrian Sevcenco wrote:
Hi! I have a strange situation where my teamd process take 100% processor without having any kind of traffic (beside my ssh connection)

I thought that is a NM problem and i disabled the connectivity check of NM .. does anyone encountered this and have any idea of the problem?
so, i found what is going on:
https://bugzilla.redhat.com/show_bug.cgi?id=1874001

are there any plans to re-build/update the team packages?
i see that there is none in testing ...

A bit more.....

The BZ you reference says....
so, now it appeared in updates and after upgrade it seems that the bug is not solved, and after a fresh reboot i see this :

[root@vbox1 ~]# ps -C teamd -o pid,pcpu,pmem,cmd
    PID %CPU %MEM CMD
1143 99.2 0.0 /usr/bin/teamd -o -n -U -D -N -t team0 -c {"runner": {"name": "loadbalance", "tx_hash": ["eth", "ipv4", "ipv6"]}}

[root@vbox1 ~]# uptime
 01:44:58 up 14 min,  1 user,  load average: 1.00, 0.98, 0.67

[root@vbox1 ~]# rpm -qa | grep libteam
libteam-1.31-2.fc32.x86_64

Any ideas about this?

Thanks a lot!
Adrian


Yeah, libteam-1.31-2.el8.x86_64 works well! Could you do proper build?

In F32, dnf info shows

Name         : libteam
Version      : 1.31
Release      : 2.fc32
Architecture : x86_64
Size         : 50 k
Source       : libteam-1.31-2.fc32.src.rpm
Repository   : updates
Summary      : Library for controlling team network device
URL          : http://www.libteam.org
License      : LGPLv2+
Description  : This package contains a library which is a user-space
              : counterpart for team network driver. It provides an API
              : to control team network devices.

---
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux