chore: Add logging for D-Bus publishing and connection closure

Added informational log messages to track when `REVPI_DBUS_NAME` is
published and its connection is closed in both `BusProviderIos1` and
`BusProviderMiddleware1`.

Signed-off-by: Sven Sager <s.sager@kunbus.com>
This commit is contained in:
Sven Sager
2026-03-13 09:07:46 +01:00
parent f6f83e236e
commit 9e5a9e0141
2 changed files with 4 additions and 0 deletions

View File

@@ -92,6 +92,7 @@ class BusProviderIos1(Thread):
*lst_interfaces,
)
self.published.set()
log.info(f"published {REVPI_DBUS_NAME} on {self._bus_address}")
except Exception as e:
log.error(f"can not publish dbus {REVPI_DBUS_NAME}: {e}")
@@ -109,6 +110,7 @@ class BusProviderIos1(Thread):
bus.con.close()
self._modio.cleanup()
log.info(f"closed {REVPI_DBUS_NAME} connection to {self._bus_address}")
log.debug("leave BusProviderIos1.run")

View File

@@ -55,6 +55,7 @@ class BusProviderMiddleware1(Thread):
*lst_interfaces,
)
self.published.set()
log.info(f"published {REVPI_DBUS_NAME} on {self._bus_address}")
except Exception as e:
log.error(f"can not publish dbus {REVPI_DBUS_NAME}: {e}")
@@ -64,6 +65,7 @@ class BusProviderMiddleware1(Thread):
log.error(f"can not run dbus mainloop: {e}")
bus.con.close()
log.info(f"closed {REVPI_DBUS_NAME} connection to {self._bus_address}")
# Clean up all interfaces
for interface in lst_interfaces: