Hello @ [amy.blais]
You can see error in URL Adress https://chat.trueconf.com
What else can you try?
I reset the default settings for mattermost:
./mattermost reset
Please look at the error
You can create first user for admin mattermost in URL https://chat.trueconf.com
Thanks @amy.blais!!
That issue seems to be related to my problem. I’ll try new rc release including changes of the PR.
@gubbins can we ask where you are getting such links with nested parentheses?
I was looking at the migration documents https://docs.mattermost.com/administration/migrating.html#migrating-the-mattermost-server.
In particular, step 4. And step 4 says:
Backup the database from the SOURCE Mattermost server and restore it in place of the database to which the DESTINATION server is connected.
And I’m like, duh. But what are the commands to do it?
I searched around and found the commands to export the database, but trying to restore it, not so lucky. There is this command:
sudo -u mattermost /opt/gitlab/embedded/bin/psql -U gitlab_mattermost -h /var/opt/gitlab/postgresql -d mattermost_production -f ./mattermost_production
But all I get is a bunch of relation exists errors. Is that normal?
Hello,
Is the desktop user activity status based on activity in the browser/desktop Mattermost application or is it based on general mouse / keyboard interaction in other applications running on the users pc?
It seems to be based on the former - can this be changed somehow?
Thanks,
Johan
I figured it out. I have to remove the old database and create a new one.
sudo -u gitlab-psql /opt/gitlab/embedded/bin/psql -h /var/opt/gitlab/postgresql/ -d gitlabhq_production
drop database mattermost_production
;
create database mattermost_production
;
\q
Once that is done, the restore command works with no errors.
JIRA uses them, e.g. https://jira/browse/ABC-123?jql=assignee%20in%20(currentUser()). We’ve also seen this with some TeamCity locators I think.
I have this configured, but I have not received any email notifications from the channels if those keywords. I am not sure if I have a setting wrong, or something. I have tested the email configuration, but it still does not work.
Is this going to be implemented? I can’t believe this is still no auto-upgrade feature!
Hi. I just updated from 5.7.0 to 5.7.1 (team version) following the posted instructions. Afterwards I checked “About Mattermost” and see that my database schema version is behind:
Mattermost Version: 5.7.1
Database Schema Version: 5.7.0
Database: postgres
Is this a problem? Have I missed a step?
Thanks!
Hi @johan.ferner,
Your activity status is based on your activity in the browser/desktop, so if you haven’t been active on Mattermost itself for 5 minutes, your status will become “away”. If you want this behaviour changed you can share it on our feature request forum: https://mattermost.uservoice.com/forums/306457-general!
Hi, @nils-schween
“RestrictCustomEmojiCreation”: “all”,
This means that the creation of custom emoji is allowed for all users as mentioned in the Custom Emoji but since you are running 5.7.0, the configuration is pulled from the database as mentioned in the Restrict Custom Emoji Creation:
In this case, can you access the database, run the following command, and provide the output?
SELECT * FROM Roles\G
SELECT * FROM Systems WHERE Name = "EmojisPermissionsMigrationComplete"\G
SELECT * FROM Users WHERE Email="<email>"\G
Meanwhile, I am interested to know if you can access the custom emoji page directly from the browser. Can you please navigate to the page directly and verify if you can see it? In my case here, it is set to https://community.mattermost.com/core/emoji
I’d like to try and understand if the functionality is completely missing from the deployment or merely just the button here:
Hello, @JinZhuXing
I won’t bluntly say that it cannot support P2P file sharing due to security issues, hence the statement “might explain” in my response earlier. Since Mattermost focuses primarily on enterprise communication, I don’t think large data transfer feature would fit as a requirement especially when uploaded files are kept in the server by default and not automatically purged after a specific period of time as @JtheBAB had mentioned.
Hello there, @mscala.
I would assume that you followed the full steps to upgrade Mattermost according to the official documentation here - Upgrading Mattermost Server, so you should not be missing on any particular step.
Cross checking the Mattermost Changelog, I do not see any specific known issues with the inconsistent mattermost and database version after upgrading from version 5.7.0 equipped with the postgres database.
In this case, may I know if you can try to log out from the sessions that you are currently on and log in again to see if the inconsistency is still observed (both web and desktop client) to see if it is not just a client caching issue? Do you also notice any issues so far in terms of chat functionality, file sharing, etc.?
Can you also run the platform version command if you have access to the backend command line of Mattermost and provide the output too? I came across an article which explains the following, so it could be the case here:
Database Schema Version
This indicates the schema version of the Mattermost database, with numbering similar to the Mattermost server version. The database schema version is set by the Mattermost server on install and on upgrades when the Mattermost database schema is updated. If no updates to the Mattermost server are made, the schema version is not updated. A list of database changes from version to version is indicated in the Mattermost changelog.
Hi, @jast0305
Gotcha. To ensure that we are getting the email / push notifications accordingly, we need to either be offline or away from Mattermost for more than 5 minutes. While you were expecting the email, can I please check if you were in either statuses (offline / away)?
I have tested the email configuration
Can you please confirm what testing method(s) was performed on the email configuration and can you share the outcome of it here? Thanks.
Hello, @UgoCloutier
Throughout my observation, there is always a caveat to auto upgrades in general. For example:
on the condition that there are no breaking changes so that security issues are automatically resolved/patched
There are known issues that some users can live with and vice versa based on the Mattermost Changelog. Hence, the reason why manual upgrade is preferred most of the time. Let us not forget that it is always a good practice to have backup before upgrading a system as well that some would overlook at times.
Unless there is a script available that can perform checks against the changelog for specific keywords for the latest version >> auto backup the instance (database, config.json, file store) >> auto upgrade the Mattermost server (basically all the steps listed in Upgrading Mattermost Server), that will be pretty awesome. 
Thanks for kind reply.
I’ll find other P2P file sharing software and use it for our file sending.
Mattermost is a good software.
Thanks.
Thank you @adanial
Hi there, @ipsecguy
I ran the following command on the database command line and verified that it is set to latin1:
mysql> SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = "mattermost";
±---------------------------+
| default_character_set_name |
±---------------------------+
| latin1 |
±---------------------------+
1 row in set (0.00 sec)
However, checking through the config.json file, the charset is supposed to be set to utf8:
root@mm:/# cat /mm/mattermost/config/config.json | grep -w “DataSource”
“DataSource”:“user:mattermost@tcp(dockerhost:3306)/mattermostcharset=utf8mb4,utf8\u0026readTimeout=30s\u0026writeTimeout=30s”,
I would take a guess that you were referring to this discrepancy. Can you please confirm which Mattermost server version that you are on and confirm where you see the mangled non-ASCII characters (desktop / web / mobile client) by sending some screen shot(s)?
Hi, @JinZhuXing
You are most welcome. I will definitely share the compliment to the rest of the Mattermost team to make their day. Have a good one!
Hi,
I just tried installing the Docker image on the latest version of Docker for Windows according to the instructions and it failed with the error message Error response from daemon: Unrecognised volume spec: invalid volume specification: './mattermost-data'.
See command line output below:
>docker run --name mattermost-preview -d --publish 8065:8065 --add-host dockerhost:127.0.0.1 mattermost/mattermost-preview
Unable to find image 'mattermost/mattermost-preview:latest' locally
latest: Pulling from mattermost/mattermost-preview
6ae821421a7d: Pull complete
a9e976e3aa6d: Pull complete
e3735e44a020: Pull complete
bfd564e9483f: Pull complete
df705f26e488: Pull complete
0c5547f73d62: Pull complete
f437382cf8a1: Pull complete
4f22805bb6d6: Pull complete
394f0f652697: Pull complete
fb068b9b9d1f: Pull complete
fdfc96ad0937: Pull complete
886a6212b9f0: Pull complete
1e96655722a9: Pull complete
b365baa15224: Pull complete
133fe2c903bf: Pull complete
096da92e1724: Pull complete
16be38d85c42: Pull complete
2173d14092cf: Pull complete
3cb91b442d2f: Pull complete
Digest: sha256:c877090d67fdfe20d14b319f7dd0974c78b0c26f36b9f19460932ecbb5af9f78
Status: Downloaded newer image for mattermost/mattermost-preview:latest
docker: Error response from daemon: Unrecognised volume spec: invalid volume specification: './mattermost-data'.
See 'docker run --help'.
>docker version
Client: Docker Engine - Community
Version: 18.09.1
API version: 1.39
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:34:26 2019
OS/Arch: windows/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.24)
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:50:10 2019
OS/Arch: windows/amd64
Experimental: true