Update dmsghttp config

[jdknives]

Updates the IPs for the prod deployment dmsghttp config with new IPs for the dmsg servers.

[0pcom]

The keys for the services were changed also ; I'm not sure if that was intentional or not, but it seems I can't connect to all the services using the dmsghttp-config

[2023-06-25T09:20:37.994557184-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:20:37.994699193-05:00] WARN retrier [utclient]: Retrying... current_backoff=10s error="uptime tracker httpauth: Get "dmsg://022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:20:38.675064564-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:20:38.675252396-05:00] ERROR [transport_manager]: Failed to connect to transport discovery, retrying... error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:20:38.675302772-05:00] WARN retrier [transport_manager]: Retrying... current_backoff=1s error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:20:57.995040584-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:20:57.995192112-05:00] WARN retrier [utclient]: Retrying... current_backoff=20s error="uptime tracker httpauth: Get "dmsg://022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:20:58.676267755-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:20:58.676399994-05:00] ERROR [transport_manager]: Failed to connect to transport discovery, retrying... error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:20:58.676452212-05:00] WARN retrier [transport_manager]: Retrying... current_backoff=1s error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:21:17.99616077-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:21:17.996346974-05:00] WARN retrier [utclient]: Retrying... current_backoff=40s error="uptime tracker httpauth: Get "dmsg://022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:21:18.677582753-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:21:18.677750249-05:00] ERROR [transport_manager]: Failed to connect to transport discovery, retrying... error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:21:18.677797506-05:00] WARN retrier [transport_manager]: Retrying... current_backoff=1s error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:21:37.997380974-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:21:38.678125537-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:21:38.678297941-05:00] ERROR [transport_manager]: Failed to connect to transport discovery, retrying... error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:21:38.678343652-05:00] WARN retrier [transport_manager]: Retrying... current_backoff=1s error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:21:57.997356458-05:00] WARN retrier [utclient]: Retrying... current_backoff=1m20s error="uptime tracker httpauth: Get "dmsg://022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:21:58.679374552-05:00] DEBUG ClientSession.DialStream [dmsg_http:dmsgDC]: Stream closed on failure. close_error=<nil> dst_addr=02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80 error="i/o deadline reached" session=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2023-06-25T09:21:58.679544735-05:00] ERROR [transport_manager]: Failed to connect to transport discovery, retrying... error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"
[2023-06-25T09:21:58.679589109-05:00] WARN retrier [transport_manager]: Retrying... current_backoff=1s error="transport discovery httpauth: Get "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80/security/nonces/02cf226af53dc6e507dc12a7a444b76d9aa7bfbd48b5f83a8124af76e14f78e39a": i/o deadline reached"

here are the keys for the prod services on develop

    "dmsg_discovery": "dmsg://022e607e0914d6e7ccda7587f95790c09e126bbd506cc476a1eda852325aadd1aa:80",
    "transport_discovery": "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80",
    "address_resolver": "dmsg://03234b2ee4128d1f78c180d06911102906c80795dfe41bd6253f2619c8b6252a02:80",
    "route_finder": "dmsg://039d89c5eedfda4a28b0c58b0b643eff949f08e4f68c8357278081d26f5a592d74:80",
    "uptime_tracker": "dmsg://022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80",
    "service_discovery": "dmsg://0204890f9def4f9a5448c2e824c6a4afc85fd1f877322320898fafdf407cc6fef7:80"

Here they are in your PR

    "dmsg_discovery": "dmsg://022e607e0914d6e7ccda7587f95790c09e126bbd506cc476a1eda852325aadd1aa:80",
    "transport_discovery": "dmsg://02b307aee5c8ce1666c63891f8af25ad2f0a47a243914c963942b3ba35b9d095ae:80",
    "address_resolver": "dmsg://03234b2ee4128d1f78c180d06911102906c80795dfe41bd6253f2619c8b6252a02:80",
    "route_finder": "dmsg://039d89c5eedfda4a28b0c58b0b643eff949f08e4f68c8357278081d26f5a592d74:80",
    "uptime_tracker": "dmsg://022c424caa6239ba7d1d9d8f7dab56cd5ec6ae2ea9ad97bb94ad4b48f62a540d3f:80",
    "service_discovery": "dmsg://0204890f9def4f9a5448c2e824c6a4afc85fd1f877322320898fafdf407cc6fef7:80"

they are the same keys so I anticipate there is some issues with the services themselves connecting to dmsg-discovery or else the config used by the services which sets the key they use to connect to dmsg is wrong.

Do the services connect to the dmsg-discovery over dmsg? I think not, as they would need to connect to a specific dmsg server first to do so.