Не запускается служба mosquito broker windows 10

When running Mosquitto Broker as a service on Windows, it will always look for a config file in the MOSQUITTO_DIR path.

If you do not have a config file there, it will fail. Usually the installer creates this for you, I suggest you to check if the configuration file is present.

answered Oct 27, 2020 at 7:55

When running Mosquitto Broker as a service on Windows, it will always look for a config file in the MOSQUITTO_DIR path.

If you do not have a config file there, it will fail. Usually the installer creates this for you, I suggest you to check if the configuration file is present.

answered Oct 27, 2020 at 7:55

Код: Выделить всё

root@orangepi:~# service mosquitto status
Usage: /etc/init.d/mosquitto start|stop
root@orangepi:~#  

Код: Выделить всё

mosquitto_pub -h localhost -t "mqtt" -m "Hello MQTT"

Код: Выделить всё

root@orangepi:~# /etc/init.d/mosquitto start
Starting mosquitto
/etc/init.d/mosquitto: line 7: /var/log/mosquitto/mosquitto.log: No such file or           directory
root@orangepi:~#
 

Код: Выделить всё

root@orangepi:/etc/mosquitto# ls
aclfile.example  mosquitto.conf  mosquitto.conf.example  pskfile.example  pwfile.example

Код: Выделить всё

echo "Starting mosquitto"
/usr/local/sbin/mosquitto -d -c /etc/mosquitto/mosquitto.conf
 >> /var/log/mosquitto/mosquitto.log 
 2>> /var/log/mosquitto/mosquitto.error
;; 

Код: Выделить всё

echo "Starting mosquitto"
/usr/local/sbin/mosquitto -d -c /etc/mosquitto/mosquitto.conf
 >> /var/log/mosquitto.log 
 2>> /var/log/mosquitto.error
;; 

I assume you’re running either without a config file or with a config file that doesn’t define a listener. As of mosquitto 2.0, this gives the behaviour you’re describing. To listen on addresses other than localhost, you need to have a config file with a «listener» line plus some authentication option. At its most wide-open, you could have

listener 1883
allow_anonymous true

It is, of course, better to restrict the listener to the IP addresses that you need and it’s often better to use some kind of authentication mechanism rather than leaving your server wide open.

If you’re upgrading from version 1.6 or earlier, you should look at ChangeLog.txt from the installation directory as it has some discussion of breaking changes. You may also want to look at https://mosquitto.org/man/mosquitto-conf-5.html

Spot on!
Thank you for your support!

It worked perfectly!
Thank you for your support!

windows OS is so Difficult

At its most wide-open, you could have

listener 1883
allow_anonymous true

I’ve just done an update to my home automation Raspberry Pi and Mosquito stopped working. After a couple of hours of panicking I found this post, edited /etc/mosquitto/mosquitto.conf and fixed it. Thank you very much!

If you’re upgrading from version 1.6 or earlier, you should look at ChangeLog.txt from the installation directory as it has some discussion of breaking changes. You may also want to look at https://mosquitto.org/man/mosquitto-conf-5.html

I assume you’re running either without a config file or with a config file that doesn’t define a listener. As of mosquitto 2.0, this gives the behaviour you’re describing. To listen on addresses other than localhost, you need to have a config file with a «listener» line plus some authentication option. At its most wide-open, you could have

listener 1883
allow_anonymous true

It is, of course, better to restrict the listener to the IP addresses that you need and it’s often better to use some kind of authentication mechanism rather than leaving your server wide open.

If you’re upgrading from version 1.6 or earlier, you should look at ChangeLog.txt from the installation directory as it has some discussion of breaking changes. You may also want to look at https://mosquitto.org/man/mosquitto-conf-5.html

I tried useful solution on above because I have a problem on below . However it isn’t useful for me. Is there anyone help me please ?
mqtt broker error: no connection could be made because the target machine actively refused it.

What do I try : I am trying connection and send/receive messeges from Esp8266 to local computer . They use same wireless network. i can send ping my from local pc to esp8266. Also ı can send/receive messages between esp8266 and my PC i use test.mosquitto.org server for MQTT broker .

I can send ping from computer that installed Mosquitto broker to ESP8266 but i can’t subscribe to ESP 8266. Also I can’t publish from ESP8266 to computer that installed Mosquitto broker.
I can communication between ESP8266 and my computer as client by show broker IP test.mosquitto.org.
I tried all things about firewall both windows and router. however i couldn’t connect IoT device and my pc that ı show MQTT broker. I search it on form website. but it is not working..
Can you help me please ? it shown related network permission but i didn’t understand. I chacked network by Netstat but it doesn’t show any communication situation for my clients

If you’re upgrading from version 1.6 or earlier, you should look at ChangeLog.txt from the installation directory as it has some discussion of breaking changes. You may also want to look at https://mosquitto.org/man/mosquitto-conf-5.html

I assume you’re running either without a config file or with a config file that doesn’t define a listener. As of mosquitto 2.0, this gives the behaviour you’re describing. To listen on addresses other than localhost, you need to have a config file with a «listener» line plus some authentication option. At its most wide-open, you could have
listener 1883
allow_anonymous true
It is, of course, better to restrict the listener to the IP addresses that you need and it’s often better to use some kind of authentication mechanism rather than leaving your server wide open.
If you’re upgrading from version 1.6 or earlier, you should look at ChangeLog.txt from the installation directory as it has some discussion of breaking changes. You may also want to look at https://mosquitto.org/man/mosquitto-conf-5.html

I tried useful solution on above because I have a problem on below . However it isn’t useful for me. Is there anyone help me please ?
mqtt broker error: no connection could be made because the target machine actively refused it.

What do I try : I am trying connection and send/receive messeges from Esp8266 to local computer . They use same wireless network. i can send ping my from local pc to esp8266. Also ı can send/receive messages between esp8266 and my PC i use test.mosquitto.org server for MQTT broker .

I can send ping from computer that installed Mosquitto broker to ESP8266 but i can’t subscribe to ESP 8266. Also I can’t publish from ESP8266 to computer that installed Mosquitto broker.
I can communication between ESP8266 and my computer as client by show broker IP test.mosquitto.org.
I tried all things about firewall both windows and router. however i couldn’t connect IoT device and my pc that ı show MQTT broker. I search it on form website. but it is not working..
Can you help me please ? it shown related network permission but i didn’t understand. I chacked network by Netstat but it doesn’t show any communication situation for my clients

Create a new file config named test.conf with 2 lines:
listener 1883
allow_anonymous true

on Window: mosquitto -v -c test.conf
on Rasp: mosquitto -v -c path of test.conf

I assume you’re running either without a config file or with a config file that doesn’t define a listener. As of mosquitto 2.0, this gives the behaviour you’re describing. To listen on addresses other than localhost, you need to have a config file with a «listener» line plus some authentication option. At its most wide-open, you could have

listener 1883 allow_anonymous true

It is, of course, better to restrict the listener to the IP addresses that you need and it’s often better to use some kind of authentication mechanism rather than leaving your server wide open.

If you’re upgrading from version 1.6 or earlier, you should look at ChangeLog.txt from the installation directory as it has some discussion of breaking changes. You may also want to look at https://mosquitto.org/man/mosquitto-conf-5.html

thank you so much, it help me to solve my problem

thank you very much Mr./Mrs.
I solved the problem.

…

Solved for me too. I was receiving rc=-2 messages :

this works great, thank you very much.
Is there a possibility to save these entries? Otherwise I would have to call the «test.conf» file in the console every time before I can connect to the broker.

How can I restrict the listener to a IP addresses?
How can I restrict access to a user with password?

I have the same issue as many who posted here, trying to connect to the mosquitto mqtt broker running on a Windows 10 PC from an ESP32 on the same wireless subnet, which constantly generates an rc = -2 error. I tried the test.conf approach suggested by sayurisa above, but when I run the the mosquitto -v -c test.conf command, I get an error that says «Error: Only one usage of each socket address (protocol/network address/port) is normally permitted.» The ESP32 is disconnected and the Arduino IDE program is not running. There is no other program running that is attempting to access the mqtt broker. I do have a node-red program set to use port 1883 as well, but it is not active when this error is received. Any assistance on what to try next is appreciated !!

Well done! No clue in the example config on dockerhub.

persistence true
persistence_location /mosquitto/data/
log_dest file /mosquitto/log/mosquitto.log

An excellent way to waste others time.

Hi, thanks a lot on this topic and almost solved my windows mosquitto problem.

listener 1883
allow_anonymous true

Almost, means that this will not work if I am running mosquitto on a command prompt.
it works if mosquitto is running as a service.

So uninstall and re-install with the ‘service’ checked and edit the config file. And this works perfectly as a service
Probably its my windows user’s permission is too low that is causing the problem.