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

stuck on "connecting database..." #66

Open
mister-monster opened this issue Jun 27, 2023 · 8 comments
Open

stuck on "connecting database..." #66

mister-monster opened this issue Jun 27, 2023 · 8 comments

Comments

@mister-monster
Copy link

So after a long process of attempting to get this software to run, raising my send buffer to 2500000 and dealing with IPFS versions and what not, upon launch of the superhighway84 binary it gets stuck on "connecting database..." I have no idea what to make of this, i was able to sort out all the other issues with my system and IPFS and their dependancy shenanigans but I have no information to work with beyond what the superhighway84 prompt is giving me upon initialization.

Thanks.

@mister-monster
Copy link
Author

update: upon waiting for a while, like 15 minutes, i get the following error:

2023/06/27 18:51:32 unable to open database: unable to fetch database manifest: context deadline exceeded
panic: unable to open database: unable to fetch database manifest: context deadline exceeded

	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1459c07]

goroutine 1 [running]:
github.com/mrusme/superhighway84/database.(*Database).Disconnect(0xc0024621e0)
	/home/runner/work/superhighway84/superhighway84/database/database.go:221 +0x27
panic({0x15d46a0, 0xc009710cc0})
	/opt/hostedtoolcache/go/1.18.9/x64/src/runtime/panic.go:838 +0x207
log.Panicln({0xc001645f48?, 0xc00355a540?, 0xc0000c70e0?})
	/opt/hostedtoolcache/go/1.18.9/x64/src/log/log.go:399 +0x65
main.main()
	/home/runner/work/superhighway84/superhighway84/superhighway84.go:125 +0x8dd

@ghost
Copy link

ghost commented Jun 28, 2023

same issue here

@mrusme
Copy link
Owner

mrusme commented Jun 29, 2023

I have just restarted the VPS that runs a permanent-online instance of SH84, which should help with connecting. Also, have you tried this? In any way, please try again now and report of connection was successfully established or you're still unable to connect.

@goodspeed34
Copy link

also here, already have auto relay enabled. It's running on a tilde server. So if you want to investigate this issue on this machine, I can make an account.

goodspeed@tilde:~$ superhighway84 
2023/07/03 17:28:18 loading configuration ...
2023/07/03 17:28:18 initializing logger ...
2023/07/03 17:28:18 initializing cache ...
2023/07/03 17:28:18 initializing TUI and loading database, please wait ...
2023/07/03 17:28:19 initializing database ...
2023/07/03 17:28:20 connecting database ...
2023/07/03 17:38:20 unable to open database: unable to fetch database manifest: context deadline exceeded
panic: unable to open database: unable to fetch database manifest: context deadline exceeded

        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1459c07]

goroutine 1 [running]:
github.com/mrusme/superhighway84/database.(*Database).Disconnect(0xc001f761e0)
        /home/runner/work/superhighway84/superhighway84/database/database.go:221 +0x27
panic({0x15d46a0, 0xc003f07b80})
        /opt/hostedtoolcache/go/1.18.9/x64/src/runtime/panic.go:838 +0x207
log.Panicln({0xc0008e7f48?, 0xc0034e9a40?, 0xc000095860?})
        /opt/hostedtoolcache/go/1.18.9/x64/src/log/log.go:399 +0x65
main.main()
        /home/runner/work/superhighway84/superhighway84/superhighway84.go:125 +0x8dd

@mrusme
Copy link
Owner

mrusme commented Jul 3, 2023

@goodspeed34 which version of SH84 are you running?

@goodspeed34
Copy link

goodspeed34 commented Jul 4, 2023

@mrusme I'm using the lastest release. https://github.com/mrusme/superhighway84/releases/tag/v0.2.4

@logistic-bot
Copy link

This is happening for me as well.

ipfs version 0.16.0
superhighway84 v0.2.4

Here are logs:

2023-12-20T21:27:28.021+0100    DEBUG   database/database.go:146        getting config root path ...
2023-12-20T21:27:28.021+0100    DEBUG   database/database.go:152        setting up plugins ...
2023-12-20T21:27:28.021+0100    DEBUG   database/database.go:157        creating IPFS node ...
2023-12-20T21:27:28.908+0100    INFO    database/database.go:169        connecting to peers ...
2023-12-20T21:27:28.909+0100    DEBUG   database/database.go:122        connected!      {"peerID": "QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb"}
2023-12-20T21:27:28.909+0100    DEBUG   database/database.go:122        connected!      {"peerID": "QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb"}
2023-12-20T21:27:28.909+0100    DEBUG   database/database.go:122        connected!      {"peerID": "QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb"}
2023-12-20T21:27:28.909+0100    DEBUG   database/database.go:122        connected!      {"peerID": "QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb"}
2023-12-20T21:27:28.909+0100    DEBUG   database/database.go:122        connected!      {"peerID": "QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb"}
2023-12-20T21:27:28.909+0100    DEBUG   database/database.go:175        connected to peer!
2023-12-20T21:27:28.909+0100    INFO    database/database.go:179        initializing database connection ...
2023-12-20T21:27:28.909+0100    DEBUG   database/database.go:49 initializing NewOrbitDB ...
2023-12-20T21:27:28.946+0100    DEBUG   database/database.go:77 initializing OrbitDB.Docs ...
2023-12-20T21:27:28.946+0100    DEBUG   baseorbitdb/orbitdb.go:537      open orbitdb store      {"address": "/orbitdb/bafyreifdpagppa7ve45odxuvudz5snbzcybwyfer777huckl4li4zbc5k4/superhighway84"}
2023-12-20T21:27:28.946+0100    DEBUG   baseorbitdb/orbitdb.go:559      Open database   {"dbAddress": "/orbitdb/bafyreifdpagppa7ve45odxuvudz5snbzcybwyfer777huckl4li4zbc5k4/superhighway84"}
2023-12-20T21:27:28.946+0100    DEBUG   baseorbitdb/orbitdb.go:566      Look from       {"directory": "/home/logistic-bot/.cache/superhighway84/database"}
2023-12-20T21:27:28.946+0100    DEBUG   cacheleveldown/leveldown.go:88  opening cache db        {"path": "/home/logistic-bot/.cache/superhighway84/database/bafyreifdpagppa7ve45odxuvudz5snbzcybwyfer777huckl4li4zbc5k4/superhighway84"}
2023-12-20T21:37:28.948+0100    ERROR   database/database.go:183        %s      {"error": "unable to open database: unable to fetch database manifest: context deadline exceeded"}
github.com/mrusme/superhighway84/database.(*Database).Connect
        /home/runner/work/superhighway84/superhighway84/database/database.go:183
main.main
        /home/runner/work/superhighway84/superhighway84/superhighway84.go:109
runtime.main
        /opt/hostedtoolcache/go/1.18.9/x64/src/runtime/proc.go:250

And output of the CLI

2023/12/20 21:27:27 loading configuration ...
2023/12/20 21:27:27 initializing logger ...
2023/12/20 21:27:27 initializing cache ...
2023/12/20 21:27:27 initializing TUI and loading database, please wait ...
2023/12/20 21:27:28 initializing database ...
2023/12/20 21:27:28 connecting database ...
2023/12/20 21:37:28 unable to open database: unable to fetch database manifest: context deadline exceeded
panic: unable to open database: unable to fetch database manifest: context deadline exceeded

	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1459c07]

goroutine 1 [running]:
github.com/mrusme/superhighway84/database.(*Database).Disconnect(0xc0005a23c0)
	/home/runner/work/superhighway84/superhighway84/database/database.go:221 +0x27
panic({0x15d46a0, 0xc00af828b0})
	/opt/hostedtoolcache/go/1.18.9/x64/src/runtime/panic.go:838 +0x207
log.Panicln({0xc00326ff48?, 0xc004317d40?, 0xc000183380?})
	/opt/hostedtoolcache/go/1.18.9/x64/src/log/log.go:399 +0x65
main.main()
	/home/runner/work/superhighway84/superhighway84/superhighway84.go:125 +0x8dd

@mrusme
Copy link
Owner

mrusme commented Dec 26, 2023

The instance that I've been running on a VPS has been shut off a while ago and I didn't turn it back on due to the lack of interest from people to run this project and contribute to the network. Hence I would assume that the reason you're unable to connect is because there simply are no peers available right now.

Of course Superhighway84 should launch nevertheless, unfortunately it seems like OrbitDB/IPFS requires at least some peer to be available for the very first sync. I could invest some time to build in a workaround that would make the TUI launch and simply be empty for the time being, it would however not change the fact that the network of peers is currently defacto not available and hence nobody will be able to sync the official database.

Having that said, everyone is free to set up their own database/network and host their own peers.

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

4 participants