Node-red-contrib-wago-cc100 excessive logging by contrib nodes

Node-RED
1

Hello.

Is there an option to set logging off on cc100 contrib nodes? 50 MB of logs is filled up in a few days for me because i cannot turn off the logging of nodes. Even if i set log level in settings.js to off.

Here is an example of my log file how it looks like :

{"log":"Set RawData=0\n","stream":"stdout","time":"2024-09-19T07:21:05.455918042Z"} {"log":"Read DO 1 on CC100 was successful.\n","stream":"stdout","time":"2024-09-19T07:21:07.431554239Z"} {"log":"Raw Data: 0\n","stream":"stdout","time":"2024-09-19T07:21:07.43402933Z"} {"log":"\n","stream":"stdout","time":"2024-09-19T07:21:07.434248747Z"} {"log":"Writing DO 1 on CC100.\n","stream":"stdout","time":"2024-09-19T07:21:07.43660813Z"} {"log":"Write DO 1 on CC100 was successful.\n","stream":"stdout","time":"2024-09-19T07:21:07.444440487Z"} {"log":"AO 1 turned on was successful.\n","stream":"stdout","time":"2024-09-19T07:21:10.462352823Z"} {"log":"Write AO 1 on CC100 was successful.\n","stream":"stdout","time":"2024-09-19T07:21:10.482872428Z"} {"log":"Set RawData=0\n","stream":"stdout","time":"2024-09-19T07:21:10.484603183Z"} {"log":"AO 1 turned on was successful.\n","stream":"stdout","time":"2024-09-19T07:21:15.446142202Z"} {"log":"Write AO 1 on CC100 was successful.\n","stream":"stdout","time":"2024-09-19T07:21:15.455168437Z"} {"log":"Set RawData=0\n","stream":"stdout","time":"2024-09-19T07:21:15.458505864Z"} {"log":"Read all DO's on CC100 was successful.\n","stream":"stdout","time":"2024-09-19T07:21:18.447931864Z"} {"log":"Raw Data: 0\n","stream":"stdout","time":"2024-09-19T07:21:18.449727369Z"} {"log":"\n","stream":"stdout","time":"2024-09-19T07:21:18.450406705Z"}

2

Take a look here : Node-RED stops responding on CC100 after 10-12 hours - #2 by quenorha

3

This is not the problem i have because i limit the size of logs. The problem is logs fill up too fast with information from the cc100 nodes which is always sending data to logs on every input, regardless of logging level in settings.js.

4

If you are using: node-red-contrib-wago-cc100 0.1.0
After looking at the source of the node, i found out every even is using “console.log(…);”
This is OK during developement of the node but not after publishing it.
There will be a need to update it asap.

Could you check this one also:
@plus4nodered/node-red-contrib-wago-cc100 2.0.2
It may be a better fork.

1 Like
5

Console.log is both used in node-red-contrib-wago-cc100 and @plus4nodered/node-red-contrib-wago-cc100 2.0.2. So i cant control its logging by using settings.js there either.

6

Not ideal, but you might want to edit the cc100 .js files to turn off verbose mode. I noticed they are all set to verboseMode=true. You can find these files in the ~/.node-red/node_modules/node-red-contrib-cc100 directory.

image
image946×791 97.8 KB

7

That’s really an oversight from the developers. you can edit the nodes files locally on your system to disable it.
console.log and verbose should only be used for debugging during development …
Sorry i don’t have another solution.
Maybe open a ticket on the GitHub to have it fixed in the next release ?