Panic when executing cscli metrics

1

I’ve had Crowdsec running on my Unraid server for awhile monitoring Nextcloud, Authelia and NPM. Today I added a remote mailserver (mailcow) and everything was working perfectly up until I received the following error when executing: “cscli metrics” on my primary server:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x11839a4]
goroutine 1 [running]:
main.NewMetricsCmd.func1(0xc000920c80?, {0xc00053e4a0?, 0x2?, 0x2?})
	/go/src/crowdsec/cmd/crowdsec-cli/metrics.go:265 +0x64
github.com/spf13/cobra.(*Command).execute(0xc000920c80, {0xc00053e480, 0x2, 0x2})
	/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:876 +0x67b
github.com/spf13/cobra.(*Command).ExecuteC(0xc0007dd400)
	/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:990 +0x3bd
github.com/spf13/cobra.(*Command).Execute(...)
	/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:918
main.main()
	/go/src/crowdsec/cmd/crowdsec-cli/main.go:230 +0xbf6

Both servers seem to be doing their job, and I can launch the same command on the remote server without panic. Anybody have some input?

2

Could we get some version details? and uptime information guessing the service has been running for a while?

EDIT: OP never responded, however, user have reported this when cscli metrics on machine where you have not set prometheus options within config.yaml please ensure these are set