Hey,
I’m running a local temporal instance on my mac for development, and after a while it is running, it gets stuck and this error log is being spammed infinitely, until i restart it and it gets fixed.
level=ERROR msg=“Operation failed with internal error.” error=“ListNamespaces operation failed. Failed to get namespace rows. Error: SQL logic error: no such table: namespaces (1)” error-type=serviceerror.Unavailable operation=ListNamespaces
Is it a known issue?
Thanks!
I am facing the same issue, but a lot earlier:
➜ temporal server start-dev --db-filename temporal.db
time=2024-11-19T16:35:40.455 level=ERROR msg="failed starting server: failed creating namespaces: error creating namespace \"default\": SQL logic error: no such table: namespaces (1)"
This local temporal played a crucial role in our decision to use temporal cloud in my startup company.
We ran a lot of tests on it before deciding to rely on it, and everything used to work great during our tests. But had this issue occur during our tests, we might have not continue with temporal.
This is why i think fixing this issue is pretty important, as it might affect the first impression on temporal in a bad way (when testing temporal for the first time)
Besides that, I must say that generally I’m very happy we use temporal.
We are also faicing this issue - any workaround? Someone from temporal can help here? Do you need additional info?
Hello,
We have pushed a fix for this issue to the SQLite driver: Implement ResetSession and IsValid methods in connection.
The next temporal release(v1.26) will have this fix: #6836.
In the mean time, if that can help anyone, I was able to work around this issue with no observable performance impact in my tests with the following command:
temporal server start-dev \
--db-filename temporal.sqlite \
--sqlite-pragma journal_mode=WAL
Note that this will create a file persisted database, which you may want to clear up between execution:
rm -f temporal.sqlite*
Thanks for the update, i appreciate! any estimation for 1.26 release date?