Posts made by Wayne Workman

@dpotesta50 said in Resyncing FOG’s service account password:

We’re running 1.5.0.RC-8

Then in the ‘Getting FOG’ instructions, you need to use the dev-branch. dev-branch is currently 1.5 rc10.

@obsidian said in Fog Replication Not working:

Image replication is globally disabled

That’s probably the problem.

@dpotesta50 said in Resyncing FOG’s service account password:

If I updated the FOG program to the latest version, will it resolve my password issues?

Yep.

@dpotesta50 said in Resyncing FOG’s service account password:

If the app I’m running is an older version, will this install the latest version of the installation files?

Yes, but ‘latest version’ lacks context here. Fog has branches, which is explained in the ‘Getting FOG’ article. The master branch has the latest stable version, which is 1.4.4 as of December 2017.

@dpotesta50 said in Resyncing FOG’s service account password:

Is what your instructing me to do just deleting the installation folder to rebuild it, or the actual installed application?

This is just the installation files. the actual FOG installation is literally all over the OS in lots of other places.

@dpotesta50 Well my advice is solid, and all I can really do here is give you advice. Here’s the command to delete that directory:
sudo rm -rf /root/fogproject_git
After that, follow along with the “Getting FOG” article.

@dpotesta50 Just delete that directory and re-clone fog. Here are steps: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

@dpotesta50 I don’t think there is any more context than what I gave. sudo -i is how to properly become root. Here’s a copy of the manual for the sudo command: https://linux.die.net/man/8/sudo Look at the -i argument. It properly simulates a login. If you don’t pass a username argument, root is assumed.
You can learn Linux for free from internet sources, there are lots of tutorials (and this is how I learned mostly). For paid resources, I’d recommend acloud.guru https://acloud.guru/learn/lpic-1 (which I’ve also went through recently).

@dpotesta50 You should do all this stuff as root. Become root properly with this command: sudo -i

@dpotesta50 Yep.

@kktwenty101 said in upgrading to 1.4.x - fog client version?:

building a brand new FOG server to supplement the old one.

You can follow along with this article: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

These distributions have completed 73 successful clean installations in a row using their latest patches with the FOG master branch:

• CentOS 7
• Debian 8
• Debian 9
• Ubuntu 16

We’re still waiting for a single winner to rise above the rest. The race for most-stable distribution continues.

@lpetelik said in Login takes 5minutes+:

following for more solutions.

I wanted to tell you that you can disable the graph for all of the storage nodes, and this really does make login pretty snappy, but of course with this you no longer have graphs for all the nodes on the dashboard. With graphs disabled, you can still see tasks in Task Management.

Since the feedback has been positive, I’ve cross-linked the old ‘upgrade to trunk’ and ‘getting fog’ articles. I also ask that when people request instructions on getting fog installed, we reference the newer ‘getting fog’ article.

@dpotesta50 Set your desired password inside of /opt/fog/.fogsettings in the username and password fields, then just re-run the installer. The installer will look at .fogsettings and go fix everything else for you.

@maikbat Read through this entire thread: https://forums.fogproject.org/topic/9779/can-i-use-some-kind-of-script-to-create-image-and-ghost-my-lab-machines/12?page=2

@tmerrick Run these db maintenance commands and see if they help:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

@tmerrick Look at the power management schedules, and scheduled tasks also. Also, if there is any task waiting for a host, fog will send WOLs to that host every minute until it starts the task.

@imagingmaster21 Nope. But an extremely fragmented disk will cause resizing to take a very long time. The more fragmented, the longer it takes. Because resizing literally moves all the in-use data on a partition to the beginning of the partition so that it can then safely shrink the partition’s free space down.

@imagingmaster21 said in Windows 7 Image:

Are these settings right below:

That ZSTD compression rate is too low. Bump it to 9 or 11. Everything else looks good.