Burrow failing silently on starting

I'm trying to setup burrow and I'v followed each step mentioned in the documentation, but when I try to launch the service, it fails silently after line Reading configuration from config/.

When I checked the directory structure, I found that every time a new log file gets created and content inside each is

panic: Failed to compile TemplateOpen [recovered]
	panic: Failed to compile TemplateOpen [recovered]
	panic: Failed to compile TemplateOpen

goroutine 1 [running]:
main.handleExit()
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/main.go:64 +0x259
panic(0x14f6280, 0xc4201cef90)
	/usr/local/go/src/runtime/panic.go:502 +0x229
github.com/linkedin/Burrow/vendor/go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc4201dc000, 0x0, 0x0, 0x0)
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/vendor/go.uber.org/zap/zapcore/entry.go:229 +0x4f4
github.com/linkedin/Burrow/vendor/go.uber.org/zap.(*Logger).Panic(0xc4201b8600, 0x15efdea, 0x1e, 0x0, 0x0, 0x0)
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/vendor/go.uber.org/zap/logger.go:225 +0x7f
github.com/linkedin/Burrow/core.configureCoordinators.func1(0xc4201b8000)
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/core/burrow.go:96 +0x7d
panic(0x14f6280, 0xc4201cef80)
	/usr/local/go/src/runtime/panic.go:502 +0x229
github.com/linkedin/Burrow/vendor/go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc4201dc000, 0xc4201e6580, 0x2, 0x2)
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/vendor/go.uber.org/zap/zapcore/entry.go:229 +0x4f4
github.com/linkedin/Burrow/vendor/go.uber.org/zap.(*Logger).Panic(0xc4201b88a0, 0x15efdea, 0x1e, 0xc4201e6580, 0x2, 0x2)
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/vendor/go.uber.org/zap/logger.go:225 +0x7f
github.com/linkedin/Burrow/core/internal/notifier.(*Coordinator).Configure(0xc4201e6380)
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/core/internal/notifier/coordinator.go:219 +0xf40
github.com/linkedin/Burrow/core.configureCoordinators(0xc4201b8000, 0x164ca80, 0xc4201da0c0, 0x164ca40, 0xc4201be4e0, 0x164c840, 0xc4201bc3c0, 0x164c900, 0xc4201bc420, 0x164c940, ...)
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/core/burrow.go:103 +0x9c
github.com/linkedin/Burrow/core.Start(0xc4201b8000, 0xc4200b29c0, 0x0)
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/core/burrow.go:148 +0x36f
main.main()
	/Users/ashwin.sinha/OSP/Burrow/src/github.com/linkedin/Burrow/main.go:115 +0x4d9

Need help with the issue, as I'm not fluent in Golang.

Start by reproducing the launch failure after “Reading configuration from config/” and read core/internal/notifier/coordinator.go around Configure, then core/burrow.go around configureCoordinators. Compare the generated log output with the stack trace and determine the configuration or template condition that causes startup to panic. Done means the failure is identified and the issue has a clear corrective path.