Multiple MQTT output nodes to same server

[Andrew Lindsay]

Hi Guys,

Is there a limit to the number of MQTT nodes that can connect to the same MQTT broker, in my case Mosquitto?

I have a number of flows, some subscribe to specific topics for actions based on the topic message, others publish to topics that are either specified within the node itself or in the message topic.

What I'm finding is that one or 2 of the output nodes dont seem to be publishing the message, even though though the same message is being fed to a debug node at the same time. As a quick check I picked one of the nodes, went to edit it and it said the config was in use by 32 nodes! It takes a deploy or a restart to kick it back into life and start publishing on the node again.

I'm not using any authentication with mosquitto. Are there any settings to check or monitoring that can be done to debug this issue?

thanks

Andrew

[Nicholas O'Leary]

We spotted today the cnfignode counts are wrong... So don't pay too much attention to them at the moment.

There isn't a limit... the all reuse the same connection to the broker. How many have you got?

Can you raise an issue on githib to track it?

N

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andrew Lindsay]

I thought 32 was a bit high! Done a quick count and its 5 input nodes and 12 output nodes.

Found the configuration tab and that shows really odd values. It lists localhost:1883 3 times with 33 nodes on one and 1 on another.

I'll head over to github and raise an issue.

thanks

Andrew

[Nicholas O'Leary]

Can you know include any console output from the nodes... Messages about connecting/disconnecting etc.

Thanks,
N

[Andrew Lindsay]

ok, may take a day or 2 to capture the data as it doesnt seem to lose connection straight away. 

thanks

Andrew

[chris mobberley]

Andrew,

Quite a few times I've had a lot of fragmentation of connection details showing up multiple times with different nodes against each and even some items in the configuration window showing that nodes are using it when they arent. A couple of times now I've deleted out all the configs and gone through and started again with them to rectify this.

To your point about mqtt sending dieing I previously had that issue also and I think I raised it as an issue either on here or git hub. I never found out why but it seems to have fixed itself after recent upgrades to node-red. However with that being said I do see a lot of connect/disconnect from broker messages in my console too.

[Andrew Lindsay]

Got some logs now and I see lots of disconnects & reconnects to the broker. Any options to increase the debug level to see what nodes are affected?

Cheers

Andrew

[Nicholas O'Leary]

Assuming you're running 0.6, the connect/disconnect log messages should already contain an id to help correlate instances of the client connection. They aren't the same thing as the node ids in your flows file, but are useful in understanding what's happening... For me at least.

N