Quantcast
Channel: Mattermost Discussion Forums - Latest posts
Viewing all articles
Browse latest Browse all 25517

Single-server, CentOS 7 initial setup -- Won't launch as service

$
0
0

Thank you, this put me onto the right track. I think it's the user that has been configured to run the service that's causing the issue.

[root@localhost bin]# su mattermost
bash-4.2$ ./platform
FileLogWriter("/opt/mattermost/logs/mattermost.log"): open /opt/mattermost/logs/mattermost.log: permission denied
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x5ec0fc]

goroutine 1 /go/src/github.com/mattermost/platform/utils/config.go:101 +0x4ec
github.com/mattermost/platform/utils.LoadConfig(0xc820144990, 0x22)
/go/src/github.com/mattermost/platform/utils/config.go:162 +0x5f5
main.main()
/go/src/github.com/mattermost/platform/mattermost.go:54 +0x43

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

goroutine 5 /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 7 0x7fb8401ab1e8, 0xc820024010)
/go/src/github.com/mattermost/platform/Godeps/_workspace/src/code.google.com/p/log4go/termlog.go:27 +0x80
created by code.google.com/p/log4go.NewConsoleLogWriter
/go/src/github.com/mattermost/platform/Godeps/_workspace/src/code.google.com/p/log4go/termlog.go:19 +0x6e

This fixed it:

[root@localhost mattermost]# cd ../logs/
[root@localhost logs]# chown -R mattermost:mattermost mattermost.log
[root@localhost logs]# chmod -R g+w mattermost.log


Viewing all articles
Browse latest Browse all 25517

Trending Articles



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