Skip to content

feat: Allow tedge run all to run multiple mappers#4253

Open
jarhodes314 wants to merge 4 commits into
thin-edge:mainfrom
jarhodes314:feat/run-all-multi-mapper
Open

feat: Allow tedge run all to run multiple mappers#4253
jarhodes314 wants to merge 4 commits into
thin-edge:mainfrom
jarhodes314:feat/run-all-multi-mapper

Conversation

@jarhodes314

@jarhodes314 jarhodes314 commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Proposed changes

Extends the tedge run all CLI to accept multiple arguments in order to run multiple mappers simultaneously, e.g.

tedge run all c8y tb c8y@profile

A bare tedge run all command now runs all mappers defined in /etc/tedge/mappers.

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
  • Documentation Update (if none of the other choices apply)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue


Checklist

  • I have read the CONTRIBUTING doc
  • I have signed the CLA (in all commits with git commit -s. You can activate automatic signing by running just prepare-dev once)
  • I ran just format as mentioned in CODING_GUIDELINES
  • I used just check as mentioned in CODING_GUIDELINES
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

@jarhodes314
Allow tedge run all to run multiple mappers
d16facc 
Signed-off-by: James Rhodes <jarhodes314@gmail.com>
@jarhodes314 jarhodes314 temporarily deployed to Test Pull Request July 14, 2026 10:29 — with GitHub Actions Inactive
@codecov

codecov Bot commented Jul 14, 2026 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 91.04478% with 18 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
crates/core/tedge_mapper/src/lib.rs 92.10% 5 Missing and 4 partials ⚠️
crates/core/tedge/src/supervisor.rs 84.00% 7 Missing and 1 partial ⚠️
crates/common/tedge_supervisor/src/lib.rs 97.29% 1 Missing ⚠️

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

reubenmiller
reubenmiller reviewed Jul 14, 2026
View reviewed changes
Comment thread crates/core/tedge/src/supervisor.rs Outdated
#[clap(subcommand)]
pub mapper: Option<MapperName>,
/// Mappers to run alongside the agent (e.g. `c8y`, `aws`, `c8y@profile`).
#[clap(trailing_var_arg = true)]

@reubenmiller reubenmiller Jul 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, I'm wondering why we have to use trailing args here and not positional args?

As I'm pretty sure with the current option the following won't work due to the flag coming after the positional args.

tedge run all c8y --log-info debug

My preference would be to not care about such ordering by using #[arg(num_args = 1..)] instead.

@jarhodes314 jarhodes314 Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No good reason, I've updated it to match your suggestion now

@github-actions

github-actions Bot commented Jul 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Robot Results

✅ Passed ❌ Failed ⏭️ Skipped Total Pass % ⏱️ Duration
891 63 7 954 93.40 2h47m43.161275999s

Failed Tests

