Docker warning unable to inject event On?

Node Operators troubleshooting
1

Hi, My Node keeps shutting down randomly! only error msg I can find is this:
[23:38:58.151][GoBackendProcess ][Warning] time=“2020-03-08T23:38:58Z” msg=“unable to inject event On:Dir Action:ChangeAttributes Path:“F:” Path:“STORJ STORAGE” Path:“storage” Path:“blobs” Path:“abforhuxbzyd35blusvrifvdwmfx4hmocsva4vmpp3rgqaaaaaaa” Path:“jp” InjectFilesystemEvent:true InvalidateCache:true for 56m40.0006706s”
[23:39:08.150][GoBackendProcess ][Warning] time=“2020-03-08T23:39:08Z” msg=“unable to inject event On:Dir Action:ChangeAttributes Path:“F:” Path:“STORJ STORAGE” Path:“storage” Path:“blobs” Path:“abforhuxbzyd35blusvrifvdwmfx4hmocsva4vmpp3rgqaaaaaaa” Path:“jp” InjectFilesystemEvent:true InvalidateCache:true for 56m50.0005356s”
[23:39:18.150][GoBackendProcess ][Warning] time=“2020-03-08T23:39:18Z” msg=“unable to inject event On:Dir Action:ChangeAttributes Path:“F:” Path:“STORJ STORAGE” Path:“storage” Path:“blobs” Path:“abforhuxbzyd35blusvrifvdwmfx4hmocsva4vmpp3rgqaaaaaaa” Path:“jp” InjectFilesystemEvent:true InvalidateCache:true for 57m0.0003075s”
[23:39:28.150][GoBackendProcess ][Warning] time=“2020-03-08T23:39:28Z” msg=“unable to inject event On:Dir Action:ChangeAttributes Path:“F:” Path:“STORJ STORAGE” Path:“storage” Path:“blobs” Path:“abforhuxbzyd35blusvrifvdwmfx4hmocsva4vmpp3rgqaaaaaaa” Path:“jp” InjectFilesystemEvent:true InvalidateCache:true for 57m10.0004962s”

Update: last few lines of Storj log below
2020-03-09T00:23:13.402Z INFO piecestore uploaded {“Piece ID”: “2Y7UQIGIBYQ7KFPFSWGNINAJ3HDFP4STDRTGZLLTSZX3ETSBDSWQ”, “Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “Action”: “PUT_REPAIR”}
2020-03-09T00:23:18.157Z INFO piecestore download started {“Piece ID”: “QRQYWUOTZBFJICD24PMUU4VZJKPOB2X3LDC4AL3ODKJD4LWGUNYQ”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “GET”}
2020-03-09T00:23:20.552Z INFO piecestore downloaded {“Piece ID”: “QRQYWUOTZBFJICD24PMUU4VZJKPOB2X3LDC4AL3ODKJD4LWGUNYQ”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “GET”}
2020-03-09T00:23:31.390Z INFO piecestore download started {“Piece ID”: “QRQYWUOTZBFJICD24PMUU4VZJKPOB2X3LDC4AL3ODKJD4LWGUNYQ”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “GET”}
2020-03-09T00:23:35.299Z INFO piecestore downloaded {“Piece ID”: “QRQYWUOTZBFJICD24PMUU4VZJKPOB2X3LDC4AL3ODKJD4LWGUNYQ”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “GET”}
2020-03-09T00:23:35.303Z INFO piecestore upload started {“Piece ID”: “M2XUXAGT4NDFF6BELCKVTDTGKWJIGQUKPY7VTD7KGTJ3DUU67JYQ”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT”, “Available Bandwidth”: 15860979058944, “Available Space”: 5749367456640}
2020-03-09T00:23:35.378Z INFO piecestore uploaded {“Piece ID”: “M2XUXAGT4NDFF6BELCKVTDTGKWJIGQUKPY7VTD7KGTJ3DUU67JYQ”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT”}
2020-03-09T00:23:36.020Z INFO piecestore deleted {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Piece ID”: “J7KHV2WKUO5QOKDNEHR4X6S6BNB3YSR5KZUDHOPMHS6ZNQKRACNA”}
2020-03-09T00:23:42.242Z INFO piecestore upload started {“Piece ID”: “CYR2USKYB2HPHZ4KU5E5GIWHEPR77HMGDT6JOQZ25M2IR2BECRZA”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT_REPAIR”, “Available Bandwidth”: 15860979058176, “Available Space”: 5749367457664}
P

Any Ideas guys?

2

Hello @Dave,
Welcome to the forum!
How is your storage connected to your PC?

What the type of filesystem on it?

3

As this question comes up really often, I suggest you check out my troubleshooting template:

And maybe consider pinning that in the troubleshooting section of the SNO subforum.

1 Like
4

Hi Alexey, thanks for getting back to me! My Storage is connected to my PC via a old IBM SAS PCI-E raid card with 4 x 2Tb SAS drives striped to make 8Tb drive, running on Windows 10 Pro 64bit NTFS with the latest stable version of the Docker 2.2.0.3(42716) and Storj version 0.33.4 and no VM machine.
update from Docker log:
[10:13:28.601][ApiProxy ][Info ] time=“2020-03-09T10:13:28Z” msg=“proxy >> HEAD /_ping\n”
[10:13:28.605][ApiProxy ][Info ] time=“2020-03-09T10:13:28Z” msg=“proxy << HEAD /_ping (4.0035ms)\n”
[10:13:28.621][ApiProxy ][Info ] time=“2020-03-09T10:13:28Z” msg=“proxy >> GET /v1.40/containers/storagenode/json\n”
[10:13:28.624][ApiProxy ][Info ] time=“2020-03-09T10:13:28Z” msg=“proxy << GET /v1.40/containers/storagenode/json (2.9984ms)\n”
[10:13:28.627][ApiProxy ][Info ] time=“2020-03-09T10:13:28Z” msg=“proxy >> GET /v1.40/containers/890f55379f947c47942d90750af8045629a919ab6d4ec9b16f89f596034e21b9/logs?stderr=1&stdout=1&tail=300\n”
[10:13:28.664][ApiProxy ][Info ] time=“2020-03-09T10:13:28Z” msg=“proxy << GET /v1.40/containers/890f55379f947c47942d90750af8045629a919ab6d4ec9b16f89f596034e21b9/logs?stderr=1&stdout=1&tail=300 (38.0005ms)\n”
[10:13:28.665][ApiProxy ][Info ] time=“2020-03-09T10:13:28Z” msg=“Cancel connection…”
[10:13:28.665][ApiProxy ][Warning] time=“2020-03-09T10:13:28Z” msg=“ignored error: The handle is invalid.”

5

Not a good idea to run a storagenode on a RAID0. I don’t know if your problem has anything to do with it though.

6

I know! it’s only temporary while i’m shifting and upgrading things. lol last month was my most stable of the lot, never went down once. Then I updated Windows 10 and the Docker at the beginning march and now it’s a bit odd, with the Docker just randomly turning off all containers and stopping my node. Saying that the last 14hrs it’s been fine!

7

You shouldn’t have updated docker at all.

8

That is not great security advise. Regardless on windows I would recommend migrating to the GUI install as it eliminates the need for docker.

9

I’ll have a go later. any good guides on moving from Docker to GUI version?

10

Yes, we have a guide on how to do that here:

https://documentation.storj.io/resources/faq/migrate-my-node#migrating-to-a-gui-install-on-windows

11

If you want to stick with a Docker for a while - then try to reset the docker from the docker UI (they hided it under “Troubleshoot” section, with icon looking like a bug).

12

Thanks! Node has been up now for 22hrs. I don’t really know why it’s stayed up for this long? maybe it fixed itself! If it happens again i’m moving to the GUI version.

3 Likes