spammy log messages with loadbalance runner
by Daniel Arena
Hello,
I have a loadbalance runner for 2 interfaces setup through
NetworkManager on fedora 30. I noticed in the system journal the teamd
messages have been quite spammy with stats updates/rebalance
information from teamd. See example log lines below. I tried looking
at `man teamd.conf` but only found the debug_level setting, which is
defaulted to 0. Is there some other way to turn these messages off? I
tried adjusting NetworkManager's log levels also, but even after
shutting off all logging, the messages from teamd still get through.
Is this actually an issue for NetworkManager, maybe it should be
capturing these log messages and filtering them with NetworkManager's
log levels?
My teamd config looks like this:
{"runner": {
"name": "loadbalance",
"tx_hash": ["eth","ipv4", "ipv6"],
"tx_balancer": {"name": "basic"}
},
"ports":{"eno1": {}, "eno2": {}}
}
Jul 03 15:41:57 server1 teamd_nm-team[32311]: stats update for port
eno2: "3257841132330".
Jul 03 15:41:57 server1 teamd_nm-team[32311]: stats update for port
eno1: "6585330648".
Jul 03 15:41:57 server1 teamd_nm-team[32311]: stats update for hash
"21": "1242456011".
Jul 03 15:41:57 server1 teamd_nm-team[32311]: stats update for hash
"16": "1270449453".
Jul 03 15:41:57 server1 teamd_nm-team[32311]: stats update for hash
"9": "3761543798".
Jul 03 15:41:57 server1 teamd_nm-team[32311]: stats update for hash
"1": "626647946".
Jul 03 15:41:57 server1 teamd_nm-team[32311]: Remapped hash "21"
(delta 447647) to port eno2.
Jul 03 15:41:57 server1 teamd_nm-team[32311]: Remapped hash "16"
(delta 5301) to port eno1.
Jul 03 15:41:57 server1 teamd_nm-team[32311]: Port eno2 rebalanced,
delta: 447647
Jul 03 15:41:57 server1 teamd_nm-team[32311]: Port eno1 rebalanced, delta: 6205
Thanks,
Dan
4 years, 5 months
- 4
- 7
[ISSUE] Failed to find "enabled" option.
by Xin Long
I found this err in "loadbalance" and "lacp" runner when adding ports.
It's caused by trying to set "enabled" option in .port_link_changed()
or .port_changed().
When a new port is added, the first 'port changed event' process is
earlier than CMD TEAM_CMD_OPTIONS_GET, in this CMD, all
the options are synchronized from kernel.
It means there's no 'enabled' option yet when calling port_link_changed
in the first 'port changed event' process. In lb_event_watch_port_link_changed
and lacp_event_watch_port_changed, they call teamd_port_check_enable
to set 'enabled' option. this err is triggered.
I'm not sure why teamd_port_check_enable needs to check if
'enabled' option exists. I checked the ab's .port_link_changed(),
it just sets it by calling team_set_port_enabled(), instead of
checking 'enabled' option first.
can we just use team_set_port_enabled to set it directly in
.port(_link)_changed OR improve teamd_port_check_enable
to avoid this err ?
Thanks.
4 years, 7 months
- 3
- 5
- ← Newer
- 1
- Older →