SIMATIC IOT2040 GETTING STUCK (used node-red to send MQTT data)

Dear all,

I'm using Simatic IOT2040 for my project. I'm using 32GB microSD class10 in it. I'm simply fetching data from PLC and coded in function for data publishing time and lastly sending it to an  MQTT out (Thingsboard) the FLOW of node-red is attached.

Before I had used 16GB microSD class4 in it and configured it. Data was sending properly from device for a period of 15 days and it stopped working. So I thought of upgrading microSD to recommended class and I upgraded it to 32GB microSD class10 and  configured it with same flow.

I had configured it on 1-Dec-2020 and data was sending perfectly till now. But on 3-Jan-2021 the same problem has been occurred (the data sending has been stopped).

After the problem occurred again I had pinged the device IP and it was pinging. Device was also accessed on PUTTY. Through WinSCP I copied the log files of device. BUT NODE-RED was not accessible. I tried a lot to access NODE-RED was couldn't access it.

Later when I checked Node-red log it displayed me only from 20-Dec-2020 to 28-Dec-2020. But problem occurred on 3-Jan-2021 so I couldn't find the root cause of  problem. And also it showed Connection Failed to MQTT broker on dated 20-Dec-2020, but data was sending on that day there was no issue. (Node-red log images attached below).

I also checked messages log file so it showed me some message dated 3-Jan-2021 (the day problem occurred). The message is

The message log file is also attached below, kindly look for it.

Later I removed Module power and again powered it up, the Node-red was accessible and data sending started. But Didn't understood what was the actual cause to occur this problem now and then.

So please have a look at the Log files and images attached below and provide me with the cause of problem and some solution to it.

I HAVE ATTACHED ALL THE LOG FILES BELOW IN ZIP. 

Thanks and Regards,

Huzaif Shaikh

Hello sir thanks for the response.

Actually the var/log/node-red.log file is 430mb so i can’t attach the file here. The node red log file doesn’t contain the total logs. It only have logs of 8days and it didn’t contain log of the day module stopped working the logging stopped 2 days before module had crash. U can check the message log file attached above as it contain some messages of OOM killer on the day module stopped working. And also you can check my node red flow attached above. After plugging out power and plugging back power to module the data sending started automatically. Please check for some solution to it sir.

Thanks and Regards

Huzaif Shaikh

Thanks for your reply sir. Actually I haven't checked the memory usage of module. The same problem has occurred again. I copied the log files from module. And again the Node-red.log file is above 400MB. But one important point has come in observation that in messages file there are messages occurred the same day module getting stuck. The message is as follow :

The same  message is in previous message log file of the last time it got stuck. The both files are attached below, please do check it and provide some solution. And please explain the above method to decrease level of logging.

Thank You

df -h

 And i will configure it to log just error and check the status of its operation and get back to you.

Regards

Huzaif Shaikh

Dear sir,

The screenshot of df -f is attached below. This screenshot is taken after 8 days of Powering up the IOT module.

And I have changed the level of logging to just "error" and observed that no info and debug is saving in log  file.

I will check the df -h after 25 days and update it later.

Thank You