Dashboard isn't available after changing the partition size

Node Operators
1

So uh, I have a weird problem.

I’ve noticed that my node was running low on space and I had more space available, but on a different partition of the same physical disk. The whole thing runs on Ubuntu with ext4. So it’s a simple operation with cfdisk, don’t have to format the whole thing which is good.

I stopped the node, removed it, made the operation with cfdisk, remade the Node and now I can’t access the dashboard. According to the logs everything works (will attach below) and the only thing I changed in the starting command is the size of my disk. So, any fix for that?

The logs:

2020-04-10T22:01:05.777Z        INFO    piecestore      upload canceled {"Piece ID": "BWVUW75TH5AQDLI3KHMHGQEVGLE27EUY3LXQSFTA5ZNLB2DDWHOA", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT", "error": "context canceled", "errorVerbose": "context canceled\n\tstorj.io/common/pb/pbgrpc.init.0.func3:70\n\tstorj.io/common/rpc/rpcstatus.Wrap:77\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).doUpload:452\n\tstorj.io/storj/storagenode/piecestore.(*drpcEndpoint).Upload:215\n\tstorj.io/common/pb.DRPCPiecestoreDescription.Method.func1:987\n\tstorj.io/drpc/drpcmux.(*Mux).HandleRPC:107\n\tstorj.io/drpc/drpcserver.(*Server).handleRPC:105\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:56\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:93\n\tstorj.io/drpc/drpcctx.(*Tracker).track:51"}
2020-04-10T22:01:07.346Z        INFO    piecestore      download started        {"Piece ID": "5QCT7IYON3O6GOEPW4CCABCEEA4RQHC7GRXQKPMPGXRTJKKB3R7A", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "GET"}
2020-04-10T22:01:07.553Z        INFO    piecestore      downloaded      {"Piece ID": "5QCT7IYON3O6GOEPW4CCABCEEA4RQHC7GRXQKPMPGXRTJKKB3R7A", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "GET"}
2020-04-10T22:01:08.264Z        INFO    piecestore      upload started  {"Piece ID": "DOICGCMJGCVNBWZH5SLWNOI43AW4WMRRZT34BKNR2O6OUE2IESXQ", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT", "Available Space": 1641337043968}
2020-04-10T22:01:08.768Z        INFO    piecestore      upload started  {"Piece ID": "KW5OGYPLJUW5GRJMVYGM6WMHZHJ6SYUNBW7UWRLCCMSJIQMT227A", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT", "Available Space": 1641337043968}
2020-04-10T22:01:09.072Z        INFO    piecestore      upload canceled {"Piece ID": "7TTORX4VSN3RSOPZJM7A23XKHMZXAS5WIGVNIZHISVJCNMSHTCTQ", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT", "error": "context canceled", "errorVerbose": "context canceled\n\tstorj.io/common/pb/pbgrpc.init.0.func3:70\n\tstorj.io/common/rpc/rpcstatus.Wrap:77\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).doUpload:452\n\tstorj.io/storj/storagenode/piecestore.(*drpcEndpoint).Upload:215\n\tstorj.io/common/pb.DRPCPiecestoreDescription.Method.func1:987\n\tstorj.io/drpc/drpcmux.(*Mux).HandleRPC:107\n\tstorj.io/drpc/drpcserver.(*Server).handleRPC:105\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:56\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:93\n\tstorj.io/drpc/drpcctx.(*Tracker).track:51"}
2020-04-10T22:01:09.838Z        INFO    piecestore      upload started  {"Piece ID": "XEGGTTWYMEJV7KSS5MI4JSL3TS6UCAW47QEXOYP7VUYYJRFLMWWQ", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT", "Available Space": 1641334724096}
2020-04-10T22:01:10.558Z        INFO    piecestore      upload canceled {"Piece ID": "DOICGCMJGCVNBWZH5SLWNOI43AW4WMRRZT34BKNR2O6OUE2IESXQ", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT", "error": "context canceled", "errorVerbose": "context canceled\n\tstorj.io/common/pb/pbgrpc.init.0.func3:70\n\tstorj.io/common/rpc/rpcstatus.Wrap:77\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).doUpload:452\n\tstorj.io/storj/storagenode/piecestore.(*drpcEndpoint).Upload:215\n\tstorj.io/common/pb.DRPCPiecestoreDescription.Method.func1:987\n\tstorj.io/drpc/drpcmux.(*Mux).HandleRPC:107\n\tstorj.io/drpc/drpcserver.(*Server).handleRPC:105\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:56\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:93\n\tstorj.io/drpc/drpcctx.(*Tracker).track:51"}
2020-04-10T22:01:11.288Z        INFO    piecestore      uploaded        {"Piece ID": "XEGGTTWYMEJV7KSS5MI4JSL3TS6UCAW47QEXOYP7VUYYJRFLMWWQ", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT"}
2020-04-10T22:01:11.325Z        INFO    piecestore      upload started  {"Piece ID": "7STBWGTWECMRP33O6ZSDHH52QPOJEZRFUWQ5TYI5GBBV2PLAND6A", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT", "Available Space": 1641331358464}
2020-04-10T22:01:12.086Z        INFO    piecestore      upload started  {"Piece ID": "2RP5YER7C4LWFI3YZHMDHB7VEIUIH3EUKEDH7EQEFGWARCESW5KA", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Available Space": 1641331358464}
2020-04-10T22:01:12.093Z        INFO    piecestore      uploaded        {"Piece ID": "2RP5YER7C4LWFI3YZHMDHB7VEIUIH3EUKEDH7EQEFGWARCESW5KA", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT"}
2020-04-10T22:01:12.732Z        INFO    piecestore      uploaded        {"Piece ID": "KW5OGYPLJUW5GRJMVYGM6WMHZHJ6SYUNBW7UWRLCCMSJIQMT227A", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT"}
2020-04-10T22:01:12.848Z        INFO    piecestore      upload started  {"Piece ID": "IWDCGKCPGDZTLMVXZVXOFWDK5JV2HMXFB6ZYASFE7WNXHW35HYFQ", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Action": "PUT", "Available Space": 1641329037056}

The “docker -ps” output:

CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS                                                  NAMES590db1507ae3        storjlabs/storagenode:beta    "/entrypoint"            6 minutes ago       Up 6 minutes        127.0.0.1:14002->14002/tcp, 0.0.0.0:28967->28967/tcp   storagenode
ab154ed430ea        storjlabs/watchtower:latest   "/watchtower storage…"   7 weeks ago         Up 6 weeks                                                                 watchtower
214a371da42d        84803293c0e3                  "/watchtower storage…"   3 months ago        Up 6 weeks                                                                 HnvIWpASSvHBlJuzwXMviiHUDsOJZheW

Could someone help?

EDIT: so uh the docker-ps output is messed up, but it says that the image has been up for 6 minutes, shich is correct.

2

Which Dashboard do you speak of?

3

The web-dashboard, where you can monitor the stats. I’m trying to access it from another PC on the same network.

4

Did you change your docker start command?

5

Please, remove the 84803293c0e3 container, and watchtower as well
then run it again:
https://documentation.storj.io/setup/cli/software-updates#automatic-updates
https://documentation.storj.io/setup/cli/storage-node#running-the-storage-node

also, please provide an info

df -h
6

Only the size of the partition. Network setting remained the same.

7

if your trying to access your dashboard on the same network you need to make it your local ip not 127.0.0.1

1 Like
8

It used to work that way before I made the partition change.

9

No it never worked that way, if you used 127.0.0.1 only the local computer could access the dashboard.

1 Like
10

I mean, it worked for me that way so I guess it shouldn’t have worked?

11

From my experience it has never worked that way if you wanted to access the dashboard over your network.

1 Like
12 
/dev/loop2       157M         157M     0          100% /snap/gnome-3-28-1804/110
/dev/loop3       1,0M         1,0M     0          100% /snap/gnome-logs/81
/dev/loop1        15M          15M     0          100% /snap/gnome-characters/399
/dev/loop4       161M         161M     0          100% /snap/gnome-3-28-1804/116
/dev/loop5        45M          45M     0          100% /snap/gtk-common-themes/1440
/dev/loop6       4,4M         4,4M     0          100% /snap/gnome-calculator/704
/dev/loop7        49M          49M     0          100% /snap/gtk-common-themes/1474
/dev/loop8       4,3M         4,3M     0          100% /snap/gnome-calculator/544
/dev/loop10       55M          55M     0          100% /snap/core18/1705
/dev/loop9       121M         121M     0          100% /snap/docker/423
/dev/loop11       55M          55M     0          100% /snap/core18/1668
/dev/loop13      1,0M         1,0M     0          100% /snap/gnome-logs/93
/dev/loop12      917M         917M     0          100% /snap/xonotic/49
/dev/loop14       92M          92M     0          100% /snap/core/8689
/dev/loop15       15M          15M     0          100% /snap/gnome-characters/495
/dev/sda1        511M         7,8M  504M            2% /boot/efi
/dev/sdb1        3,7T         2,0T  1,5T           57% /mnt/storjnode
tmpfs            779M          32K  779M            1% /run/user/1000

Also the above procedure didn’t help.

13

Huh, it appears I was wrong. Not sure why it worked before though. Thanks a lot!

It’s not even local ip, it’s just using only the ports in the appropriate field.

14

Yeah that way works too, But that allows for all IPs, I have mine setup to use only the local IP.

15

So, should that be my PC IP or my router IP?

16

That would be the PC that its running on the local IP of it.

17

And what if I want all devices on my netwrok to be able to access the dashboard? Say, I sometimes check the status from my phone

18

On the same network? Or outside of your house.

19

Still the same network in my house, yeah.

20

Then your phone would still be able to connect to it less you have more then one network inside of your house.

1 Like