Ok, so now i think were getting a real error, after changing to the ip address
Error: Error creating revocation database: revocation database: boltdb: open config/revocations.db: permission denied
storj.io/storj/storage/boltdb.New:44
storj.io/storj/private/revocation.openDBBolt:52
storj.io/storj/private/revocation.OpenDB:35
storj.io/storj/private/revocation.OpenDBFromCfg:23
main.cmdRun:202
storj.io/private/process.cleanup.func1.4:377
storj.io/private/process.cleanup.func1:395
github.com/spf13/cobra.(*Command).execute:852
github.com/spf13/cobra.(*Command).ExecuteC:960
github.com/spf13/cobra.(*Command).Execute:897
storj.io/private/process.ExecWithCustomConfigAndLogger:92
main.main:478
runtime.main:250
2023-03-14 08:04:12,837 INFO exited: storagenode (exit status 1; not expected)
2023-03-14 08:04:13,839 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2023-03-14 08:04:14,842 WARN received SIGQUIT indicating exit request
2023-03-14 08:04:14,845 INFO waiting for processes-exit-eventlistener, storagenode-updater to die
2023-03-14T08:04:14.842Z INFO Got a signal from the OS: "terminated" {"Process": "storagenode-updater"}
2023-03-14T08:04:14.843Z ERROR Error retrieving version info. {"Process": "storagenode-updater", "error": "version checker client: Get \"https://version.storj.io\": context canceled", "errorVerbose": "version checker client: Get \"https://version.storj.io\": context canceled\n\tstorj.io/storj/private/version/checker.(*Client).All:68\n\tmain.loopFunc:21\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tmain.cmdRun:136\n\tstorj.io/private/process.cleanup.func1.4:377\n\tstorj.io/private/process.cleanup.func1:395\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:92\n\tmain.main:20\n\truntime.main:250"}
2023-03-14 08:04:14,846 INFO stopped: storagenode-updater (exit status 0)
2023-03-14 08:04:14,847 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
Okay, so i knoiw you guys want to keep focusing on my network being the problem.
So i just did an apt-get update && apt-get upgrade, on the vm that storjnode is running on, and it updated, no problem.
acking python3-apt (2.0.1ubuntu0.20.04.1) over (2.0.1) ...
Preparing to unpack .../ubuntu-release-upgrader-core_1%3a20.04.41_all.deb ...
Unpacking ubuntu-release-upgrader-core (1:20.04.41) over (1:20.04.40) ...
Preparing to unpack .../python3-distupgrade_1%3a20.04.41_all.deb ...
Unpacking python3-distupgrade (1:20.04.41) over (1:20.04.40) ...
Setting up motd-news-config (11ubuntu5.7) ...
Setting up python-apt-common (2.0.1ubuntu0.20.04.1) ...
Setting up python3-apt (2.0.1ubuntu0.20.04.1) ...
Setting up python3-distupgrade (1:20.04.41) ...
Setting up ubuntu-release-upgrader-core (1:20.04.41) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.4git20200323-0ubuntu6.2) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for install-info (6.7.0.dfsg.2-5) ...
Processing triggers for initramfs-tools (0.136ubuntu6.7) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-144-generic
[storjnode]:</data/>
So iām pretty sure thereās something wrong inside stroragenode.
You need to change permissions in your data location to your user and group,
sudo chown $(id -u):$(id -g) -R /data
still suggests that it have problems with DNS resolution and may be there some firewall or iptables issues related to the docker installation - the outgoing requests are blocked for some reason.
Yes Alexey i have changed permiossions, somehow i had a mix of my ownership and root, smh
As i said before i have no firewall currently running running and also did not setup any iptables or anything, unless it got installed by default, which would have been months and months go, when all was still working.
So whatās the best easiest way to reset this system ? start from fresh ?
It just seems like were chasing each other around the tree.
You may try to reinstall docker, may be it could fix issues with iptables.
But more likely some OS update changed some defaults.
For example CentOS is often unexpected blocking something, see
Nope, doesnāt look like it, other than with nslookup
storjnode (172.17.0.1) 2023-03-16T00:29:55-0500
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. (no route to host)
Then perhaps itās better to remove them.
After that you likely will need to stop and remove the container and run it back using all your parameters.
Regarding the firewall, well it could be enabled by default, you may check:
are you running baremetal or in a hypervisorā¦
i had one case where my hypervisor dns was wrong which cut the internet access for most of my vmās.
happened because i was changing between ispās and thus had two ispās for a couple of months while everything was being reconfigured, so it ofc worked while both was active but then as the old one was disconnected, i started seeing issues, took me a bit to realize it was the hypervisor dns that make every container not work on that server.
come to think about it, it might only have been the containers that was affected, but still figured i would mention it, just in case.
|