mirror of
https://github.com/plashchynski/crono.git
synced 2026-01-11 21:10:24 +01:00
Crono writes system full log #26
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @derotune on GitHub (Feb 12, 2016).
Hey, crono runs fine but it also posts unlimited log entries till the system space is full. What is this?
@carolyn-idi commented on GitHub (Feb 12, 2016):
I had the same issue. It seems to be saving the crono log into one cell in the crono table. This will quickly reach the cell limit and causes crono to stop. Although I really like crono, I had to switch to something else that was a bit more reliable and have not had any issues since.
@derotune commented on GitHub (Feb 16, 2016):
@ceospfx In my situation crono writes into ENV.log in the rails app. What do you use now?
@carolyn-idi commented on GitHub (Feb 17, 2016):
For rails crono creates a table in your database to keep track of when it
ran.
It's generally one row in the table that keeps getting updated. In that
table one of the cells is keeping track of the log records - this is what
grows each time crono runs and it will eventually reach the cell limit and
die.
Hope that helps,
C.
On Tue, Feb 16, 2016 at 12:33 AM, BeeZerk notifications@github.com wrote:
Insomniac Digital, Inc.
Direct: 310-502-6666
@plashchynski commented on GitHub (Jun 24, 2016):
Hello @ceospfx do you use MySQL? Because Postgres has an unlimited
textfield. Anyway, it's a good case. As temporary solutions, you can change your crono_jobs text field type from TEXT to LONGTEXT:@plashchynski commented on GitHub (Jun 24, 2016):
Hello @LordPrettyFlacko could you send me the command line you use to start crono and your cronotab. Thank you.
@reiz commented on GitHub (Oct 27, 2016):
I have the same issue with MariaDB. Keeping pumping unlimited text into a SQL database is not the smartest thing. Anyway I'm not interested in ALL the logs. The last 7 days would be more than enough. Would be cool if it would be configurable.
Is there a quick way to turn off all the logs?
@reiz commented on GitHub (Oct 27, 2016):
@plashchynski I thought again about this problem and indeed it would be cool if we could configure the number of logs. I'm only interested in the last 50 log messages. Everything what is older is not important for my use case. Would be awesome if we could configure that number :-)
@plashchynski commented on GitHub (Oct 27, 2016):
@reiz fair enough
@reiz commented on GitHub (Nov 28, 2016):
Hi @plashchynski. How much time would it take for you to fix this issue? What is your estimate?
I'm working on VersionEye, which is fully open source as well. And I know how annoying it is when everybody is complaining but nobody is willing to pay Money or at least contributing. For me it would be worth $50 if you fix this ticket. Feel free to invoice me (reiz [at] versioneye.com) if you close this ticket :-)
@plashchynski commented on GitHub (Nov 30, 2016):
Now you can specify:
Also, there is increased text size limit in the migration for MySQL users
@reiz commented on GitHub (Nov 30, 2016):
@plashchynski Awesome 👍 I will try it today. Just transferred you the $50.
@reiz commented on GitHub (Nov 30, 2016):
@plashchynski Will you push a new release to RubyGems today?
@plashchynski commented on GitHub (Nov 30, 2016):
@reiz Thanks. There's a new version 1.1.1 with these changes.
@reiz commented on GitHub (Dec 1, 2016):
@plashchynski Great! I just deployed it to production with the new config and it seems to work like expected. Many thanks for the fast turnaround!
@plashchynski commented on GitHub (Dec 1, 2016):
@reiz You're welcome :)