Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] crashloop for mattermost bot on new deploy #87

Closed
hijak opened this issue May 9, 2019 · 5 comments

Comments

Projects
None yet
5 participants
@hijak
Copy link

commented May 9, 2019

Describe the bug
I am unable to use botkube with mattermost, am facing the following error

To Reproduce
i have tried deploying from the helm chart and via the yaml file. all needed config for mattermost is configured correctly

INFO[2019-05-09T08:37:29Z] Allowed Events - map[{Resource:clusterrole Namespace:all}:true {Resource:configmap Namespace:all}:true {Resource:daemonset Namespace:all}:true {Resource:deployment Namespace:all}:true {Resource:ingress Namespace:all}:true {Resource:job Namespace:all}:true {Resource:namespace Namespace:all}:true {Resource:node Namespace:all}:true {Resource:persistentvolume Namespace:all}:true {Resource:persistentvolumeclaim Namespace:all}:true {Resource:pod Namespace:all}:true {Resource:role Namespace:all}:true {Resource:rolebinding Namespace:all}:true {Resource:secret Namespace:all}:true {Resource:service Namespace:all}:true]
INFO[2019-05-09T08:37:29Z] Starting controller
INFO[2019-05-09T08:37:29Z] Starting mattermost bot
panic: runtime error: invalid memory address or nil pointer dereference
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x115de22]

goroutine 52 [running]:
github.com/infracloudio/botkube/vendor/github.com/mattermost/mattermost-server/model.(*WebSocketClient).Listen.func1.1(0x0)
	/go/src/github.com/infracloudio/botkube/vendor/github.com/mattermost/mattermost-server/model/websocket_client.go:101 +0x22
panic(0x1314c20, 0x2322130)
	/usr/local/go/src/runtime/panic.go:522 +0x1b5
github.com/infracloudio/botkube/vendor/github.com/mattermost/mattermost-server/model.(*WebSocketClient).Listen.func1(0x0)
	/go/src/github.com/infracloudio/botkube/vendor/github.com/mattermost/mattermost-server/model/websocket_client.go:109 +0x64
created by github.com/infracloudio/botkube/vendor/github.com/mattermost/mattermost-server/model.(*WebSocketClient).Listen
	/go/src/github.com/infracloudio/botkube/vendor/github.com/mattermost/mattermost-server/model/websocket_client.go:99 +0x3f
@hijak

This comment has been minimized.

Copy link
Author

commented May 9, 2019

oh also my mattermost server has valid letsencrypt cert referfencing other issue

@hijak

This comment has been minimized.

Copy link
Author

commented May 10, 2019

Hi

i have managed to get this working by setting the mattermost url to be the internal dns name with in the cluster. Im guessing it has something to do with mattermost being behind something

also ive noticed that the attatchments in mattermost are not using correct colors, as far as i know mattermost cannot interpret danger and primary type colors and you have to use hex

@PrasadG193

This comment has been minimized.

Copy link
Member

commented May 10, 2019

Hey @hijak,
What is the version of Mattermost you are using?

@hijak

This comment has been minimized.

Copy link
Author

commented May 10, 2019

Mattermost Version: 5.10.0

@mugdha-adhav

This comment has been minimized.

Copy link
Member

commented May 10, 2019

Hi @hijak,
A pull request #83 is already created for fixing the issue and we are working on it.

@arush-sal arush-sal closed this Jun 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.