Topics created by Joseph Hales

@joseph-hales That article needs overhauled I suppose. Probably re-titled too. I’ll see what I can do.

@Joseph-Hales the new client always shipped with plain text passwords as the security model is fundamentally different.

@Joseph-Hales Ok, thanks for reporting back on this. Will mark this solved then. Feel free to open a new post on the AD issue if you can’t figure it out yourself.

There is a client update.

I remember you were the one that had load issues in the past. You’ll be relieved that the communications between the client & server have been reworked to be far more efficient. I think your load issues are behind you now.

@Joseph-Hales said:

It is likely that I am the only one who is trying to run SVN at this time most large shops won’t upgrade till final release.

And that is greatly appreciated, you’re helping support FOG just by running trunk in your organization and working with the developers on issues. People like you help make FOG releases solid for everyone else.

I created this script from various install files:

https://github.com/AdmissionRegret/utils/blob/master/fog-resetpermissions.sh

wget https://raw.githubusercontent.com/AdmissionRegret/utils/master/fog-resetpermissions.sh chmod +x fog-resetpermissions.sh

@Uncle-Frank I remotes in with Joseph last night. We fixed the issue. Basically he had a link in www and www/html. They both pointed at each other which was causing the problem.

@Tom-Elliott said:

You are running legacy client, so you would have to update all of the clients to receive these new configs?

set the interval for checkin
reinstall the legacy client on a computer.
copy C:\Program Files (x86)\FOG\etc\config.ini
push that file out as an update…

There is an option here:
Service Configuration -> Client Updater

This area will allow you to push out the new config.

Tom pointed me to the max_upload_size as well I should have remembered.

@Joseph-Hales I agree with the plan to solve the thread but not for the reasons you describe, rather for the fact this was likely somewhat related to the issues found earlier.

that fixed it thanks

4696 should fix this for you now.

Thanks for reporting.

Ok bit the bullet and restored a backup of the database seems to have fixed the issue I will keep an eye on how it behaves under load today.

i would add a note that it’s only specific versions of Ubuntu

I’m solving this thread. The reason your systems were failing to register wasn’t, specifically, a problem with FOG directly, but seemingly specific to this one system. Does this sound correct?

I’m gonna shelve this for a bit we break for vacation today when i get back I will hit this again and get all the logs posted.

You should be able to install a clean copy of FOG Trunk straight away on Debian 8.1 without any sort of prior installation.

The @Developers will need to answer your storage node question because I’m unsure.

No idea if this is the best way, but it seems to be working. I’ll let y’all know when it finishes compressing.

for f in *.img; do mv "$f" "${f%.img}-bak.img"; done for f in *bak.img; do pigz -d -c $f | pigz -9 > "${f%-bak.img}.img"; done

Here is what I have set currently. menu.png
Maybe it would be simpler to add a check box to add these to the advanced menu amd then check the login box there.

We’re not using the new client yet I upgraded to SVN 3463 this morning which fixed the missing client issue.