Error frappe.exceptions.SessionBootFailed

Hello,

I am getting below error after restoring site…

Traceback (most recent call last):
File “apps/frappe/frappe/www/app.py”, line 27, in get_context
boot = frappe.sessions.get()
^^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/sessions.py”, line 138, in get
bootinfo = get_bootinfo()
^^^^^^^^^^^^^^
File “apps/frappe/frappe/boot.py”, line 40, in get_bootinfo
get_user(bootinfo)
File “apps/frappe/frappe/boot.py”, line 278, in get_user
bootinfo.user = frappe.get_user().load_user()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/utils/user.py”, line 213, in load_user
d = frappe.db.get_value(
^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/database/database.py”, line 519, in get_value
result = self.get_values(
^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/database/database.py”, line 623, in get_values
out = self._get_values_from_table(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/database/database.py”, line 896, in _get_values_from_table
return query.run(as_dict=as_dict, debug=debug, update=update, run=run, pluck=pluck)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/query_builder/utils.py”, line 87, in execute_query
result = frappe.db.sql(query, params, *args, **kwargs) # nosemgrep
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/database/database.py”, line 234, in sql
self._cursor.execute(query, values)
File “env/lib/python3.11/site-packages/pymysql/cursors.py”, line 153, in execute
result = self._query(query)
^^^^^^^^^^^^^^^^^^
File “env/lib/python3.11/site-packages/pymysql/cursors.py”, line 322, in _query
conn.query(q)
File “env/lib/python3.11/site-packages/pymysql/connections.py”, line 558, in query
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “env/lib/python3.11/site-packages/pymysql/connections.py”, line 822, in _read_query_result
result.read()
File “env/lib/python3.11/site-packages/pymysql/connections.py”, line 1200, in read
first_packet = self.connection._read_packet()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “env/lib/python3.11/site-packages/pymysql/connections.py”, line 772, in _read_packet
packet.raise_for_error()
File “env/lib/python3.11/site-packages/pymysql/protocol.py”, line 221, in raise_for_error
err.raise_mysql_exception(self._data)
File “env/lib/python3.11/site-packages/pymysql/err.py”, line 143, in raise_mysql_exception
raise errorclass(errno, errval)
pymysql.err.OperationalError: (1054, “Unknown column ‘default_workspace’ in ‘field list’”)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “apps/frappe/frappe/website/serve.py”, line 20, in get_response
response = renderer_instance.render()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/website/page_renderers/template_page.py”, line 84, in render
html = self.get_html()
^^^^^^^^^^^^^^^
File “apps/frappe/frappe/website/utils.py”, line 523, in cache_html_decorator
html = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/website/page_renderers/template_page.py”, line 95, in get_html
self.update_context()
File “apps/frappe/frappe/website/page_renderers/template_page.py”, line 163, in update_context
data = self.run_pymodule_method(“get_context”)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/website/page_renderers/template_page.py”, line 223, in run_pymodule_method
return method(self.context)
^^^^^^^^^^^^^^^^^^^^
File “apps/frappe/frappe/www/app.py”, line 29, in get_context
raise frappe.SessionBootFailed from e
frappe.exceptions.SessionBootFailed

Clear your browser cookies and then give it another try

I am getting the same error after restoring a site to a new bench site. Can anyone help

can anyone solved this?

i found this https://stackoverflow.com/questions/76963794/this-error-where-add-frappe-erpnext-after-bench-update and solved on my case

bench --site {site} migrate
1 Like

Solved it also for me on a deployment in kubernetes. If doc types or the database schema changes, then you need to do a bench migrate.

Trying to summarize: How are updates handled with docker images? When a new version is deployed that requires a bench migrate, this should be performed automatically. This is important especially for a kubernetes set-up - if a pod is being moved to another worker, it would pull the latest image and needs to trigger a migration. In the Helm chart this has been fixed lately fix: migrate job by revant · Pull Request #154 · frappe/helm · GitHub by @revant_one