Seems like Redis instance is not running as it should. Are you using docker compose (development ones) here? If so are you running Baserow via our dev.sh script?
@petrs, based on the containers running, it looks like it’s somehow using our Helm chart. @jpca999 we would need to have more details on how you’re self-hosting specifically, and how/where you’re running the PostgreSQL and Redis database because I didn’t see those services in your screenshot.
let me know how & when we can connect on a live call to get this resolved!
Hey @jpca999, I’m afraid we can only offer community support in this forum. We can only give support over a video call to our enterprise customers. I’m not still more than happy to help you here, but I barely have any insights in how your environment is working. We would need to know as many details as possible on how you’re self-hosting. Specifically:
- How did you setup the Baserow environment? With the Helm chart?
- Where are you running the PostgreSQL and Redis database?
- Are you using a tool to self-host Baserow? The reason I’m asking is because I don’t recognize the screenshots.
Alternatively, you can also explore the all-in-one Docker image (Install with Docker) for self-hosting. This one is much easier to configure because it’s a single container.
Hi,
Thank you for your message and for offering support through the forum. I completely understand the policy regarding enterprise-level support. However, I want to point out that I’m essentially testing your product for free, identifying bugs, and providing detailed feedback to help improve it. The goal here is to make your product better and more robust for everyone, which is a win-win for both sides.
While I appreciate the community support, it would be far more efficient to resolve these issues via a quick video call or a more direct interaction, especially considering the complexity of self-hosting environments and the specific bugs I’ve encountered.
Let me know if this is possible or if there’s another way we can expedite resolving these issues.
- How did you setup the Baserow environment? With the Helm chart? No help , i just run on local 3000.
- Where are you running the PostgreSQL and Redis database? Yes i make sure to start it in the docker.
- Are you using a tool to self-host Baserow? The reason I’m asking is because I don’t recognize the screenshots. No tools just docker.
Hey @jpca999, this is not giving me enough information. Can you please share detailed steps on how you setup your self-hosted environment and how you’re stopping and starting it? The more details, the better.
Let’s focus on resolving the error. Another person has identified the cause, and it appears to be the following:
• The issue occurs when a user inputs a data string that exceeds the desired length.
• The system does not display an error or validation message to the user, allowing the invalid input to proceed.
• This is now causing problems with exporting data and duplicating the table.
This issue is not related to where the system is hosted. Based on my observations, the problem seems to be with the data type for long text.
Please investigate and get this fixed.
unexpected: DataError(‘value too long for type character varying(255)\n’)
psycopg2.errors.StringDataRightTruncation: value too long for type character varying(255)
packages/django/db/backends/utils.py”, line 105, in _execute
@bram @olgatrykush @joffcom @petrs
I removed the data from my notes where the string was too long, but the issue still isn’t resolved.
Somebody has to try using console log in the code to find where the error is happening.
Heres’ the same error log :
2025-01-21 12:30:19 [2025-01-21 17:30:19,771: INFO/MainProcess] Task baserow.core.jobs.tasks.run_async_job[0081b13e-50c3-418e-9e68-4bd0caf152ad] received
2025-01-21 12:30:24 [2025-01-21 17:30:24,678: ERROR/ForkPoolWorker-6] Task baserow.core.jobs.tasks.run_async_job[0081b13e-50c3-418e-9e68-4bd0caf152ad] raised unexpected: DataError(‘value too long for type character varying(255)\n’)
2025-01-21 12:30:24 Traceback (most recent call last):
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/backends/utils.py”, line 105, in _execute
2025-01-21 12:30:24 return self.cursor.execute(sql, params)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 psycopg2.errors.StringDataRightTruncation: value too long for type character varying(255)
2025-01-21 12:30:24
2025-01-21 12:30:24
2025-01-21 12:30:24 The above exception was the direct cause of the following exception:
2025-01-21 12:30:24
2025-01-21 12:30:24 Traceback (most recent call last):
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/celery/app/trace.py”, line 453, in trace_task
2025-01-21 12:30:24 R = retval = fun(*args, **kwargs)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/celery/app/trace.py”, line 736, in protected_call
2025-01-21 12:30:24 return self.run(*args, **kwargs)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/core/jobs/tasks.py”, line 33, in run_async_job
2025-01-21 12:30:24 JobHandler.run(job)
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/core/jobs/handler.py”, line 73, in run
2025-01-21 12:30:24 out = job_type.run(job, progress)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/contrib/database/table/job_types.py”, line 62, in run
2025-01-21 12:30:24 new_table_clone = action_type_registry.get_by_type(DuplicateTableActionType).do(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/contrib/database/table/actions.py”, line 336, in do
2025-01-21 12:30:24 new_table_clone = TableHandler().duplicate_table(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/core/telemetry/utils.py”, line 72, in _wrapper
2025-01-21 12:30:24 raise ex
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/core/telemetry/utils.py”, line 68, in _wrapper
2025-01-21 12:30:24 result = wrapped_func(*args, **kwargs)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/contrib/database/table/handler.py”, line 895, in duplicate_table
2025-01-21 12:30:24 imported_tables = database_type.import_tables_serialized(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/contrib/database/application_types.py”, line 518, in import_tables_serialized
2025-01-21 12:30:24 self._import_table_views(serialized_table, id_mapping, files_zip, progress)
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/contrib/database/application_types.py”, line 856, in _import_table_views
2025-01-21 12:30:24 view_type.import_serialized(table, serialized_view, id_mapping, files_zip)
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/contrib/database/views/view_types.py”, line 153, in import_serialized
2025-01-21 12:30:24 grid_view = super().import_serialized(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/backend/src/baserow/contrib/database/views/registries.py”, line 426, in import_serialized
2025-01-21 12:30:24 view_filter_object = ViewFilter.objects.create(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/manager.py”, line 87, in manager_method
2025-01-21 12:30:24 return getattr(self.get_queryset(), name)(*args, **kwargs)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/query.py”, line 679, in create
2025-01-21 12:30:24 obj.save(force_insert=True, using=self.db)
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/base.py”, line 822, in save
2025-01-21 12:30:24 self.save_base(
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/base.py”, line 909, in save_base
2025-01-21 12:30:24 updated = self._save_table(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/base.py”, line 1071, in _save_table
2025-01-21 12:30:24 results = self._do_insert(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/base.py”, line 1112, in _do_insert
2025-01-21 12:30:24 return manager._insert(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/manager.py”, line 87, in manager_method
2025-01-21 12:30:24 return getattr(self.get_queryset(), name)(*args, **kwargs)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/query.py”, line 1847, in _insert
2025-01-21 12:30:24 return query.get_compiler(using=using).execute_sql(returning_fields)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/models/sql/compiler.py”, line 1823, in execute_sql
2025-01-21 12:30:24 cursor.execute(sql, params)
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/backends/utils.py”, line 122, in execute
2025-01-21 12:30:24 return super().execute(sql, params)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/backends/utils.py”, line 79, in execute
2025-01-21 12:30:24 return self._execute_with_wrappers(
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/backends/utils.py”, line 92, in _execute_with_wrappers
2025-01-21 12:30:24 return executor(sql, params, many, context)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/backends/utils.py”, line 100, in _execute
2025-01-21 12:30:24 with self.db.wrap_database_errors:
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/utils.py”, line 91, in exit
2025-01-21 12:30:24 raise dj_exc_value.with_traceback(traceback) from exc_value
2025-01-21 12:30:24 File “/baserow/venv/lib/python3.11/site-packages/django/db/backends/utils.py”, line 105, in _execute
2025-01-21 12:30:24 return self.cursor.execute(sql, params)
2025-01-21 12:30:24 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-21 12:30:24 django.db.utils.DataError: value too long for type character varying(255)
2025-01-21 12:30:24
Hey @jpca999, there is a good chance that you’re running into two separate problems.
In one of the earlier logs you shared, it clearly says that no connection can be made to your Redis server. That also explains why the CSV export is stuck.
2025-01-09 12:35:39 [2025-01-09 17:35:39,830: ERROR/MainProcess] consumer: Cannot connect to redis://:@redis:6379/0: Error -2 connecting to redis:6379. Name or service not known…
Anyway, when duplicating a table, it looks like something goes wrong when creating a specific filter. This is interesting because it’s duplicating a filter, and the original length of the value also can’t exceed 255 characters, so when recreating it, it shouldn’t fail.
Would you be able to provide us with an export of your workspace so that we can debug the problem? You can find how to do this here Export a workspace. Note that if the export doesn’t start, we would need to have output logs again, because that might confirm my previous message about the Redis server.
As a side note, it does look like you’re self-hosting the development environment because I see containers like baserow-otel-collector and baserow-celery-flower. Hence, I first thought you were using the Helm chart, but if that’s not the case, you’re using the docker-compose.dev.yml file. Any reason why that is?
The repository has two branches: develop and master.
I’m using the master branch to run the local. and run git pull to get the latest changes. I am not familiar with the Helm chart.
Hey @jpca999, I’m really sorry to say it, but this conversation is not going anywhere. The explanation about branches and doing a git pull doesn’t tell me anything about how you’re hosting Baserow. There is also no export like I requested. I can’t help you any further.
I am running it on localhost and cannot provide a full export of my confidential data.
Could you please guide me on how to run it locally in a way that ensures it operates quickly and without any issues? Thank you!
Sure, I recommend using the all-in-one Docker image Install with Docker.
1 Like
This is working great for me.
1 Like
Glad to hear that it’s working for you @jpca999!
Question: Once the setup is complete, how do I upgrade to the latest code changes?
Please see the documentation Install with Docker