Percentage of uptime about go-btfs HOT 24 CLOSED

In the last two days a got a lailure message.
On 2020-08-14 the same failure for three times and once on 2020-08-15.

BTFS is up-to-date.
2020-08-14T09:41:18.904+0200 ERROR upload upload/init.go:303 failed to download shard QmTzZXfBitXfFkQBR67JJztMUrxgR21v1dZ7PQUmZncgXL from file QmVEJsBwYoH6uYEScsgssXa4AkmsgwRJmcwB2TRUv3gL9N with contract id f322bdae-67b9-4057-8ba4-7ccd5ae6e99d,57ac0705-c41b-463b-842d-fe112447ad92: [failed to get block for QmdJRuF8j89QmFmZX2o1qryEqcidjk1wjykckj3qaSaAc6: context deadline exceeded]
2020-08-14T10:12:49.921+0200 ERROR upload upload/init.go:303 failed to download shard QmRuUKxi6DHLvVSxsehcrwAQ5o1UZK9A4XGredGeZ1AKqY from file QmYNBddrjKzADNhWFbJazBSsUTH14f4r5kk8YSCFat1xHs with contract id c2ea41d8-1343-446c-86f8-f410a668a11e,dfbecf7f-5241-40e2-84e4-bae434c319f1: [failed to get block for QmVYab9HjcGj6z58E3dmNvFE8mFpx6ZmCdEJj8Furiwc4w: context deadline exceeded]
2020-08-14T13:42:30.599+0200 ERROR upload upload/init.go:303 failed to download shard QmYM4ohkRCeFEbW6uA5VckMJXnN4dBbzpoQr9MHuigQSBm from file QmcCK6eVdwTsX5UuKcoykAqSNRxgU5fLhCwtFqmUHiCscB with contract id 3900f3ce-152d-40c5-93c8-c7fc50fd46cd,4d325c26-a3eb-4167-92bd-d6ccbcb8c2c6: [failed to get block for QmP67x99qUnmoWtX3Nd7x8WP2MGGcG9y8aaoF49xuN8n7w: context deadline exceeded]
BTFS is up-to-date.
2020-08-15T13:55:17.828+0200 ERROR upload upload/init.go:303 failed to download shard QmcMnjzoXhgiSLxDxYQPDYASQoKWK41Dn1eSULAVJfJkM8 from file QmZZmthBtur6QxPkSvdSNGWyhy2nUMq6rUcNNwuNWUDgvz with contract id 0de93bb7-ecc3-4bc1-aa94-06341be3b426,735457dd-ebb3-4d56-aa15-2eb62701579a: [failed to get block for QmQduhe5a9m5bjDWVqCKJD7o3NthJHssqDAU1uisEkJPsk: context deadline exceeded]
BTFS is up-to-date.

I get this failure constantly. Like 30 - 40 times a day. I understand it may have been a contract that was removed while it was syncing, but that seems super excessive.

from go-btfs.

@Hgaesd65 Could you post the output of btfs id and also a screenshot of seeing this payment date? Thanks.

from go-btfs.

Are there any sporadic failures in your btfs daemon logs?

from go-btfs.

I couldn'd find any failures.

from go-btfs.

I’m still at 95%.

from go-btfs.

i have same prob too.

I have made my NODE live stream at DLIVE TOO.

https://dlive.tv/Pavan_santani

It is 24x7 online the node & stream.

But score & percentage uptime remains same ..

from go-btfs.

I am also STUCK WITH SAME SCORE SINCE LAST POST OF MINE.

NODE ID: 16Uiu2HAmAzcZoULDd7Q38FHPzA46VxsiaRm1psrBvoSV1RkUygLW

U GUYZ CAN CHECK URSELF..

I AM BEING ONLINE 24X7 & AND STREAMING TOO.. ON DLIVE

https://dlive.tv/Pavan_santani

from go-btfs.

In the last two days a got a lailure message.
On 2020-08-14 the same failure for three times and once on 2020-08-15.

