Docker container restarting after 0.15.3 update

Node Operators troubleshooting
1

Hello,
For the past couple of days my node stopped working immediately after the update.

I searched for 2 days a solution on the forum but no success.
I’ve removed the container, pulled a fresh container, wiped the storage drive, couple of computer reboots, checked for the latest updates, checked my port forwarding, everything that comes to mind.

I even tried selecting a different drive for storage, no luck.

2019-07-18T16:20:14.566Z INFO running on version v0.15.3
2019-07-18T16:20:14.572Z INFO db.migration Latest Version {“version”: 13}
2019-07-18T16:20:14.572Z INFO vouchers Checking vouchers
2019-07-18T16:20:14.574Z INFO piecestore:monitor Remaining Bandwidth {“bytes”: 50000000000000}
2019-07-18T16:20:14.574Z WARN piecestore:monitor Disk space is less than requested. Allocating space {“bytes”: 499988365312}
2019-07-18T16:20:14.574Z ERROR piecestore:monitor Total disk space less than required minimum {“bytes”: 500000000000}
2019-07-18T16:20:14.574Z INFO Node 1me8DeS4MTh5RKkFEx12TyLuuK3P4shN4tZQ61dcuKDBGrm2Ha started
2019-07-18T16:20:14.574Z INFO Public server started on [::]:28967
2019-07-18T16:20:14.574Z INFO Private server started on 127.0.0.1:7778
2019-07-18T16:20:14.574Z ERROR Failed to do periodic version check: Get https://version.alpha.storj.io: context canceled
2019-07-18T16:20:14.575Z INFO vouchers Requesting voucher {“satellite”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2019-07-18T16:20:14.575Z INFO vouchers Requesting voucher {“satellite”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2019-07-18T16:20:14.575Z INFO vouchers Requesting voucher {“satellite”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”}
2019-07-18T16:20:14.575Z INFO vouchers Requesting voucher {“satellite”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2019-07-18T16:20:14.624Z ERROR vouchers Error requesting voucher {“satellite”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “error”: “voucher: unable to connect to the satellite: transport error: no address”, “errorVerbose”: “voucher: unable to connect to the satellite: transport error: no address\n\tstorj.io/storj/storagenode/vouchers.(*Service).request:132\n\tstorj.io/storj/storagenode/vouchers.(*Service).Request:116\n\tstorj.io/storj/storagenode/vouchers.(*Service).RunOnce.func1:103\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2019-07-18T16:20:14.674Z ERROR vouchers Error requesting voucher {“satellite”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “error”: “voucher: unable to connect to the satellite: transport error: no address”, “errorVerbose”: “voucher: unable to connect to the satellite: transport error: no address\n\tstorj.io/storj/storagenode/vouchers.(*Service).request:132\n\tstorj.io/storj/storagenode/vouchers.(*Service).Request:116\n\tstorj.io/storj/storagenode/vouchers.(*Service).RunOnce.func1:103\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2019-07-18T16:20:14.716Z ERROR vouchers Error requesting voucher {“satellite”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “voucher: unable to connect to the satellite: transport error: no address”, “errorVerbose”: “voucher: unable to connect to the satellite: transport error: no address\n\tstorj.io/storj/storagenode/vouchers.(*Service).request:132\n\tstorj.io/storj/storagenode/vouchers.(*Service).Request:116\n\tstorj.io/storj/storagenode/vouchers.(*Service).RunOnce.func1:103\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2019-07-18T16:20:14.765Z ERROR vouchers Error requesting voucher {“satellite”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “error”: “voucher: unable to connect to the satellite: transport error: no address”, “errorVerbose”: “voucher: unable to connect to the satellite: transport error: no address\n\tstorj.io/storj/storagenode/vouchers.(*Service).request:132\n\tstorj.io/storj/storagenode/vouchers.(*Service).Request:116\n\tstorj.io/storj/storagenode/vouchers.(*Service).RunOnce.func1:103\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}

2

Bad Idea! That is one thing you never should do.

But this error shows you the reason. It seams that you allocate ~11MB to less.

1 Like
3

Hi godmaryus,

I see a few problems here. First and foremost, if you wiped the storage drive and the database along with it you could be in trouble with the sats. Even though the network was wiped, that doesn’t mean you can just wipe your node and start fresh. An admin can probably comment further on that.

Second, these lines in your log:

2019-07-18T16:20:14.574Z WARN piecestore:monitor Disk space is less than requested. Allocating space {“bytes”: 499988365312}
2019-07-18T16:20:14.574Z ERROR piecestore:monitor Total disk space less than required minimum {“bytes”: 500000000000}

It means that your node is not sharing the minimum 500 GB. You should increase your allocation to more than 500 GB. I’m not sure if this will solve your problem, but it needs to be fixed first before more troubleshooting can take place.

(edit: removed extra line from log snippet)

1 Like
4

In this case the node actually detects there is less space available in the disk than is allocated to the node. It seems the disk itself simply does not have at least 500GB free. So you may have allocated enough, but that doesn’t matter if there is not enough free space.

5

I understand the problem, what I’m confused is how come up until now this was not a problem? The storagenode worked fine until it got updated to 0.15.3

6

Maybe you had just enough free space until now. Might be some OS files or garbage data that pushed you over the edge. You barely dropped below the threshold by a few MB. So anything small could have pushed you below it. The check has been implemented for a while now, so before now your free space must have been enough.

7

Solved. The issue was the space on the hard-drive that disappeared (i still don’t know how and where).
The storage node is working on la larger drive.
Thank you for the support.

1 Like