Google Git
Sign in
gbmc / gbmcweb / a08c990a897bc365ca00129d97915bda3a40f0b5
commita08c990a897bc365ca00129d97915bda3a40f0b5[log] [tgz]
authorgBMC Team <gbmc-core@google.com>Fri Oct 10 15:34:10 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Fri Oct 10 15:34:46 2025 -0700
treeff89d7059e5e7acb4585cc0622dcafea455e5d35
parentc40a84150978382c43124cd3f77a3101a1b4e8a8 [diff]
Not recoverable lock exception reproducer. This reliably allows the CLI to reliably put the shared memory segment lock into a bad state.

example output usage to reproduce:

fiterman@fiterman-dev:/google/src/cloud/fiterman/tlbmc_dev/google3$ blaze-bin/third_party/milotic/external/cc/tlbmc/hal/shared_mem/demo/shared_mem_cli -command get_metrics
.....

fiterman@fiterman-dev:/google/src/cloud/fiterman/tlbmc_dev/google3$ blaze-bin/third_party/milotic/external/cc/tlbmc/hal/shared_mem/demo/shared_mem_cli -command crash_test
Crashing the process under lock
Killed
fiterman@fiterman-dev:/google/src/cloud/fiterman/tlbmc_dev/google3$ blaze-bin/third_party/milotic/external/cc/tlbmc/hal/shared_mem/demo/shared_mem_cli -command get_metrics
WARNING: Logging before InitGoogle() is written to STDERR
E0000 00:00:1760066642.216733 1199762 segment_manager.cc:63] Not recoverable lock exception happened: boost::interprocess::lock_exception. Will remove the init file and shared memory, then create a new one.
W0000 00:00:1760066642.216888 1199762 segment_manager.cc:106] Creating shared memory; this should only happen once per boot.
W0000 00:00:1760066642.217411 1199762 segment_manager.cc:122] Created shared memory object; created file at : /run/tlbmc/shm_initialized
Metrics pointer is 0x7f4c932ce118
Metrics is {
....
PiperOrigin-RevId: 817811283
Change-Id: I0ec1d6ddc7a5f1d37dfb90a75c83d656e3ee40cb
1 file changed
tree: ff89d7059e5e7acb4585cc0622dcafea455e5d35
  1. .github/
  2. config/
  3. g3/
  4. http/
  5. include/
  6. install/
  7. plugins/
  8. redfish-core/
  9. redfish_authorization/
  10. scripts/
  11. src/
  12. static/
  13. subprojects/
  14. test/
  15. tlbmc/
  16. .clang-format
  17. .clang-tidy
  18. .clang-tidy-ignore
  19. .dockerignore
  20. .gitignore
  21. .markdownlint.yaml
  22. .openbmc-enforce-gitlint
  23. .openbmc-no-clang
  24. .openbmc-no-sanitize
  25. .prettierignore
  26. .shellcheck
  27. AGGREGATION.md
  28. CLIENTS.md
  29. COMMON_ERRORS.md
  30. copy.bara.sky
  31. DBUS_USAGE.md
  32. DEVELOPING.md
  33. gcovr.cfg
  34. HEADERS.md
  35. LICENSE
  36. meson.build
  37. meson_options.txt
  38. OEM_SCHEMAS.md
  39. OWNERS
  40. PLUGINS.md
  41. README.md
  42. README_GOOGLE.md
  43. Redfish.md
  44. run-ci
  45. setup.cfg
  46. TESTING.md
  47. UNIT_TESTING.md
README.md

OpenBMC webserver

This project is Google's version of BMCWeb.

See Readme Google for Google added features. The following is the original README of OpenBMC/BMCWeb.

==============================================================================

This component attempts to be a “do everything” embedded webserver for OpenBMC.

Features

The webserver implements a few distinct interfaces:

  • DBus event websocket. Allows registering on changes to specific dbus paths, properties, and will send an event from the websocket if those filters match.
  • OpenBMC DBus REST api. Allows direct, low interference, high fidelity access to dbus and the objects it represents.
  • Serial: A serial websocket for interacting with the host serial console through websockets.
  • Redfish: A protocol compliant, DBus to Redfish translator.
  • KVM: A websocket based implementation of the RFB (VNC) frame buffer protocol intended to mate to webui-vue to provide a complete KVM implementation.

Protocols

bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.

AuthX

Authentication

Bmcweb supports multiple authentication protocols:

  • Basic authentication per RFC7617
  • Cookie based authentication for authenticating against webui-vue
  • Mutual TLS authentication based on OpenSSL
  • Session authentication through webui-vue
  • XToken based authentication conformant to Redfish DSP0266

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.

Authorization

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.

Configuration

bmcweb is configured per the meson build files. Available options are documented in meson_options.txt

Compile bmcweb with default options

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.

Use of persistent data

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.

TLS certificate generation

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.

Redfish Aggregation

bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.