Updating Database failed! Failed to open stream!
-
@george1421 I just dragged 54bf64334d40 folder to images with no issues
-
@george1421 the original error appears to indicate it is trying to move 54bf64334d40 on the 172.16.220.246 though?
-
@Kevin-Talbot well this is a good one. It “should be” working.
In the storage node configuration for this remote node. The image path and ftp path point to
/images? -
@Kevin-Talbot said in Updating Database failed! Failed to open stream!:
@george1421 the original error appears to indicate it is trying to move 54bf64334d40 on the 172.16.220.246 though?
Ah that explains the not able to find the stream error. I’m looking at the kernel parameters from your post. I don’t see where its referencing 172.16.220.246. From the kernels parameters it should be interacting with 172.16.100.246
Can you post a screen shot of the storage node configuration for this remote node?
-
-
@Kevin-Talbot We may need to turn this back over to the developers since it should not be doing what its doing.
Just for clarity, are you using the location plugin to direct the clients to the proper storage nodes?
-
@george1421 said in Updating Database failed! Failed to open stream!:
proper storage nodes?
George you are the HERO thankyou !!!
So a long time ago we did use locations but stopped using them.
However, it appears a colleague has added a new location with the new node name attached and ticked the: Use inits and kernels from this node box…grrrrrr
I added the location to the host and restarted the capture and bingo all sorted!!!
Sorry to waste your time!
-
@Kevin-Talbot Well this is one for the record books.
As always, its the last place you looked is where the problem is found. We should have started looking in the last place first.
I’m glad you have it sorted out. Everything was pointing towards it should have been working…
-
@george1421 said in Updating Database failed! Failed to open stream!:
s it should have been working…
Always the way George unfortunately but we go there many thanks for your help!
-
@george1421 if I delete the one location will it just go by the image storage group default?
-
@Kevin-Talbot correct without the location plugin and locations being defined all target computers will use the main fog server for image capture. If you want to capture and deploy from storage nodes you need the location plugin, then assign the storage node and target computers to that location so everything stays local to the storage node.
-
Hello
I do not understand …
I have this problem but I find the plugin rental customers?
Thank you
