service fails to start after upgrading to release 0.1.1-165

[xmidt-org]

service fails to start after upgrading to release 0.1.1-165

[schmidtw]

@ganeshprasads is this still an issue?

[ganeshprasads]

@schmidtw Still facing the issue in 0.1.1-207
I was using the default yaml config and service terminates with below crash log:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xd0 pc=0x7b2535]
goroutine 1 [running]:
vendor/github.com/spf13/viper.(*Viper).AllKeys(0x0, 0x7, 0xc42017f868, 0x411f59)
/root/rpmbuild/BUILD/talaria-0.1.1/src/vendor/github.com/spf13/viper/viper.go:1378 +0x45
vendor/github.com/spf13/viper.(*Viper).AllSettings(0x0, 0x4127a8)
/root/rpmbuild/BUILD/talaria-0.1.1/src/vendor/github.com/spf13/viper/viper.go:1458 +0x51
vendor/github.com/spf13/viper.(*Viper).Unmarshal(0x0, 0xb34140, 0xc42000e8b8, 0x0, 0x8)
/root/rpmbuild/BUILD/talaria-0.1.1/src/vendor/github.com/spf13/viper/viper.go:738 +0x2f
vendor/github.com/Comcast/webpa-common/service/servicecfg.NewEnvironment(0xd86660, 0xc42019e540, 0xd86960, 0x0, 0xc4200205a0, 0xd90480, 0xc4201b3680, 0x0)
/root/rpmbuild/BUILD/talaria-0.1.1/src/vendor/github.com/Comcast/webpa-common/service/servicecfg/environment.go:25 +0xd1
main.talaria(0xc42001e1b0, 0x1, 0x1, 0x0)
/root/rpmbuild/BUILD/talaria-0.1.1/src/talaria/talaria.go:96 +0x96e
main.main.func1(0xc42006e058)
/root/rpmbuild/BUILD/talaria-0.1.1/src/talaria/talaria.go:186 +0x49
main.main()
/root/rpmbuild/BUILD/talaria-0.1.1/src/talaria/talaria.go:189 +0x22

talaria.yaml:
---
primary:
address: ":8080"
health:
address: ":8888"
pprof:
address: ":9999"
log:
file : "/var/run/talaria/talaria.log"
level : "DEBUG"
maxSize : 50
maxBackup : 3

[kristinapathak]

@ganeshprasads Is this still an issue?