-
Notifications
You must be signed in to change notification settings - Fork 36
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
The daemon died after some time for no reason #21
Comments
Do you have any logs from this session? |
I have the same thing happening. Nothing useful in my logs. The process just seems to randomly die after a period of time. |
@downspot do you have debug enables logging? Also could you send the log anyway, it might be useful for debugging. |
Don't have debugging enabled. I am not sure I see an option for that. Running Automated EBS Snapshots version 0.4.1. Github is not letting me attach the file. 2015-10-11 00:33:42,818 - auto-ebs - INFO - Connecting to AWS EC2 in us-east-1 |
I do not see the debug enabled option, how can enable it? |
any update about this. |
Sorry, have been too busy with other stuff. I intent to take a look sometime during this week or weekend. But a quick look in the code says at least that the debug option is always enabled per default. But there is not so much debug logging :/ |
good, keep me posted please. |
I have not been able to reproduce this, my daemon runs continuously without any crashes. @farassadek do you have an error like the one @downspot reported too in your logs? I can't really see why that error would pose an issue for the daemon though, but it's the only oddity I see in the log.. |
Yeah that error seems like a moot point it's only referring to a snapshot that can't be removed as it's in use for an AMI. On a side note I should point out that that I am also running a cron job in addition to the daemon that is automatically generating the config files for watched and unwatched volumes. I shouldn't be doing something like this however as the daemon could be in the middle of reading those files while running and possibly crash the process? Basically I am doing this on a job, every 45 mins: /opt/rh/python27/root/usr/bin/automated-ebs-snapshots --config /etc/aws/auto-ebs-snapshots.conf --watch-file /etc/aws/auto-ebs-snapshots-volumes-active.conf /opt/rh/python27/root/usr/bin/automated-ebs-snapshots --config /etc/aws/auto-ebs-snapshots.conf --unwatch-file /etc/aws/auto-ebs-snapshots-volumes-inactive.conf Which is adding and removing volumes based on whether the instance is running or not. The daemon could be reading these files while running and possibly be causing my crashes. Also since reporting this in the ticket I haven't had a crash, so there's that. |
Just looked in the logs again and there is nothing that's error based other than the one pasted above. It's been running clean. My thinking is there is some other underlying problem unrelated to automated-ebs-snapshots. Will continue to monitor on my side. |
YES, On Sat, Oct 17, 2015 at 2:12 PM, Sebastian Dahlgren <
Faras Sadek |
Possibly found what is killing the damon on my end. This is the last log entry I see before the damon died. 2015-12-06 01:57:25,042 - auto-ebs - ERROR - 400 Bad Request |
No description provided.
The text was updated successfully, but these errors were encountered: