#1132938 [debian trixie 13.4] not possible to start mosquitto service

Package:
mosquitto
Source:
mosquitto
Description:
MQTT version 5.0/3.1.1/3.1 compatible message broker
Submitter:
Jean-Marc LACROIX
Date:
2026-04-12 12:03:01 UTC
Severity:
normal
#1132938#5
Date:
2026-04-07 19:43:23 UTC
From:
To:
Package:   mosquitto
Version:   2.0.21-1
Severity:  important

Dear maintainers,

I am trying to use mosquitto On Debian trixie (armhf arch)...
My current configuration is ...

ansible@hn-cubietruck-300:~$ uname -a
Linux hn-cubietruck-300 6.12.74+deb13+1-armmp-lpae #1 SMP Debian
6.12.74-2 (2026-03-08) armv7l GNU/Linux
ansible@hn-cubietruck-300:~$

ansible@hn-cubietruck-300:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 13 (trixie)
Release:        13
Codename:       trixie
ansible@hn-cubietruck-300:~$

ansible@hn-cubietruck-300:~$ dpkg -l |grep mosquitto
ii  libmosquitto1:armhf                    2.0.21-1
        armhf        MQTT version 5.0/3.1.1/3.1 client library
ii  mosquitto                              2.0.21-1
        armhf        MQTT version 5.0/3.1.1/3.1 compatible message broker
ii  mosquitto-clients                      2.0.21-1
        armhf        Mosquitto command line MQTT clients
ansible@hn-cubietruck-300:~$

ansible@hn-cubietruck-300:~$ LC_ALL=C dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                   Version
        Architecture Description
+++-======================================-====================================-============-================================================================================
ansible@hn-cubietruck-300:~$

For this target, my configuration file is ....


ansible@hn-cubietruck-300:~$ cat /etc/mosquitto/mosquitto.conf  |grep -v
'#' |grep -v ^$
allow_anonymous        true
autosave_interval      60
autosave_on_changes    false
connection_messages    true
pid_file               /run/mosquitto/mosquitto.pid
persistence            true
persistence_file       mosquitto.db
persistence_location   /var/lib/mosquitto/
log_dest               /var/log/mosquitto/log_mosquitto.log
log_timestamp           true
log_timestamp_format    %Y-%m-%dT%H:%M:%S
log_type                all
max_inflight_bytes      1000
max_inflight_messages    1
max_keepalive            3600
max_packet_size          256
max_queued_bytes         1000
max_queued_messages      1000
memory_limit             100000
set_tcp_nodelay            false
sys_interval               10
per_listener_settings false
listener                1883 localhost
listener                1883 hn-cubietruck-300-service.sub-dns-paris.TLD.jml

max_connections         30
max_topic_alias          5
protocol                 mqtt
socket_domain             ipv4
ansible@hn-cubietruck-300:~$

When launching process into one shell with following command ....

ansible@hn-cubietruck-300:~$ sudo mosquitto -v
1775589266: mosquitto version 2.0.21 starting
1775589266: Using default config.
1775589266: Starting in local only mode. Connections will only be
possible from clients running on this machine.
1775589266: Create a configuration file which defines a listener to
allow remote access.
1775589266: For more details see
https://mosquitto.org/documentation/authentication-methods/
1775589266: Opening ipv4 listen socket on port 1883.
1775589266: Opening ipv6 listen socket on port 1883.
1775589266: Warning: Address family not supported by protocol
1775589266: mosquitto version 2.0.21 running

Question Q1: In my configuration, i set
socket_domain limited to ipv4, therefore, i don't understand why daemon
try to open ipv6 socket ???, is it one error ???

Question Q2: according documentation, it seems possible to listen on
many ipv4 sockets.
In my configuration , i have set 2 ipv4 addresses, but it seems that
only localhost is used ???? because...

ansible@hn-cubietruck-300:~$ sudo lsof |grep mosquitto
mosquitto 20587                  mosquitto cwd       DIR      179,1
4096      16025 /home/ansible
mosquitto 20587                  mosquitto rtd       DIR      179,1
4096          2 /
mosquitto 20587                  mosquitto txt       REG      179,1
198188      13977 /usr/sbin/mosquitto
mosquitto 20587                  mosquitto mem       REG      179,1
525776       1659 /usr/lib/arm-linux-gnueabihf/libzstd.so.1.5.7
mosquitto 20587                  mosquitto mem       REG      179,1
71320       1901 /usr/lib/arm-linux-gnueabihf/libz.so.1.3.1
mosquitto 20587                  mosquitto mem       REG      179,1
67084       6521 /usr/lib/arm-linux-gnueabihf/libcap.so.2.75
mosquitto 20587                  mosquitto mem       REG      179,1
1188080      13611 /usr/lib/arm-linux-gnueabihf/libc.so.6
mosquitto 20587                  mosquitto mem       REG      179,1
396852      13938 /usr/lib/arm-linux-gnueabihf/libwebsockets.so.19
mosquitto 20587                  mosquitto mem       REG      179,1
329136      13615 /usr/lib/arm-linux-gnueabihf/libm.so.6
mosquitto 20587                  mosquitto mem       REG      179,1
3283084       7390 /usr/lib/arm-linux-gnueabihf/libcrypto.so.3
mosquitto 20587                  mosquitto mem       REG      179,1
733696       7391 /usr/lib/arm-linux-gnueabihf/libssl.so.3
mosquitto 20587                  mosquitto mem       REG      179,1
111480       5894 /usr/lib/arm-linux-gnueabihf/libdlt.so.2.18.10
mosquitto 20587                  mosquitto mem       REG      179,1
790368       2425 /usr/lib/arm-linux-gnueabihf/libsystemd.so.0.40.0
mosquitto 20587                  mosquitto mem       REG      179,1
67376       3645 /usr/lib/arm-linux-gnueabihf/libwrap.so.0.7.6
mosquitto 20587                  mosquitto mem       REG      179,1
133776      13608 /usr/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3
mosquitto 20587                  mosquitto   0u      CHR      136,4
0t0          7 /dev/pts/4
mosquitto 20587                  mosquitto   1u      CHR      136,4
0t0          7 /dev/pts/4
mosquitto 20587                  mosquitto   2u      CHR      136,4
0t0          7 /dev/pts/4
mosquitto 20587                  mosquitto   3u     sock        0,9
0t0   34728419 protocol: TCP
mosquitto 20587                  mosquitto   4u     IPv4   34728424
0t0        TCP localhost:1883 (LISTEN)
mosquitto 20587                  mosquitto   5u  a_inode       0,14
   0         66 [eventpoll:4]
