Skip to content

Set RCON_IP reliably via DNS command. #34

@slothbear

Description

@slothbear

[under construction]

Last week the RCON_IP was not set, though the log said it was (add log from last week).

Suspecting some kind of timing problem, I added a 2-second wait after setting the IP. I'm not sure why, but the RCON_IP was set correctly this week. Setting the config_var restarts the server, but perhaps that restart takes a moment?

Aliasing host iron-boots.pickaxe.club to ip 142.99.183.75
Nov 13 18:05:55 wither app/web.1 ---=== moving pickaxe to iron-boots at 142.99.183.75
Nov 13 18:05:57 wither app/web.1 ---=== having slept, setting RCON_IP to 142.99.183.75
Nov 13 18:05:57 wither app/web.1 ---=== [[unreachable code, since set_config_var reboots?]]
Nov 13 18:05:57 wither app/web.1 54.198.138.148 - - [14/Nov/2020:02:05:57 +0000] "POST /hook HTTP/1.1" 201 2 2.7202
Nov 13 18:05:57 wither app/web.1 54.91.248.236 - - [14/Nov/2020:02:05:57 +0000] "POST /hook HTTP/1.1" 200 4 0.0005
Nov 13 18:05:57 wither heroku/router at=info method=POST path="/hook" host=wither.herokuapp.com request_id=f2c251bc-3ec0-4fbc-84eb-188d62d3af5b fwd="54.198.138.148" dyno=web.1 connect=1ms service=2726ms status=201 bytes=212 protocol=https
Nov 13 18:05:57 wither heroku/router at=info method=POST path="/hook" host=wither.herokuapp.com request_id=dae81673-df35-4a45-b186-0a654fdbcf22 fwd="54.91.248.236" dyno=web.1 connect=5ms service=970ms status=200 bytes=209 protocol=https
Nov 13 18:05:57 wither app/api Release v724 created by user paul@morganthall.com
Nov 13 18:05:57 wither app/api Set RCON_IP config vars by user paul@morganthall.com
Nov 13 18:05:58 wither heroku/web.1 Restarting

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions