Some users are reporting nodes restarting often for seemingly no reason. When turning on debug logging the reason becomes visible. To turn on debug logging change the log level in config.yaml to debug and restart your node: docker restart -t 300 storagenode 2019-07-19T15:18:09.845Z DEBUG Fatal err…

Stop the storagenode docker stop storagenode run the sqlite3 container (replace the /mnt/storagenode to your path to the data): docker run --rm -it -v /mnt/storagenode/storage/info.db:/data/info.db sstc/sqlite3 sqlite3 ./info.db` And execute this SQL script: SELECT datetime(strftime('%Y-%m-%dT%…

The app tries to write data into the which seems to be already there or like the other post maybe here the bandwidth_usage_rollups table is also missing.

I’m seeing an issue similar to the ones reported for v0.15.2 however I’m still seeing the issue with v0.15.3 as well. The container comes up for only around 30 seconds, during which time the dash actually appears pretty normal with the Last Contact time updating. Grand total of the logs produced b…

An extra curiosity, on the first run after a reboot the pattern is slightly different. The node will come up for nearly 5 minutes and report only the following. 2019-07-19T02:54:16.797Z INFO Configuration loaded from: /app/config/config.yaml 2019-07-19T02:54:16.829Z INFO Operator email: REDACTED 2…

I had same issue… what worked for me was to stop and remove all storj containers (including watchtower). Then remove all docker images for storagenode and watchtower and re-download docker images. After that it went back to normal and 0.15.3 start working fine.

@qf3l3k Thanks! @billstanden please, can you try to what @qf3l3k has commented?

Same behaviour after a full docker stop, prune and redownload unfortunately.

Hello @billstanden , Welcome to the forum! Have you removed the container?

Hi Alexey, yes I have. Both an individual deletion and rebuild and a complete docker system prune --all as well. Behaviour remains the same. What’s useful to you for debugging?

Please, edit your config.yaml to enable debug level of the logging: replace the info to debug, save the configuration file and restart the container: docker restart -t 300 storagenode Then search for the FATAL errors: docker logs storagenode 2>&1 | grep -i FATAL For Powershell: docker logs storag…

Cheers Alexey. Full debug log from a single run below. 2019-07-21T02:39:55.288Z INFO Configuration loaded from: /app/config/config.yaml 2019-07-21T02:39:55.289Z DEBUG debug server listening on 127.0.0.1:48372 2019-07-21T02:39:55.320Z INFO Operator email: REDACTED 2019-07-21T02:39:55.320Z INFO Oper…

Storj Community Forum (official)

DEBUG Fatal error: infodb: UNIQUE constraint failed: bandwidth_usage_rollups.interval_start

Node Operators troubleshooting