Mgmt EOF disconnect error log msg #21936
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sudhanshukumar22
requested review from
qiluo-msft,
xumia and
lguohan
as code owners
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
sudhanshukumar22
force-pushed
the
mgmt_eof_disconnect_error
branch
from
d52a71e to
1be0ec4
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sudhanshukumar22
force-pushed
the
mgmt_eof_disconnect_error
branch
2 times, most recently
from
13f5423 to
b065ef5
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
which is already closed by peer. For e.g., the other side may have been killed during warmboot or using pkill. Hence, changing the log level to INFO
sudhanshukumar22
force-pushed
the
mgmt_eof_disconnect_error
branch
from
b065ef5 to
9118e2c
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
mgmtd: Change log level to INFO for EOF disconnect error, which can also happen in a valid scenario
Description: This error happens when we try to write to a socket or pipe
which is already closed by peer. For e.g., the other side may have been
killed during warmboot or using pkill. Hence, changing the log level to INFO.
Note: I have avoided changing bgp.sh script because the error could be seen in other scenarios also(apart from warmboot/fast boot, for e.g., if we just kill zebra, we will see this log).
Signed-off-by: sudhanshukumar22 ([email protected])
Work item tracking
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
2025 Mar 5 10:22:59.234007 sonic INFO bgp#mgmtd[33]: [GR5PJ-Q2R72] BE-adapter: mgmt_msg_read: got EOF/disconnect
2025 Mar 5 10:22:59.234845 sonic INFO bgp#supervisord 2025-03-05 10:22:59,234 WARN exited: zebra (terminated by SIGKILL; not expected)
2025 Mar 5 10:22:59.235034 sonic INFO bgp#supervisord: fpmsyncd Connection lost, reconnecting...
2025 Mar 5 10:22:59.235078 sonic INFO bgp#supervisord: fpmsyncd Waiting for fpm-client connection...
2025 Mar 5 10:22:59.239697 sonic INFO bgp#supervisor-proc-exit-listener: Process 'zebra' exited unexpectedly. Terminating supervisor 'bgp'
2025 Mar 5 10:22:59.239987 sonic NOTICE bgp#supervisor-proc-exit-listener: :- publish: EVENT_PUBLISHED: {"sonic-events-host:process-exited-unexpectedly":{"ctr_name":"bgp","process_name":"zebra","timestamp":"2025-03-05T10:22:59.239786Z"}}
2025 Mar 5 10:22:59.241330 sonic INFO bgp#supervisord 2025-03-05 10:22:59,241 WARN received SIGTERM indicating exit request
2025 Mar 5 10:22:59.241770 sonic INFO bgp#supervisord 2025-03-05 10:22:59,241 INFO waiting for supervisor-proc-exit-listener, rsyslogd, mgmtd, staticd, bgpd, bgpcfgd, bgpmon, fpmsyncd, staticroutebfd to die
2025 Mar 5 10:23:00.244898 sonic INFO bgp#supervisord 2025-03-05 10:23:00,244 INFO stopped: staticroutebfd (exit status 0)
2025 Mar 5 10:23:00.246125 sonic INFO bgp#supervisord 2025-03-05 10:23:00,245 WARN stopped: fpmsyncd (terminated by SIGTERM)
2025 Mar 5 10:23:00.247716 sonic INFO bgp#supervisord 2025-03-05 10:23:00,247 WARN stopped: bgpmon (terminated by SIGTERM)
2025 Mar 5 10:23:02.251113 sonic INFO bgp#supervisord 2025-03-05 10:23:02,250 INFO waiting for supervisor-proc-exit-listener, rsyslogd, mgmtd, staticd, bgpd, bgpcfgd to die
2025 Mar 5 10:23:05.255125 sonic INFO bgp#supervisord 2025-03-05 10:23:05,254 INFO waiting for supervisor-proc-exit-listener, rsyslogd, mgmtd, staticd, bgpd, bgpcfgd to die
2025 Mar 5 10:23:08.258691 sonic INFO bgp#supervisord 2025-03-05 10:23:08,258 INFO waiting for supervisor-proc-exit-listener, rsyslogd, mgmtd, staticd, bgpd, bgpcfgd to die
2025 Mar 5 10:23:10.261208 sonic INFO bgp#supervisord 2025-03-05 10:23:10,260 WARN killing 'bgpcfgd' (50) with SIGKILL
2025 Mar 5 10:23:10.264011 sonic INFO bgp#supervisord 2025-03-05 10:23:10,263 WARN stopped: bgpcfgd (terminated by SIGKILL)
2025 Mar 5 10:23:10.266753 sonic INFO bgp#supervisord 2025-03-05 10:23:10,266 WARN stopped: bgpd (terminated by SIGKILL)
2025 Mar 5 10:23:11.268288 sonic INFO bgp#supervisord 2025-03-05 10:23:11,267 INFO waiting for supervisor-proc-exit-listener, rsys
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)