Skip to content
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

Data likely corrupted on quit #234

Open
dergoegge opened this issue Dec 9, 2020 · 1 comment
Open

Data likely corrupted on quit #234

dergoegge opened this issue Dec 9, 2020 · 1 comment

Comments

@dergoegge
Copy link
Contributor

I ran into this on the test server.

On block : 426901
On block : 427001
On block : 427101
^CUser exit signal received. Exiting...
Program timed out. Force quitting. Data likely corrupted

// Sometimes there are bugs that make the program run forever.
// Utreexo binary should never take more than 10 seconds to exit
go func() {
time.Sleep(60 * time.Second)
fmt.Println("Program timed out. Force quitting. Data likely corrupted")
os.Exit(1)
}()

I don't suspect that there is a bug but rather that the test server is too slow to finish up in 60sec. I was using the cow forest for which it is normal to take longer when quitting since it has to commit a bunch of data to disk.
We should remove the timeout or increase it.

@kcalvinalvin
Copy link
Member

Yeah this has been on my TODO for a bit... if the user's disk is slow, it'll time out.

An easy fix would be to just increase it. Another (more elegant) fix could be to only force quit when given SIGINT twice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants