Your message dated Tue, 17 Feb 2026 11:33:09 +0000 (UTC)
with message-id <[email protected]>
and subject line closing
has caused the Debian Bug report #1127984,
regarding mosquitto doesn' start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1127984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127984
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mosquitto
Version: 2.0.22-5
Severity: important
Dear Maintainer,
at start I have the following:
systemctl start mosquitto.service
Job for mosquitto.service failed because the control process exited with error
code.
See "systemctl status mosquitto.service" and "journalctl -xeu
mosquitto.service" for details.
systemctl status mosquitto.service says:
× mosquitto.service - Mosquitto MQTT Broker
Loaded: loaded (/usr/lib/systemd/system/mosquitto.service; enabled; preset:
enabled)
Active: failed (Result: exit-code) since Sat 2026-02-14 20:35:17 CET; 1s ago
Invocation: 8dccca852b1d43d8974cced6bde6069d
Docs: man:mosquitto.conf(5)
man:mosquitto(8)
Process: 28170 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf
(code=exited, status=127)
Main PID: 28170 (code=exited, status=127)
Mem peak: 2M
CPU: 11ms
févr. 14 20:35:17 atom.dagami.top systemd[1]: mosquitto.service: Scheduled
restart job, restart counter is at 5.
févr. 14 20:35:17 atom.dagami.top systemd[1]: mosquitto.service: Start request
repeated too quickly.
févr. 14 20:35:17 atom.dagami.top systemd[1]: mosquitto.service: Failed with
result 'exit-code'.
févr. 14 20:35:17 atom.dagami.top systemd[1]: Failed to start mosquitto.service
- Mosquitto MQTT Broker.
and journalctl -xeu mosquitto.service says:
[...]
févr. 14 20:35:17 atom.dagami.top mosquitto[28170]: /usr/sbin/mosquitto: error
while loading shared libraries: libdlt.so.2: cannot open shared object file: No
such file or directory
févr. 14 20:35:17 atom.dagami.top systemd[1]: mosquitto.service: Main process
exited, code=exited, status=127/n/a
Subject: Unit process exited
Defined-By: systemd
Support: https://www.debian.org/support
An ExecStart= process belonging to unit mosquitto.service has exited.
The process' exit code is 'exited' and its exit status is 127.
[...]
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.18.9+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mosquitto depends on:
ii adduser 3.154
ii init-system-helpers 1.69
ii libc6 2.42-13
ii libcjson1 1.7.19-2
ii libdlt2 3.0.0-2
ii libmosquitto1 2.0.22-5
ii libssl3t64 3.5.5-1
ii libsystemd0 259.1-1
ii libwebsockets19t64 4.3.5-3
ii libwrap0 7.6.q-36+b2
ii sysvinit-utils 3.15-6
mosquitto recommends no packages.
Versions of packages mosquitto suggests:
ii apparmor 4.1.6-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello, sorry for missing this.
I uploaded the new binary in binNEW queue before discovering this bug.
Hold on, as soon as it is accepted, it will make things better :)
G.
--- End Message ---
