1.6.0-alpha.1377 not showing available images on host

[JJ Fullmer]

@Tom-Elliott @sideone @MatMurdock
I can confirm this is fixed in the latest

[sideone]

Not working for me, I’m getting chainloading failed once I select the image I want to deploy.

[Tom Elliott]

@sideone That 500 means I will need your error log.

Assuming you’re using ubuntu it will be in:

/var/log/apache2/error.log I believe.

Assuming redhat version:

/var/log/php-fpm/www-error.log

[sideone]

@Tom-Elliott sorry - was out of office yesterday. Have attached error log. Thanks!

www-error.log

[Tom Elliott]

@sideone No problems, it seems (based on what I can tell), you are having issues with getting files off the server possible.

That error is trying to get the files for snapins, logs, or images. (It’s a common function)

but the response is returning nothing.

Specifically the url to get it would be:
‘<schema|http|https>://<FOG-IP>/fog/status/getfiles.php?path=<path to get items>’

So if you’re willing in a browser try to acces probably /images/

[sideone]

http://<FOG-IP>/fog/status/getfiles.php?path=/opt/fog/snapins brings back a list of my snapins

Code blocked by spam filter

http://10.16.46.84/fog/status/getfiles.php?path=/images brings back a list of my images

Code blocked by spam filter

So that looks OK for both. If there’s a trailing / at the end of that URL, I get an empty set back.

[Tom Elliott]

@sideone Can you look at your storage node list and validate that the image paths on all of them, do not have that trailing slash?

I suspect the DB is storing with the slash and that’s returning the empty set you’re seeing which is why you’re seeing the error.

I can try to take care of that myself as well, but for the moment, it will help with suspicions of the cause you’re seeing.

[Tom Elliott]

@sideone Assuming that was the case, I have pushed code that should try to right trim the directory seperators from the paths being looked for.

Hopefully that might help you as well.

[sideone]

Hi @Tom-Elliott, sorry for the delay. One of my storage nodes has failed in the update to 1.6, would this be the cause of the error?

EDIT: I’ve turned off the faulty storage node and it seems to be working correctly now. I guess I need to fix / rebuild the storage node! Thanks for the assistance.

Not sure if there’s a better thread / place for this, but what’s the optimum specification for a master server. The UI is often quite slow to load, does throwing more cores or RAM at the server help at all?

[Tom Elliott]

@sideone So 1.6 should be pretty speedy on even pretty (generally) basic specifications.

I use a dual core / 4gb tester laptop (cost $130 lol) for “showing” and simplistic development right now and it runs perfectly fine for the UI loading.

Now, we have heard occasionally people have UI loading slowdowns when they’re suing FOG Client in their environment and the number of machines and check in times are just too frequent for the FOG Server to keep up and respond to all of them.

In those cases, I don’t know if any amount of vertical scaling would help until you add a larger network interface.

[sideone]

@Tom-Elliott said in 1.6.0-alpha.1377 not showing available images on host:

Now, we have heard occasionally people have UI loading slowdowns when they’re suing FOG Client in their environment and the number of machines and check in times are just too frequent for the FOG Server to keep up and respond to all of them.

Sounds about right, I’ve turned it to 5 minutes but maybe I’ll try it at 30 and see what happens. We have about 1300 host entries (although they’re probably not all active now) but most should be off during the summer holidays. Thanks