11:51 <stellar-slack> <raymens> By running the sample: A Local full network on the docker-stellar-core page I ran into the following error message: ``` 2015-10-08T11:48:25.230 2a7455 [] [default] INFO * 2015-10-08T11:48:25.230 2a7455 [] [default] INFO * Force-starting scp from thecurrent db state. (`force scp` flag cleared in the db) 2015-10-08T11:48:25.230 2a7455 [] [default] INFO * 2015-10-08T11:48:25.230 2a7455 [] [Herder] INFO Fo

11:51 <stellar-slack> stellar-core: herder/HerderImpl.cpp:165: virtual void stellar::HerderImpl::bootstrap(): Assertion `mSCP.isValidator()' failed. exited 56 ``` Does anyone have any idea what that could mean?

11:53 <stellar-slack> <sacarlson> you might want to post your config file also

11:53 <stellar-slack> <sacarlson> and maybe the full command line used to perform it

11:59 <stellar-slack> <raymens> The command (just like the one in the readme of https://github.com/stellar/docker-stellar-core/): ``` for N in 1 2; do docker run --name db$N -p 544$N:5432 --env-file examples/local.env -d stellar/stellar-core-state docker run --name node$N --net host -v ~/.aws:/root/.aws --volumes-from db$N --env-file examples/local.env -d stellar/stellar-core /start node$N fresh forcescp done for N in 3; do docker

11:59 <stellar-slack> --env-file examples/local.env -d stellar/stellar-core-state docker run --name node$N --net host -v ~/.aws:/root/.aws --volumes-from db$N --env-file examples/local.env -d stellar/stellar-core /start node$N fresh done ``` The config is https://github.com/stellar/docker-stellar-core/blob/master/examples/local.env With an edit to have the history local (copied from https://github.com/stellar/docker-stellar-core/blob/m

12:00 <stellar-slack> <raymens> which means having this for the history files instead of using AWS: ``` HISTORY_GET=cp history/%s/{0} {1} HISTORY_PUT=cp {0} history/%s/{1} HISTORY_MKDIR=mkdir -p history/%s/{0} ```

12:41 <stellar-slack> <raymens> And on running the stellar-core using the testnet sample config it crashes due to not being able to setup a transport socket. Is this related to blocked ports? If so, what ports (11625?)

13:03 <stellar-slack> <sacarlson> from what little I've seen so far raymens it looks like you might be looking to setup a standalone stellar-core? I've never run from within docker so I'm not sure of some things here

13:06 <stellar-slack> <raymens> Yeah a sim env of 3 nodes. Actually running it with standalone=true is no problem (outside of docker)

13:11 <stellar-slack> <sacarlson> well looks like you will need the help of the bigboys as this is outside my expertise. they should be on line in a short time to help you out. I think the info you now present should be good

13:12 <stellar-slack> <raymens> All right, I'll await their reply. Thanks

14:46 <stellar-slack> <jed> raymens: I think those example configs are out of date for docker. let me fix now

14:47 <stellar-slack> <raymens> @jed: awesome :)

14:47 <stellar-slack> <raymens> thanks for looking into it

14:56 <stellar-slack> <jed> ok try with those changes

15:02 <stellar-slack> <jed> actually hold on. maybe an issue with the latest buidl

15:09 <stellar-slack> <raymens> oh okay, was just checking

15:12 <stellar-slack> <raymens> they seem to be running now though, not sure about the state they're in

15:12 <stellar-slack> <jed> oh really?

15:13 <stellar-slack> <raymens> somewhat, they're dropping their peers all the time

15:13 <stellar-slack> <raymens> not crashing anymore though

15:13 <stellar-slack> <raymens> "Transport endpoint is not connected [TCPPeer.cpp:363]"

16:42 <stellar-slack> <sacarlson> I had more thoughts about offline transactions that I think I have a method that might work. I plan to add the feature of witness to my multi-sign-server system that will people to use it as witness points to show a locked account with fund balance without ever needing acess to the funds

21:13 <stellar-slack> <scott> deploying horizon master to testnet

23:53 <stellar-slack> <jed> testnet down for an upgrade