git2consul crashes when a configured repo cannot be accessed
Opened this issue · 1 comments
When a git repo that is configured cannot be accessed an error like below appears in the log:
{"name":"git2consul","hostname":"3cba13b113c4","pid":1,"level":50,"msg":"Failed to create repos due to Failed to load repo bla/bla due to Error: Error: Command failed: Cloning into 'bla'...\nfatal: could not read Username for 'https://stash': No such device or address\n Cloning into 'bla'...\nfatal: could not read Username for 'https://stash': No such device or address","time":"2017-03-07T16:06:49.059Z","v":0}
{"name":"git2consul","hostname":"3cba13b113c4","pid":1,"level":40,"msg":"Waiting for branch master in repo git2consul","time":"2017-03-07T16:06:49.059Z","v":0}
Shortly after that the process exits. I would expect it to keep running in this case and still server the other repositories.
use 'https://username:password@stash' can success.