Talk chats broken after table recration

ℹ️ Support 💬 Talk (spreed)
,
1
Support intro

Nextcloud version (eg, 24.0.1): current
Talk Server version (eg, 14.0.2): current
Custom Signaling server configured: no
Custom TURN server configured: no
Custom STUN server configured: no

The issue you are facing:

Yeah I know removing database tables will/can result into breakage. But we had to rebuild the Talk database tables because one table was missing, after this, Talk was running and working. But now we experience the following behavior, Users don’t have the Default Chat Rooms provided by the system (“Talk updates, etc..”). Now when Users start a chat with another user the “What is new in Talk” Message gets posted. We tried to uninstall and reinstall Talk but that didn’t help. So that’s why I created the docker compose file below to run tests for a solution. I’m running out of things to check and test, any directions would help.

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

  1. Run Compose:
volumes:
  nextcloud:
  db:
networks:
  nextcloud:

services:
  db:
    container_name: nextcloud-db
    image: mariadb:10.6
    restart: always
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    volumes:
      - db:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=test
      - MYSQL_PASSWORD=test
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
    networks:
      - nextcloud
  phpmyadmin:
    image: phpmyadmin/phpmyadmin
    container_name: pma
    ports:
     - "81:80"
    links:
      - db
    environment:
      PMA_HOST: nextcloud-db
      PMA_PORT: 3306
      PMA_ARBITRARY: 1
    restart: always
    networks:
      - nextcloud
  app:
    container_name: nextcloud-app
    image: nextcloud
    restart: always
    ports:
      - 80:80
    links:
      - db
    volumes:
      - nextcloud:/var/www/html
    environment:
      - MYSQL_PASSWORD=test
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=nextcloud-db
    networks:
      - nextcloud
  1. Install Talk Extension
  2. Create Test Users
  3. Start Chats with Test Users
  4. Empty all Tables with talk in the name
  5. Observe bugged behaviour
2

Hello @BeatrizGabrielEric,

welcome to the Nextcloud community! :handshake:

Definitely you are walking the wrong path :slight_smile: messing with the DB is never a good choice.. but now what is your problem? you see that clearing out tables results in a problem and as far I get your post you can repro the issue in your docker test bed. Depending on your knowledge and time you are willing to spend you should start from scratch - carefully review the content of the Talk tables (especially after clean install) and try to add/rebuild content required for Talk function into your production DB.