Skip to content
This repository has been archived by the owner on Sep 8, 2018. It is now read-only.

Local node unable to connect to self after netowrk change #139

Open
xla opened this issue Jul 29, 2018 · 0 comments
Open

Local node unable to connect to self after netowrk change #139

xla opened this issue Jul 29, 2018 · 0 comments
Labels

Comments

@xla
Copy link
Collaborator

xla commented Jul 29, 2018

Observed the following error:

ts=2018-07-29T14:09:48.652160779Z level=warn component=Consumer op=gather warning="Get http://192.168.0.50:7650/ingest/next: dial tcp 192.168.0.50:7650: connect: no route to host" msg="ingester 192.168.0.50:7650, during /next: fatal error"

This happened during local development and with the following start command:

oklog ingeststore -ui.local -store.segment-replication-factor 1

My assumption is this is to local ip addresses changing when switching networks on travels. Just wanted to leave it here for a second look.

@xla xla added the bug label Jul 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant