On Thu, Jul 11, 2019 at 10:47 AM Daniel Arena daniel.arena@smartplay.com wrote:
On Thu, Jul 11, 2019 at 6:01 AM Jiri Pirko jiri@resnulli.us wrote:
That is odd. The messages you mentioned in the original email are debug messages printed out by teamd_log_dbg->daemon_log(LOG_DEBUG,..)
Please check the config for "debug_level" option.
Another thing is, it might be good idea to move these messages to: teamd_log_dbgx(ctx, 2, ..)
Looks like it is disabled... here is output of teamdctl state dump
"setup": { "daemonized": false, "dbus_enabled": true, "debug_level": 0, "kernel_team_mode_name": "loadbalance", "pid": 32311, "pid_file": "/var/run/teamd/nm-team.pid", "runner_name": "loadbalance", "zmq_enabled": false },
Thanks, Dan
FYI, if I run `journalctl -pinfo` then they are filtered out since they are logged with debug priority. It looks like these messages could indeed be moved to teamd_log_dbgx, and then they would not land in the journal at all unless debug_level is enabled. At least they don't also land in /var/log/messages since my rsyslogd config defaults to only logging up to info level, not debug.
Thanks, Dan