Your message dated Sat, 19 Aug 2023 14:40:26 +0200
with message-id <eb8a3e6508124ebe764bcc82b653ef03b2848029.ca...@heute-morgen.de>
and subject line No longer relevant
has caused the Debian Bug report #877346,
regarding mosquitto doesn't start after upgrade (jessie to stretch)
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 ow...@bugs.debian.org
immediately.)
--
877346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mosquitto
Version: 1.4.10-3
Severity: normal
Dear Maintainer,
After upgrading from jessie to stretch (raspbian) the service failed to
start. No clear error message was shown.
The issue was caused by the still existing log file (in
/var/log/mosquitto) which was not owned by user mosquitto.
fix: chown mosquitto /var/log/mosquitto/*
-- System Information:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.1 (stretch)
Release: 9.1
Codename: stretch
Architecture: armv7l
Kernel: Linux 4.9.41-v7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mosquitto depends on:
ii adduser 3.115
ii libc6 2.24-11+deb9u1
ii libssl1.1 1.1.0f-3
ii libuuid1 2.29.2-1
ii libwebsockets8 2.0.3-2
ii libwrap0 7.6.q-26
ii lsb-base 9.20161125+rpi1
mosquitto recommends no packages.
Versions of packages mosquitto suggests:
pn apparmor <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
I am closing this because it is specific for the upgrade from jessie to
stretch. The log file is owned by mosquitto since.
Thanks for reporting the bug, it likely helped others having the same
problem.
Sincerely,
Joachim
--- End Message ---
