For what it’s worth, I’d be interested in this also. I use nothing but LUKS at home. DD and RAW is slow, would be great for FOG to handle the creation of the needed LVM pieces /w encryption. I’d like to figure it out, but that’s probably a year or more away for me.
Posts made by Wayne Workman
-
RE: Is there a way to make FOG compatible with LUKS encryption?
-
RE: FOG External Reporting
We’re at 534 dev installations of FOG that have reported wiithin the last week. We started tracking this about 10 months ago. Coming up on a year of version tracking.
-
RE: Migrate Fog on a new server
The old and new fog versions do not need to be the same version. The only restriction here is that you cannot downgrade. You can go from older to newer, but not from newer to older.
-
RE: FOG Install init.php permission
@rets34 What are the output of the following two commands?
ls -laht /var/www ls -laht /var/www/html
-
RE: Problems installing Fog client in OSX
@matthew-wyneken Are you using the right address for the fog server during installation? Can you do a
curl
orwget
of the certificate using Terminal on the MacOS system? -
RE: Lenovo T15 Gen2 Slow Imaging
@jconway1006 Need more information. Fog version, screenshot of the issue. Number of fog clients, FOG Client checkin time, FOG Server hardware specs. Where is the fog server in relation to the node being imaged? What’s the network speed between the fog server and the node being imaged?
-
RE: Force push storage node replication?
@tesparza This should happen automatically. If it’s not, you have some sort of configuration problem. There’s a replication log you can look at in the web UI. Check that for errors.
Also, there’s this article on the location plugin. While this is meant to cover location plugin functionality, it also explains default functionality pretty well. https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin
-
RE: Question regarding Snapin install order
@jyost Search the forums for
snapin order
. You’ll find several threads. Here’s one that probably will help:
https://forums.fogproject.org/topic/12784/snapin-order -
RE: REboot Server
@stu There’s a wiki article all about passwords: https://wiki.fogproject.org/wiki/index.php?title=Password_Central
Though, if you cannot log in via terminal or SSH, you might could try a Linux password reset boot utility. Use your favorite search engine to search for
reset Linux password
. Highly advise to backup / create snapshot before trying anything you find. -
RE: REboot Server
@stu If you have terminal access, log in, and just type
reboot
-
RE: FOG 1.6 Locations Causing internal server error
@brmitmhart have you tried downgrading? Backup your DB first.
-
RE: Storage nodes or Master nodes?
@george1421 said in Storage nodes or Master nodes?:
Storage nodes can only send images via unicast images.
What’s the technical reason for this? Just wondering. Like, why can’t it be done? Or, has it simply not been implemented?
-
RE: Snapins on Windows 7 stays "Checked in"
@willingmost7 have you rebuilt your fog server? Or, is it possible the client installed in that Windows 7 image is super old? A while back (maybe years), fogproject replaced the certificate & signature in the client.
-
RE: Create Image via API
@makswojciech You might look here at the community contributed powershell modules, they might give you a good direction. https://github.com/FOGProject/fog-community-scripts/tree/master/PowershellModules
Though, sometimes it’s best to go look at the source code. Have a look-see at the files with the word
image
in their name here: https://github.com/FOGProject/fogproject/tree/master/packages/web/lib/fog -
RE: Boot iso from ipxe menu
@willingmost7 That’s just one way. There are lots of ways. This is pretty beyond my skill set. Luckily, @george1421 has done an excellent job producing this tutorial about the topic: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/8
-
RE: Could not resize (expandPartition)
@omegaxis Because the root cause seems to be identified, I won’t pursue recreating the issue. Ping me directly if you find this to not be true. I’d need to know your Linux system layout & sizes, as well as source HDD size and destination HDD size. I can replicate all this stuff using VMs.
-
RE: RHEL 8, CentOS 8, master branch, July 22, 2021
The difference between
dev-branch
andmaster
branch appears to be http vs https.Here’s the commit that made the change:
https://github.com/FOGProject/fogproject/commit/349a8fa2df00d82df857527b1cf45aa204363834Introduced in 1.5.9.58 of
dev-branch
-
RE: RHEL 8, CentOS 8, master branch, July 22, 2021
Today pictured below, for example. This is what normally happens. Master fails and dev-branch succeeds. Yet, dev-branch and master branch are executing against the same OS, same patch level. The way these tests are setup is - the VMs get a snapshot restored. Then they are patched. Then they get the specified branch installed. This is repeated for each branch. Fresh snapshot applied and fresh patching performed before every installation.
CentOS 8 Output for master branch: 2021-07-30_12-00-PM_output.log
CentOS 8 Error Log for master branch: 2021-07-30_12-00-PM_fog_error.log
dev-branch
fog_error output for CentOS 8:package remi-release-8* is not installed warning: /var/tmp/rpm-tmp.AVYE4j: Header V4 RSA/SHA256 Signature, key ID 5f11735a: NOKEY Retrieving https://rpms.remirepo.net/enterprise/remi-release-8.rpm Verifying... ######################################## Preparing... ######################################## Updating / installing... remi-release-8.4-1.el8.remi ######################################## Extra Packages for Enterprise Linux Modular 8 - 1.9 MB/s | 798 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 24 MB/s | 10 MB 00:00 Remi's Modular repository for Enterprise Linux 772 B/s | 858 B 00:01 Remi's Modular repository for Enterprise Linux 3.0 MB/s | 3.1 kB 00:00 Importing GPG key 0x5F11735A: Userid : "Remi's RPM repository <remi@remirepo.net>" Fingerprint: 6B38 FEA7 231F 87F5 2B9C A9D8 5550 9759 5F11 735A From : /etc/pki/rpm-gpg/RPM-GPG-KEY-remi.el8 Remi's Modular repository for Enterprise Linux 795 kB/s | 779 kB 00:00 Safe Remi's RPM repository for Enterprise Linux 1.6 kB/s | 858 B 00:00 Safe Remi's RPM repository for Enterprise Linux 3.0 MB/s | 3.1 kB 00:00 Importing GPG key 0x5F11735A: Userid : "Remi's RPM repository <remi@remirepo.net>" Fingerprint: 6B38 FEA7 231F 87F5 2B9C A9D8 5550 9759 5F11 735A From : /etc/pki/rpm-gpg/RPM-GPG-KEY-remi.el8 Safe Remi's RPM repository for Enterprise Linux 1.9 MB/s | 1.9 MB 00:01 bc-1.07.1-5.el8.x86_64 curl-7.61.1-18.el8.x86_64
master
branch fog_error output for CentOS8:package remi-release-8* is not installed warning: /var/tmp/rpm-tmp.fFeNbj: Header V4 RSA/SHA256 Signature, key ID 5f11735a: NOKEY Retrieving http://rpms.remirepo.net/enterprise/remi-release-8.rpm Verifying... ######################################## Preparing... ######################################## Updating / installing... remi-release-8.4-1.el8.remi ######################################## Extra Packages for Enterprise Linux Modular 8 - 4.7 MB/s | 798 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 32 MB/s | 10 MB 00:00 Remi's Modular repository for Enterprise Linux 568 B/s | 858 B 00:01 Remi's Modular repository for Enterprise Linux 3.0 MB/s | 3.1 kB 00:00 Importing GPG key 0x5F11735A: Userid : "Remi's RPM repository <remi@remirepo.net>" Fingerprint: 6B38 FEA7 231F 87F5 2B9C A9D8 5550 9759 5F11 735A From : /etc/pki/rpm-gpg/RPM-GPG-KEY-remi.el8 Is this ok [y/N]: Remi's Modular repository for Enterprise Linux 2.4 kB/s | 858 B 00:00 Error: Failed to download metadata for repo 'remi-modular': repomd.xml GPG signature verification error: Bad GPG signature bc-1.07.1-5.el8.x86_64 curl-7.61.1-18.el8.x86_64
-
RE: RHEL 8, CentOS 8, master branch, July 22, 2021
@sebastian-roth Yeah, today’s tests look like a mess. Though, what your saying about this GPG key. All the tests use the same OS, same patch level each day. If there was an issue with a GPG key in master branch, wouldn’t it be true that the same problem exists in dev branch? Most days, this is not the case. Most days, just master branch fail for CentOS 8 and RHEL 8.
There are ways to inject commands before installation, though the point of these tests is just to see in an automatic way if there are any issues that arise for a typical installation.