Today I wanted to set up a new node. As usual, I made sure the signed identity files are placed in the right directory, I copied my config.yaml template and filled it with info for the new storage node, and started docker container. But… 2020-10-10T19:48:57.611Z INFO Configuration loa…

Have you tried --log.output stderr ?

Please, use the storagenode setup instead. Because all needed info, include databases will be created only with this command. The storagenode run will not create them to prevent the start from scratch if there is something missed - either config.yaml or databases or folders tree (this useful when y…

It’s quite unusual to use a configuration file as a flag this way. From my sysadmin experience the usual practice is to drop configuration files for a service in the right places, only then install/run the actual service—this is for example what is done on Debian, as all services are already being s…

It’s documented: https://documentation.storj.io/setup/cli/storage-node#storage-node-concepts We do not require to create a config.yaml in advance as you can see. If you follow the documentation - you will succeed with setup. The Linux installer and updater would be available soon.

I don’t see any documentation regarding config.yaml there. The only mention of this file is here: https://documentation.storj.io/resources/faq/redirect-logs And this is why I need config.yaml.

Yes, it’s a tweak after setup. You are right there is no any mention of config.yaml at the setup process. I’ll create a ticket in the documentation project to add a sentence like “your destination folder must be empty for a new node”, since it’s not obvious as turned out.

[image] Alexey: I’ll create a ticket in the documentation project to add a sentence like “your destination folder must be empty for a new node”, since it’s not obvious as turned out. Please make sure that you explicitly mention that not even config.yaml can be there, this will be very helpful…

The usual convention - to install the service then configure. In most cases you even will not have a folder or configs before the service got installed. But you can configure before the installation, if service is allowing to do so. The storagenode container do not allowing to do so. [image] T…

[image] Alexey: The usual convention - to install the service then configure. In most cases you even will not have a folder or configs before the service got installed. Depends on the system, probably. The Debian practice is to drop configuration files where they’re supposed to, then apt inst…

[image] Toyoo: Depends on the system, probably. The Debian practice is to drop configuration files where they’re supposed to, then apt install service . Could you please, show that in the Debian documentation, as a reference? For honestly I didn’t heard such requirement anywhere, unless you b…

This is defined in the Debian Policy, section 9.3.3.1 : The default behaviour is to enable autostarting your package’s daemon. BTW, maybe the best way would be to provide a command-line switch for the log.output setting?

Storj Community Forum (official)

Can't set up config.yaml before a new node starts

Node Operators troubleshooting