search

NebulousLabs / Sia

Blockchain-based marketplace for file storage. Project has moved to GitLab: https://gitlab.com/NebulousLabs/Sia
https://sia.tech
MIT License
2.71k stars 440 forks source link

Missed storage proof #1862

Open mtlynch opened 7 years ago

mtlynch commented 7 years ago

I'm seeing a lot of entries in my host.log saying "Missed storage proof. Revenue would have been...":

$ grep proof host.log
2017/04/23 10:23:20.374783 storageobligations.go:575: Missed storage proof. Revenue would have been 28041465401979693369917440.
2017/04/25 06:19:28.893826 storageobligations.go:575: Missed storage proof. Revenue would have been 42044787803384516685332480.
2017/04/29 03:47:09.905632 storageobligations.go:575: Missed storage proof. Revenue would have been 64044788828658827693916160.
2017/05/02 17:08:29.988152 storageobligations.go:575: Missed storage proof. Revenue would have been 93044789341295983198208000.
2017/05/03 19:04:56.117655 storageobligations.go:575: Missed storage proof. Revenue would have been 94044789341295983198208000.
2017/05/05 09:20:59.541486 storageobligations.go:575: Missed storage proof. Revenue would have been 108044789341295983198208000.
2017/05/05 09:20:59.563966 storageobligations.go:575: Missed storage proof. Revenue would have been 107044789341295983198208000.
2017/05/05 18:44:30.087300 storageobligations.go:575: Missed storage proof. Revenue would have been 107044789341295983198208000.
2017/05/07 00:08:43.077733 storageobligations.go:575: Missed storage proof. Revenue would have been 119044789341295983198208000.
2017/05/07 11:17:56.318427 storageobligations.go:575: Missed storage proof. Revenue would have been 120044789341295983198208000.
2017/05/08 01:48:35.603738 storageobligations.go:575: Missed storage proof. Revenue would have been 122044789341295983198208000.
2017/05/08 01:52:16.685029 storageobligations.go:575: Missed storage proof. Revenue would have been 121044789341295983198208000.
2017/05/08 01:52:16.799666 storageobligations.go:575: Missed storage proof. Revenue would have been 120044789341295983198208000.
2017/05/08 13:04:28.447039 storageobligations.go:575: Missed storage proof. Revenue would have been 120044789341295983198208000.
2017/05/08 13:04:28.658554 storageobligations.go:575: Missed storage proof. Revenue would have been 119044789341295983198208000.
2017/05/10 06:31:03.691053 storageobligations.go:575: Missed storage proof. Revenue would have been 125044789341295983198208000.
2017/05/11 02:22:52.867200 storageobligations.go:575: Missed storage proof. Revenue would have been 125044789341295983198208000.
2017/05/11 07:16:21.213163 storageobligations.go:575: Missed storage proof. Revenue would have been 126044789341295983198208000.
2017/05/12 08:47:10.911169 storageobligations.go:575: Missed storage proof. Revenue would have been 127044789341295983198208000.
2017/05/14 03:47:27.618005 storageobligations.go:575: Missed storage proof. Revenue would have been 131044789341295983198208000.
2017/05/15 01:51:59.006246 storageobligations.go:575: Missed storage proof. Revenue would have been 131044789341295983198208000.
2017/05/16 15:41:49.110522 storageobligations.go:575: Missed storage proof. Revenue would have been 133044789341295983198208000.
2017/05/17 07:58:57.626637 storageobligations.go:575: Missed storage proof. Revenue would have been 134044789341295983198208000.
2017/05/17 13:38:53.312861 storageobligations.go:575: Missed storage proof. Revenue would have been 134044789341295983198208000.
2017/05/19 10:00:17.487060 storageobligations.go:575: Missed storage proof. Revenue would have been 134044789341295983198208000.
2017/05/19 13:25:35.477974 storageobligations.go:575: Missed storage proof. Revenue would have been 133044789341295983198208000.
2017/05/20 17:15:46.275097 storageobligations.go:575: Missed storage proof. Revenue would have been 133044789341295983198208000.
2017/05/21 23:26:35.688118 storageobligations.go:575: Missed storage proof. Revenue would have been 133044789341295983198208000.
2017/05/23 04:11:27.521606 storageobligations.go:575: Missed storage proof. Revenue would have been 134044789341295983198208000.
2017/05/23 21:45:02.719684 storageobligations.go:574: Missed storage proof. Revenue would have been 135044789341295983198208000.
2017/05/24 09:54:34.145588 storageobligations.go:574: Missed storage proof. Revenue would have been 134044789341295983198208000.
2017/05/26 23:57:19.775492 storageobligations.go:574: Missed storage proof. Revenue would have been 141044789341295983198208000.
2017/05/27 18:25:56.325223 storageobligations.go:574: Missed storage proof. Revenue would have been 142044789341295983198208000.
2017/06/01 01:50:55.608516 storageobligations.go:574: Missed storage proof. Revenue would have been 145044789341295983198208000.

My host is always online: http://siahub.info/host/1424

DavidVorick commented 7 years ago

Yeah, seen another log like this. Couple of things stand out to me:

  1. I know that our storage proof checking system has holes in it. Meaning, hosts don't always realize that they have a contract which is expiring and needs a storage proof.

  2. The 'Revenue would have been' value is strictly increasing. That's pretty confusing to me, because from what I remember it's a local value, not a global value. This suggests to me that it's probably just one storage proof that's reporting itself as failed repeatedly. Or the wrong value is being logged, which is also possible.

  3. These missed proofs are days apart.

Just to double check - are you running the most recent release? v1.2.2

mtlynch commented 7 years ago

Just to double check - are you running the most recent release? v1.2.2

Yep, you can verify in the SiaHub host information.

tlightsky commented 7 years ago

this is mine,some success,some missed

$ grep proof host.log
2017/04/17 03:09:20.068999 storageobligations.go:563: Succesfully submitted a storage proof. Revenue is 10401091801962057173219503097.
2017/04/19 00:54:59.418882 storageobligations.go:579: Missed storage proof. Revenue would have been 10435882736329848612695676832.
2017/04/21 09:14:56.253826 storageobligations.go:579: Missed storage proof. Revenue would have been 10521597386517393471439142327.
2017/04/21 20:08:32.804541 storageobligations.go:563: Succesfully submitted a storage proof. Revenue is 10525255592755428494527541064.
2017/04/26 03:32:14.707195 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 10573228513033856747362007079.
2017/04/27 17:15:47.074275 storageobligations.go:575: Missed storage proof. Revenue would have been 10595124635771406090056322327.
2017/04/27 17:27:55.555233 storageobligations.go:575: Missed storage proof. Revenue would have been 10575124635771406090056322327.
2017/04/27 17:53:59.725829 storageobligations.go:575: Missed storage proof. Revenue would have been 10555124635771406090056322327.
2017/04/29 17:22:03.421300 storageobligations.go:575: Missed storage proof. Revenue would have been 10667014763045382558680363822.
2017/05/04 14:43:39.446329 storageobligations.go:575: Missed storage proof. Revenue would have been 10998009947019990800345994075.
2017/05/06 06:33:07.063843 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11083434211333034151685398319.
2017/05/06 06:33:07.806370 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11063424544860415487143834504.
2017/05/08 18:55:50.395985 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11152775633353105351246541127.
2017/05/09 09:14:40.853369 storageobligations.go:575: Missed storage proof. Revenue would have been 11137127115239472807181742407.
2017/05/09 13:50:27.939429 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11117253822056420692215918919.
2017/05/09 13:50:28.542954 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11097252354050020693155443015.
2017/05/11 06:29:03.060308 storageobligations.go:575: Missed storage proof. Revenue would have been 11160236880577919676592091463.
2017/05/11 20:03:07.522064 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11181145069572439873515359841.
2017/05/17 02:16:36.908898 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11438027764284341563344249373.
2017/05/17 12:07:18.670573 storageobligations.go:575: Missed storage proof. Revenue would have been 11480078638664170497182774265.
2017/05/19 08:17:24.126228 storageobligations.go:575: Missed storage proof. Revenue would have been 11749915754255153519725879267.
2017/05/20 06:16:22.480309 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11790780385790996529794507100.
2017/05/21 22:11:10.800862 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11900709230247368468547204154.
2017/05/23 01:49:43.021553 storageobligations.go:575: Missed storage proof. Revenue would have been 11867091682840826876192846906.
2017/05/23 13:11:21.138714 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 11847391209157768917234213209.
2017/05/25 06:24:37.429410 storageobligations.go:574: Missed storage proof. Revenue would have been 11868464129997247446758810707.
2017/05/26 12:43:32.069614 storageobligations.go:574: Missed storage proof. Revenue would have been 11868470524563220739435357267.
2017/05/27 17:34:29.113061 storageobligations.go:574: Missed storage proof. Revenue would have been 11872253524122326829180484133.
2017/05/29 13:04:47.324755 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:04:53.255954 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:09.966975 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:16.028296 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:22.895035 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:27.148014 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:30.703516 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:36.859533 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:48.554555 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: transaction spends a nonexisting siacoin output
2017/05/29 13:05:51.484340 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:56.461574 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:05:58.127768 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:06:08.549824 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:06:14.487367 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: transaction spends a nonexisting siacoin output
2017/05/29 13:06:18.302823 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:06:56.329135 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:06:58.516191 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:07:01.510560 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:07:10.126528 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set has prereqs, but is still invalid: cannot fetch storage proof segment for unknown file contract
2017/05/29 13:07:14.183745 storageobligations.go:821: Host unable to submit storage proof transaction to transaction pool: consensus conflict: provided transaction set is standalone and invalid: cannot fetch storage proof segment for unknown file contract
2017/05/30 04:00:43.591123 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 11895348400846644943091759653.
2017/05/31 12:59:08.883423 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 11869112236356220731629861413.
2017/06/02 15:58:45.249212 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 11849075376637905955964411147.
2017/06/02 19:06:13.441169 storageobligations.go:574: Missed storage proof. Revenue would have been 11814549102231141188124892427.
2017/06/02 19:06:49.238480 storageobligations.go:574: Missed storage proof. Revenue would have been 11794549102231141188124892427.
2017/06/02 19:07:41.839568 storageobligations.go:574: Missed storage proof. Revenue would have been 11774549102231141188124892427.
2017/06/03 05:13:02.961557 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 11754549102231141188124892427.
2017/06/03 20:59:55.241784 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 11773733055726370945522031883.
2017/06/04 07:12:03.986694 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 11752881191030525869699194123.
lasat commented 7 years ago
  1. The 'Revenue would have been' value is strictly increasing. That's pretty confusing to me, because from what I remember it's a local value, not a global value. This suggests to me that it's probably just one storage proof that's reporting itself as failed repeatedly. Or the wrong value is being logged, which is also possible.

That's seems not be true: 

2017/05/23 04:11:27.521606 storageobligations.go:575: Missed storage proof. Revenue would have been 134044789341295983198208000.
2017/05/23 21:45:02.719684 storageobligations.go:574: Missed storage proof. Revenue would have been 135044789341295983198208000.
2017/05/24 09:54:34.145588 storageobligations.go:574: Missed storage proof. Revenue would have been 134044789341295983198208000.

Here are my log entries (containing decreasing value too):

2017/05/15 22:30:38.660980 storageobligations.go:559: Successfully submitted a storage proof. Revenue is 1727340033310836853212993328.
2017/05/21 18:48:33.257082 storageobligations.go:575: Missed storage proof. Revenue would have been 2555969007832692426629392182.
2017/05/24 08:38:12.422082 storageobligations.go:574: Missed storage proof. Revenue would have been 2702973290298557400474662520.
2017/05/26 22:52:51.611031 storageobligations.go:574: Missed storage proof. Revenue would have been 2826799145226746378661869176.
2017/06/05 00:15:59.827904 storageobligations.go:574: Missed storage proof. Revenue would have been 3554338145496502757492998866.
2017/06/05 10:30:55.675324 storageobligations.go:574: Missed storage proof. Revenue would have been 3589646203135911806198039250.
2017/06/06 15:10:20.117349 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 3605403020088764025807258322.
2017/06/06 18:08:10.529596 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 3605828446935670945455751890.
2017/06/08 03:18:53.519992 storageobligations.go:574: Missed storage proof. Revenue would have been 3700198148087880122168984274.
2017/06/09 05:57:43.811886 storageobligations.go:574: Missed storage proof. Revenue would have been 3813896776243294108500838376.
2017/06/09 23:17:09.140405 storageobligations.go:574: Missed storage proof. Revenue would have been 3937215622034737192390319168.
2017/06/10 04:54:30.743778 storageobligations.go:574: Missed storage proof. Revenue would have been 3928057914882234055211048000.
2017/06/10 21:53:07.797146 storageobligations.go:574: Missed storage proof. Revenue would have been 4014252780185473570654346862.
2017/06/14 02:43:02.619541 storageobligations.go:574: Missed storage proof. Revenue would have been 4233493941406114720652701460.
2017/06/14 15:50:07.388652 storageobligations.go:574: Missed storage proof. Revenue would have been 4316296152022940285887820098.
2017/06/15 21:01:57.842055 storageobligations.go:574: Missed storage proof. Revenue would have been 4401750432586126025285678680.
2017/06/17 02:53:56.742200 storageobligations.go:574: Missed storage proof. Revenue would have been 4493843329640800980348169430.
2017/06/17 11:08:26.308120 storageobligations.go:574: Missed storage proof. Revenue would have been 4509905223381262377473535190.
2017/06/20 18:35:38.175141 storageobligations.go:574: Missed storage proof. Revenue would have been 4683196814839690494405256020.
2017/06/21 01:08:09.848032 storageobligations.go:574: Missed storage proof. Revenue would have been 4700224740046338345813680980.
2017/06/24 18:05:47.163949 storageobligations.go:574: Missed storage proof. Revenue would have been 4798717574913619625435737472.
2017/06/24 18:08:20.794466 storageobligations.go:574: Missed storage proof. Revenue would have been 4793717574913619625435737472.
2017/06/27 11:29:24.340266 storageobligations.go:574: Missed storage proof. Revenue would have been 4793329197781898570166972334.
2017/06/28 13:27:44.706610 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 4791027303750081546505433750.
2017/07/03 22:30:14.827169 storageobligations.go:574: Missed storage proof. Revenue would have been 4837859295899613782079729194.
2017/07/06 06:26:11.687664 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 4820163829314094007062916650.
2017/07/06 11:01:47.324049 storageobligations.go:574: Missed storage proof. Revenue would have been 4800000318013543935176371754.
2017/07/06 23:21:45.627312 storageobligations.go:574: Missed storage proof. Revenue would have been 4795152497799877789864980010.
2017/07/07 23:34:32.162658 storageobligations.go:574: Missed storage proof. Revenue would have been 4785419134992697729967499524.
makistsantekidis commented 7 years ago

