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.

Sign up for GitHub

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

Jump to bottom

sqlite3 sometimes fail with status 1280 #8

Closed
mvysny opened this issue Sep 20, 2022 · 2 comments
Closed

sqlite3 sometimes fail with status 1280 #8

mvysny opened this issue Sep 20, 2022 · 2 comments
Assignees
@mvysny

Comments

@mvysny
Copy link
Owner

mvysny commented Sep 20, 2022

1280/256=5 which means SQLITE_BUSY. This can happen when the sqlite database is read by Grafana and at the same time it's attempted to be written to by us.

PRAGMA busy_timeout = 1000; could help?
@mvysny mvysny self-assigned this Sep 20, 2022
mvysny added a commit that referenced this issue Sep 20, 2022
@mvysny
#8 try to prepend PRAGMA busy_timeout before every statement execution
466a2c0
@mvysny
Copy link
Owner Author

mvysny commented Sep 20, 2022

Seems to be fixed by the PRAGMA statement. Closing as fixed.

@mvysny mvysny closed this as completed Sep 20, 2022
@mvysny
Copy link
Owner Author

mvysny commented Sep 20, 2022

Similar issue can be seen in Grafana+sqlite plugin. Filed a bug: fr-ser/grafana-sqlite-datasource#99

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mvysny mvysny

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mvysny