-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Unable to open database #47
Comments
Hey there, can you try starting it several more times and waiting for the context to timeout? I saw a similar issue before but it disappeared before I got to debug it. It might have to do with #46 which I'm currently investigating. You could try a Superhighway84 version < 0.2.0, since it was working flawlessly before the upgrade to IPFS 0.12.2. |
Hi, thanks for the advice, I will run it several times and see what happens. I did try v0.1.2 and it also panicked, but already at "initializing TUI and loading database" and much quicker. |
Yeah ... I understand #46 is a priority. I hope you will tell us what you found after you crack it! I ran version 0.2.0 about 10 times consecutively with the same results. I then tried with 0.1.1 and it waits at: TUI and loading database, please wait ... I left that to work for 2 hours, without visible results, but it is doing tons of work in the background, not just hanging. I then restarted it after setting: ipfs config profile apply lowpower That might help, because I'm running it in a VM. |
Hi, I did a bit of debugging and it hangs in database.go at:
It never returns from that call. Any idea why that could be? |
@mp-netis could you check this issue and see if any of that helps? |
It does not seem to be that issue.
I do use go1.17.4 and not 1.17 ... but that should not be an issue. |
Thank you for confirming. Can you try resetting the IPFS repo and deleting the cache? Here is how that works. I honestly don't know what else to suggest for now otherwise and will have to dig deeper into this. Yet again, 0.2.0 has some issues in general in which the database doesn't seem to correctly sync anymore, which I'm currently investigating. Maybe that same issue is what prevents a fresh install from starting in first place. |
Hi, I have been resetting repo, cache and config all the time. I now tried it all together again, with the prebuilt 0.1.1. and all the kernel settings ... unfortunately same behaviour. We must be missing something very trivial. If it works from fresh for you and also @diyism, there must be something strange on my end. |
@mp-netis v0.2.1 is building as I write this. Feel free to give it another try when it's published. It should support IPFS 0.12 and sync right away. |
Hey @mrusme I'm having the same issue as @mp-netis . I am trying to runsh84 behind Docker though. This is my current Dockerfile:
Building and running docker as (I've tried without --net=host and --privileged as well):
Any ideas? |
Hey there, have you checked the SH84 log that's usually under |
Thanks for the quick reply. That's the output:
|
Thanks, could you give the |
Thanks. I tried these but didn't help. I'm not sure if you were able to replicate using the Dockerfile. I tried on Ubuntu 22.04. This is the first IPFS project I tried. I'll get more familiar with IPFS and see if I can find a solution for what's going on. |
Haven't tried running it within a Docker container tbh. If you don't mind the effort, launch some micro VPS online and try launching it there. If it fails to connect on that as well there might indeed be an issue. So far I'd say though that it's simply not able to fetch the DB in time, before the context cancels. That could be due to it being unable to set up P2P connectivity. |
Hi,
I cannot get superhighway84 to go thru the first run. This is what gets output:
The log file says:
The database LOG file in .cache says:
This is version 0.2.0 and IPFS is 0.12.2 running on Ubuntu 20.04.4.
I ran ipfs init and accepted all the default values offered by superhighway84.
I've tried everything I could find without effect:
What else can I try? I would appreciate some hints.
Thnx.
The text was updated successfully, but these errors were encountered: