Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding '--quiet' does not suppress warning #1284

Closed
robdejonge opened this issue May 18, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@robdejonge
Copy link

commented May 18, 2019

Firing mosquitto_pub from scripts launched by both systemd and Duplicati, in both cases results in an error message:

Warning: Unable to locate configuration directory, default config not loaded

I run mosquitto_pub with a defined MQTT host, topic and message as parameters. The script launched by systemd is just printing messages into the syslog, but the script fired by Duplicati is actually resulting in warnings being passed up the chain. I'm not happy with this and would like the warnings gone. Running directly from the command line does not throw those errors.

What I've already tried:

  • Installed the mosquitto daemon, to see if this would install some kind of configuration that the tool would be happy enough with. Nope.
  • Tried to figure out how and where a config should be saved, but couldn't find much information to this.

So I thought I'd use the ugly solution:

  • Add the --quiet switch as it's advertised to not print error messages.

Doesn't work!

@robdejonge robdejonge changed the title Adding "--quiet" does not suppress warning Adding '--quiet' does not suppress warning May 18, 2019

ralight added a commit that referenced this issue May 21, 2019

@ralight ralight added this to the 1.6.3 milestone May 21, 2019

@ralight

This comment has been minimized.

Copy link
Contributor

commented May 21, 2019

Thanks Rob, I've pushed a change that fixes that. It'll be in 1.6.3.

@ralight ralight closed this May 21, 2019

ralight added a commit that referenced this issue Jun 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.