this is continuation of [Handling EU868 and US915 same time](http://handling EU868 and US915 same time).
I have chirpstack-network-server
docker container configured to work on EU868
frequency plan.
So I need to run second chirpstack-network-server
configured to another required frequency plan (US915
).
For that I simply change port in chirpstack-network-server-us915.toml
[network_server.api]
# ip:port to bind the api server
bind="0.0.0.0:7999"
And run second contailer:
docker run -d -p 127.0.0.1:7999:7999 --network="common" --name lora_server_US915 loraserver_chirpstack-network-server ./chirpstack-network-server -c chirpstack-network-server-us915.toml
Seems it starts as expected:
time="2020-04-24T23:34:56Z" level=info msg="starting ChirpStack Network Server" band=US915 docs="https://www.chirpstack.io/" net_id=000000 version=3.9.0-30-gbe5d7a1
time="2020-04-24T23:34:56Z" level=info msg="disabling all channels"
time="2020-04-24T23:34:56Z" level=info msg="enabling channels" channels="[0 1 2 3 4 5 6 7]"
time="2020-04-24T23:34:56Z" level=info msg="storage: setting up storage module"
time="2020-04-24T23:34:56Z" level=info msg="storage: setting up Redis client"
time="2020-04-24T23:34:56Z" level=info msg="storage: connecting to PostgreSQL"
time="2020-04-24T23:34:56Z" level=info msg="storage: applying PostgreSQL data migrations"
time="2020-04-24T23:34:56Z" level=info msg="storage: PostgreSQL data migrations applied" count=0
time="2020-04-24T23:34:56Z" level=info msg="gateway/mqtt: connecting to mqtt broker" server="tcp://lora_mosquitto:1883"
time="2020-04-24T23:34:56Z" level=info msg="no geolocation-server configured"
time="2020-04-24T23:34:56Z" level=info msg="configuring join-server client" ca_cert= server="http://lora_appserver:8003" tls_cert= tls_key=
time="2020-04-24T23:34:56Z" level=info msg="backend/gateway: connected to mqtt server"
time="2020-04-24T23:34:56Z" level=info msg="gateway/mqtt: subscribing to gateway event topic" qos=0 topic=gateway/+/event/+
time="2020-04-24T23:34:56Z" level=info msg="api: starting network-server api server" bind="0.0.0.0:7999" ca-cert= tls-cert= tls-key=
time="2020-04-24T23:34:56Z" level=info msg="starting downlink device-queue scheduler"
time="2020-04-24T23:34:56Z" level=info msg="starting multicast scheduler"
But when I try to create new network server in chirpstack-application-sever
I get following error from application server:
Here is error messages in logs of chirpstack-application-server
:
time="2020-04-24T23:45:32Z" level=warning msg="creating insecure network-server client" server="172.18.0.11:7999"
time="2020-04-24T23:45:32Z" level=info msg="finished client unary call" ctx_id=4d25e158-5d18-4afb-bfd5-7c7b231e5e27 error="rpc error: code = AlreadyExists desc = object already exists" grpc.code=AlreadyExists grpc.ctx_id=3d18f461-2677-4b69-9827-7b7479e7dddb grpc.duration=1.075654ms grpc.method=CreateRoutingProfile grpc.service=ns.NetworkServerService span.kind=client system=grpc
time="2020-04-24T23:45:32Z" level=info msg="finished unary call with code AlreadyExists" ctx_id=4d25e158-5d18-4afb-bfd5-7c7b231e5e27 error="rpc error: code = AlreadyExists desc = object already exists" grpc.code=AlreadyExists grpc.method=Create grpc.service=api.NetworkServerService grpc.start_time="2020-04-24T23:45:32Z" grpc.time_ms=4.21 peer.address="127.0.0.1:38928" span.kind=server system=grpc
and chirpstack-network-server
:
time="2020-04-24T23:45:32Z" level=info msg="finished unary call with code AlreadyExists" ctx_id=3d18f461-2677-4b69-9827-7b7479e7dddb error="rpc error: code = AlreadyExists desc = object already exists" grpc.code=AlreadyExists grpc.method=CreateRoutingProfile grpc.service=ns.NetworkServerService grpc.start_time="2020-04-24T23:45:32Z" grpc.time_ms=0.571 peer.address="172.18.0.9:52744" span.kind=server system=grpc
Seems that lora-app-server compares something else than just nerwork name and server address?