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

Connection to the Bitcoin network failed because of an error: java.lang.IllegalStateException: Expected PENDING or IN_CONFLICT, was BUILDING. #6714

Closed
pprvggc6um opened this issue May 26, 2023 · 4 comments · Fixed by #6961

Comments

@pprvggc6um
Copy link

pprvggc6um commented May 26, 2023

Description

Bisq had been working without issue for a while
had to restart system for something

Start Bisq
In less than a minute, get java exception

Warning
Connection to the Bitcoin network failed because of an error: java.lang.IllegalStateException: Expected PENDING or IN_CONFLICT, was BUILDING.

Version

1.9.10

Steps to reproduce

I do not know how to reproduce this issue.

Expected behaviour

Bisq should start normally

Actual behaviour

Screenshots

Device or machine

HP laptop
Windows 7 Pro
Version 6.1.7601 Service Pack 1 Build 7601

Additional info

Bisq had been working without issue for a while
had to restart system for something

Start Bisq
In less than a minute, get java exception

Warning
Connection to the Bitcoin network failed because of an error: java.lang.IllegalStateException: Expected PENDING or IN_CONFLICT, was BUILDING.

java lang IllegalStateException

click close

After a while with a screen reporting no connection to tor network

connection-failed

Get the "Connection problems" screen
delete-tor-files

Click "Delete outdated tor files and shutdown"

Tor file deletion completes
tor-deleted

click shutdown

Start up Bisq again

Back to the java exception error and then the "Connection Problems?" screen suggesting to delete outdated tor files and shutdown.

I moved my data directory aka started up Bisq with a new profile, and this started as expected.

Bisq log file:
bisq.log

@appideias
Copy link

Same here.

@pazza83
Copy link

pazza83 commented Aug 25, 2023

An SPV resync should fix this:

https://bisq.wiki/Resyncing_SPV_file

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Copy link

github-actions bot commented Dec 1, 2023

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@appideias @pazza83 @pprvggc6um and others