Move connection count requests to warning#1377
Open
gtmills wants to merge 2 commits intoibm-openbmc:1120from
Open
Move connection count requests to warning#1377gtmills wants to merge 2 commits intoibm-openbmc:1120from
gtmills wants to merge 2 commits intoibm-openbmc:1120from
Conversation
Up the tracing for requests and ip addresses and the connection count to warning. This will help debug problems with running out of connections. Since log levels are runtime now, can move to warning without filling the journal with a ton of traces. Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Contributor
Author
|
While debugging the subscription history related to the code update, it would be easier to find where/when the subscription may be removed. Move these to WARNING. - Register a new subscription ``` Oct 24 19:11:21 p11bmc bmcweb[1839]: [ERROR event_service_manager.hpp:447] Subscription ID: 3622702393 is added ``` - A subscription is deleted ``` Oct 24 19:12:13 p11bmc bmcweb[1839]: [ERROR event_service_manager.hpp:545] Subscription ID: 3437703746 is deleted ``` - Restart bmcweb & check whether the persistent subscriptions ``` Oct 24 19:12:19 p11bmc systemd[1]: Stopping Start bmcweb server... Oct 24 19:12:19 p11bmc systemd[1]: bmcweb.service: Deactivated successfully. Oct 24 19:12:19 p11bmc systemd[1]: Stopped Start bmcweb server. Oct 24 19:12:21 p11bmc systemd[1]: Started Start bmcweb server. Oct 24 19:12:21 p11bmc bmcweb[1871]: [ERROR event_service_manager.hpp:144] Subscription ID: 3622702393 is loaded ``` Note: If the subscription is deleted due to the max retry, it may look like ``` Oct 24 18:53:19 p11bmc bmcweb[1579]: [ERROR http_client.hpp:445] Maximum number of retries reached. https://9.10.239.119:8080/Test-Redfish-Event-Listener Oct 24 18:53:19 p11bmc bmcweb[1579]: [ERROR subscription.cpp:102] Subscription 4212505157 is deleted after MaxRetryAttempts Oct 24 18:53:19 p11bmc bmcweb[1579]: [ERROR event_service_manager.hpp:545] Subscription ID: 4212505157 is deleted ``` Signed-off-by: Myung Bae <myungbae@us.ibm.com> Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
gtmills
force-pushed
the
move-connection-count-requests-to-warning
branch
from
86160ac to
4032048
Compare
jeaaustx
approved these changes
Oct 29, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
WIP: A possible solution to easily debug GET requests. Move to WARNING log level
Up the tracing for requests and ip addresses and the connection count to
warning. This will help debug problems with running out of connections.
Since log levels are runtime now, can move to warning without filling
the journal with a ton of traces.
Also pull in Myung's subscription added/deleted but move it to WARNING.