Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autarc_LAN_User_Stats stopped working after +-12 h #62

Open
powtac opened this issue Jun 7, 2015 · 11 comments
Open

Autarc_LAN_User_Stats stopped working after +-12 h #62

powtac opened this issue Jun 7, 2015 · 11 comments
Assignees

Comments

@powtac
Copy link
Owner

powtac commented Jun 7, 2015

While doing the first real world test the setup stopped working after about 12-14 hours.

@PcTim suggests it might be connected to the DHCP renewal. I think this could be solved by calling Ethernet.maintain(); http://www.arduino.cc/en/Reference/EthernetMaintain every some hours. Or maybe when starting a new IP scan loop.

Another idea was that it stopped working because of some memory overflow.

@powtac
Copy link
Owner Author

powtac commented Jun 7, 2015

I think I will do a long term test with opened Arduino IDE Serial Monitor attached.

@PcTim
Copy link
Collaborator

PcTim commented Jun 7, 2015

If I'm right, Ethernet.maintain(); is called. I'll have a look at this problem. Doing a long term test with the serial monitor is a good idea. Please post the last few lines. There should be a note that the Ethernet connection failed and the board tried to reconnect.

@PcTim
Copy link
Collaborator

PcTim commented Jun 7, 2015

Ethernet.maintain(); is called. Also it should be reconnect by itself. Please check the Serial print

@powtac
Copy link
Owner Author

powtac commented Jun 8, 2015

Currently the tracker is functioning about 24h in a row!

@powtac
Copy link
Owner Author

powtac commented Jun 12, 2015

I think I found the reason for this problem: The Apache server crashed tonight and around the same time the tracker completely stooped to work. So this seem to crash the tracker. Can could that be solved by an timeout on the client that stops waiting after let's say 1-2 minutes when the server does not respond?

@PcTim
Copy link
Collaborator

PcTim commented Jun 13, 2015

Great!
Hmm... A crash shouldn't cause this problem.
When a connection to the server fails, the board tries it x times (can be configured in setup). If it also fails, the board will check its own network connection by pinging the gateway. If the gateway is available it will retry it again to connect to the server and so on...
If the gateway is offline, the board tries to start a new connection.

@PcTim
Copy link
Collaborator

PcTim commented Jun 13, 2015

Oh! I'll see! It's a recursive function! Probably we have a buffer overflow after to many fails!
I'll check how to solve it!

@PcTim PcTim closed this as completed in 1d1622a Jun 13, 2015
@PcTim
Copy link
Collaborator

PcTim commented Jun 13, 2015

Can you check it again please?

@PcTim PcTim reopened this Jun 13, 2015
@powtac
Copy link
Owner Author

powtac commented Jun 13, 2015

I will check it soon. Not sure when. Maybe tomorrow. Thanks for fixing it!

@powtac powtac assigned powtac and unassigned PcTim Jun 13, 2015
@PcTim
Copy link
Collaborator

PcTim commented Aug 11, 2015

Have you checked yet?
I'll have a try at #65 so it would be easier to check possible issues.

@powtac
Copy link
Owner Author

powtac commented Aug 11, 2015

I think it worked. The tracker is still running, but I'm currently not sure on which firmware...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants