@Quazz Thanks heaps for digging into this even more. I guess it will be very hard to actually track down when and how this was introduced.

This problem is rare enough on its own already (personally haven’t come across it at all)

I would have said so myself a day or two ago. But then I even ran into the same issues when debugging a different partition layout problem for another user in my VM test setup (VirtualBox).

@jmeyer Sorry for the late reply. Couldn’t get to this any earlier. Is this still an issue for you? I have had a look at the code but can’t make sense of this yet. I suppose we’d need the start of the output - the first “Attempting to check in” output line to understand this.

But looking through it I have a feeling that maybe one of the settings is wrong in your setup. Please connect to the database and run the following query:

shell> mysql -u root -p Password: ... mysql> use fog; ... mysql> SELECT * FROM globalSettings WHERE globalSettings.settingKey IN ('FOG_DEFAULT_LOCALE', 'FOG_HOST_LOOKUP', 'FOG_MEMORY_LIMIT', 'FOG_REAUTH_ON_DELETE', 'FOG_REAUTH_ON_EXPORT', 'FOG_TZ_INFO', 'FOG_VIEW_DEFAULT_SCREEN'); ...

Get the full output and post here (as text or picture).

@Tom-Elliott Happy to help ! 😉

@Sebastian-Roth
I make new install of Fog under Debian.
I was using Ubuntu years ago so it’s old install (3 years old).

I have been testing Fog version since years with Tom.
And as i work with VM, i can revert change easily.

In a remote session we figured out that the database schema version was kind of oddly set. Still not sure why that was. Fixed that and applied the last couple of schema changes. That fixed a couple of odd issues including the Storage Node setting changes that can be done now again.

@Tom-Elliott
Strange. What’s even weirder is it started working once I entered into a forum thread… Now it’s working fine. LOL!

For what it’s worth, I’m running Ubuntu 19 and the Chrome Browser…

I’m OK with it since it’s working now. Can’t explain it though! Ha!

Thanks Tom!

@austinjt01 Ok that is a great starting point. I’ll again refer you to my tutorial: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

Look at the fog.custominstall script. Start with that script and then in this section add your code:

echo "Done" debugPause . ${postdownpath}fog.copydrivers # . ${postdownpath}fog.updateunattend umount /ntfs

Remove the call to the fog.copydrivers and fog.updateunattended and insert your code. At this point in the code /ntfs has been mounted onto the windows (C: drive) partition, wherever it may be. The script takes into account nvme vs sata as well as partitions being in different order or locations.

@EduardoTSeoane Sorry for the late reply. This is fixed in dev-branch already. Thanks @Fernando-Gietz

@Tom-Elliott I try the fix and its ok. Thanks for your works

Fixed in dev-branch.

@Quazz I´m sorry, I was sick for a long time. Now this day is my first day. I will test it if I have time. But I´m busy with an other project. I hope I can test it next week. Please don´t close this thread. Thanks

@Sebastian-Roth Thanks, its properly replicating now

@sourcaffeine said in FOG Client Not Working:

I am not exactly sure what was different but it seems to be working now without issue on the workstations with a new image with a new copy of the fog client installed.

The re-install does something very important. It pins to the current FOG server certificate and downloads the right FOG Project CA cert as well.

Thank you very much Tom for the info.

Hi, I’ve just looked into it, and it seems there’s potentially a bug that affects some PHP versions causing this problem. (The search page just fails with code 500 otherwise.)

I’ve made a PR to fix the problem here: https://github.com/FOGProject/fogproject/pull/299

@Tom-Elliott Thanks for the information.

You can see the code in this link:

https://github.com/FOGProject/fogproject/commit/501e2e947abe55f61fec434751e51e517dcba4d4

@Fernando-Gietz Hi.

No, I’m only using your plugins, the site one and the accesscontrol. I said, this is not a problem really, because if I add the user again, it is working.

Thx again.

@Sebastian-Roth
Cannot replicate the issue at the moment either. But I did an upgrade from 1.5.2. to 1.5.4. in the mean time.
Maybe this fixed it.

Please close it. If it reoccurs, I will show up again.

@sgennadi Thanks again for the report. Obviously I have missed out on purging php-mycrypt from the fogsettings automatically when we decided to not use that package for FOG anymore last Autumn. I just tested and pushed a fix to dev-branch. Please pull the latest and give it a try.