I have Ingress but no Egress any clue why?

Node Operators troubleshooting
,
1

So I have been running my Storj node for about an hour now. I have 500mb of ingress and stored on my disk. But how come I see not egress? Also when I look at my log I see this error message repeated atleast 10,000 times for all different upload failed request.

Example error:
2024-03-02T21:23:41Z ERROR piecestore upload failed {“process”: “storagenode”, “Piece ID”: “OH6S44SGIEBGMJ3POCPCTLIPEKYOWXPOQNJ4ULF4R2EZMR3VIHIA”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Action”: “PUT”, “error”: “pieces error: filestore error: chmod config/storage/temp/blob-2786949508.partial: operation not permitted”, “errorVerbose”: “pieces error: filestore error: chmod config/storage/temp/blob-2786949508.partial: operation not permitted\n\tstorj.io/storj/storagenode/blobstore/filestore.(*blobWriter).Commit:133\n\tstorj.io/storj/storagenode/pieces.(*MonitoredBlobWriter).Commit:69\n\tstorj.io/storj/storagenode/pieces.(*Writer).Commit.func1:131\n\tstorj.io/storj/storagenode/pieces.(*Writer).Commit:199\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).Upload.func6:478\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).Upload:541\n\tstorj.io/common/pb.DRPCPiecestoreDescription.Method.func1:243\n\tstorj.io/drpc/drpcmux.(*Mux).HandleRPC:33\n\tstorj.io/common/rpc/rpctracing.(*Handler).HandleRPC:61\n\tstorj.io/common/experiment.(*Handler).HandleRPC:42\n\tstorj.io/drpc/drpcserver.(*Server).handleRPC:124\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:66\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:114\n\tstorj.io/drpc/drpcctx.(*Tracker).track:35”, “Size”: 181504, “Remote Address”: “79.127.220.99:42632”}

Some images of Ingress and Egress
Imgur
Imgur

Thank you for any response I may end up getting.

2

permissions for your storage are not correct

2 Likes
3

Thank you for the response. I am on Linux where would I find this path to change the permissions it has?

4

if you didn’t change anything, it should be under ~/.local/share/storj/storagenode/

5

that might be where it is going wrong. Because currently I have my /storage/temp set up to this path: “~/mount/Storj/storage/temp/blob” which I assume it is not looking at for some reason. Any clue how to change that? .Also it knows about the place because it is writing to the temp file in here, its just not reading it or something.

This is how I mounted it for this:

Let me know if I did something wrong with the following path:

type=bind,source=“/home/user/.local/share/storj/identity/storagenode”,destination=/app/identity**
mount type=bind,source=“/home/user/mount/Storj”,destination=/app/config **

6

I don’t use docker sorry.

2 Likes
7

this is the response I get if I check the permissions of the folder. Which I believe it should have access to read then. Could also be wrong as still bit new to linux.

Command: ~/mount/Storj/storage/temp$ ls -ld
Response: drwxrwxrwx 2 1028 users 0 Mar 2 15:28 .

8

Set full owneship, recursively, to all storj folders to the user the storagenode is running as.

2 Likes
9

Hello @MiniMethod,
Welcome to the forum!

How did you make this:

Please show the result of the command:

df --si -T

P.S. you shouldn’t split a storage directory to different drives, it could work, but you likely will have problems. It’s recommended that the entire content of the storage directory should be on the same filesystem, not junctions or symlinks or different mounts.

10

Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 17G 0 17G 0% /dev
tmpfs tmpfs 3.4G 2.3M 3.4G 1% /run
/dev/nvme0n1p5 ext4 118G 38G 75G 34% /
tmpfs tmpfs 17G 0 17G 0% /dev/shm
tmpfs tmpfs 5.3M 4.1k 5.3M 1% /run/lock
tmpfs tmpfs 17G 0 17G 0% /sys/fs/cgroup
/dev/loop0 squashfs 68M 68M 0 100% /snap/core20/2105
/dev/loop3 squashfs 367M 367M 0 100% /snap/gnome-3-38-2004/143
/dev/loop1 squashfs 68M 68M 0 100% /snap/core20/2182
/dev/loop2 squashfs 78M 78M 0 100% /snap/core22/1122
/dev/loop4 squashfs 78M 78M 0 100% /snap/core22/1033
/dev/loop5 squashfs 364M 364M 0 100% /snap/gnome-3-38-2004/115
/dev/loop6 squashfs 57M 57M 0 100% /snap/snap-store/558
/dev/loop7 squashfs 13M 13M 0 100% /snap/snap-store/959
/dev/loop11 squashfs 97M 97M 0 100% /snap/gtk-common-themes/1535
/dev/loop10 squashfs 43M 43M 0 100% /snap/snapd/20671
/dev/loop8 squashfs 132k 132k 0 100% /snap/bare/5
/dev/loop9 squashfs 522M 522M 0 100% /snap/gnome-42-2204/141
tmpfs tmpfs 3.4G 17k 3.4G 1% /run/user/125
tmpfs tmpfs 3.4G 46k 3.4G 1% /run/user/1000
/dev/sda1 exfat 1.1T 52G 949G 6% /media/user/PortableSSD
//IP ADDRESS/Name cifs 28T 16T 13T 57% /home/user/mount

11

Also how I have it set up right now is. My local computer is running storj and has the /storagenode on it. While my mount to a seperate place that is only harddrives has the /storage/temp on it.

Now looking at it they have different owners, how would I make it so they have the same owners? If I try and run chmod or chown on it, it just says permission denied to change owners (for the one with /storage/temp)

12

The network filesystems are not supported, only iSCSI can work normally.
I would suggest to run the node directly on this file server instead.

You may try to force it to work, but it will stop work sooner or later, so I would suggest to avoid it right away.

3 Likes
13

I don’t want to run it on the file server as I feel its uneccessary stress for it to compute that, I am currently running Sia like this with no issues and they seem to be fine, Also what is this config folder it keeps mentoning in the error log?

pieces error: filestore error: chmod config/storage/temp/blob-3346945828.partial: operation not permitted"

14

One more thing, this is how I changes the mounts to see if it would make a different. It did not… but still wondering what the config folder is becuase I can’t seem to find it anywhere.

--mount type=bind,source="/home/tye/mount/Storj/node/storagenode",destination=/app/identity \
--mount type=bind,source="/home/tye/mount/Storj/storjs_storage",destination=/app/config \
15

It doesn’t have access to this folder:

If you use --user $(id -u):$(id -g) option in your docker run command, you need to change the owner recursively to this user.

sudo chown $(id -u):$(id -g) -R "/home/tye/mount/Storj/storjs_storage"

Or you do not need to use this option, always use sudo to run the container and change the owner to root.
However, SMB will not work normally anyway, see Topics tagged smb, the same is for Topics tagged NFS.

1 Like