@george1421 Figured. Thanks. Can you mark this solved? I can’t see where I can do it. I’ll open another post if I run into something else I think I need your help with. Thanks again for your assistance.

So is this solved?

With the postinit scripts messed up, deployment/capture will probably not happen. The postinit scripts are run first then tasking starts.

@zpoling said in Error capturing image after increasing drive size:

So if I ever encounter an error, should I go to the Wiki first and not the forums?

All of the standard troubleshooting we recommend for standard problems is usually documented in the wiki as best as we can.
This list has all of our troubleshooting articles:
https://wiki.fogproject.org/wiki/index.php?title=Installation#Troubleshooting

But there are of course nuggets spread all over the wiki.

@taspharel said in CPU Usage high:

In the long term the question remains: Why did that happen at all and is it related to our error regarding the web-gui “freeze” when looking at scheduled tasks?

Well it might be related as in the “freeze” might have been caused by the same “zombie” jobs. But I don’t really know.

Looking at the three tasks in the database again I see that all of them had stImageID zero. Don’t think that is valid. Not sure if that was causing it.

Had time to run the DB commands and that solved my problem. Thanks.

FOG Project is a new creature to me and despite the challenges I am really enjoying what it can do!

So, it’s still even in FOG 1.4.4…
If you want to deploy debian-based(mint in my case) distribs propertly, i made a
workaround, just copy-paste it in terminal(as root), change sda5 to your swap partition name, right before you get ready to made an image(before clicking the capture button). Then made a capture task and reboot the machine.
[CODE]
echo ‘#!/bin/sh’ > /usr/bin/fst.sh
echo ‘OLDUID=$(grep swap /etc/fstab |grep -v “#” |cut -d’ ’ -f1)’ >> /usr/bin/fst.sh
echo ‘NEWUID="UUID=$(ls -la /dev/disk/by-uuid/ |grep sda5|rev|cut -d’ ’ -f3|rev)"’ >> /usr/bin/fst.sh
echo ‘sed -ie “s/$OLDUID/$NEWUID/” /etc/fstab’ >> /usr/bin/fst.sh
echo ‘crontab -u root -l | grep -v ‘/usr/bin/fst.sh’ | crontab -u root -’ >> /usr/bin/fst.sh
echo ‘rm /usr/bin/fst.sh’ >> /usr/bin/fst.sh
chmod +x /usr/bin/fst.sh
(crontab -u root -l ; echo “@reboot /usr/bin/fst.sh > /dev/nul 2>&1”) | crontab -u root -

[/CODE]

https://www.pastiebin.com/5a36ef8163a91

@sebastian-roth

thank you . I will open a new thread and You can mark it as closed.

This is fixed in working branch.

@fall711 said in FOG offline installation:

The problem is that centos repo system use random host with different IP address and some are not allowed.

You can easily specify exactly what mirror you want to use by commenting out the mirrorlist directive inside of all the /etc/yum.repos.d/*.repo files and instead using the baseurl directive. Here’s a writeup on it, there are many others online too:
https://www.centos.org/forums/viewtopic.php?t=20390

Just pick a mirror nearby you, and explicitly define that. You will need to do the same for the remi repository as well:
https://www.centos.org/download/mirrors/
http://rpms.famillecollet.com/

There is never a problem that cannot be solved.

Although it has been awhile . . . . I discovered that FOG was “seeing” the OS drive as /dev/sdc. Once I changed the “primary drive” to /dev/sdc all functioned properly.

Thank you for your help on this problem (now solved.)

Thank you !!!

@andreiv and is it fixed?

Then you may need to reset the state of your environment.

git reset --hard
git checkout dev-branch
git pull
…

@olivier-c said in Roger.postdonload et variable environnement:

I would like to retrieve the value of the fog group to write in the firefox settings

You mean the group a host is assigned to I guess!? First, one host can be assigned to several groups so this could be an issue. Second, as far as I know this information is not handed to the client yet and I don’t see why we should do so. Third, you should be able to retrieve the information (group name) via an external API call from the FOG backend. Search the forum on how to use the API.

@jackiejack Right, I do have a tutorial for that already written up: https://forums.fogproject.org/topic/10450/adding-additional-image-storage-space-to-fog-server

@fredlenomade Looking great! Thanks heaps for the detailed explanation on this. The mono keystore is quite a problem on some systems. So it’s great to have this manual on how to make it work in CentOS!

@trebor said:

Capturing the screen “lsblk” output from a pxe client, I am not sure how to do? Suggestions?

Schedule a debug capture task for this client. Hit ENTER twice then you can run any command on the shell. Best if you can test mounting the RAID devices as well as getting a picture of lsblk from that shell so we see how FOG sees your system.

@gfontenot Once you fixed what is in the gui, then where you downloaded the upgrade files to, just rerun ./installfog.sh script again.

@sebastian-roth
Thanks that worked for it!

Thanks for staying on top of this, they never asked back, I guess they just accepted that thats something we needed. 🙂