The Storj Developer Hub

Welcome to the Storj developer hub. You'll find comprehensive guides and documentation to help you start working with Storj as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Support
Ask A Question

Questions

1
ANSWERED

Problem with 2 nodes out of 4

Hello, I started 2 new nodes (total 4 nodes work on PC). And they do not work. I waited a few days. Nothing changes. Storjshare status shows 0 allocs, shares - three points. Peers is normal (83 peers). Help solve the problem. Health.sh test of one of the nodes show: NodeID: a0d08c21b4f4e7bf17a39f5f3f9845a0354d06cf Status: Node running Bridge status: Bridge connected Reputation: API Server does not contain a parameter Restarts Count: 0 Log_file: /home/storj/.config/storjshare/logs/a0d08c21b4f4e7bf17a39f5f3f9845a0354d06cf_2018-2-23.log ResponseTime: API Server does not contain a parameter Address: 46.151.157.138 User Agent: 8.6.0 Last Seen: 2018-02-22T12:43:26.724Z Port: 4001 / open Protocol: 1.2.0 Uptime: 23h 46m 41s Last Timeout: API Server does not contain a parameter Timeout Rate: - / API Server does not contain a parameter DeltaTime: 21 / Good - Your clock is synced with a time server Share_allocated: 2.6TB Share_Used: ... Share_Percent: ... Last publish: - Last offer: - Last consigned: - Last download: - Last upload: - Offers: null Peers: 8 DataReceivedCount 0 Publish counts: 0 Download counts: 0 Upload counts: 0 Last contract sent: API Server does not contain a parameter Space Available: true Consignment counts: 0 Logs are filled with the same type of errors: {"level":"warn","message":"missing or empty reply from contact","timestamp":"2018-02-23T00:05:29.418Z"} {"level":"warn","message":"rpc call 720b629af5ccdc6d40bab8586cf2062aa0f0091e timed out","timestamp":"2018-02-23T00:06:45.444Z"} {"level":"warn","message":"rpc call da44a4785369126a6686f71cb816e0e233826199 timed out","timestamp":"2018-02-23T00:06:45.483Z"} {"level":"warn","message":"error returned from remote host: {\"error\":\"Client cannot service request at this time\"}","timestamp":"2018-02-23T00:09:06.890Z"} {"level":"warn","message":"missing or empty reply from contact","timestamp":"2018-02-23T00:09:06.890Z"} {"level":"warn","message":"rpc call a10834626bc09fb3ea5b074853397f98e3c8c295 timed out","timestamp":"2018-02-23T00:09:45.552Z"} {"level":"warn","message":"error returned from remote host: request timeout after 30000ms","timestamp":"2018-02-23T00:15:40.734Z"} {"level":"warn","message":"missing or empty reply from contact","timestamp":"2018-02-23T00:15:40.734Z"} {"level":"warn","message":"error returned from remote host: request timeout after 30000ms","timestamp":"2018-02-23T00:15:40.734Z"} {"level":"warn","message":"missing or empty reply from contact","timestamp":"2018-02-23T00:15:40.735Z"} {"level":"warn","message":"error returned from remote host: request timeout after 30000ms","timestamp":"2018-02-23T00:15:40.801Z"} {"level":"warn","message":"missing or empty reply from contact","timestamp":"2018-02-23T00:15:40.801Z"} {"level":"warn","message":"rpc call 1f8800d40700f6151164710f1610b5a2023aed1b timed out","timestamp":"2018-02-23T00:15:45.669Z"} {"level":"warn","message":"rpc call d6dc2e4a158b4a2ddd0e58e9963f9b0e06ebec61 timed out","timestamp":"2018-02-23T00:15:45.707Z"} {"level":"warn","message":"rpc call 38fb38a038bc3054976c7b260acca06c52cfdd53 timed out","timestamp":"2018-02-23T00:15:45.707Z"} {"level":"warn","message":"error returned from remote host: {\"error\":\"Unable to route to tunnel, client is not connected\"}","timestamp":"2018-02-23T00:16:25.6$ {"level":"warn","message":"missing or empty reply from contact","timestamp":"2018-02-23T00:16:25.644Z"} {"level":"warn","message":"missing or empty reply from contact","timestamp":"2018-02-23T00:16:53.450Z"} {"level":"warn","message":"error returned from remote host: connect ETIMEDOUT 46.98.196.10:49780","timestamp":"2018-02-23T00:16:53.450Z"} {"level":"warn","message":"rpc call 01218634b6d47ca622a33a7a4868ea3e1f3ddd82 timed out","timestamp":"2018-02-23T00:17:15.732Z"} {"level":"warn","message":"error returned from remote host: connect ETIMEDOUT 46.98.196.10:49780","timestamp":"2018-02-23T00:17:18.026Z"}

Posted by Aleksandr about 12 hours ago

1
ANSWERED

Issues

Hi, I've been running a node with port forwarding for 15 hours and have yet to see any shards. Is that normal? I've shared out 3 TB. Here's what the stats look like: 0 0fe31b14c12e3401e81746ee5bbb6f24767566c1 ON E:\root\ 16h 27m 2s 0 33 Connected 2 (0 received) ... (...%) 26ms 4000 (TCP) log analysis: Node ID: 0fe31b14c12e3401e81746ee5bbb6f24767566c1 Last Seen: 2018-02-20T23:10:48.650Z Port: 4000 Address: 172.116.198.144 User Agent: 8.6.0 Protocol: 1.2.0 Response Time: 9762.18889292383 Last Timeout: Timeout Rate: 0 Your node is reachable. Delta: | Cannot find your delta in the log. Status: Your address is public and traversal strategies are disabled. Good. Receiving: ... You have received 11 alloc requests. | Good. You have not sent any alloc responses. | If you have not received any allocs, or your node is out of space, this is normal. No shards have been reaped. (Removed) From the website: https://api.storj.io/contacts/0fe31b14c12e3401e81746ee5bbb6f24767566c1 {"lastSeen":"2018-02-21T14:41:40.443Z","port":4000,"address":"172.116.198.144","userAgent":"8.6.0","protocol":"1.2.0","spaceAvailable":true,"responseTime":9547.307158496782,"reputation":0,"nodeID":"0fe31b14c12e3401e81746ee5bbb6f24767566c1"} I have a second computer I've set it up on and it's also showing very little activity: 11a1a240ef68e34edb20c97824d830c898ad8475 ON C:\ 15h 55m 19s 0 66 Connected 7 (0 received) 3.01MB (0%) 28ms 4006 (TCP) Logs parsing: Node ID: 11a1a240ef68e34edb20c97824d830c898ad8475 Last Seen: 2018-02-21T06:39:58.817Z Port: 4006 Address: 172.116.198.144 User Agent: 8.6.0 Protocol: 1.2.0 Response Time: 9482.95718575262 Last Timeout: Timeout Rate: 0 Your node is reachable. Delta: | Cannot find your delta in the log. Status: Your address is public and traversal strategies are disabled. Good. Receiving: ... You have not received any alloc requests. | If your node is new this may be normal. If older than 1 hour, it may be an issue. You have not sent any alloc responses. | If you have not received any allocs, or your node is out of space, this is normal. No shards have been reaped. (Removed) These are logs from today. There is another file from yesterday but I didn't parse that. Please help?

Posted by Amar Manro a day ago