Name Message ⏱️ Duration Suite
Filter packages list using both patterns tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_extract_inverted_gulf cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 49.247 s Sm-Plugin
Measurement units can be cleared not enough measurements were found. args=() [RETRY] FAIL on 3. retry. 33.601 s Thin-Edge Device Telemetry
Thin-edge devices support sending simple measurements with custom type not enough measurements were found. args=() [RETRY] FAIL on 3. retry. 32.089 s Thin-Edge Device Telemetry
Thin-edge devices support sending simple measurements with custom type in topic not enough measurements were found. args=() [RETRY] FAIL on 3. retry. 32.005 s Thin-Edge Device Telemetry
Thin-edge devices support sending simple measurements with custom type in payload not enough measurements were found. args=() [RETRY] FAIL on 3. retry. 31.441 s Thin-Edge Device Telemetry
Thin-edge devices support sending custom measurements not enough measurements were found. args=() [RETRY] FAIL on 3. retry. 31.517 s Thin-Edge Device Telemetry
Thin-edge devices sending metadata properties along measurements not enough measurements were found. args=() [RETRY] FAIL on 3. retry. 31.583 s Thin-Edge Device Telemetry
Thin-edge devices support sending simple measurements Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.032 s Thin-Edge Device Telemetry Built-In Bridge
Built-in bridge reports health status Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.032 s Thin-Edge Device Telemetry Built-In Bridge
Bridge stops if mapper stops running Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.032 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending simple measurements with custom type Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.029 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending simple measurements with custom type in topic Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.051 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending simple measurements with custom type in payload Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.081 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom measurements Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.041 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom events Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.041 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending large events Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.045 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom events overriding the type Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.076 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom events without type in topic Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.056 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom alarms #1699 Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.053 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom alarms overriding the type Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.041 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom alarms without type in topic Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.042 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom alarms without severity in payload Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.055 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom alarms with unknown severity in payload Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.066 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending custom alarms without text in payload Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.088 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge devices support sending alarms using text fragment Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.089 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge device supports sending custom Thin-edge device measurements directly to c8y Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.092 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge device supports sending custom bulk measurements directly to c8y Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.063 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge device supports sending custom bulk events directly to c8y Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.078 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge device supports sending custom bulk alarms directly to c8y Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.065 s Thin-Edge Device Telemetry Built-In Bridge
Thin-edge device support sending inventory data via c8y topic Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.067 s Thin-Edge Device Telemetry Built-In Bridge
Previously cleared property should be sent to cloud when set again #2365 Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.068 s Thin-Edge Device Telemetry Built-In Bridge
Send measurements to an unregistered service Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.047 s Thin-Edge Device Telemetry Built-In Bridge
Send measurements to a registered service Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.052 s Thin-Edge Device Telemetry Built-In Bridge
Send alarms to an unregistered service Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.055 s Thin-Edge Device Telemetry Built-In Bridge
Send alarms to a registered service Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.046 s Thin-Edge Device Telemetry Built-In Bridge
Send events to an unregistered service Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.072 s Thin-Edge Device Telemetry Built-In Bridge
Send events to a registered service Parent suite setup failed: tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cue_oily_salt cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.065 s Thin-Edge Device Telemetry Built-In Bridge
Upload a file to Cumulocity from main device Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_composite_citron_service cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.055 s Tedge C8Y Upload
Upload a file to Cumulocity from child device Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_composite_citron_service cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.052 s Tedge C8Y Upload
Upload a file to Cumulocity from the main device on behalf of a child device Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_composite_citron_service cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.092 s Tedge C8Y Upload
Watchdog does not kill mapper if it responds Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_blister_icy_velvet cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.068 s Health Tedge-Mapper-Aws
Stop tedge-mapper-az Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.068 s Health Tedge-Mapper-Az
Update the service file Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.083 s Health Tedge-Mapper-Az
Reload systemd files Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.107 s Health Tedge-Mapper-Az
Start tedge-mapper-az Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.071 s Health Tedge-Mapper-Az
Start watchdog service Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.050 s Health Tedge-Mapper-Az
Check PID of tedge-mapper-az Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.053 s Health Tedge-Mapper-Az
Kill the PID Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.186 s Health Tedge-Mapper-Az
Recheck PID of tedge-mapper-az Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.062 s Health Tedge-Mapper-Az
Compare PID change Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.062 s Health Tedge-Mapper-Az
Stop watchdog service Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.055 s Health Tedge-Mapper-Az
Remove entry from service file Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.112 s Health Tedge-Mapper-Az
Watchdog does not kill mapper if it responds Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_crash_khaki_angler cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.055 s Health Tedge-Mapper-Az
tedge-agent health status Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_cut_novel_gutter cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.066 s MQTT health endpoints
Publish events to subscribed topic Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_lessen_tender_singularity cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.059 s Custom Sub Topics Tedge-Mapper-C8Y
Publish measurements to unsubscribed topic Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_lessen_tender_singularity cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.042 s Custom Sub Topics Tedge-Mapper-C8Y
Renew certificate tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_populate_global_chili cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/ecdsa-p384-vVD0K4Y4.pem cryptoki: socket (key: pkcs11:token=tedge;object=ecdsa-p384-vVD0K4Y4) bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 83.117 s Current
Renew certificate tedge reconnect c8y returned an unexpected exit code stdout: stderr: Disconnecting from Cumulocity: Removing bridge config file... ✓ Restarting mosquitto to apply configuration... ✓ Disabling tedge-mapper-c8y... ✓ Reconnecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_gallop_unsorted_credenza cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/ecdsa-p384-cUuRXSuT.pem cryptoki: socket (key: pkcs11:token=tedge;object=ecdsa-p384-cUuRXSuT) bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured [ Message content over the limit has been removed. ] Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 86.253 s Initial
Wrong package name Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_barbecue_vibrato_camera cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.048 s Improve Tedge Apt Plugin Error Messages
Wrong version Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_barbecue_vibrato_camera cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.037 s Improve Tedge Apt Plugin Error Messages
Wrong type Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_barbecue_vibrato_camera cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.060 s Improve Tedge Apt Plugin Error Messages
Missing package metadata field Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_barbecue_vibrato_camera cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.040 s Improve Tedge Apt Plugin Error Messages
Run workflow on child device Parent suite setup failed: tedge connect c8y returned an unexpected exit code stdout: stderr: Connecting to Cumulocity: mapper configuration file: /etc/tedge/mappers/c8y/mapper.toml device id: TST_lateral_current_status cloud profile: <none> cloud host: qaenvironment.eu-latest.cumulocity.com:8883 auth type: Certificate certificate file: /etc/tedge/device-certs/tedge-certificate.pem cryptoki: off bridge: built-in service manager: systemd mosquitto version: 2.0.11 proxy: Not configured Updating bridge rule templates... ✓ Creating device in Cumulocity cloud... ✓ Restarting mosquitto... ✓ Waiting for mosquitto to be listening for connections... ✓ Enabling tedge-mapper-c8y... ✓ Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 1 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy Connection test failed, attempt 2 of 3 Verifying device is connected to cloud... ✗ error: Failed to verify device is connected to Cumulocity: Connection to Cumulocity is not healthy warning: Bridge has been configured, but Cumulocity connection check failed. Enabling tedge-agent... ✓ error: Connection check failed [RETRY] FAIL on 3. retry. 0.034 s Run Workflow On Child Device