ansible@hn-cubietruck-300:~$

For DNS point of vue, my configuration listen address is correctly
resolved by DNS, because ...

ansible@hn-cubietruck-300:~$ sudo ping
hn-cubietruck-300-service.sub-dns-paris.TLD.jml
PING hn-cubietruck-300-service.sub-dns-paris.TLD.jml (192.168.70.49)
56(84) bytes of data.
64 bytes from hn-cubietruck-300-service.sub-dns-paris.TLD.jml
(192.168.70.49): icmp_seq=1 ttl=64 time=0.205 ms
^C
--- hn-cubietruck-300-service.sub-dns-paris.TLD.jml ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.205/0.205/0.205/0.000 ms
ansible@hn-cubietruck-300:~$


Ans of course, this ipv4 is on local ip address

ansible@hn-cubietruck-300:~$ ip route ls
192.168.70.0/24 dev if-service proto kernel scope link src 192.168.70.49
192.168.73.0/24 dev if-admin proto kernel scope link src 192.168.73.49
ansible@hn-cubietruck-300:~$



Question Q3: I set log file into log_dest via ....
log_dest               /var/log/mosquitto/log_mosquitto.log

Why in previous command, my configuration for logfile does not
appear to be taken into account ?


Question Q4: After killing process, is seems not possible to start
daemon with standard command, (I am using sysvinit, not systemd),
because ...

ansible@hn-cubietruck-300:~$ sudo bash -x /etc/init.d/mosquitto start
+ set -e
+ NAME=mosquitto
+ USER=mosquitto
+ DAEMON=/usr/sbin/mosquitto
+ PIDDIR=/run/mosquitto
+ PIDFILE=/run/mosquitto/mosquitto.pid
+ LOGDIR=/var/log/mosquitto
+ CONFFILE=/etc/mosquitto/mosquitto.conf
+ test -x /usr/sbin/mosquitto
+ umask 022
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in $(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2> /dev/null)
++ '[' -r /lib/lsb/init-functions.d/00-verbose ']'
++ . /lib/lsb/init-functions.d/00-verbose
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ export
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/sbin:/sbin
+
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/sbin:/sbin
+ case "$1" in
+ init_is_upstart
+ '[' -x /sbin/initctl ']'
+ return 1
+ create_dirs
+ mkdir -p /run/mosquitto
+ chown mosquitto /run/mosquitto
+ mkdir -p /var/log/mosquitto
+ chown mosquitto /var/log/mosquitto
+ log_daemon_msg 'Starting network daemon' mosquitto
+ '[' -z 'Starting network daemon' ']'
+ log_daemon_msg_pre 'Starting network daemon' mosquitto
+ :
+ '[' -z mosquitto ']'
+ echo -n 'Starting network daemon: mosquitto'
Starting network daemon: mosquitto+ log_daemon_msg_post 'Starting
network daemon' mosquitto
+ :
+ start-stop-daemon --user mosquitto --chuid mosquitto --start --quiet
--oknodo --background --pidfile /run/mosquitto/mosquitto.pid --exec 
/usr/sbin/mosquitto -- -c /etc/mosquiconf
+ log_end_msg 0
+ '[' -z 0 ']'
+ log_end_msg_pre 0
+ :
+ log_use_fancy_output
+ '[' -t 1 ']'
+ '[' xxterm '!=' x ']'
+ '[' xxterm '!=' xdumb ']'
+ '[' -z ']'
+ return 0
+ esc=$'\E'
+ red=''
+ yellow=''
+ normal=''
+ '[' 0 -eq 0 ']'
+ echo .
.
+ log_end_msg_post 0
+ :
+ return 0
+ exit 0


Exit code is ok, but process is not launched, because ...

ansible@hn-cubietruck-300:~$ sudo lsof |grep mosquitto
ansible@hn-cubietruck-300:~$


Thanks in advance for you help


best regards

#1132938#10
Date:
2026-04-12 09:50:45 UTC
From:
To:
Please check if your issues are caused by the fact that stopping
mosquitto with sysv init is not working. I took a closer look and found
that

#pid_file /run/mosquitto/mosquitto.pid

is commented out by default. If you uncomment this stopping via sysv
init should be working, which might resolve them.

Sincerely,
Joachim

#1132938#15
Date:
2026-04-12 11:59:50 UTC
From:
To:
Am Sonntag, dem 12.04.2026 um 11:50 +0200 schrieb Joachim Zobel:

Sorry, just saw that you have uncommented this line. But your issues
might actually be caused by mosquitto not stopping correctly. Please
check if this is the case.

Sincerely,
Joachim