Database error on editing event homepage (v3.2.9)

1

Thank you for a fantastic resource. I am helping maintain an instance of Indico on a Rocky Linux server for a small conference. One of the conference organizers alerted me that they were unable to update the event homepage, with a “Something went wrong - There was a database error while processing your request” pop-up.

I checked /opt/indico/log/celery.log and found thousands of instances of the same error message including the following exception:

Traceback (most recent call last):
  File "/opt/indico/.venv/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1905, in _execute_context
    self.dialect.do_execute(
  File "/opt/indico/.venv/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
    cursor.execute(statement, parameters)
psycopg2.errors.UndefinedTable: relation "plugin_livesync.agents" does not exist
LINE 2: FROM plugin_livesync.agents

However, I’m not certain this exception is related.

We recently did a minor version update to v3.2.9 when installing the plug-ins, which broke the site. A colleague of mine who administrates the server ran a database migration that seemed to resolve the issue. I’m guessing that we are running into residual migration issues but I’m not sure where to begin. Any tips greatly appreciated. I will continue to check the forum for possible dups.

2

Does not seem to be related to 3143 (multiple revisions)

psql (13.16)
Type "help" for help.

indico=> select \* from alembic_version;
 version_num  
--------------
 aba7935f9226
(1 row)

indico=> \\q
3

indico db --plugin livesync upgrade to create the DB tables for the plugin.

However, since it’s quite unlikely that you actually make use of the livesync plugin (unless you really use an external search engine for indico search), I’d rather suggest you to disable the livesync plugin (and citadel plugin in case it’s enabled) in indico.conf instead of running the above command.

Also, please note that v3.2.9 has been released almost 2 years ago and is end-of-life and thus unsupported, including security fixes that have been made in v3.3.x releases. You should update to the latest v3.3.x release ASAP.

4

That did the trick, thanks so much!
Re: major version update, we are just about to open abstract submission for the upcoming meeting so I need to postpone this but we will definitely do the upgrade.