This is just a note for anyone running into the same issues that I was running into.
There are point in documentation that suggest running /platform -version, or similar things. This just adds confusion when dealing with GitLab Mattermost. Here’s what worked for me:
sudo -u mattermost ./mattermost -config=/var/opt/gitlab/mattermost/config.json
This was the only way to get it to work. In other words, “sudo -u mattermost ./mattermost” takes the place of “platform” anywhere you see it in documentation, and you have to append -config at the end.
Hopefully this will help clarify things for other users.
Thanks! I found this helpful
When trying to run
sudo -u mattermost ./mattermost -config=/var/opt/gitlab/mattermost/config.json -version
command mattermost can't be found.
Trying this however:
sudo -u mattermost /opt/gitlab/embedded/bin/mattermost -config=/var/opt/gitlab/mattermost/config.json -version
is returning following error:
panic: Failed to load system translations for 'en'
goroutine 1 [running]:
goroutine 17 [syscall, locked to thread]:
goroutine 5 [syscall]:
created by os/signal.init.1
goroutine 6 [chan receive]:
github.com/alecthomas/log4go.(*ConsoleLogWriter).run(0xc82000e580, 0x7fe2513041e8, 0xc820032010)
created by github.com/alecthomas/log4go.NewConsoleLogWriter
Hi @derblub, this issue happens in Mattermost 2.0, and was fixed in Mattermost 2.1. You can upgrade to the next version to resolve this issue.
Mattermost 2.0 introduced multi-language support and this issue was caused by that change, and fixed in the next monthly release.
Sorry, but apparently it isn’t fixed.
Mattermost Team Edition
Build Date:Fri Apr 15 18:40:19 UTC 2016
I’m on GitLab CE 10.1.1 running on docker. That’s how it works for me:
docker exec -it -u mattermost <container> bash
mattermost -c /var/opt/gitlab/mattermost/config.json version