Group Details Private

Senior Developers

  • RE: FOG Update IPXE Issues

    @wkratky said in FOG Update IPXE Issues:

    Yeah still no joy. I am about to the end of my rope.

    Please tell us which commands you used? It’s pretty hard to read between the lines.

    I just did a test install using dev-branch. It did not fail on “Downloading kernel, init and fog-client binaries”!

    I could imagine old binaries still being in the fogproject tmp folder. So go to fogproject/tmp/ (or fogproject-1.5.9/tmp/ in your case) and delete all the files from that subfolder. Then re-run the FOG installer.

    posted in FOG Problems
  • RE: Deployment task loops when deploying a Windows image

    @devlinn said in Deployment task loops when deploying a Windows image:

    Failed to mount C :
    mount: can’t find /systemdisk in /etc/fstab

    As far as I know this is not part of the official FOG/FOS code base. Please see if you custom have post deploy scripts enabled that are causing this issue.

    posted in FOG Problems
  • RE: Raw image dd deploy error

    @gn_ro Not exactly sure why you run into this issue but looking through the code and searching the web for this error message I might have an idea what’s going on. After the deployment (through partclone.dd in this case) FOS looks for any NTFS partition, tries to mount it and see if it can modify registry files to change the hostname of the machine (pre Windows boot up!). This feature is called “early hostname change” and can be turned off. In the FOG web UI go to FOG Configuration -> FOG Settings -> section General Settings -> uncheck CHANGE HOSTNAME EARLY and save settings.

    Unfortunately this can only be turned on and off globally. Most people want to keep that turned on and so might you for most of your machines. But I think it’s appropriate for you to quickly turn it off whenever you need to deploy that special machine.

    posted in Bug Reports
  • RE: RHEL 8, CentOS 8, master branch, July 22, 2021

    @Wayne-Workman Figured that you can’t confirm the GPG key for REMI’s repo when running the installer in silent mode (confirm all questions). We do import the key via rpm --import ... via the installer script but turns out this is not enough when dnf is used because it uses a different gpg database “by design”: https://bugzilla.redhat.com/show_bug.cgi?id=1768206#c4

    Do you have some kind of mechanism in your test setup that allows to run some commands before the installer test? You might run this command on CentOS 8 and RHEL 8 for the time being.

    sed -i -e 's/dnf check-update/dnf -y check-update/g' /path/to/fogproject/lib/redhat/config.sh
    

    As I said, we work on the next release but can’t give you a date yet.

    Looking at the test results today we see that dev-branch fails on CentOS 8 and RHEL 8 as well. Strange error for RHEL 8:

    package remi-release-8* is not installed
    warning: /var/tmp/rpm-tmp.da0Ljt: 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           ########################################
    curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to rpms.remirepo.net:443 
    error: https://rpms.remirepo.net/RPM-GPG-KEY-remi: import read failed(2).
    

    And similar for CentOS 8:

    package remi-release-8* is not installed
    curl: (52) Empty reply from server
    error: skipping https://rpms.remirepo.net/enterprise/remi-release-8.rpm - transfer failed
    Retrieving https://rpms.remirepo.net/enterprise/remi-release-8.rpm
    

    And even CentOS 7:

    package remi-release-7* is not installed
    curl: (56) TCP connection reset by peer
    error: skipping https://rpms.remirepo.net/enterprise/remi-release-7.rpm - transfer failed
    Retrieving https://rpms.remirepo.net/enterprise/remi-release-7.rpm
    

    Probably a network issue…

    posted in General
  • RE: Chainloading failed

    @jherron Great to hear you figured it out. Well done!

    I was going to setup a test scenario to see if I can replicate the issue. But would have been very hard to figure out not knowing that you use the location plugin.

    posted in FOG Problems
  • RE: Partclone freezes or crawls after kernel update

    @dashwell Well that’s interesting! The logs you posted come from the FOG server, right?! That would mean the FOG server NFS daemon is playing up. Could be caused by the FOS client kernel confusing the FOG server NFS or it could be just the NFS daemon having an issue by itself.

    What Linux OS and version do you use as FOG server? Don’t think I’ve ever seen this before but we can try to replicate the issue if you let us know what exactly your setup looks like.

    posted in FOG Problems
  • RE: REFInd-Initializing - hangs

    @Trev-lchs Have you played with the mentioned refind.conf yet? Search the forum for more hints in this topic.

    Which versions of rEFInd have you tried? All of them?

    posted in FOG Problems
  • RE: Fog stalls curing capture upload

    @jim-holcomb said in Fog stalls curing capture upload:

    Not yet - but thought of moving the fog server to this building, which is where my new office is located

    Definitely try out moving the client towards the FOG server first, probably less work I would think.

    By the way, your Ubuntu and FOG versions are years old and out of support.

    posted in FOG Problems
  • RE: RHEL 8, CentOS 8, master branch, July 22, 2021

    @Wayne-Workman I am pretty sure I did a plain test install with 1.5.9 on CentOS 8 and it worked. Will try again.

    posted in General
  • RE: Very slow boot.php and bzImage during pxe boot

    @rodluz said in Very slow boot.php and bzImage during pxe boot:

    (gc64d)

    OK that’s definitely the current iPXE version I pushed to dev-branch not long ago.

    Thought that you might have different DHCP options set that might explain the issue. But doesn’t look like it.

    Hmm, you can try updating to dev-branch but I can’t think of a change we pushed since 1.5.9 that would explain what you describe. Anyhow, give it a go.

    posted in FOG Problems