Closed davidgasquez closed 3 weeks ago
Many thanks @davidgasquez
I can confirm that I was able to reproduce this error locally. My initial suspicion was a resource usage limitation but after testing on a 64 core, 1 TiB RAM system the issue is still present.
Is there anything I can try/do to help add more information to this one? We're running lily
to index the chain and this causes jobs to fail. Recent jobs, being bigger, have more chances to fail due this error.
@TippyFlitsUK could you share the steps you followed to reproduce this?
Hey Forrest 👋
Simply ran the following command on different spec servers:
lotus chain export --recent-stateroots=2880 test.chain
Any updates on this one @TippyFlitsUK? Basically, I'm curious if this is something that will get worked on soon. :sweat_smile: No worries if not as Forrest is patching things up on Lily's side but still wanted to check.
Checklist
Latest release
, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Describe the Bug
We are running some jobs on non-bootstrapped nodes using Lily. Some of these nodes usually get the following message.
The
lily
daemon gets killed in this case. I think @TippyFlitsUK has been able to reproduce it in Lotus.This also appears in the Lily logs:
@rvagg left a comment on that in the original issue: https://github.com/filecoin-project/filet/issues/22#issuecomment-1383295745.
Logging Information
Repo Steps