| commit | 5d138943e557006a42f4b0a135f47fe7fac0dd1e | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Wed Sep 07 10:26:21 2022 -0500 |
| committer | Gunnar Mills <gmills@us.ibm.com> | Tue Sep 27 19:45:18 2022 +0000 |
| tree | 87a5039a96224097196b483fabcf4cb213a1862f | |
| parent | c7229815e9318ce3052b036717738f92340b9040 [diff] |
Bump timeout for code update file This 10 second timeout is for the write, untar, inotify fire, and creation of a software D-Bus object. IBM has large images for its p10bmc, 125M and growing. We have seen this take longer than 10 seconds on a AST2600. Bump this timeout to 25 seconds. Most of the 10 seconds seems to be the untar. This default 10 seconds is only used for the http upload path. TFTP already bumps this timeout to 600 seconds. [1] https://github.com/openbmc/bmcweb/blob/master/redfish-core/lib/update_service.hpp#L488 Could have instead added the 25 seconds to the monitorForSoftwareAvailable call but figured having the default be 25 is reasonable. [1] https://github.com/openbmc/bmcweb/blob/master/redfish-core/lib/update_service.hpp#L530 On a fail: ``` Sep 07 12:15:01 p10bmc phosphor-version-software-manager[752]: Untaring /tmp/images/69fe6e22-2bd0-42c4-be69-7f388debc6d1 to /tmp/images/imageHaTO5K Sep 07 12:15:08 p10bmc bmcweb[2299]: (2022-09-07 12:15:08) [ERROR "update_service.hpp":392] Timed out waiting for firmware object being created Sep 07 12:15:08 p10bmc bmcweb[2299]: (2022-09-07 12:15:08) [ERROR "update_service.hpp":394] FW image may has already been uploaded to server Sep 07 12:15:08 p10bmc bmcweb[2299]: (2022-09-07 12:15:08) [CRITICAL "error_messages.cpp":233] Internal Error ../git/redfish-core/include/../lib/update_service.hpp(403:49) `redfish::monitorForSoftwareAvailable(const std::shared_ptr<bmcweb::AsyncResp>&, const crow::Request&, const string&, int)::<lambda(const boost::system::error_code&)>`: ``` Tested: On a BMC hitting this, saw the Internal Error on upload without this change. With this change, the update now works. Change-Id: I47940f074ac42ceb59011411b79679ff4c8360d6 Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
This component attempts to be a "do everything" embedded webserver for OpenBMC.
The webserver implements a few distinct interfaces:
bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.
Bmcweb supports multiple authentication protocols:
Each of these types of authentication is able to be enabled or disabled both via runtime policy changes (through the relevant Redfish APIs) or via configure time options. All authentication mechanisms supporting username/password are routed to libpam, to allow for customization in authentication implementations.
All authorization in bmcweb is determined at routing time, and per route, and conform to the Redfish PrivilegeRegistry.
*Note: Non-Redfish functions are mapped to the closest equivalent Redfish privilege level.
bmcweb is configured per the meson build files. Available options are documented in meson_options.txt
meson builddir ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson will automatically download them via its wrap dependencies mentioned in bmcweb/subprojects.
bmcweb by default is compiled with runtime logging disabled, as a performance consideration. To enable it in a standalone build, add the
-Dlogging='enabled'
option to your configure flags. If building within Yocto, add the following to your local.conf.
EXTRA_OEMESON:pn-bmcweb:append = "-Dbmcweb-logging='enabled'"
bmcweb relies on some on-system data for storage of persistent data that is internal to the process. Details on the exact data stored and when it is read/written can seen from the persistent_data namespace.
When SSL support is enabled and a usable certificate is not found, bmcweb will generate a self-signed a certificate before launching the server. Please see the bmcweb source code for details on the parameters this certificate is built with.