Similar problem here as well

2017/07/27 23:21:36.181402 storageobligations.go:574: Missed storage proof. Revenue would have been 605911075360702508402141670042.
2017/07/28 13:03:15.555232 storageobligations.go:851: file contract complete, id b6b7b3d321b7346f147878dcb13c27d583cf756fc7d309aebfaf68443ec04b1c
2017/07/28 13:03:15.874165 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 605841075360702508402141670042.
2017/07/31 07:58:21.595337 storageobligations.go:851: file contract complete, id 9e49bf1ad0583e8005f666504f578d8edd155d7e1bd8ca99a751e18d80055545
2017/07/31 07:58:21.790832 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 605739866930456393402000976538.
2017/08/02 21:54:10.610267 storageobligations.go:574: Missed storage proof. Revenue would have been 605639846910033661591617120922.
2017/08/03 08:11:44.784356 storageobligations.go:851: file contract complete, id e172b8caa721ccdccaa45ccdc25e6bafd7bb59521b508255aa207092bfa0607c
2017/08/03 08:11:45.117266 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 605619846910033661591617120922.
2017/08/05 08:32:51.966890 storageobligations.go:735: Error submitting transaction to transaction pool consensus conflict: provided transaction set has prereqs, but is still invalid: transaction has a file contract with an outdated revision number
2017/08/06 04:34:30.614584 storageobligations.go:851: file contract complete, id 18f16ac2b214c02945a585f6c789aa76abef8a441efab80292ae123dd538f307
2017/08/06 04:34:30.836922 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 605519675531416901930872562882.
2017/08/06 11:04:44.630046 storageobligations.go:851: file contract complete, id c843b3a83d017098eb28d79e8579dad86fcaab9de504046fc6bf2ef93e75e3b6
2017/08/06 11:04:44.876427 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 605419477408807124279893255362.
2017/08/06 12:55:10.461121 storageobligations.go:574: Missed storage proof. Revenue would have been 605318872503371533555062629570.
2017/08/06 13:48:30.280627 storageobligations.go:851: file contract complete, id 7672f25c3be28780fb2d7fc2c9dc1dd3e41c5e256e963515a81fccc0b6a9d405
2017/08/06 13:48:30.326674 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 605218872503371533555062629570.
2017/08/08 01:01:10.724122 storageobligations.go:851: file contract complete, id 23060c45438057b44d0d74b290ed1798811941046bb12dcbcd587eeecc9ea81c
2017/08/08 01:01:11.389582 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 605118374177724932418581914818.
2017/08/08 23:10:31.992092 storageobligations.go:851: file contract complete, id e9a1c60e6b770c95c74ab918b8076144019c73b267917ba10ad1fbd3853998cb
2017/08/08 23:10:32.256857 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 604983721187982874383407905538.
2017/08/10 05:08:43.996051 storageobligations.go:574: Missed storage proof. Revenue would have been 604874239259497333664325529310.
2017/08/10 05:10:58.161691 storageobligations.go:574: Missed storage proof. Revenue would have been 604774239259497333664325529310.
2017/08/10 11:52:24.326687 storageobligations.go:574: Missed storage proof. Revenue would have been 604674239259497333664325529310.
2017/08/10 13:42:56.878662 storageobligations.go:851: file contract complete, id 0aff966b2b15eb0dba0dba577fda345f66caa764ca9df6966852c06457021bed
2017/08/10 13:42:57.180436 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 604574239259497333664325529310.
2017/08/10 20:56:01.471591 storageobligations.go:851: file contract complete, id b9a47bf67387667359115071e7b10a28c6e191f5df66f2852d1a5786b5f42890
2017/08/10 20:56:02.255619 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 604448715749912604354426400478.
2017/08/11 16:03:58.117987 storageobligations.go:574: Missed storage proof. Revenue would have been 604326858049363283252055574787.
2017/08/11 18:48:50.807882 storageobligations.go:574: Missed storage proof. Revenue would have been 604226858049363283252055574787.
2017/08/11 22:01:31.851669 storageobligations.go:851: file contract complete, id 66333533c1a624c900a5ce083484eb59b1a4a8b2435353f453629073c93f1c9a
2017/08/11 22:01:32.179395 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 604126858049363283252055574787.
2017/08/12 09:21:00.525606 storageobligations.go:574: Missed storage proof. Revenue would have been 604025179455083968912720847662.
2017/08/12 14:40:31.640647 storageobligations.go:574: Missed storage proof. Revenue would have been 603995179455083968912720847662.
2017/08/12 19:36:23.689855 storageobligations.go:851: file contract complete, id 99b44a4e4a4ee803b6ef7c2cfccd23210c3fe5921ccc6e67be12dfa886c1097b
2017/08/12 19:36:23.822558 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 603965179455083968912720847662.
2017/08/13 00:31:52.319759 storageobligations.go:851: file contract complete, id 7a45a4d27630bc4890c2b7fed76934aa621f9223ed733458627c5f5b7f7d3c2a
2017/08/13 00:31:52.538739 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 603935172471130902250523910958.
2017/08/13 01:13:57.977491 storageobligations.go:851: file contract complete, id 7b4a377e91d10c52f35d0c8fafdf1685e1dfa74209550e29896c22398aa18453
2017/08/13 01:13:58.266988 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 603904742840804953511210181422.
2017/08/13 01:28:36.696353 storageobligations.go:574: Missed storage proof. Revenue would have been 603871702083029789465615983406.
2017/08/13 10:55:44.602642 storageobligations.go:851: file contract complete, id 211eb37fb30d62714800d067b0c5df753f525c9332a14d9c947422633042cb99
2017/08/13 10:55:44.847211 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 603841702083029789465615983406.