BTFS is up-to-date.
2020-08-14T09:41:18.904+0200 ERROR upload upload/init.go:303 failed to download shard QmTzZXfBitXfFkQBR67JJztMUrxgR21v1dZ7PQUmZncgXL from file QmVEJsBwYoH6uYEScsgssXa4AkmsgwRJmcwB2TRUv3gL9N with contract id f322bdae-67b9-4057-8ba4-7ccd5ae6e99d,57ac0705-c41b-463b-842d-fe112447ad92: [failed to get block for QmdJRuF8j89QmFmZX2o1qryEqcidjk1wjykckj3qaSaAc6: context deadline exceeded]
2020-08-14T10:12:49.921+0200 ERROR upload upload/init.go:303 failed to download shard QmRuUKxi6DHLvVSxsehcrwAQ5o1UZK9A4XGredGeZ1AKqY from file QmYNBddrjKzADNhWFbJazBSsUTH14f4r5kk8YSCFat1xHs with contract id c2ea41d8-1343-446c-86f8-f410a668a11e,dfbecf7f-5241-40e2-84e4-bae434c319f1: [failed to get block for QmVYab9HjcGj6z58E3dmNvFE8mFpx6ZmCdEJj8Furiwc4w: context deadline exceeded]
2020-08-14T13:42:30.599+0200 ERROR upload upload/init.go:303 failed to download shard QmYM4ohkRCeFEbW6uA5VckMJXnN4dBbzpoQr9MHuigQSBm from file QmcCK6eVdwTsX5UuKcoykAqSNRxgU5fLhCwtFqmUHiCscB with contract id 3900f3ce-152d-40c5-93c8-c7fc50fd46cd,4d325c26-a3eb-4167-92bd-d6ccbcb8c2c6: [failed to get block for QmP67x99qUnmoWtX3Nd7x8WP2MGGcG9y8aaoF49xuN8n7w: context deadline exceeded]
BTFS is up-to-date.
2020-08-15T13:55:17.828+0200 ERROR upload upload/init.go:303 failed to download shard QmcMnjzoXhgiSLxDxYQPDYASQoKWK41Dn1eSULAVJfJkM8 from file QmZZmthBtur6QxPkSvdSNGWyhy2nUMq6rUcNNwuNWUDgvz with contract id 0de93bb7-ecc3-4bc1-aa94-06341be3b426,735457dd-ebb3-4d56-aa15-2eb62701579a: [failed to get block for QmQduhe5a9m5bjDWVqCKJD7o3NthJHssqDAU1uisEkJPsk: context deadline exceeded]
BTFS is up-to-date.

from go-btfs.

OK my problem of UPTIME & SCORE not changing is kinda solved...

but sometimes is go back to same old score for no reason & comes back up after few hrs.

i think it requires more time on some system to get the score updated..

in comparison to the server's

from go-btfs.

Feel free to send your host node id and any daemon logs you find relevant to [email protected], we can take a closer look at why your uptime isn't increasing.

from go-btfs.

HOST NODE ID: 16Uiu2HAm3VLV7C5Z21ZRuWEyZgJH4V5iG2z1z79jjL3Y6uRgz3ZS

2020-08-19T02:02:03.744+0200 ERROR spin spin/analytics.go:209 failed to send data to status server: rpc error: code = Unknown desc = FATAL #53300 remaining connection slots are reserved for non-replication superuser and rds_superuser connections
2020-08-19T02:12:03.236+0200 ERROR spin spin/hosts.go:63 Failed to sync HOST contracts: payout status batch returned wrong length of contracts, need 271, got 100
2020-08-19T03:12:03.689+0200 ERROR spin spin/hosts.go:63 Failed to sync HOST contracts: payout status batch returned wrong length of contracts, need 271, got 100
2020-08-19T04:12:03.623+0200 ERROR spin spin/hosts.go:63 Failed to sync HOST contracts: payout status batch returned wrong length of contracts, need 271, got 100
2020-08-19T05:12:03.547+0200 ERROR spin spin/hosts.go:63 Failed to sync HOST contracts: payout status batch returned wrong length of contracts, need 271, got 100
2020-08-19T06:12:04.803+0200 ERROR spin spin/hosts.go:63 Failed to sync HOST contracts: payout status batch returned wrong length of contracts, need 271, got 100
2020-08-19T07:12:01.064+0200 ERROR spin spin/hosts.go:63 Failed to sync HOST contracts: payout status batch returned wrong length of contracts, need 140, got 100
2020-08-19T08:12:01.033+0200 ERROR spin spin/hosts.go:63 Failed to sync HOST contracts: payout status batch returned wrong length of contracts, need 140, got 100

from go-btfs.

@Hgaesd65 Please follow instructions here to help us test the master build in order to resolve your errors: #624 (comment)

from go-btfs.

After sudo make install
i get the message
make: *** [mk/golang.mk:114: check_go_version] error 127

My system is:
System version: amd64/linux
Golang version: go1.14.6

from go-btfs.

O.K.
make install worked now

but now i got the message
root:~/go-btfs$ btfs daemon
Find metadata failed: No such file or directory

from go-btfs.

@Hgaesd65 make install should have installed it into your $GOPATH/bin, could you run $GOPATH/bin/btfs daemon instead? If your $GOPATH is unset, it should be ~/go

from go-btfs.

O.K. it's running now in the directory path root/go/bin/s
The btfs file is there.
The daemon is running. ---> Up to now no failure
BTFS is up-to-date.

from go-btfs.

O.K. it's running now in the directory path root/go/bin/
The btfs file is there.
The daemon is running. ---> Up to now no failure
BTFS is up-to-date.

from go-btfs.

Uptime 96%

from go-btfs.

I just got the failure
2020-08-19T14:49:07.420+0200 ERROR core/commands commands/wallet.go:214 wallet get balance failed, ERR: Failed to get exchange tron balance, reason: context canceled

from go-btfs.

Next payment date
Jan 01, 10000

from go-btfs.

from go-btfs.

The output of btfs id:
{
"ID": "16Uiu2HAm3VLV7C5Z21ZRuWEyZgJH4V5iG2z1z79jjL3Y6uRgz3ZS",
"PublicKey": "CAISIQJ3zcarJgYZ4AdfoxVa9Vmg/V5GlrdVNLUGtyXFt7QheQ==",
"Addresses": [
"/ip4/127.0.0.1/tcp/4001/p2p/16Uiu2HAm3VLV7C5Z21ZRuWEyZgJH4V5iG2z1z79jjL3Y6uRgz3ZS",
"/ip4/192.168.178.37/tcp/4001/p2p/16Uiu2HAm3VLV7C5Z21ZRuWEyZgJH4V5iG2z1z79jjL3Y6uRgz3ZS",
"/ip4/192.168.178.36/tcp/4001/p2p/16Uiu2HAm3VLV7C5Z21ZRuWEyZgJH4V5iG2z1z79jjL3Y6uRgz3ZS",
"/ip6/::1/tcp/4001/p2p/16Uiu2HAm3VLV7C5Z21ZRuWEyZgJH4V5iG2z1z79jjL3Y6uRgz3ZS"
],
"AgentVersion": "go-btfs/1.3.6-dev/5a9c53012",
"ProtocolVersion": "btfs/0.1.0",
"DaemonProcessID": 5188,
"TronAddress": "TJe8ZhZybFHjZxxRNJrR72XNuBdnRRVLKQ"
}

from go-btfs.

Thank you, there are some inconsistent data issues we are looking into. Unfortunately yours falls into this category. We will provide an update soon.

from go-btfs.

As mentioned in other posts, please email us at [email protected] with your node id for understanding of your uptime. Most of the inquiries we receive are from users who do have intermittent internet issues that prevent them from 100%. Do note that we have many users with 99%+ uptime.

For the date payment issue, please open a new issue to track it as no other issue has explicitly mentioned it (we are already looking into it, though).

from go-btfs.