The Storage Groups associated storage node is not valid

[george1421]

Can you confirm that on your storage node Willy, that your images are in really in the /images folder. Depending on the size of the image and the connection speed it may take some time to replicate the images from your main storage node (typically your FOG server) to your remote storage node.

As far as I know you can only capture images to your main storage node. So I can understand why capture works, but deploy might not.

Is it safe to assume that you are also using the location plugin to allocate your storage node to a specific location that is different from your main storage node?

[raumin]

@george1421
yes, the image directory is /images .

My storage node is a QNAP Nas, everything was working well until an update, the paths are correct (/images), credentials are ok, the storage node is the “Master node”.
i can browse in the FTP.

I am not using the location plugin.

I suspect a problem in the database, i’m checking the tables…

[george1421]

OK, that tells me everything I need to know. You are not using a linux box for a FOG storage node. I ran into the same error when setting up a synology NAS as well as a windows server as a storage node. https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-fin/6
The newer versions of FOG makes some http web calls to the storage node (it didn’t do this with 1.2.0 stable). The storage node did not respond correctly to the master node so the The storage groups associated storage node is not valid error was thrown in my testing. If the @Developers could add an option to the function of master node so that if the storage node is not a linux server the master node would react like FOG 1.2.0 and just assume the storage node is functional.

This is only speculation since I have not researched the code to see where this error is actually being thrown.

[Tom Elliott]

@george1421 It’s probably simpler than all that. I can actually add back the FTP checks that were in place, in the case the node doesn’t return any data/error 404.

[george1421]

@Tom-Elliott With my testing everthing was in place on the windows storage node. All of the images where there, in debug mode the target computer could map to the windows storage node via nfs. I was just able to trap the http calls in IIS and it was about the same time the error was displayed on the target computer.

BUT I love simple fixes too.

[Tom Elliott]

@george1421 It’s simpler to check if any data exists in the return, and if not use FTP data to get the same info. Just a little bit more work, but should do the job nicely.

[raumin]

how can i fix it ? It’s a bit annoying

[Wayne Workman]

@raumin said:

how can i fix it ? It’s a bit annoying

Just wait, Tom is working on a fix. He will inform everyone here in this thread when it’s ready. It shouldn’t be too long.

[Tom Elliott]

@raumin what a bit while i work on it.

Sorry, I’m fast but i also have other things sometimes.

[raumin]

@Tom-Elliott

No problem Tom, i did not undestand that you were working on it

[Tom Elliott]

Readded the ftp checking. Please test and let us know.

[raumin]

@Tom-Elliott Yep it works great, thank you for this quick fix.

[george1421]

@Tom-Elliott Ok so this means I can restart the windows storage node POC again? Its not that I need this solution only to prove that it can or can’t be done. I was also working on the howto for synology and ran into the same roadblock.

[Tom Elliott]

@george1421 Yes.