Version 

$ ./siac version
Sia Client v1.3.0
Sia Daemon v1.3.0
MaxMaximus commented 6 years ago

I have seen same error in last official release (1.3.0). Host continuously lose some of it's contracts due to missed storage proofs while it running nonstop @ 24/7, available(reachable) from internet on default port and wallet kept unlocked. Here example from host.log (i have also checked other logs but did not find any other errors at day when host missed storage proofs). Here is an example of log:

...........................
2017/10/08 19:33:34.833321 storageobligations.go:851: file contract complete, id 5a7c861c645905c6acba525630573cb0080e99c3d697ed844d45591b418f42cd
2017/10/08 19:33:35.142339 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 16033884056015692848170634.
2017/10/09 16:35:36.423782 storageobligations.go:851: file contract complete, id 10eb12f01aa3a62f567673847a7eb6bedf8dcabcb11ef6944d237fe2cce7b692
2017/10/09 16:35:37.058819 storageobligations.go:558: Successfully submitted a storage proof. Revenue is 15024599416522057141190656.
2017/10/11 14:47:22.414355 storageobligations.go:574: Missed storage proof. Revenue would have been 14522069707503999230410752.
2017/10/11 20:04:43.601020 storageobligations.go:574: Missed storage proof. Revenue would have been 14022069707503999230410752.
2017/10/11 20:30:16.916762 storageobligations.go:574: Missed storage proof. Revenue would have been 13522069707503999230410752.
.............................

And it is not just an logging bug - host actually is loosing contracts and corresponding locked collateral coins. I have checked this. So it is a one of the critical issues.

I do not know reason for such errors. But my best guess: it can happens to contracts without actual data stored in it. Eg: renter never uploaded data to contract or deleted all data before contract expire. And host can not create valid storage prof because it can not find any piece of stored data related to such contract.