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

Chain exports exits in success when daemon is killed #4098

Closed
travisperson opened this issue Sep 29, 2020 · 0 comments · Fixed by #4179
Closed

Chain exports exits in success when daemon is killed #4098

travisperson opened this issue Sep 29, 2020 · 0 comments · Fixed by #4179
Labels
P1 P1: Must be resolved

Comments

@travisperson
Copy link
Contributor

Describe the bug
When running a chain export, if the daemon goes away (connection closes, dies, etc) the chain export will exit in success. This makes it really hard to ensure a proper export.

In this example, I issued a kill -15

➜  ~ lotus chain export --tipset @92000 test.car
➜  ~ echo $status
0

In this example, I issued a kill -9

➜  ~ lotus chain export --tipset @92000 test.car
2020-09-29T19:36:56.555Z	WARN	rpc	go-jsonrpc@v0.1.2-0.20200822201400-474f4fdccc52/websocket.go:660	failed to write close message: write tcp 127.0.0.1:35346->127.0.0.1:1234: write: broken pipe
➜  ~ echo $status
0
@travisperson travisperson changed the title Chain exports exists in success when daemon is killed Chain exports exits in success when daemon is killed Sep 29, 2020
@jennijuju jennijuju added the P1 P1: Must be resolved label Oct 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 P1: Must be resolved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants