Extremely high ingress + massive node fault

[Aka985]

This file do not move?

[pangolin]

This file is not related to database. Dont move it!

[pangolin]

Move only *.db files.

[Aka985]

I moved only DB’s, but now node doesn’t start:

[pangolin]

I dont use quotation marks in config file.

[Aka985]

And now it is this error:

Can it be related what C: is system drive?

After I moved DB’s back node immidiately started

[pangolin]

Maybe it cannot handle empty spaces in directory names?

[Aka985]

тв now this:

2024-06-10T17:29:47Z    INFO    Configuration loaded    {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "healthcheck.details"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.email"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage2.database-dir"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "contact.external-address"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "healthcheck.enabled"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.address"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.private-address"}
2024-06-10T17:29:47Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "console.address"}
2024-06-10T17:29:47Z    INFO    Anonymized tracing enabled      {"Process": "storagenode-updater"}
2024-06-10T17:29:47Z    INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2024-06-10T17:29:47Z    INFO    Running on version      {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.104.5"}
2024-06-10T17:29:47Z    INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2024-06-10T17:29:47Z    INFO    Downloading versions.   {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2024-06-10T17:29:47Z    INFO    Operator email  {"Process": "storagenode", "Address": "7437493@gmail.com"}
2024-06-10T17:29:47Z    INFO    Operator wallet {"Process": "storagenode", "Address": "0xE158e01cDb77F9f220d8359335Fe0b75799829AA"}

[pangolin]

This is normal info message. No errors.

[Aka985]

Wrong log? this one:

Looks I am too stupid for this

[pangolin]

I just realised you are using docker…

So your storagenode cannot access the ssd directory directly. You have to mount it in the docker start command.

[Aka985]

Do you mean like this?
docker run -d --restart unless-stopped --stop-timeout 300 -p 192.168.4.50:28968:28967/tcp -p 192.168.4.50:28968:28967/udp -p 127.0.0.1:14004:14002 -e WALLET=“0xE158e01cDb77F9f220d8359335Fe0b75799829AA” -e EMAIL="7437493@gmail.com" -e ADDRESS=“XX.XXX.149.224:28968” -e STORAGE=“16.1TB” --mount type=bind,source=“F:\Identity\storagenode D1.6”,destination=/app/identity --mount type=bind,source=“F:\StorjD1.6”,destination=/app/config --name storagenodeD1.6 storjlabs/storagenode:latest --storage2.database-dir: C:\Storj_DB\D1.6

[nerdatwork]

@Aka985

Do you mean

How to move DB’s to SSD on Docker

How to move DB’s to SSD on Docker Before you beginning, please make sure that your SSD has good endurance (MLC is preferred), I personally recommend using SSD mirror. look into the official documentation and make sure that you are using –mount type=bind parameter in your docker run string Prepare a folder with mounted SSD outside of <storage-dir> from the official documentation. (it your folder with pieces) Add a new mont string to your docker run string: Now we have: docker run -d --restar…

[Alexey]

you need to mount C:\Storj_DB\D1.6 to the folder inside the container and use the path inside the container for the databases option, i.e.

docker run -d --restart unless-stopped --stop-timeout 300 -p 192.168.4.50:28968:28967/tcp -p 192.168.4.50:28968:28967/udp -p 127.0.0.1:14004:14002 -e WALLET="0xE158e01cDb77F9f220d8359335Fe0b75799829AA" -e EMAIL="7437493@gmail.com" -e ADDRESS="XX.XXX.149.224:28968" -e STORAGE="16.1TB" --mount type=bind,source="F:\Identity\storagenode D1.6",destination=/app/identity --mount type=bind,source="F:\StorjD1.6",destination=/app/config --mount type=bind,source=C:\Storj_DB\D1.6,destination=/app/dbs --name storagenodeD1.6 storjlabs/storagenode:latest --storage2.database-dir: dbs

[AiS1972]

@surfercool

1.5 TB of bandwidth this month already.

Wow! Bro, take it easy! How do you like this, Elon?

[Alexey]

You may add up:

Automatically Backing Up Tesla Sentry Mode and Dashcam videos - Storj Docs