Ignatious11

Okay so I've made some progress but now I cannot get into the docker container to authorize the identity because it immediately shuts down ("gracefulexit") after starting. Here's the latest from the log: 2021-10-29T20:04:22.694Z INFO contact:service context cancelled {"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6"} 2021-10-29T20:04:22.694Z ERROR contact:service ping satellite failed {"Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "attempts": 1, "error": "ping satellite: rpc: dial tcp: operation was canceled", "errorVerbose": "ping satellite: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:107\n\tstorj.io/common/rpc.TCPConnector.DialContext:71\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:220\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:110\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:105\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:128\n\tstorj.io/common/rpc.Dialer.dialPool:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL:109\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2. (*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"} 2021-10-29T20:04:22.694Z INFO contact:service context cancelled {"Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB"} 2021-10-29T20:04:22.694Z ERROR gracefulexit:blobscleaner couldn't receive satellite's GE status {"error": "context canceled"} Error: piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory

One I noticed is that I had to use -e SETUP="true" in the initial setup. It wouldn't work without the quotation marks.

Thanks for getting back to me! Good question, I'm not sure if the certs were done 'correctly' as I've had them for a while now. I think I'll start from scratch again and see if that fixes it. If not, I'll post the log on here. Thanks again!

Wondering if you might be able to help me: I've done exactly what you stated here but the initial provisions are not initialized when I use '-e SETUP=true' nor if I try '-e SETUP="true"'.... I can see that no folders are created in the two shares I've created and mounted with the container. If I try to run the container after removing the -e command I get the following: Error: Error starting master database on storagenode: group: --- stat config/storage/blobs: no such file or directory --- stat config/storage/temp: no such file or directory --- stat config/storage/garbage: no such file or directory --- stat config/storage/trash: no such file or directory any ideas?

Hi everyone, this thread has been super helpful but I'm getting stuck somewhere and I can't find any solutions. I ended up following along the YT video posted by geeksheik and after creating the Docker container, it says 'success' but none of the contents of the two folders get altered they do in the video (thus leading to the error posted below). I've tried using -e SETUP="true" as well as -e SETUP=true in the extra parameters line. Here is the error if I try to run the container: Error: Error starting master database on storagenode: group: --- stat config/storage/blobs: no such file or directory --- stat config/storage/temp: no such file or directory --- stat config/storage/garbage: no such file or directory --- stat config/storage/trash: no such file or directory This is the full string I'm using in the extra parameters: "-e SETUP=true --mount type=bind,source="/mnt/user/Storj1/identity/storagenode/",destination=/app/identity --mount type=bind,source="/mnt/user/Storj1/data",destination=/app/config" Any help would be greatly appreciated.

Thanks for getting back to me. One of my VMs (Windows 10x64) was acting a little laggy. Suspecting the CPU, I looked at the CPU pinning settings to realize that several docker containers (Bitnode, Ravenode, Jdownloader, Krusader) were not pinned to any cores. I have 16 logical cores on this server, 8 of which pinned by the Win10x64 VM, so I pinned the containers to an open dual set of cores. Upon clicking 'Apply' the 'Updating' spinning wheel appeared in front of each container. This went on for a couple minutes with no change so I began to watch TV and forgot about it. At least an hour later when I checked back, still the same story. Figuring a error, I hit refresh on the browser page and when it reloaded the containers were no longer listed on the CPU Pinning page. When I clicked over to the Docker tab, they were missing there as well. Hoping for the best, I rebooted the sever but they still appeared to be missing. This is the point at which I wrote the post. Afterwards, I attempted to reinstall the containers using the pre-existing images and appdata (or whatever) but they wouldn't function properly despite having the appear of proper configuration using the previous data/settings. So, I ended up having to reinstall all of them after deleting any previously existing data, images, or settings.

Posting here in 'Docker Engine' as Docker Containers wasn't available. Also total noob here. I'm guessing the solution to this issue will be 'shut down the dockers before changing the CPU pinning.' That said, however, I had changed the pinning in the past without issues, so my concern is that there is something awry that I'm not seeing. Would greatly appreciate another set of eyes on this so I can avoid any further complications. tower-diagnostics-20210910-0923.zip tower-syslog-20210910-1322.zip

Holy heckin' this was helpful. I had it completely backwards. This helped me resolve the exact same issue. Many thanks!