Jump to content
Jcloud

[Support] QDirStat, Jcloud - cryptoCoin templates

321 posts in this topic Last Reply

Recommended Posts

3 hours ago, physikal said:

you're a badass...I forget if you sent me your ETH address or not. If not, please send.  I need to donate.

You don't NEED(I can't stress that enough) to do anything on my part, but if you want to:   (Give me 12-hrs from this post to double check that ETH address before you send - I'm at work, I don't want you send it off into the ether) Address confirmed.

0xe09a2b205d3a76196a88505f059c78df7d7c556f

Honestly, I've felt my work to be sub-par in comparison of the rest of the unRAID Community. I'm also, super critical of my own work/self.  :D

 

But hey, I'm glad it's working well for someone other than just me, based on feed-back so far. LOL 

I'm just in it for the learning experience, mostly.  Storj tokens have some potiental for fiat gains. :)

 

Edited by Jcloud

Share this post


Link to post

So I've noticed something very odd with my repo, the first node seems to be ignoring the config file 

┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐
│ Node                                        │ Status  │ Uptime   │ Restarts │ Peers   │ Allocs        │ Delta   │ Port     │ Shared    │ Bridges      │
├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤
│ e0e9ce647217d368e554024bc6519bbb9a328d17    │ running │ 23h 59m… │ 0        │ 205     │ 93            │ 40ms    │ 40001    │ 6.62GB    │ connected    │
│   → /storj/share                            │         │          │          │         │ 14 received   │         │ (Tunnel) │ (1%)      │              │
├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤
│ 945c7da42cf0b06b5c4ed3c709ccca6658967b75    │ running │ 23h 59m… │ 0        │ 114     │ 90            │ 19ms    │ 4001     │ 1.36GB    │ connected    │
│   → /storj/Node_1                           │         │          │          │         │ 0 received    │         │ (TCP)    │ (0%)      │              │
├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤

Also storjstat lists that node as some IP address. Not sure what's going on there. Going to try and investigate, but in meantime keep an eye on those nodes and don't nuke your old storj container just yet. ;)  Update: After running regular Storj container  the port went back to UPnP (which is my normal status for 4000) and back to port 4000. Stopped the container and started my custom container, and seems to be running fine again. Hmmm more oddity.  I think I need to get that auto-builds going.... Perhaps something changes in the backgound in the node.js structure? IDK, "typing out-loud" here.

 

EDIT2:

So I found something in my /stor/config.json file (node_0) that I struck out as different from other nodes. 

  // doNotTraverseNat: true requires you to have an external ip address.
  // You can use a proxy to gain an external IP address.
  // doNotTraverseNat: false Enables NAT traversal strategies
  // first UPnP, then reverse HTTP tunnel
  // if that fails. Disable if you are public or using dynamic DNS
"doNotTraverseNat": true,

where as all the other nodes are FALSE, and also don't allow for tunnels (and I know why - command flag when making a node). So I changed the above line to false and now PORT 4000 reports TCP. 

 

 

 

Edited by Jcloud
My software is BETA or kuality - "Yes, quality with a 'k'!" Or is it?

Share this post


Link to post

In case people want, or need, to compare their firewall rules versus mine - for trouble shooting or any reason. Seen a number of folks mention pfsense, and other firewalls. Pfsense requires a, "Firewall rule" and a, "Port forward rule" if you have a NAT network.  I also had an issue earlier today were overly aggressive SNORT service settings blocked traffic to storjstat.com -- called that one my fault, I was tinkering with it the night before. (oops)

 

 

storjFW1.jpg

storjFW2.jpg

Edited by Jcloud

Share this post


Link to post
11 hours ago, Jcloud said:

Fuuuu...  Um, yeah.  Is that node running from a different container, or was this from consolidating multiple containers/paths into my new container?

 

It is container with a single node that existed previously on ht old template. But I am getting the same error on the completely new nodes

 

I also just restarted an old mode in host mode, to check that it is not the problem and I have the same error. The only other thing I changed in the config is: Do Not Traverse NAT to True.

 

* starting node with config at /storj/config.json
{"level":"info","message":"got status query","timestamp":"2018-04-21T07:21:34.665Z"}
[07:21:34] 94fc2d886f6c664a20f55f8c357c189775f79a46 | Submit to Storjstat
[07:21:34] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}

 

Share this post


Link to post
1 minute ago, MrChunky said:

But I am getting the same error on the completely new nodes

 

1 minute ago, MrChunky said:

[07:21:34] 94fc2d886f6c664a20f55f8c357c189775f79a46 | Submit to Storjstat [07:21:34] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}

On empty nodes I've totally seen this, and I think that's normal; once the empty node got data it went away.

However, the one that has data in it I don't like, and I don't know what's going on with that. :/  

Share this post


Link to post
7 hours ago, Jcloud said:

...

where as all the other nodes are FALSE, and also don't allow for tunnels (and I know why - command flag when making a node). So I changed the above line to false and now PORT 4000 reports TCP. 

 

 

In my case, when I set it to False, I get UPnP connection. When it is set to true I get TCP. All my nodes are set to do not traverse and working fine.

 

I have a floating rule for the ports on PfSence since I wanna circumvent pfblockerng geo blocking.

 

 

Edited by MrChunky

Share this post


Link to post
16 hours ago, Jcloud said:

Are the file and directory permissions the same on root folder as it is with the sub folders? Perhaps that's what is going on?

Yep, sorted it out. Unassigned devices runs under nobody on the /storj folder. Changed perms to root and its all good now.

Share this post


Link to post

Sorry for the spam. I was thinking that it would make sense (to me) to not start the main node that resides in the root folder and only start additional nodes. It would make the folder structure make more sense, as all nodes will be in respective sub folders. Also potentially avoid complications with debugging several conditions (main/ additional nodes).

Share this post


Link to post
25 minutes ago, MrChunky said:

Sorry for the spam. I was thinking that it would make sense (to me) to not start the main node that resides in the root folder and only start additional nodes

The suggestion makes a certain amount of sense. I must admit, as for the layout of files, I've just been following the 'defaults' (if you want to call it that) of the original source container.

 

I'm easy though, if the consensus is "move it," I can do that. :D

 

Share this post


Link to post

Anyone else experiencing this? image.thumb.png.1d7384b6efcd4f706d7a50d5073825e7.png

 

all but 2 nodes are connected and working fine.  The other 2 are "connecting".  Odd right?

Share this post


Link to post
2 hours ago, physikal said:

.  The other 2 are "connecting".  Odd right?

Are you running container as bridge or host mode? And yes, definitely odd. Also, for S's and G's, double check your firewall to make sure it includes those ports.

 

EDIT:

I'd also look at the different config.json files of node0,5, and a working one like 1 -- if these were imported from another container. 

But, my gut feeling says firewall, or at least starting there.

 

 

Edited by Jcloud

Share this post


Link to post

br0 w/ fixed IP.  Worked fine for my other version (and the rest of the nodes).  Just odd those 2 won't connect.

Share this post


Link to post

oh interesting, just checked and now only 1 is "connecting", the rest are connected.  I'll just give it more time :)

Share this post


Link to post
52 minutes ago, physikal said:

oh interesting, just checked and now only 1 is "connecting", the rest are connected.  I'll just give it more time :)

"Slow node" perhaps? Honestly, IDK.

 

EDIT: Hmm have an idea about that since you you're on bridge. I need to look at if it would a change on my end or something you can tweak.

Edited by Jcloud

Share this post


Link to post
On 4/21/2018 at 5:06 AM, MrChunky said:

Yep, sorted it out. Unassigned devices runs under nobody on the /storj folder. Changed perms to root and its all good now.

 

10 hours ago, phithor said:

I'm still seeing errors for submitting data usage, otherwise the docker image is working fine. 

@MrChunky since you were able to see and resolve your issue, could you put up the steps you did to check and fix your issue? Please.

 I'm thinking @phithor may have the same permission issues you resolved -- or at least I'd like to check for it.

 

Thanks for your time.

Share this post


Link to post

Hmm, id ont get it.

 

I copied conf files, startet new storj + cli, and get 

 

* starting daemon in foreground

{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:02:33.433Z"}

* starting node with config at /storj/config.json
{"level":"info","message":"got status query","timestamp":"2018-04-24T12:02:33.750Z"}
[12:02:33] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[12:02:34] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}

 

 

Share this post


Link to post

I just changed host to briged, bc i dont want that many uselss IPs in my network... also i wonder, i dont see anything from storjstat in the directory?

 

Okay, i changed back to host, now the node is atleast reachable from outside (i dont know why its no longer working in bridge mode) Still, storjmonitor throws:

* starting daemon in foreground

{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:25:48.841Z"}

* starting node with config at /storj/config.json
{"level":"info","message":"got status query","timestamp":"2018-04-24T12:25:49.094Z"}
[12:25:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[12:25:49] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}

Edited by nuhll

Share this post


Link to post

If i use host this container uses (only) the Standard ports, even when i add new -> add port 4005, it still uses 4000-4003

 

Only in bridge i can select my ports and this container use it...

 

I dont understand whats happening.

 

What did i do?

 

I stopped old storj and installed new storj in same directory.

 

-> its not working on any of my nodes (11), the first i can run in host, but all others i need to run in bridge (i dont like one docker for multiple nodes) and in host i cant change the ports (i dont know why this happens)

 

Doesnt matter if i use host or bridge, none of the nodes seem to be able to report to storj monitor.

 

If host is needed, why i cant change the ports? And also, the first node, which is in host, should work, but it fails to send data to storjstat, like all other nodes.

 

This node is running for months: (and currently in Host mode)

 

┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐
│ Node                                        │ Status  │ Uptime   │ Restarts │ Peers   │ Allocs        │ Delta   │ Port     │ Shared    │ Bridges      │
├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤
│ 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0    │ running │ 2m 27s   │ 0        │ 120     │ 0             │ -109ms  │ 4000     │ 52.34GB   │ connected    │
│   → /storj/share                            │         │          │          │         │ 0 received    │         │ (TCP)    │ (26%)    │              │
└─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘




* starting daemon in foreground

{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:25:48.841Z"}

* starting node with config at /storj/config.json
{"level":"info","message":"got status query","timestamp":"2018-04-24T12:25:49.094Z"}
[12:25:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[12:25:49] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}
{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:30:33.688Z"}
{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:30:51.931Z"}
{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:32:03.657Z"}
{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:32:21.563Z"}
{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:32:25.463Z"}
{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:33:50.235Z"}
{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:37:46.575Z"}
{"level":"info","message":"got status query","timestamp":"2018-04-24T12:40:49.179Z"}
[12:40:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[12:40:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Error
{"level":"info","message":"got status query","timestamp":"2018-04-24T12:55:49.281Z"}
[12:55:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[12:55:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Error
{"level":"info","message":"got status query","timestamp":"2018-04-24T13:10:49.380Z"}
[13:10:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[13:10:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Error
{"level":"info","message":"got status query","timestamp":"2018-04-24T13:25:49.485Z"}
[13:25:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[13:25:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Error
{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T13:31:36.720Z"}
{"level":"info","message":"got status query","timestamp":"2018-04-24T13:40:49.583Z"}
[13:40:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[13:40:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Error
{"level":"info","message":"got status query","timestamp":"2018-04-24T13:55:49.685Z"}
[13:55:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[13:55:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Error

Edited by nuhll

Share this post


Link to post
3 hours ago, nuhll said:

copied conf files, startet new storj + cli, and get 

 

Yeah I tried that too in testing, before I posted, and got the same errors. I think it has to do with encryption, and/or storj configuration, not knowing about other nodes because it didn't build it.

 

3 hours ago, nuhll said:

[12:25:49] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}

I see that error whenever the container is empty. Did the container create new directories in your /storj area? If so the container just created new nodes (I think based on your description).

3 hours ago, nuhll said:

-> its not working on any of my nodes (11), the first i can run in host, but all others i need to run in bridge (i dont like one docker for multiple nodes) and in host i cant change the ports (i dont know why this happens)

 

I think the container isn't initially setup (logic in my shell-script) to handle what you were doing before. The webui had the ports removed, because I changed it to host (yup my fault) -- if you change it to bridge, then at bottom you can click on "Add ports, variable, path" and add the port field back in.  

 

That's all I can do for now -- late to employment.

Share this post


Link to post

FWIW I also noticed an issue using the CA Backup plugin the StorjMonitor docker doesn't start up on it's own properly.  I didn't capture any error logs or anything - sorry I'm not more help lol.

Share this post


Link to post

Okay, it might be that your install scripts didnt run, because the node is already there...

 

How to manually run the install script once?

 

I wouldnt really like to remove all nodes.

 

From my side it dont seem like he created anything new. The nodes also seem to run just fine, but just without storj monitor.. 

 

Can i manuall run the script to install the storj monitor script? If so, how? Would be a waste to start with all 11 nodes from scratch... 

 

edit:
just to clarify this, i dont use your multi node thingy, im just adding a docker per node storj1 storj2 storj3 ...

i accidently deleted my first storj node with 100gb data... and used ur script to do a fresh install, ofc it shows error, bc it has nothing stored, but this node should probably work. How can i get my other nodes working?

 

i tried something by myself but it seems like i have no idea what im doin... :D

 

root@Unraid-Server:~# docker run -it --entrypoint /bin/sh zugz/r8mystorj

/ # StorjMonitor/storjMonitor-install.sh
/bin/sh: StorjMonitor/storjMonitor-install.sh: not found
/ # chmod +x StorjMonitor/storjMonitor-install.sh
/ # StorjMonitor/storjMonitor-install.sh
/bin/sh: StorjMonitor/storjMonitor-install.sh: not found
/ # cd StorjMonitor
/StorjMonitor # chmod +x storjMonitor-install.sh
/StorjMonitor # ./storjMonitor-install.sh
/bin/sh: ./storjMonitor-install.sh: not found

/StorjMonitor # ls
README.md                bin                      node_modules             package.json             storjMonitor-install.sh  storjMonitor.bat         storjMonitor.js          storjMonitor.sh
/StorjMonitor # ./storjMonitor.sh
[17:48:26] Error connecting to StorjShare Client, are you sure its running?
[17:48:26] Error: connect ECONNREFUSED 127.0.0.1:45015

 

 

/StorjMonitor # sh storjMonitor-install.sh

> weak@1.0.1 install /StorjMonitor/node_modules/weak
> node-gyp rebuild

gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at failNoPython (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:401:14)
gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:330:11
gyp ERR! stack     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:16)
gyp ERR! stack     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:123:15)
gyp ERR! System Linux 4.14.34-unRAID
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /StorjMonitor/node_modules/weak
gyp ERR! node -v v6.7.0
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
StorjMonitor@0.0.1 /StorjMonitor
+-- bindings@1.2.1
+-- dnode@1.2.2
| `-- jsonify@0.0.0
+-- dnode-protocol@0.2.2
+-- jquery@3.1.0
+-- q@0.9.7
+-- requestify@0.2.5
+-- traverse@0.6.6
`-- underscore@1.8.3

npm ERR! Linux 4.14.34-unRAID
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE

npm ERR! weak@1.0.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the weak@1.0.1 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the weak package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs weak
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls weak
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /StorjMonitor/npm-debug.log

 

Edited by nuhll

Share this post


Link to post

 

10 hours ago, nuhll said:


just to clarify this, i dont use your multi node thingy, im just adding a docker per node storj1 storj2 storj3 ...

i accidently deleted my first storj node with 100gb data... and used ur script to do a fresh install, ofc it shows error, bc it has nothing stored, but this node should probably work. How can i get my other nodes working?

I'm sorry for your data loss, and if it is because of trying to use this container my apologies.  

 

10 hours ago, nuhll said:

Can i manuall run the script to install the storj monitor script? If so, how? Would be a waste to start with all 11 nodes from scratch... 

:D I accidentally did that to all 11 of my nodes while working on this container. LOL Oops, there went a month of contracts. Sorry, it is easy for me to laugh at myself after the fact.  I'll do my best to get this to work and not lose data. 

 

It should be installed but if you want to check for it:

Get inside the container

 docker exec -ti StorjMonitorContainerNameHere /bin/sh

Can we go in the StorjMonitor folder (this is inside the container):

cd /StorjMonitor

If that works, great! Check for files, type command: 

ls -al

This should produce a list like this:

/StorjMonitor # ls -al
total 24
drwxr-xr-x    1 root     root           218 Apr 25 03:45 .
drwxr-xr-x    1 root     root           212 Apr 19 07:32 ..
drwxr-xr-x    1 root     root           138 Apr 19 05:31 .git
-rw-r--r--    1 root     root          1170 Apr 19 05:31 README.md
drwxr-xr-x    1 root     root            16 Apr 19 05:31 bin
drwxr-xr-x    1 root     root           152 Apr 19 05:31 node_modules
-rw-r--r--    1 root     root           760 Apr 19 05:31 package.json
-rwxr-xr-x    1 root     root           125 Apr 19 05:31 storjMonitor-install.sh
-rw-r--r--    1 root     root            34 Apr 19 05:31 storjMonitor.bat
-rw-r--r--    1 root     root          2131 Apr 25 03:45 storjMonitor.js
-rwxr-xr-x    1 root     root            21 Apr 19 05:31 storjMonitor.sh
/StorjMonitor #

Check to see if StorjMonitor API key is inserted and correct, type command:

head storjMonitor.js

The last line of the output should read:

var token = "YOUR-TOKEN-HERE"; //api token can be create under "Nodes" -> "API-Key"

Where "YOUR-TOKEN-HERE" should read a sting of letters and numbers, your Storjstat.com API-key.

IF it actually reads "YOUR-TOKEN-HERE" then it didn't get it from the webui template (and I don't know why that would be) AND this needs to be fixed!

 

To fix the error, run this command:  (Take note)

  •       Leave "YOUR-TOKEN-HERE" as "YOUR-TOKEN-HERE"
  •       Change "MONITORKEY" to your API-key  (recommend using copy/paste here)
sed -i "s/YOUR-TOKEN-HERE/MONITORKEY/" /StorjMonitor/storjMonitor.js

 

EXAMPLE

 

sed -i "s/YOUR-TOKEN-HERE/H8WvafR770FPK2zA8ZTs7NTX2QH3GB5xC9curPDs/" /StorjMonitor/storjMonitor.js

 

 

Verify the change worked, run command (again):

head storjMonitor.js

 

If you want to run the storjMonitor script manually then run:

./storjMonitor.sh 

 

I hope that helps.

 

Share this post


Link to post
11 hours ago, nuhll said:

ust to clarify this, i dont use your multi node thingy, im just adding a docker per node storj1 storj2 storj3 ..

Can you give me a screen shot of your Storj webui template you use, that works. And an example of storj2 on new container template webui?

Share this post


Link to post

The error below showing at docker image start is caused by the StorjMonitor being loaded before the node has fully started up. It should be the last thing to be started and preferably at least 10 seconds after the last node start command to be sure.

 

* starting daemon in foreground

{"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-24T12:25:48.841Z"}

* starting node with config at /storj/config.json
{"level":"info","message":"got status query","timestamp":"2018-04-24T12:25:49.094Z"}
[12:25:49] 1d065de2cb7e749bcb6415f4b4f555e8b475a5d0 | Submit to Storjstat
[12:25:49] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}

Edited by phithor

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.