-
Notifications
You must be signed in to change notification settings - Fork 61
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
Homer fails to capture after a few days of running #56
Comments
Hi @arainero this sounds definitely like rotation - we're working this issue, for now in order to confirm could you execute the rotation script manually inside the container? |
Executing /opt/homer_mysql_rotate.pl in the homer-cron container appears to have resolved this issue for now. |
If anyone feels brave enough to give take this for a spin and improve it, I hacked together a test image at |
I'm having the same issue. I'm having to run @lmangani I'm going to give |
Hi @davidmaitland please let me know your results, this seems to be a common issue it could solve, but needs some hands to test |
@lmangani it's stuck in a restart loop at the moment. Any ideas? Let me know if you want me to create a new issue for this.
|
@davidmaitland if you could post that in the homer-nocron repo we can quickly resolve it, thanks! |
I don't know if this is related or not, but I haven't had this issue occur again after changing adding "define('RTCP_TABLE_PARTITION', 0);" to webapp/preferences.php. |
Hello,
It appears that Homer stops capturing data after being ran for a few days. If I do a docker-compose down and docker-compose up Homer starts to capture and display new data again. Old data is still accessible.
I do not know for certain, but I suspect it has to do with rotation. Any advice would be appreciated.
The text was updated successfully, but these errors were encountered: