Closed leiyu-bytedance closed 3 years ago
Please answer the bug template as it's written. Namely, you omit what system you're on.
Please answer the bug template as it's written. Namely, you omit what system you're on.
It's a downstream system so I did not put the name. I think the bmcweb revision and the stack backtrace already gives enough information, is it?
Closing the bug given that this isn't an upstream system. In open source we don't know what code or configuration changes you've made in your downstream, so we can't support you in this bug. If this reproduces on an upstream system, or you submit patches to upstream your system, feel free to reopen.
I do not think I could not open a bug based on a downstream system, because:
bmcweb doesn't run in isolation, and is part of openbmc, which you don't include a revision for (presumably because you're operating on your fork). Considering your crash looks like it occurred somewhere in OpenSSL, it's quite possible and likely it's a system issue. If this reproduces on an upstream machine that we can inspect the configuration of, let me know, but it's too much to debug issues on everyones forks.
If you're interested in resubmitting this, please upstream your system, then if it still reproduces, we can reopen this.
Describe the bug bmcweb hangs and consuming all CPU cycles.
Environment The bmcweb revision is 19a8815adc2d58d69a15f492266ae0e921816102
To Reproduce We could not find stable reproduce steps, the BMC is being used for a few weeks, various operations are done via WebUI. When the issue occurs, bmcweb does not accept new requests, and it consumes all CPU cycles.
Manually trigger a coredump, and the stack backtrace shows below: