Mattermost Peer-to-Peer Forum

Proper CLI usage in Gitlab


#1

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:

From
/opt/gitlab/embedded/bin

I ran
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.


CLI crashes with error message: "panic: Failed to load system translations for 'en'"
#2

Thanks! I found this helpful :smiley:


#3

When trying to run
sudo -u mattermost ./mattermost -config=/var/opt/gitlab/mattermost/config.json -version
I get: 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]:
github.com/mattermost/platform/utils.GetTranslationsBySystemLocale(0xc820162460)
	/go/src/github.com/mattermost/platform/utils/i18n.go:44 +0x19a
github.com/mattermost/platform/utils.InitTranslations()
	/go/src/github.com/mattermost/platform/utils/i18n.go:29 +0x2e9
main.main()
	/go/src/github.com/mattermost/platform/mattermost.go:54 +0x2c

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
	/usr/local/go/src/runtime/asm_amd64.s:1721 +0x1

goroutine 5 [syscall]:
os/signal.loop()
	/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
	/usr/local/go/src/os/signal/signal_unix.go:28 +0x37

goroutine 6 [chan receive]:
github.com/alecthomas/log4go.(*ConsoleLogWriter).run(0xc82000e580, 0x7fe2513041e8, 0xc820032010)
	/go/src/github.com/mattermost/platform/Godeps/_workspace/src/github.com/alecthomas/log4go/termlog.go:33 +0x69
created by github.com/alecthomas/log4go.NewConsoleLogWriter

Any ideas?
Thanks!


#4

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.


#5

Sorry, but apparently it isn’t fixed.

Mattermost Team Edition
Version:2.2.0
Build Number:6671
Build Date:Fri Apr 15 18:40:19 UTC 2016
Build Hash:8e883ad2f516820942cc0131241268c1ea909ff3

#6

Thanks @derblub, appreciate the report, ticket has been re-opened on this.


#7

did you use the best practice described in [Found workaround]CLI tool still crashing and throwing errors in 2.1.0


#8

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
cd /opt/gitlab/embedded/service/mattermost
mattermost -c /var/opt/gitlab/mattermost/config.json version
Version: 4.2.0