-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Container keeps restarting (loop) #1
Comments
Hi, thanks for reporting a problem. Can I please get you to send the output of |
(I just want to know the architecture you're running on) |
Also can you please post your |
Paging @xenon149... :) |
Hi, it's been a week since you opened this issue with no response back. I'm going to close this issue as "no response", however if you're still having the issue please let me know and I'd be more than happy to re-open and help you troubleshoot. Cheers! |
Hey, apologies for not replying! Apparently, I forgot to change my email address on my Github account... Don't really use this account much. Here is the system info that you asked for:
System is a raspberry pi zero.
The run command I'm using is as follows:
and to show that the influxdb service is responding on this address/port to requests:
Thank you so much for your help! |
Hi @xenon149 no problems at all. I think the issue might be with the
Did you want to give that a try and let me know how you get on? If you get stuck with any of this, let me know and I'd be happy to help further. -Mike |
@mikenye I'm experiencing the same "container restarting" loop issue. I'm running my docker instance on a Synology NAS:
I can confirm network connectivity between the NAS and my RPi3b+ running piaware. The piaware db gets created in Influx but nothing further happens beyond that. See logs below, appears connection is good and data is being received, however processing of that data results in an error.
Thoughts? |
Hi @natedzl, Sorry you're having problems. I cannot replicate this problem in my environment so I'm going to need some additional information from you. I need to generate some commands for you to run in order to troubleshoot, however in order for me to do this I need the command line (or a screen shot of the settings) that you used to create your docker container. Are you able to provide this information please? Alternatively if you can get onto a shell within the container (eg:
On my working container they look like this:
Thanks. -Mike |
One other thing @natedzl, when you need to quote multiple lines, do it by placing three backticks on a blank line, then paste your multi-line output, then place another three backticks on a blank line. Eg:
... will give you:
Thanks. -Mike |
Hi Mike, I've rebuilt everything on an Ubuntu VM to rule out anything with the Synology setup. The container still actively restarts. There's a lot of storms in my area today so flight traffic is quite low, I've noticed the container will run when there's no data stream coming in from dump1090, however, once the data begins the container restarts. Not sure if that is helpful, but I believe that supports my earlier theory with the data processing part. I'm currently running Piaware v 3.6.2 Docker Command:
InfluxDB Ping:
Dump1090 Messages:
Thanks, |
Hi Nate, Thanks for getting back to me with that information. I agree there is definitely a bug and I'm actively working on fixing it. Thanks for your patience. Kind regards, |
Hi Nate, The issue appears to be with a difference in how your dump1090 is formatting the data. Here's the output from my dump1090:
And here's the output from your dump1090:
Note the timestamps I've highlighted; your dump1090 has a significantly higher time resolution than mine - 10 digits as opposed to 3. I have no idea why this is the case. I'm running piaware on x86 platform so it might be due to architecture differences if you're running on an RPi (armv7l) platform. Regardless, I'll implement a fix for this. Thanks for your help on this. -Mike |
On some platforms, dump1090 is sending a timestamp with more resolution than python can handle. In issue #1, the timestamps have the format: `07:37:23.1568119043`. Python datetime's `%f` directive supports from one to six digits, and was causing a `ValueError` for the extra digits. Adding a restriction `[0:15]` for the time string simply drops the additional digits from the end of the string, preventing an error for these situations.
Hi Nate, I've implemented a fix and tested in my environment. As I couldn't replicate your problem, could I trouble you to test in your environment? I've pushed a new image: Provided the container restart issue is fixed, if you could post the first 30 lines or so of the container ( If your feedback is positive, I'll merge these changes into the master branch, do a cross-platform build and push a new "latest" tagged container. Thanks! -Mike |
Thanks for your quick responses Mike, Container is still restarting. Here's the logs, let me know if I can get you any further info.
Thanks, |
Thanks for the output. The good news is that the issue with the timestamp is solved. I'll work on fixing this. Thanks for your patience! |
Implement a set to hold hexidents to clean, then perform the 'del' operation outside of the "for hexident in self.database:" loop.
Hi Nate, Could you please retry your testing with image Could please post the first 30 lines or so of the container logs after it has been running for several minutes and captured some data? Thanks. -Mike |
Mike - appreciate the fast turn-around! The container loop issue appears to be solved! However, I'm not getting any data flowing into Influx. I stopped the piaware2influx container, deleted the DB from Influx and restarted the container. The database did get re-created as expected but I'm not seeing any data nor am I seeing anything in the logs that point to any write failures, etc. Thoughts?
Thanks, |
Hi Nate, No problems! It's very odd you're continually getting the "CLEANUP" messages - these should only be happenning very sparsely. This is likely the reason why you're not getting any data. I'm going to put together a release with debug logging, stay tuned for this. Thanks again for your patience. -Mike |
Hi Nate, I'm wondering if you could check the date and time on your piaware/dump1090 host, and also the host running piaware2influx. I have a hunch that what might be happening is that the clock on the piaware/dump1090 host may be wrong, which is triggering the piaware2influx script to prematurely run its clean up procedures when it receives a message with a timestamp that is older than 15 minutes. I should have a debug container ready for you in a few hours when I get home from my day job, but if you could ensure the clocks on your hosts are synchronized and correct it would be greatly appreciated. Thanks. -Mike |
Hi Nate, I've pushed a debug image that will generate a tonne of logs that I can go through. Please run You can then stop the container and send me through the logs. Thanks. -Mike |
Mike, I've got data getting into influx! |
This is awesome news! OK. I'll roll the changes made in this image into the master branch, and update the readme to recommend setting the TZ paramater. Thanks so much for helping me troubleshoot this issue and making the container better for everyone! -Mike |
Implement S3 overlay. Logging improvements.
OK, the new amd64 image is up: Thanks. -Mike |
Hi Nate, That is fantastic and I'm relieved to see it working for you. :-) I've merged the changes with the master branch, built the new image on all platforms and pushed a new Please use that, and let me know if you have any issues in the future. Thanks again for your help troubleshooting these issues. The image was overdue for some love and attention so its been great getting it up to scratch. I'll now close this issue out! Kind regards, |
Hey!,
I think I have found an issue with this code
The Docker Container keeps restarting after I try spinning it up using the run commands.
docker version: _ 18.06.1
ce3-0 5:18.09.03-0_Tried recreating container.
No log output.
The text was updated successfully, but these errors were encountered: