Hi
I am trying to write some data to an influxdb database but I am getting an EMFILE error which I cant seem to understand. Does anyone have any ideas?
Here is a screenshot of the relevant parts of my flows along with the error showing from the debug node (I have blanked out the IP address of the server running the database other than the port number which is 8086).
I know influxdb expects a very specific format for input which I think I have correct so I suspect it has something to do with trying to connect to the database (which happens to run on a google cloud compute engine instance).
Regards
Colin
3 March 2019 14:32
3
That error means that you have tried to open too many files/sockets. What could be the cause of that I don't know.
by the startup log I understand that I should stop node red and then start it again and see what comes up on the command line screen....correct?
Colin
3 March 2019 16:47
5
Yes, it starts with the Welcome to node-RED message.
Here is the start up log:
Starting as a systemd service.
3 Mar 16:45:58 - [info] Node-RED version: v0.19.5http://127.0.0.1:1880/
Your flow credentials file is encrypted using a system-generated key.
3 Mar 16:46:05 - [info] Starting flows
Colin
3 March 2019 16:49
7
I don't see the error there.
Sorry...I didnt run the flows...here it is:
3 Mar 16:48:18 - [info] [tcp in:MySensors Gateway] Error: connect ETIMEDOUT 192.168.1.20:5003
Colin
3 March 2019 16:57
9
There are several things there I don't understand. Perhaps someone else can comment.
Does the error occur immediately or not till you send the node something? If not till you send something what are you sending. Also export the influx node so we can see how it is configured. If there is any sensitive information in that node or the influx server node that will get exported too then change those before exporting.
The data consists of the following:
Latitude measurement
You can see the object in the following picture from the debug node before it gets formatted into the correct structure for Influxdb:
Then I have a function node to format the data for influx which contains the following:
msg.payload.Lat = parseFloat(msg.payload.Lat);
msg.payload = [
The first section changes the data from strings into floats and the timestamp into a date/time format and the second section structure the data into the right format according to the influxdb node documentation.
Finally the influxdb node just has the configuration for my influxdb server as follows:
I have grayed out the host in the picture which is the ip address for my server where the influxdb database is running.
Colin
3 March 2019 17:32
11
Is the server address that you have greyed out the one in the error message? 35.246...
Colin
3 March 2019 17:44
13
You did not say whether you get the error even if you don't send anything to the db node.
If I disconnect the influxdb node then everything is fine...its only once I connect it that I get the error
Colin
3 March 2019 17:55
15
Enable the debug node showing what is going to the db node, expand everything and check ok
ok here it is:
Similar to the other debug node but the structure is slightly different and strings are now turned to numbers and date is in date format
If you had to grey out the server IP you might want to remove the log that is displaying it over and over....
1 Like
Colin
3 March 2019 20:16
18
Looking at the info tab for the influx node I don't see where it says that the payload can be an array of 1 element containing an object of that form.
I copied the structure from the example batch node at the very end of the page for "node-red-contrib-influxdb" which shows the following structure:
msg.payload = [
I just replaced the fields and tags according to my data which is why I thought I had done it correctly...but it appears not.
Colin
3 March 2019 21:46
20
Ah, you are using the batch node that is not present in the version of node-red-contrib-influxdb that I am using.
Hi Colin
Yes I can access the server, but when I review the firewall logs (I created a firewall rule to open port 8086) there is no record of any activity so I suspect the issue may be in getting the connection out of node red.
