apache
Burr S3 Tracking - Deployment and Docker Image
Hey Guys,
I am using the Dockerfile provided to host s3 backed server tracker on EKS. I am able to get the UI and stuff and link S3 bucket but for some reason I run into the error
[INFO] 2025-08-26 06:27:39,817 burr.tracking.server.run(79): Updating backend index... [ERROR] 2025-08-26 06:27:39,819 burr.tracking.server.run(99): Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/tortoise/backends/sqlite/client.py", line 43, in translate_exceptions_ return await func(self, query, *args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/tortoise/backends/sqlite/client.py", line 155, in execute_query rows = await connection.execute_fetchall(query, values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/aiosqlite/core.py", line 202, in execute_fetchall return await self._execute(self._execute_fetchall, sql, parameters) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/aiosqlite/core.py", line 122, in _execute return await future ^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/aiosqlite/core.py", line 105, in run result = function() ^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/aiosqlite/core.py", line 83, in _execute_fetchall cursor = self._conn.execute(sql, parameters) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlite3.OperationalError: no such table: project During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/fastapi_utils/tasks.py", line 90, in loop await _handle_func(func) File "/usr/local/lib/python3.11/site-packages/fastapi_utils/tasks.py", line 23, in _handle_func await func() File "/usr/local/lib/python3.11/site-packages/burr/tracking/server/run.py", line 80, in sync_index await backend.update() File "/usr/local/lib/python3.11/site-packages/burr/tracking/server/s3/backend.py", line 520, in update await self._update_projects() File "/usr/local/lib/python3.11/site-packages/burr/tracking/server/s3/backend.py", line 231, in _update_projects current_projects = await Project.all() ^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/tortoise/queryset.py", line 1235, in _execute instance_list = await self._db.executor_class( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/tortoise/backends/base/executor.py", line 108, in execute_select _, raw_results = await self.db.execute_query(sql, values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/tortoise/backends/sqlite/client.py", line 45, in translate_exceptions_ raise OperationalError(exc) tortoise.exceptions.OperationalError: no such table: project
i am not able to grasp it, I am populating the S3 with the burr data itself from a client based on the architecture
Have you done the initialization? Does this only happen on EKS, and not locally?
https://github.com/apache/burr/blob/f499c42d6968fab79fe8384d77dab1ed7d0885e4/burr/tracking/server/s3/README.md?plain=1#L1
I think I managed to start it and it is working, but ran into another issue, with S3 as backend, it is randomly skipping some old logs and files which were once visible and are no longer added to burr UI.
is there a config for that which might enable that feature for me?
is there a config for that which might enable that feature for me?
Which part? It shouldn't be randomly skipping things. It uses a timestamp mechanism to determine things. Are those files still being updated? or?
