`ordhook service start` can silently fail when user's machine "max per-process number of file descriptors" set by `ulimit` is too low

[mefrem]

Summary: User must manually set ulimit -Sn 10000 so that ordhook process can handle work required when creating tables for ordinals inscription indexes, however both 1) the error messages suggesting a problem are hidden by default and 2) the error messages themselves don't contain or suggest the fix (increasing ulimit -Sn 10000).

Description of problem: With ordhook service start running, this screen would persist (indefinitely?) with no indication that certain indexing actions aren't working:

These would be the error logs that suggest an error:

Solution is to have user manually increase ulimit -Sn 10000 — maybe create a special class of error message indicating fix required on part of user?

[lgalabru]

@taoyouxian this looks like a different issue. could you share the commands that you're sending, along with configuration file? Thanks!

[taoyouxian]

@taoyouxian this looks like a different issue. could you share the commands that you're sending, along with configuration file? Thanks!

Thanks for replying. I have fixed it by upgrading the Bitcoin version.

[lgalabru]

This is being worked on with https://github.com/hirosystems/ordhook/pull/200 and https://github.com/hirosystems/ordhook/pull/206

[mefrem]

@lgalabru should I update docs to include ulimit instruction?

[lgalabru]

The README already includes this instruction. Will close this ticket, thanks @mefrem!