Posts made by Wayne Workman

@mechalas Please see the NFS section of the .fogsettings documentation, and set it to not overwrite your exports file:

https://wiki.fogproject.org/wiki/index.php?title=.fogsettings#NFS

@Sebastian-Roth there appears to be an /etc/exports.d functionality I’d suggest looking into. Maybe fogs config can be put into its own separate file:
https://serverfault.com/questions/910827/how-do-i-use-etc-export-d
Because this would be an improvement and not a break-fix, I’d suggest backlogging this until more pressing things are sorted.

@moderators @developers is there a curl or wget command he could run to attempt to manually download the latest init? Doing this manually may more directly reveal any potential problems.

Also, sometimes an organization’s web filter / web proxy / content firewall really messes with this step. Be sure that fogproject.org is whitelisted in any of those.

@jemerson93 Read the sysprep section here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

It’s probably going to be two weeks or longer before I can adjust the daily tests - I’m super busy this weekend, next week, and vacation is the week after. But I’m pretty confident I can test upgrades. At least upgrading from the last release.

I’ve thought about testing upgrades, I don’t think it’d be too tough. Basically, I’d add 6 more instances - all the same OSs already being tested. But I’d install the last release of FOG on them - and then snapshot.
That way, the original 6 still have clean snapshots and would be labeled as ‘clean’, and the other 6 would have a fog installation on them and be labeled as ‘upgrade’. All the other commands remain the same I think.

@Sebastian-Roth you can use our slack project to test.

@george1421 said in FOG 1.5.6 Officially Released:

Why not setup both http and https in apache.

I’d say that’s a good idea.

I’ve added Fedora 30 to the daily installation tests, you can see results in my signature. Seems to be going good. After a couple days, I’m going to be removing Fedora 29 from the tests to keep costs down. Also, I’ve added some documentation on how to add a new OS to the daily tests. If anyone was curious, running the tests once per day for a full month costs about 20 USD.

It’s worth noting that FOG is open source and runs on Linux and Apache. There’s a thousand articles on the internet about applying SSL to Apache. Anyone can secure their FOG installation with a self signed cert, or an organization-trusted cert. One could even say that securing things with SSL is the admin’s job.

@george1421 said in FOG 1.5.6 Officially Released:

Now if fog could use one of those fee root traceable ssl certificates (like from lets encrypt) and then created the FOG SSL certificate using that then the IT admins would not get the browser nag messages.

using Let’s Encrypt for FOG installation wouldn’t work in >98% of cases because those fog servers are not open to inbound traffic from the internet. They couldn’t pass the DNS http challenge/response.

Mostly, FOG is used at universities and public school districts. While I can see a university maybe already having a self-signed cert installed in the OS’s trust store, it’s not my experience or observation that public schools do this. While I’m 100% fully on-board with end-to-end encryption all the time everywhere, I feel it’d only be an unwanted hurdle to jump for most FOG users that are just trying to get some computers imaged.

Perhaps it could be made easier to setup SSL, rather than forcing it? Perhaps make it optional, and defaulting to ‘no’.

At any rate, this is just my 2 cents.

This is really great, way to go FOG team!

@pdit does ip addr not work?

@Junkhacker just going off of the below quote. Are you suggesting a conversion tool would have no utility?

@Sebastian-Roth said in The future of partclone and therefore FOG as it is:

What that essentially means is that if we also move forward and add Partclone 0.3.x to FOG that would break all existing images I reckon (not tested yet).

@michaeloberg right click the installer-> run as -> administrator
Does that work?
Also try turning off any antivirus, if turning off AV works, you’ll need to create a permanent exception in your AV.
Also ensure your supplying the installer with the correct fog server dns address, or (less desirably) the correct ip.

@pdit ok that’s odd, you should just supply the correct interface name to the installer when it asks that question.

Would you mind sharing the output of these command please, so that we might see what’s going wrong?
ip addr
ifconfig

@pdit what do you mean port? The installer should suggest an existing network interface name. If it’s a wrong name, type the right one in.

Didn’t read all the responses, has anyone volunteered to build a tool to convert old images to the new format?

@carmonj probably an ftp credential problem, just guessing. This maybe will help: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

You need to very closely pay attention to the end of the capture for errors. Record it on video with your phone if you need to, because we would need the exact errors to best help you.

@Sebastian-Roth said in Issues after changing server IP:

Hint: I think the great changeIP script does not handle dnsmasq config changes as this is not a standard setup.

Correct, it doesn’t.