dpblnt

Also for ```ruby api.sendMessage(this_chat_id, "the message", {"parse_mode"=> "HTML"}) ``` i get ```telegram 400 Bad Request /usr/local/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:223:in `exception_with_response' /usr/local/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:103:in `return!' /usr/local/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:809:in `process_result' /usr/local/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:725:in `block in transmit' /usr/lib/ruby/2.3.0/net/http.rb:853:in `start' /usr/local/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:715:in `transmit' /usr/local/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:145:in...

> For the record, `yarn` simply _refuses_ to install packages correctly for me. I have terrible luck with that package manager. same here ``` installing web dependencies ... yarn install...

`renice -15 $( pidof stellar-core )` `renice -13 $( pidof horizon )` helps it for me

> Can you share more logs? Stellar-Core can become unresponsive when Horizon ingests state. In this case it's normal. I'm sorry I can not, I run that node without logging....

> > `renice -15 $( pidof stellar-core )` `renice -13 $( pidof horizon )` > > helps it for me > > How it works? can you give me ref...

here is one log from me, with LOG_LEVEL=warn got "ERROR read timeout reached" on client side (not horizon error code) WARN[2022-06-02T16:26:03.439+03:00] Herder: surge pricing in effect! 1051 > 1000 pid=5468...

and another one 2 minutes later WARN[2022-06-02T16:30:49.822+03:00] could not load stellar-core info: http request errored: Get "http://localhost:11626/info": context deadline exceeded pid=5468 ERRO[2022-06-02T16:30:49.823+03:00] failed to load the stellar-core info err="http request...

Is there a way to force horizon not to reset captive-core's database to genesis ledger on every horizon startup, regardless of the `--in-memory` parameter?

It was a simple `horizon serve`, it was running for some hours already, it was synced and serving.

I can not reproduce it. It happened only once.