-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[error] gen_server.erl:949 Generic server ar_chunk_storage terminating. Reason: {{badmatch,{error,timeout}},[{ar_chunk_storage,handle_call,...},{gen_server,...}|...] #385
Comments
Hi, timeouts are often temporary and recoverable, but |
Thank you for your fast reply! yes it recovers.. but now ten hours there is a similar error: ( LOCK: No locks available )
and berfore there were hundreds of this new error messages today:
This node is my strongest, as i want to download the full weave. Dual EPYC CPU, 600 GB RAM, 3 TB Enterprise NVMe for data folder, ext4, Ubuntu22. only chunk_storage is symlinked to a nfs server ( HDD drives RAID6 as ext4 ). on the other hand i guess i should not put too much stress on the HDDs? i often see these messages which i did not see on a ssd chunk_storage:
my config:
mining is false, fs.file-max = 4194304, vm.nr_hugepages=1250 |
update on this: one more error failed_to_instantiate_rocksdb_iterator / IO error: lock hold by current process
|
Hi Lev, thank you for your continous work here. As i use arweave more and more, i discover more and more errors. i check the old issues, but my errors seem all to be "new". are you interested in all of them? or should we accept the fact that there are problems from time to time..
This crash leaves arweave in a "half open" state - process still running but not responding to http request or doing anything else. But luckily it can be fixed with a restart.
The text was updated successfully, but these errors were encountered: