02:52 <stellar-slack> <sacarlson> I'm ready to give stellar network testnet horizon another try, is it working today or do we still have amazon problems?

03:39 <stellar-slack> <sacarlson> wow it seems I still can't connect to the stellar network from here with stellar-core: 2015-09-21T10:38:35.810 19b6b8 [140320780736384] [Ledger] INFO Catchup awaiting checkpoint (ETA: 0 seconds), buffering close of ledger 74156

03:46 <stellar-slack> <sacarlson> it seems it's working on the web interface now so must be something on this side?

03:54 <stellar-slack> <dzham> network is working for me

03:55 <stellar-slack> <sacarlson> good to know thanks dzham

03:57 <stellar-slack> <dzham> I am, but horizon still pushes things to the network

03:59 <stellar-slack> <sacarlson> yes I can run my system now in horizon mode but I can't bring up a stellar-core instance here in thailand at this time

03:59 <stellar-slack> <jed> get="curl -sf https://s3-eu-west-1.amazonaws.com/history.stellar.org/prd/core-testnet/core_testnet_001/{0} -o {1}

04:00 <stellar-slack> <sacarlson> so add that line?

04:00 <stellar-slack> <jed> make sure your config file has _ rather than -

04:00 <stellar-slack> <jed> for core_testnet_001

04:00 <stellar-slack> <jed> it will already be there

04:00 <stellar-slack> <jed> but may have -

04:00 <stellar-slack> <sacarlson> ok I'll try that

04:03 <stellar-slack> <sacarlson> seems it's already there

04:04 <stellar-slack> <sacarlson> oh wait

04:15 <stellar-slack> <sacarlson> ok now I have sync. I note that we may now be running horizon on stellar-core 1a24aedfdfcb5b56887f149579f98424f28e3b05 is that what we are running?

04:17 <stellar-slack> <sacarlson> it seems in this version all the amazon names have changed

06:07 <stellar-slack> <buhrmi> the change from - to _ fixed it for me too

09:05 <stellar-slack> <matschaffer> Sorry about that change folks. It was the simplest way to make the config setup docker 1.8 compatible (1.7 allowed hyphens in env var names, 1.8 doesn't)