search

iotaledger / iri

IOTA Reference Implementation
Other
1.15k stars 370 forks source link

Lost connection to client - cannot send response #1320

Open Hissi88 opened 5 years ago

Hissi88 commented 5 years ago

Bug description

IRI log shows the error: ERROR com.iota.iri.service.API - Lost connection to client - cannot send response

After that line the CPU load is at 100% and the to process / to replay Tx are rising, but not the LMI. IRI API doen't respond. Restart of IRI needed.

In the moment of the error, there are lots of open connections to IRI (sudo lsof -Pni:14265) https://cdn.discordapp.com/attachments/477382787955949568/540922881681522689/connection_dump.txt

After I deleted the full DB (taken over from 1.5.6) and started with downloaded snapshot files, the CPU load is now <15% and the error didnt occur again yet (2 days). With the full DB (32GB), the CPU load was ~50% and the error occured every 6-12 hours.

IRI version

1.6.0

Hardware Spec

4 Core, 8 RAM, Ubuntu 16.04 Database since 1.5.6. (32GB)

Steps To Reproduce

  1. Have a huge DB (>30 GB)
  2. Have an average CPU load of 50%

Errors

ERROR com.iota.iri.service.API - Lost connection to client - cannot send response

f-ben commented 5 years ago

Same problem here also with Ubuntu, 1.6.0, 4 core, 8 GB. Difference is that I use local snapshots.

LOCAL_SNAPSHOTS_ENABLED = true LOCAL_SNAPSHOTS_PRUNING_ENABLED = true LOCAL_SNAPSHOTS_PRUNING_DELAY = 120000

Right now I prevent the error to happen with restarting IRI every 2 hours.