Closed platisd closed 6 years ago
@platisd hmm, what is your setup like?
I tried running the ins_server on my machine and it runs for over 1 hour, and also accepted request thereafter. See the time-stamp prints in the screenshot below.
I will investigate further...
I still have the server running, I will see how long before I reproduce the problem.
How did it go? Weird... otherwise it must be some local weird error, since I could consistently reproduce it.
Still running at 19:38 ...
Weird... Let's close this for now and I will open it again if I have a different angle on it.
@lexious89 can you try to run the server on your box and let's see if you can reproduce the problem.
I manage to reproduce this issue. I will be investigating further...
Interesting, keep us posted! :+1:
Strangely enough, I am on my second attempt to reproduce the problem after the first crash with no success. Will be testing on both my ubuntu box and rasberrypi.
On a side note, @platisd are you on slack?
I sure am! 😛
Send invite to my work mail if you're making a channel
Done.
OK, couldn't get it to crash. So, am making a new run on rasberrypi now.
[2017-12-09 17:36:55.200]
[2017-12-09 18:16:52.178]
[2017-12-09 18:35:01.948]
This will be running all night, so, fingers crossed.
What is your setup like? Are you using the wifi_module.ino without letting it sleep?
Yes, modified wifi_module to not sleep and send data continuously with delay(20000);
. I am using NodeMCU device for this.
For the server, I am running on a fresh installation of rasberrypi.
Strange that INS service has been running all night/day and still running (on rasberrypi)
[2017-12-10 14:01:14.282]
I had to press reset button on ins_node this morning because it wasn't sending out data. I guess due to network connection.
I will also try to debug this when I find the time. Any suggestions on where to add extra logs?
Okay, great! As for extra logs, none that I can think of now.
Closing this issue since we haven't observed this issue lately. This can be re-opened again if problem reoccur
I agree. That being said, I think it could make sense to invest in making a Docker image to make sure everyone is running things in the same environment. :+1:
Haha, nice idea. Taking it to another level :smile_cat:
Description
The
ins_server
core-dumps after approximately 16 minutes of operation, regardless of whether it is handling incoming data or not. The defect was reproducible 100% of the times.Ways to reproduce
Have
ins_server
executing for long amounts of time.Related logs
Definition of Done
The
ins_server
can run for indefinite amounts of time.