Quantcast
Channel: Mattermost Discussion Forums - Latest posts
Viewing all 25523 articles
Browse latest View live

How to start the server without pinging the DB

$
0
0

Hi Jesse,

Thank you very much for the response.

Yes. The problem I am having is that I want to use the serverless Aurora DB service but the end point of the DB can’t be pinged. I asked AWS support to see if it can be changed and they said no.

This is the error I am getting when starting the server:

{“level”:“info”,“ts”:1551280409.4031305,“caller”:“app/app.go:143”,“msg”:“Server is initializing…”}
{“level”:“info”,“ts”:1551280409.405245,“caller”:“sqlstore/supplier.go:207”,“msg”:“Pinging SQL master database”}
[mysql] 2019/02/27 15:13:59 packets.go:36: read tcp x.x.x.x:36150->x.x.x.x:3306: i/o timeout
{“level”:“error”,“ts”:1551280439.434761,“caller”:“sqlstore/supplier.go:219”,“msg”:“Failed to ping DB retrying in 10 seconds err=context deadline exceeded”}

However, I can connect no problem to the DB using:
mysql — user=[user] --password -h [endpoint of cluster])

Thank you for your help!
Miguel


How to start the server without pinging the DB

$
0
0

Hmm, that error is just the server failing to connect to the Aurora DB service – it’s not necessary to be able to “ping” the database endpoint in an ICMP sense. (We’re just using the term in the logs because it’s illustrative of a connectivity test.)

Are you running that mysql invocation on the same box as the server in question? I’d suggest trying to narrow down connectivity issues between the box running Mattermost and the Aurora DB endpoint in question.

It’s also possible that there’s some kind of incompatibility between database/sql (and https://github.com/go-sql-driver/mysql) and Aurora’s serverless infrastructure, but it seems unlikely (otherwise it would break the mysql protocol).

How to start the server without pinging the DB

$
0
0

The MySQL DB is running on a cluster of instances that I do not have root access to. This DB cluster is “created” for me when I create an Aurora DB and I tell it to be in serverless mode.

There doesn’t seem to be any problems of connectivity though. I am running the mysql command from the EC2 instance the Mattermost server is installed on. I also can telnet on port 3306 from this EC2 to the DB endpoint.

Miguel

Cannot "Log in with GitLab"

$
0
0

Hi @stavros,

Here is a response from a community member:

The error page indicates that the SSO endpoint returned unexpected HTTP status code, i.e., not 200. To debug this further you might want look at the SSO provider’s log files.

API Upload File not uploading

$
0
0

Hi @paulus,

From a community member:

Would you be able to provide a curl command line to reproduce the issue? How did you confirm that the file you want to upload is available? (More a FYI: pr-mattermost-server-9835 )

Limitation about Pinned message and Flagging messages

$
0
0

Hi @Judy,

From a community member:

The amount of flagged/pinned messages is unlimited (assuming infinite disk space; if you have only a finite amount of disk space that’s most likely the limiting factor).

Run Mattermost using AWS Aurora serverless

$
0
0

Hi @Miguel,

From a community member:

You might be confusing DB pings and ICMP echo requests. The TCP i/o timeout looks suspicious. Would you be able to post your Mattermost database configuration?

Built-in WebRTC video and audio calls removed in v5.6 in favor of open source plugins

$
0
0

Extracting actual WebRTC code from Mattermost to create is very necessary sometimes. Will it be available?


Restoring mattermost DB from docker file

$
0
0

Summary

I am trying to do a db restore from docker by declaring

  • ./db/postgres.sql:/docker-entrypoint-initdb.d/initdb.sql

Inside docker-compose.yml


Observed behavior

However I am getting this error message from the docker db logs

/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/initdb.sql
SET
SET
SET
ERROR: cannot drop the currently open database
STATEMENT: DROP DATABASE mattermost;
psql:/docker-entrypoint-initdb.d/initdb.sql:14: ERROR: cannot drop the currently open database


I have tried multiple ways to declare the initdb but keeps having the same problem. I know I can restore it by doing docker exec -i mattermost_db_1 psql -U mmuser mattermost < db/postgres.sql but I want to avoid that method if possible

Limitation about Pinned message and Flagging messages

$
0
0

Hi, @amy.blais

This is a very useful information that can help answer similar question from future users. Perhaps it will be good to include this information in the Pinning Messages? For example:

:exclamation: Take note that the amount of flagged / pinned messages that you can have in a channel is only limited to the disk space.

It can be rephrased to deliver a clearer message nevertheless. What’s your thought about that?

Interactive Dialog Dropdowns not working properly on web

$
0
0

Summary

Cant scroll through dropdowns in interactive dialogs on web app

Steps to reproduce

Mattermost Version : 5.7
Send an interactive dialog through the api using this json:

{"callback_id":"abcd","title":"Test Dialog","elements":[{"display_name":"Test Dropdown","name":"test","type":"select","optional":false,"options":[{"text":"data1","value":"data1"},{"text":"data2","value":"data2"},{"text":"data3","value":"data3"}]}],"submit_label":"Submit","notify_on_cancel":false}

Expected behavior

The dropdown in the dialog should be scrollable

Observed behavior

The dropdown only shows the last entry. The rest of the entries can be searched by typing, but do not show up in the scroll view. They are getting hidden behind the title of the dialog.

P2P File Sending

Interactive Dialog Dropdowns not working properly on web

Run Mattermost using AWS Aurora serverless

$
0
0

Hi Amy, thank you for your help!

Here is the DB configuration (password edited)

“SqlSettings”: {
“DriverName”: “mysql”,
“DataSource”: “mmuser:password@tcp(172.16.3.114:3306)/mattermosm?charset=utf8mb4,utf8\u0026readTimeout=30s\u0026writeTimeout=30s”,

    "DataSourceReplicas": [],                                                                                                           
    "DataSourceSearchReplicas": [],                                                                                                     
    "MaxIdleConns": 20,                                                                                                                 
    "ConnMaxLifetimeMilliseconds": 3600000,                                                                                             
    "MaxOpenConns": 300,                                                                                                                
    "Trace": false,                                                                                                                     
    "AtRestEncryptKey": "**key**",                                                                             
    "QueryTimeout": 30                                                                                                                  
},

Limitation about Pinned message and Flagging messages


Cannot "Log in with GitLab"

$
0
0

I’d add that that usually means the endpoints that Mattermost uses to connect to GitLab are incorrect. If you’re using GitLab Omnibus, they’d be configured automatically, but if you configured those settings yourself, you may want to double check those values.

[SOLVED] Users automatically joining multiple public channels

MatterMost Client - Multiple Chat Windows

$
0
0

I think this is the right topic.

I’m resuming this old conversation because it’s one of the first link reported by google when looking for “mattermost separate windows” and I hope that adding the link above will upvote this feature :wink:

Community Design Meeting: Folded Reply Threads

$
0
0

For us, it would be interesting to see the current approach somewhere upfront to think about. I want to attend this meeting - however, only, if your plan differs from what Slack does for folded threads (which works very very well).

Hope to see some data before the meeting starts in two days!

All the best,
D.R.

Forced to select team on login even though already a member

$
0
0

We have users that are reporting from time to time when they login to the web client they are forced to choose a public team to join, even though they are existing users that have logged in previously and already part of several teams. It forces them to join a public team (that they don’t necessarily want to be a member of) and then have to leave the team. They are then able to switch teams to ones they are already members of. Any idea what may cause something like this?

Viewing all 25523 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>