4

Whenever I submit a transaction I get a timeout error (after 60 secs). The server is a docker quickstart image in standalone mode. To solve the issue I am have to run the image with -e LOG_LEVEL="debug". In this case I get the reply in a few seconds as expected.

My question is how can I fix this issue without using LEVEL="debug" which I cannot use in production?

Configuration that has the problem:

docker run -d --rm -it -p "8000:8000" -v "/dev_data:/opt/stellar" --name stellar_dev stellar/quickstart --standalone

Configuration that solves the problem:

docker run -d --rm -it -e LOG_LEVEL="debug" -p "8000:8000" -v "/dev_data:/opt/stellar" --name stellar_dev stellar/quickstart --standalone
Improve this question
7
  • Both commands were the same. Please check my edit to make sure it's what you intended.
    – Synesso ♦
    Jan 23 '19 at 11:41
  • Could you confirm the version of your Horizon? It is reported that Horizon v0.15.4 could ease quite much of this issue.
    – cesarm
    Jan 24 '19 at 6:10
  • @synesso Yes you are absolutely right! sorry about that!
    – Massimo Nicolardi
    Jan 24 '19 at 7:32
  • @cesarm horizon_version: v0.14.1, core_version: v10.0.0
    – Massimo Nicolardi
    Jan 24 '19 at 7:39
  • 1
    @cesarm it works like a charm! the problem disappeared after upgrading to v0.15.4
    – Massimo Nicolardi
    Jan 24 '19 at 8:14
0

I am digging on this problem and I got some conclusion. log_level='debug' isn't solution about this. The key is horizon was restarted. I don't know the exact problem.

If you want to make timeout situation, you restart horizon, PostgreSQL, stellar-core sequentially in supervisorctl.

Improve this answer
2

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.