Sqlite3 /Volumes/Storj/StorjV3/storage/satellites.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/reputation.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/pricing.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/piecestore.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/pieceinfo.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/piece_spaced_used.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/piece_expiration.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/orders.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/notifications.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/info.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/heldamount.db "PRAGMA integrity_check " Sqlite3 /Volumes/Storj/StorjV3/storage/bandwidth.db "PRAGMA integrity_check " rw-r-r- 1 shoffman admin 80M Jul 24 14:53 used_serial.db rw-r-r- 1 shoffman admin 300K Jul 24 14:53 storage_usage.db rw-r-r- 1 shoffman admin 32K Jul 24 14:53 satellites.db rw-r-r- 1 shoffman admin 24K Jul 24 14:53 reputation.db
rw-r-r- 1 shoffman admin 24K Jul 24 14:53 pricing.db rw-r-r- 1 shoffman admin 11M piecestore.db
rw-r-r- 1 shoffman admin 110M Jul 24 14:53 pieceinfo.db rw-r-r- 1 shoffman admin 24K Jul 24 14:53 piece_spaced_used.db rw-r-r- 1 shoffman admin 68K Jul 24 14:53 piece_expiration.db rw-r-r- 1 shoffman admin 615M Jul 24 14:53 orders.db rw-r-r- 1 shoffman admin 32K Jul 24 14:53 notifications.db rw-r-r- 1 shoffman admin 16K Jul 24 14:53 info.db rw-r-r- 1 shoffman admin 40K Jul 24 14:53 heldamount.db rw-r-r- 1 shoffman admin 16M Jul 24 14:53 bandwidth.db Some are rather large and I suspect piecestore.db isn’t used anymore based on the timestamp: $ ls -lh *.db : 1.03GB (1.50GB swap on computer used)Īll databases check out OK. : 71.5 MB (1.94GB swap on computer used) : 10.03 GB (11.36GB swap on computer used) start storjnode, dashboard, and tail logs storj dashboard and docker logs -f also runningĨ:47pm CT, checking internal disk already 1.1G usedįilesystem 1K-blocks Used Available Use% Mounted on I also notices that the overlay VM is growing slowly using df in the container, but not sure that is related since a restart shouldn’t change the underlying filesystem contents of the same container instance. Here are some numbers to back things up with a timeline and some data points on memory use. The current workaround is to restart docker twice a day to keep things running.
I was wondering if anybody else is seeing this issue running on a mac? Also, don’t tell me run docker in linux in a vm please. I don’t really want to revert backwards on the docker version of storj/storagenode as I’m sure that hasn’t been tested and would likely hose my configuration. I tried downgrading docker from current (2.3.0.3) to the previous minor line (2.2.0.5), but didn’t help. In trying to troubleshoot this I saw that the memory used by the mac’s mount handler grows quickly over time and once the computer runs out of swap space it kinda freezes up. I’ve been running a storagenode for over a year in this configuration with uptimes for a running container in the weeks range – now I can’t get thru a day. So I hope this doesn’t devolve into a finger pointing match between docker on mac and storj, but over the last couple weeks my computer has been locking up.
0 kommentar(er)
