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.

Sign up for GitHub

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

Jump to bottom

bisq problem gesperrte beträge wegen fehler im programm!!! #2935

Closed
gandi777 opened this issue Jul 2, 2019 · 24 comments
Closed

bisq problem gesperrte beträge wegen fehler im programm!!! #2935

gandi777 opened this issue Jul 2, 2019 · 24 comments
Labels
was:dropped

Comments

@gandi777
Copy link

gandi777 commented Jul 2, 2019

bisqerror02072019.log
cannot access open handles! logged money!! what to do???
@ripcurlx
Copy link
Contributor

ripcurlx commented Jul 3, 2019

@gandi777 Do you see this logs also after a re-start?

@ripcurlx
Copy link
Contributor

ripcurlx commented Jul 3, 2019

And it would help if you describe your problem in more detail and how it happened. Otherwise it is quite hard to help out.

@gandi777
Copy link
Author

gandi777 commented Jul 3, 2019 via email

@gandi777
Copy link
Author

gandi777 commented Jul 3, 2019

bisq-error-03072019.log
this is the new/updated error-log

@a123b
Copy link
Contributor

a123b commented Jul 4, 2019

Looks like another case of #2910

@gandi777
Copy link
Author

gandi777 commented Jul 4, 2019 via email

@a123b
Copy link
Contributor

a123b commented Jul 4, 2019

There is probably going to be a "cleanup build" specific to this issue that you would have to run once to repair your Bisq data directory.

Until it gets released, you are going to have to wait until the other trader opens a dispute. Then you can confirm to the arbitrator that you received the buyer's payment to get the BTC unlocked.
After that, you will be able to go to the "Open Trades" tab again. (But your "History" tab might get broken then, in which case you'll need to wait for the cleanup build to access it.)

If you absolutely need to make trades while your "Open Trades" tab is broken, I'd suggest you use a new Bisq instance until the arbitrator closes the problematic trade.

@gandi777
Copy link
Author

gandi777 commented Jul 5, 2019

...thank you for your info!! so i will wait... :-)

@gandi777
Copy link
Author

gandi777 commented Jul 11, 2019 via email

@ghost
Copy link

ghost commented Jul 11, 2019

@gandi777 what is the onion address of your arbitrator ?

@gandi777
Copy link
Author

gandi777 commented Jul 11, 2019 via email

@ghost
Copy link

ghost commented Jul 11, 2019 •
edited by ghost
Loading

go read the details for your problematic trade.
This info screen should mention a "selected arbitrator" field which contains the arbitrator's onion address.

Also, please, if you could avoid recopying previous messages + your super long signature, that would help make this issue a bit more readable.

@gandi777
Copy link
Author

sorry for making problems with the mail! i see, that i can post it on github also! think, this is better?
so, here is the adresse of the arbitrator:
s6yrrpezc3zp6biy.onion:9999

thank you for help!

@ghost
Copy link

ghost commented Jul 11, 2019 •
edited by ghost
Loading

Concerned arbitrator is keo (-> @keo-bisq )
I just pinged him.
Maybe he can help, but that's not 100% sure.

@gandi777
Copy link
Author

thank you very much!! should i write him or means the ping that he is informed and will write?

@ghost
Copy link

ghost commented Jul 11, 2019

The ping just means I sent a ping.
If he's present, he will certainly contact you.
If he's absent ... there will be some delay.

@gandi777
Copy link
Author

ah! :-) thanks a lot!

@keo-bisq
Copy link

Can I have the tradeID?

@gandi777
Copy link
Author

of course! thank you for help!! @keo-bisq

989351-1fda558e-bed7-4283-8654-c99f7ecd16c0-112

@gandi777
Copy link
Author

@keo-bisq thank you very much for helping me!!

@a123b
Copy link
Contributor

a123b commented Jul 16, 2019

@gandi777 The cleanup build I wrote about earlier is released now. If you can't view your trade history now, running this build once will fix that. You can find it here (the file called Bisq-cleanup-trades-64bit). After you ran the cleanup build, be sure to upgrade to the regular Bisq v1.1.3 to prevent this issue from happening again in the future!

@gandi777
Copy link
Author

thank you first! but: i did the cleanup first. when i start bisq then, the message comes: cleanup done, shutting down!
than an run the normal bisq-update 1.1.3. now bisq starts, but when i go to my history, the same java message comes: java.lang.illegalargumentexception :-(. i am afraid to use bisq in the moment, what to do? :-(

@stale
Copy link

stale bot commented Oct 14, 2019

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.

@stale stale bot added the was:dropped label Oct 14, 2019
@stale
Copy link

stale bot commented Oct 21, 2019

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

@stale stale bot closed this as completed Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
was:dropped
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ripcurlx @a123b @keo-bisq @gandi777