mattermost-docker icon indicating copy to clipboard operation
mattermost-docker copied to clipboard

ERROR: relation "idx_teams_description" does not exist

Open nvjacobo opened this issue 4 years ago • 11 comments

Hi

I am running Mattermost 5.14.1 with docker-compose. The db container prints the following error:

db_1   | LOG:  database system was shut down at 2019-09-03 04:57:08 UTC
db_1   | LOG:  MultiXact member wraparound protections are now enabled
db_1   | LOG:  database system is ready to accept connections
db_1   | LOG:  autovacuum launcher started
db_1   | ERROR:  relation "idx_teams_description" does not exist
db_1   | STATEMENT:  SELECT $1::regclass

Thanks

nvjacobo avatar Sep 03 '19 05:09 nvjacobo

Hi,

I updated to Mattermost 5.15. It persists:

web_1  | 2019/09/22 20:52:53 [warn] 1#1: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/conf.d/mattermost.conf:15
web_1  | nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/conf.d/mattermost.conf:15

nvjacobo avatar Sep 23 '19 02:09 nvjacobo

Hi

I am running Mattermost 5.14.1 with docker-compose. The db container prints the following error:

db_1   | LOG:  database system was shut down at 2019-09-03 04:57:08 UTC
db_1   | LOG:  MultiXact member wraparound protections are now enabled
db_1   | LOG:  database system is ready to accept connections
db_1   | LOG:  autovacuum launcher started
db_1   | ERROR:  relation "idx_teams_description" does not exist
db_1   | STATEMENT:  SELECT $1::regclass

Thanks

Same error in postgres DB after starting the Mattermost container version 5.21 or 5.22.

Mattermost won't start...

customizeXF avatar Apr 02 '20 21:04 customizeXF

Hi I am running Mattermost 5.14.1 with docker-compose. The db container prints the following error:

db_1   | LOG:  database system was shut down at 2019-09-03 04:57:08 UTC
db_1   | LOG:  MultiXact member wraparound protections are now enabled
db_1   | LOG:  database system is ready to accept connections
db_1   | LOG:  autovacuum launcher started
db_1   | ERROR:  relation "idx_teams_description" does not exist
db_1   | STATEMENT:  SELECT $1::regclass

Thanks

Same error in postgres DB after starting the Mattermost container version 5.21 or 5.22.

Mattermost won't start...

Hi @customizeXF,

It persists for me at 5.22. But I can up all containers.

nvjacobo avatar Apr 02 '20 22:04 nvjacobo

Hm, my container is up, but getting error 502 when trying to visit the site.

customizeXF avatar Apr 02 '20 22:04 customizeXF

Hm, my container is up, but getting error 502 when trying to visit the site.

app container is up?

nvjacobo avatar Apr 02 '20 22:04 nvjacobo

Same error for me trying the latest version... This is getting me crazy.

adechassey avatar Apr 03 '20 10:04 adechassey

Hey guys! Nya update on this issue?

amir-khalili avatar Aug 03 '20 16:08 amir-khalili

Hey guys! Nya update on this issue?

Hi @amir-khalili,

In my instance this error persists.

Details:

Mattermost Version: 5.25.1 Database Schema Version: 5.25.0 Database: postgres Build Date: Thu Jul 23 20:08:58 UTC 2020

nvjacobo avatar Aug 07 '20 03:08 nvjacobo

This error message does not seem to indicate a problem as the index is to be removed since v3.6.1 ( https://github.com/mattermost/mattermost-server/commit/dd6fac50f2741ecc8e7e07c42a3e94b37720bd5e )

Guess it's just a side product of the RemoveIndexIfExists call:

store/sqlstore/team_store.go:	s.RemoveIndexIfExists("idx_teams_description", "Teams")

dhx avatar Sep 25 '20 18:09 dhx

Nice @dhx! Is there a quick fix (for a Docker installation)?

bor8 avatar Apr 29 '21 15:04 bor8

@bor8 while I guess it would be nice to not print this error message, it seems to be unrelated to the observed problems as I don't see how the cause of the message would result in Mattermost not starting (or 502 results).

dhx avatar Apr 30 '21 07:04 dhx