Changed log level to error on windows and after PC restart, node is will not start

Node Operators troubleshooting
1

Hello,

So Its quite a new node after my last fuckup, but it seems everything was going fine now until i change my log level to ERROR.

I’m getting this:

2024-08-06T15:54:15+02:00 FATAL Unrecoverable error {“error”: “Failed to create storage node peer: listen tcp myip:28969: bind: The requested address is not valid in its context.”, “errorVerbose”: “Failed to create storage node peer: listen tcp myip:28969: bind: The requested address is not valid in its context.\n\tmain.cmdRun:86\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:77\n\tstorj.io/common/process.ExecWithCustomConfig:72\n\tstorj.io/common/process.Exec:62\n\tmain.(*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78”}

(i removed my public ip from the error log i copy pasted.)
My other 2 nodes that are running from a raspberry are still on and running without mistake.

Tried to change back log level to info, maybe it had to do something with it, but it does not help.
The node won’t start anymore.

Any tips?

Thanks,
T.

2

Windows or docker? Either way I don’t think your public ip should be in there, that’s more for the satellite to contact you. Process itself should bind to your local port.

For docker, in config.yaml:

# public address to listen on
server.address: :28967
# the public address of the node, useful for nodes behind NAT
contact.external-address: <public hostname>:28969

And docker parameters:

-p 28969:28967/tcp
-p 28969:28967/udp
-p 14002:14002
-e ADDRESS="<public hostname>:28969"

In my logs on startup:
Public server started on [::]:28967 {"Process": "storagenode"}

1 Like
3

Its Windows, it was working fine until now. I only changed the log level

4

I don’t have my windows node anymore but I’m pretty sure I never put my public ip/dns elsewhere than in the contact.external-address config.yaml field. Same for you?

5

This is the storagenode log not my config file.
I have my domain name in the yaml config, did not touch it, i only touched the log level in the config and after PC restart it does not work anymore. Everything worked fine before.

6

Take a screenshot of the line you changed and paste it here.

7

I understand but changing log level would not cause such an error. And I find it odd that your log shows the public ip (it should not know/care) so reviewing your configuration is likely your best bet.

8

image

9

Change it to

log.level: info

make sure there is no space at the end of info. Keep it in lower case.

10

Yep, i did. did not help. I think it has nothing to do with the log level change. it has something to do with the pc restart and maybe with a Storj update.
Was not restarted for more than a week.

I had a previous node on the same client, with same config and i deleted my identity by accident, that i could not retrieve.
I reinstalled everything, created new identity, new node, got 9tb downloaded already into the node, everything was fine until now.

11

Try reinstalling the node software. Make sure your data and identity files are safe.

12

image
rip

13
2024-08-06T17:01:34+02:00 INFO Anonymized tracing enabled {Process: storagenode}
2024-08-06T17:01:34+02:00 FATAL Unrecoverable error {Process: storagenode, error: open G:\trash\.trash-uses-day-dirs-indicator: The file exists.}
14

Rename this file and try installing again.

1 Like
15

Ah bro, bless your soul, it works again.

2 Likes
16

I believe that you duplicated the parameter and the node is refused to start.
Each parameter should be unique in the config.yaml.

17

I double checked, i did not.

18

Did you use Notepad++ to edit a config file and saved it in UTF8 without BOM?
However, there was an easy check, you might run the node from the PowerShell:

& "C:\Program Files\Storj\Storage Node\storagenode.exe" run --config-dir "C:\Program Files\Storj\Storage Node\\" --log.output=stderr

Perhaps the node would have printed out what the reason was.