08:22 <stellar-slack> <sacarlson> I'm having some new problems today starting up stellar-core that seems to lock up my computer. it ends up taking all cpu and mem

08:25 <stellar-slack> <sacarlson> first fail, seems to lock up when I try to abort ctl-C

08:25 <stellar-slack> <sacarlson> tried soft restart and again locks up my computer after fail to sync and try to abort

08:29 <stellar-slack> <sacarlson> secound and third attempt the same with this output on soft reset, will try full reset database

08:30 <stellar-slack> <sacarlson> this is with stellar-core commit 28bcca5b669e17fe59f1fea9b596cd5ff399a4e6

08:45 <stellar-slack> <sacarlson> even with full database reset it seems to be stuck

09:23 <stellar-slack> <sacarlson> full reset isn't fixing this problem it's still stuck at the level 7 after full reset

09:23 <stellar-slack> <sacarlson> did I miss some change to the network?

09:50 <stellar-slack> <sacarlson> I created a new issuer https://github.com/stellar/stellar-core/issues/839

10:28 <stellar-slack> <sacarlson> tried regress to stellar-core commit f081395ccb766115d9c1febf0a15f000682c2211 and did a full database reset now I get a different error

10:53 <stellar-slack> <sacarlson> runs ok in standalone so guess that's what I will have to live with for now

13:10 <stellar-slack> <jed> Sacarlson you sure it isn't just taking a long time?

13:10 <stellar-slack> <sacarlson> prity sure

13:10 <stellar-slack> <jed> We have been doing stress testing of testnet so there is a lot more data

13:10 <stellar-slack> <sacarlson> no one else with the problem?

13:11 <stellar-slack> <sacarlson> that might be what broke it then?

13:11 <stellar-slack> <jed> If you run the latest master info will tell you where it is in catchup

13:11 <stellar-slack> <jed> I think it just takes a lot longer

13:12 <stellar-slack> <jed> How long are you waiting?

13:12 <stellar-slack> <sacarlson> ok I'll try that later, I did see your added prints in the later version that I didn't try

13:12 <stellar-slack> <sacarlson> I waited maybe 15 minutes stuck on level 7

13:13 <stellar-slack> <jed> Are you also trying to get full history?

13:13 <stellar-slack> <sacarlson> also had the lock up that I now want to put stellar-core in a cage to prevent it from killing my system

13:14 <stellar-slack> <sacarlson> the startup script and configs should tell you as I'm not sure I just use those scripts

13:14 <stellar-slack> <sacarlson> oh full history would be a full reset so yes

13:15 <stellar-slack> <jed> When you say it locks up, is it not printing log lines after that?

13:15 <stellar-slack> <sacarlson> it's using 99% cpu and 89% or more mem

13:16 <stellar-slack> <sacarlson> on a quad core system with 8gb mem

13:16 <stellar-slack> <sacarlson> that hapened about 2 or 3 times before I tried the full reset

13:16 <stellar-slack> <jed> You can configure it to get full history or just start from current ledger. You only need full history for horizon

13:17 <stellar-slack> <jed> But when that happened were there new log lines?

13:17 <stellar-slack> <sacarlson> ok I would need the script or command line needed to prevent need for full history

13:17 <stellar-slack> <sacarlson> the logs are in the report

13:18 <stellar-slack> <jed> Yes but when you tailed the log was it still writing lines?

13:19 <stellar-slack> <sacarlson> no it just stoped at that last line seen in the log

13:19 <stellar-slack> <jed> What you posted doesn't tell me if there were more lines later :)

13:19 <stellar-slack> <jed> Ah ok cool

13:19 <stellar-slack> <jed> So certainly a bug

13:20 <stellar-slack> <sacarlson> hope you can duplicate it

13:21 <stellar-slack> <sacarlson> I tried two stellar-core commits but only published one of the failures

13:21 <stellar-slack> <jed> I'm on my phone so look at the example.cfg in the docs folder. There is a configuration value call CATCH_UP_COMPLETE or something. Set it to false

13:22 <stellar-slack> <sacarlson> ok I'll take a look

13:25 <stellar-slack> <bartek> `CATCHUP_COMPLETE=false`

13:25 <stellar-slack> <sacarlson> from what it shows in the docs the default is already false

13:25 <stellar-slack> <sacarlson> but I've now added it to my config

13:29 <stellar-slack> <sacarlson> no change with that added setting but I'm now setup running the taged version

13:31 <stellar-slack> <sacarlson> commit f081395ccb766115d9c1febf0a15f000682c2211

13:40 <stellar-slack> <jed> can you paste your config?

13:59 <stellar-slack> <sacarlson> config is in the report

14:01 <stellar-slack> <sacarlson> opps did I forget it

14:01 <stellar-slack> <sacarlson> https://drive.google.com/folderview?id=0B4pSHwxHXW9Sejczc3RTX3dxUnM&usp=sharing

14:33 <stellar-slack> <sacarlson> and this is the config from the last test above with your added line CATCHUP_COMPLETE=false

18:18 <stellar-slack> <jed> Sacarlson how much ram do you have on that machine?

18:18 <stellar-slack> <sacarlson> 8gb

18:19 <stellar-slack> <jed> Ah yeah just saw in the issue

18:20 <stellar-slack> <sacarlson> any luck duplicating it?

18:20 <stellar-slack> <jed> Well they commented on the issue. Can you take a look?

18:20 <stellar-slack> <sacarlson> ya sure

18:31 <stellar-slack> <sacarlson> I gave them a screen shot of cpu and mem usage at one captured point. tomaro I'll try give that level 7 point more time and see what comes of it

19:02 <stellar-slack> <jed> Yeah maybe let it run over night and see if it syncs

21:02 <stellar-slack> <brian.ebert> I'm finding a delay of 15-20 minutes when creating an account by generating a Keypair and requesting friendbot to fund the account. If I call the horizon test net and get the account data, I get 404 errors for a while, then finally a response to the https get. Is this expected? It seems to violate my expectation that consensus is found within seconds.

21:13 <stellar-slack> <jed> Brian.ebert we are stress testing test net and horizon is falling behind

21:13 <stellar-slack> <jed> Stellar-core is keeping up fine though

21:14 <stellar-slack> <jed> I'll reduce the stress load when I get back and then horizon will catch up

22:45 <stellar-slack> <brian.ebert> Thank you!