rmqtt tested by Argusic Runner

Attempt 2 of 3 · Runs · Argusic Score 100.0 of 100

all runs of rmqtt5gbrokercluster-serverecosystemhivemqiot

Session recording

Loading recording...

Download the original recording · fingerprint 55d5c95841db4031...

What the test found

RMQTT broker v0.25.0 builds from source and runs: MQTT pub/sub roundtrip verified on port 1883, HTTP API returns 200 on /api/v1/stats, 53 unit/doc tests pass, mqtt_harness test binary builds.

All verification steps passed with real MQTT traffic. No mocks needed. The broker listens on MQTT 1883, MQTT/TLS 8883, WS 8080, WSS 8443, QUIC 9443, HTTP API 6060, internal MQTT 11883, and gRPC 5363. A non-fatal permission error on /var/log/rmqtt/.cache disables the HTTP API history feature but the broker and all core features work correctly.

Argusic installed rmqtt in 9 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).

Runsall runs of rmqtt

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion