While I’m super glad to have pushed up RC-25, I just wanted others to understand the idea.

The original issue is I switched over to a much less SQL tasking request system. Basically, the way things where (while much progress had been made originally anyway) very sql taxing. For a host, you might have had 12 separate SQL queries per each host to get the data.

I figured out a nicer mechanism around this, but missed two steps. While I was testing things, I was very minimally doing so just ensuring things were operational, not necessary “working” if that makes sense.

To fix this particular issue I basically had to have the class load itself again which doesn’t do much to get away from sql queries.

I’ve since fixed this issue, tested, and validated it’s operational and functional as well without the excess SQL queries which will be available for RC-26.

Just thought it’d be good to give everyone a heads up on it.

Thanks.

@Tom-Elliott worked like a charm sir

This is the same issue described here:
https://forums.fogproject.org/topic/8406/fog-client-printer-not-displaying

There isn’t a fix yet. The best you can do is deal with the FOG Client’s printer sensitivities.

I’ve also found that a FOGService restart helps a lot (reboot). For whatever reason, sometimes the fog client in my building just stops working for the duration of said computer being on, until the next reboot.

@Tom-Elliott Great! 🙂 Thank you!

Confirmed both and both are now fixed for the working branch.

@Tom-Elliott Thanks!

@Tom-Elliott said in Installation script error phpfpm:

@Claude-Girard And now? (Yes repull and try again.)

Yes it’s ok now.
Thank you

I agree.

@Duncan yes.

Is it possible to solve this thread yet?

I ask because I worked on a few systems last week, and they all seemed to have been getting their information and things appeared to be setting properly.

The noted items was if I manually stopped/started the FOG Service on the machines, the default printer setting would not happen, which is (as I recall it) expected as the default setter happens via the FOGUserService, not the FOGService element. When you manually stop the FOGService, the FOGUserService is closed to, but on FOGService start (manually) the FOGUserService is not automatically restarted.

Aha, that’s why I didn’t find that post in a search. Can’t keyword search attached pictures.

Changing mine to

FOG_URL_AVAILABLE_TIMEOUT = 3000

… fixed it for me. Thank you.

Ok, so the interface name wasn’t showing because somehow it was wrong in the storage node’s settings.

I never changed that… so that’s probably something broken with the auto-registering auto-correcting stuff @Tom-Elliott

< https://youtu.be/If3SXJeZzMQ >

I found the isEnabled issue. This was only present on new snapins. It’s fixed for RC-23 (while annoying it’s not as important as the functionality of the client which I’m more focused on anyway, among the other issues RC-22 was released to help correct).

Excellent! Good to know it wasn’t me! Updating now, much appreciated!

@Tom-Elliott Confirmation was made.

RC-22 officially released. Please update and all should be much more betterer.

Found and fixed for RC-22.

@Tom-Elliott
Yep i ran through your instructions and made any relevant changes but the thing that fixed it was adding the user back to mysql, not sure why it disappeared though.

@Tom-Elliott I think you can close, I had to clean registry on these computers but when my image is clean deployment is ok.