Odmin
21
Thanks a lot for quik resolution!
One my node is updated automaticaly via watchtower wothout any issues (node that used for our tests):
[6631368048638566497] storj.io/storj/storagenode/orders.(*Service).cleanArchive
parents: 2906475801789212806
current: 0, highwater: 1, success: 1, errors: 0, panics: 0
success times:
0.00: 20.172396ms
0.10: 20.172396ms
0.25: 20.172396ms
0.50: 20.172396ms
0.75: 20.172396ms
0.90: 20.172396ms
0.95: 20.172396ms
1.00: 20.172396ms
avg: 20.172396ms
ravg: 20.172396ms
failure times:
0.00: 0s
0.10: 0s
0.25: 0s
0.50: 0s
0.75: 0s
0.90: 0s
0.95: 0s
1.00: 0s
avg: 0s
ravg: 0s
Everything is moved smoothly
How does your node update so fast I have 3 nodes and none of them have updated with watch tower yet…
John.A
23
Ill Guess good timing with watchtower👍
Odmin
24
I just lucky, here is the log of watchtower:
2019-12-18T16:26:28.097300234Z time="2019-12-18T16:26:28Z" level=info msg="Found new storjlabs/storagenode:beta image (sha256:af10e412d0dbb8ac097783ffda2e196ea790cd34aacf53c1686eab7ab380a672)"
2019-12-18T16:26:28.097320892Z time="2019-12-18T16:26:28Z" level=debug msg="Pulling storjlabs/watchtower:latest for /watchtower"
2019-12-18T16:26:28.097343642Z time="2019-12-18T16:26:28Z" level=debug msg="No credentials for storjlabs in /config.json"
2019-12-18T16:26:28.097359481Z time="2019-12-18T16:26:28Z" level=debug msg="Got auth value: "
2019-12-18T16:26:28.097395333Z time="2019-12-18T16:26:28Z" level=debug msg="Got image name: storjlabs/watchtower:latest"
2019-12-18T16:26:28.097406841Z time="2019-12-18T16:26:28Z" level=debug msg="No authentication credentials found for storjlabs/watchtower:latest"
2019-12-18T16:26:30.280704390Z time="2019-12-18T16:26:30Z" level=debug msg="No new images found for /watchtower"
2019-12-18T16:26:30.280737424Z time="2019-12-18T16:26:30Z" level=debug msg="This is the watchtower container /watchtower"
2019-12-18T16:26:30.280745800Z time="2019-12-18T16:26:30Z" level=debug msg="No pre-update command supplied. Skipping"
2019-12-18T16:26:30.280752977Z time="2019-12-18T16:26:30Z" level=info msg="Executing pre-update command."
2019-12-18T16:26:30.401567472Z time="2019-12-18T16:26:30Z" level=info msg="Stopping /storagenode (41072aba9c23abb3ed08197c95b73afa5917abdc0ec1247403b0f713607975ae) with SIGTERM"
2019-12-18T16:26:31.435959426Z time="2019-12-18T16:26:31Z" level=debug msg="Removing container 41072aba9c23abb3ed08197c95b73afa5917abdc0ec1247403b0f713607975ae"
2019-12-18T16:26:31.450077253Z time="2019-12-18T16:26:31Z" level=info msg="Creating /storagenode"
2019-12-18T16:26:31.512891147Z time="2019-12-18T16:26:31Z" level=debug msg="Starting container /storagenode (ca0af60590ce1d2213510a92906efff74682a71396d289eb333ae7a738a8085a)"
2019-12-18T16:26:31.906334039Z time="2019-12-18T16:26:31Z" level=info msg="Removing image sha256:06be91d6a7c3712d868aa245f51fcbc2e6b64ca3a4dbc7e1147386dfee0ac9ff"
2019-12-18T16:26:31.919376863Z time="2019-12-18T16:26:31Z" level=debug msg="Scheduled next run: 2019-12-18 22:26:24 +0000 UTC"
Checking is every 6 hours like on our documentation. I like not to force anything.
Wow im impressed, Guess your pretty lucky then
Krey
26
[3503991517435968770] storj.io/storj/storagenode/orders.(*Service).cleanArchive
parents: 3076941709357294410
current: 0, highwater: 1, success: 13, errors: 0, panics: 0
success times:
0.00: 24.660136ms
0.10: 179.961331ms
0.25: 994.2272ms
0.50: 1.553947008s
0.75: 2.168879872s
0.90: 2.621204275s
0.95: 2.736727296s
1.00: 2.826576384s
avg: 1.524255176s
ravg: 1.524255232s
failure times:
0.00: 0s
0.10: 0s
0.25: 0s
0.50: 0s
0.75: 0s
0.90: 0s
0.95: 0s
1.00: 0s
avg: 0s
ravg: 0s
fixed thanks