4. Curious about errors

Curious about errors

  • R

    I've noticed, there are some errors logged in the host.log
    Now I'm curious if these are "critical", are these caused by my host/configuration and will these errors affect a hosts revenue.
    I see some entries like:

    • 2017/06/07 11:22:07.080409 errors.go:151: internal error: error with 94.135.226.239:59060: incoming RPCReviseContract failed: RPCRecentRevision failed: challenge failed: could not get 6dd006cc0123ecc907fd27aae382a58b929cb75cd8b890230a3cc7183c143d58 lock: the requested file contract is currently locked

    So, what does it mean "the requested file contract is currently locked"? Should I worry about that?
    Next there are some entries about i/o error, related to the same renter (IP address):

    • 2017/06/07 11:24:09.212198 errors.go:151: connection error: error with 94.135.226.239:51263: incoming RPCReviseContract failed: revision iteration failed: unable to read revision modifications: read tcp 192.168.1.230:9982->94.135.226.239:51263: i/o timeout
    • 2017/06/07 11:39:28.878422 errors.go:151: connection error: error with 94.135.226.239:51153: incoming RPCReviseContract failed: revision iteration failed: unable to read revision modifications: read tcp 192.168.1.230:9982->94.135.226.239:51153: i/o timeout
    • 2017/06/07 11:59:40.238533 errors.go:151: connection error: error with 94.135.226.239:57769: incoming RPCReviseContract failed: revision iteration failed: unable to read revision modifications: read tcp 192.168.1.230:9982->94.135.226.239:57769: i/o timeout

    But there are 3 scary log entries:

    • 2017/06/05 10:46:59.299478 storageobligations.go:574: Missed storage proof. Revenue would have been 348080880970476100209607401.
    • 2017/06/05 22:24:15.872507 storageobligations.go:574: Missed storage proof. Revenue would have been 348080880970476100209607401.
    • 2017/06/08 03:24:58.531682 storageobligations.go:574: Missed storage proof. Revenue would have been 364554760991267499525805151.

    The last (scary) one may be not related to the first mentioned (locked contract and i/o errors), as the timestamp differs significantly, but there are only a couple of errors (a bunch of "renter proposed a file contract with a too-long duration" filtered out) logged between them:

    • 2017/06/07 14:44:58.329112 errors.go:151: connection error: error with 73.61.18.211:23136: incoming RPCReviseContract failed: revision iteration failed: unable to read revision modifications: unexpected EOF
    • 2017/06/08 03:14:07.084576 errors.go:151: connection error: error with 200.104.102.64:48316: incoming RPCReviseContract failed: revision iteration failed: unable to read revision modifications: read tcp 192.168.1.230:9982->200.104.102.64:48316: i/o timeout

    So, the question is-
    should I worry about these errors?

    0
  • R

    @Core-Dev
    I continue to get log entries about Missed storage proofs:

    2017/06/05 10:46:59.299478 storageobligations.go:574: Missed storage proof. Revenue would have been 348080880970476100209607401.
2017/06/05 22:24:15.872507 storageobligations.go:574: Missed storage proof. Revenue would have been 348080880970476100209607401.
2017/06/08 03:24:58.531682 storageobligations.go:574: Missed storage proof. Revenue would have been 364554760991267499525805151.
2017/06/09 23:22:37.939284 storageobligations.go:574: Missed storage proof. Revenue would have been 399881213430902433861608917.
2017/06/09 23:32:55.565822 storageobligations.go:574: Missed storage proof. Revenue would have been 394881213430902433861608917.
2017/06/10 22:03:14.966098 storageobligations.go:574: Missed storage proof. Revenue would have been 404092512616132750637802965.
2017/06/14 03:03:10.586422 storageobligations.go:574: Missed storage proof. Revenue would have been 423607805507032517349221845.
2017/06/17 11:45:28.988035 storageobligations.go:574: Missed storage proof. Revenue would have been 465073289117346613608594413.
2017/06/20 19:01:13.566135 storageobligations.go:574: Missed storage proof. Revenue would have been 483985812552452604013072901.
2017/06/24 05:00:53.947502 storageobligations.go:574: Missed storage proof. Revenue would have been 494570764578434880985125381.
2017/06/27 11:48:48.740624 storageobligations.go:574: Missed storage proof. Revenue would have been 499778847398037624639738373.
2017/06/30 16:26:15.602573 storageobligations.go:574: Missed storage proof. Revenue would have been 510025418578372857287430661.
2017/07/01 21:42:50.174865 storageobligations.go:574: Missed storage proof. Revenue would have been 511015103268553443657142789.

    Do I have to worry about such entries or not?

    0
Log in to reply