@jarhodes314
Ensure SIGUSR1 doesn't restart a standalone tedge-mapper
b5934e4 
Signed-off-by: James Rhodes <jarhodes314@gmail.com>
@jarhodes314 jarhodes314 requested a review from a team as a code owner July 14, 2026 14:14
@reubenmiller reubenmiller changed the title Allow tedge run all to run multiple mappers feat: Allow tedge run all to run multiple mappers Jul 14, 2026
@reubenmiller reubenmiller added the skip-release-notes Don't include the ticket in the auto generated release notes label Jul 14, 2026
@jarhodes314 jarhodes314 deployed to Test Pull Request July 15, 2026 12:46 — with GitHub Actions Active
@Bravo555 Bravo555 self-assigned this Jul 15, 2026
@Bravo555 Bravo555 self-requested a review July 15, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@reubenmiller reubenmiller reubenmiller left review comments
@didier-wenzek didier-wenzek Awaiting requested review from didier-wenzek didier-wenzek is a code owner
@albinsuresh albinsuresh Awaiting requested review from albinsuresh albinsuresh is a code owner
@rina23q rina23q Awaiting requested review from rina23q rina23q is a code owner
@Bravo555 Bravo555 Awaiting requested review from Bravo555

At least 1 approving review is required to merge this pull request.

Assignees

@Bravo555 Bravo555

Labels

skip-release-notes Don't include the ticket in the auto generated release notes

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@jarhodes314 @reubenmiller @Bravo555