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

Cronjob breaks database if you aren't fully up to date first #168

Closed
lukepighetti opened this issue Mar 25, 2018 · 0 comments
Closed

Cronjob breaks database if you aren't fully up to date first #168

lukepighetti opened this issue Mar 25, 2018 · 0 comments

Comments

@lukepighetti
Copy link

I haven't tested this extensively but it seems that if your 1 minute update chronjob triggers while the previous one is still running it wreaks havoc on the database forcing you to use the patch in #118

That is to say that you should do a full update before setting up your chronjob otherwise you'll spend a lot of time deleting tmp/index.pid

Again, this is a poorly formed issue submission but that's what I've got for now.

Thanks

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

No branches or pull requests

2 participants