-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
Stuck indexing and not responding to incoming connections #734
Comments
I encountered this again today in local dev after pulling in a lot of new data. Indexing was stalling at 97% and the server wasn't fully booting and so wasn't responding to whoami. After updating ssb-db to the latest version I did get some new errors in server logs that I hadn't seen before, so maybe they were causing the stall before:
|
I encountered ssbc#734 and after installing [email protected] this stalling issue went away, so it appears to fix ssbc#734.
ssb-server as of v16 can get into an unresponsive state. In this state, it rejects incoming connections and does not index the flumelog.
When a secret-handshake client tries to connect to the server - even a local one - the server rejects the connection a few seconds after sending the first response packet. Example transcript from trying to connect to the server:
If the server is configured to use the unix noauth socket,
sbotc
can connect using that. (The-4
option used above forces it to use TCP and thus SHS instead of the noauth socket). Connecting with sbotc using the noauth socket reveals that ssb-server is not indexing its flumelog, as this command shows the progress stuck:It looks to me that ssb-server v16 gets into this state when it starts while the flumelog is not caught up. In previous versions, doing this would not be problem. ssb-server should allow appending data to the flumelog while it is offline and then indexing and catching up when it starts. Running ssb-server v15 causes it to catch up indexing, and then switching back to ssb-server v16 works again.
SSB thread reporting this issue:
%xPim4b5fwQ+3YDWkJ34WS2dN61gteHuu9UDqCY3Ipxg=.sha256
The text was updated successfully, but these errors were encountered: