• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Tom Elliott
    3. Posts
    • Profile
    • Following 27
    • Followers 80
    • Topics 116
    • Posts 18,782
    • Best 2,568
    • Controversial 0
    • Groups 0

    Posts made by Tom Elliott

    • RE: PXE Boot Error - "Kernel Panic" Issue "XZ decompressor ran out of memory"

      @lperoma @fabritrento Please try updating dev-branch to the latest version.

      I have added some additional checking.

      Granted 32 bit binaries should be able to work without problem but alas it seems there’s an issue currently.

      The latest dev-branch tries to address this by taking account of the buildarch of the ipxe binary being i386, but the CPU architecture being 64 bit. I need testing please of course if both of you wouldn’t mind?

      Thanks in advance.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG Very Slow to Deploy Image - Lenovo Neo 50Q Gen 4

      @Quintin-Giesbrecht basically I think this is something in the kernel, but what it is we don’t have enough information yet. It’s possible a newer kernel might help.

      Then again it could be something like:
      https://forums.fogproject.org/topic/13620/very-slow-cloning-speed-on-specific-model/105?_=1729271500055

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG Very Slow to Deploy Image - Lenovo Neo 50Q Gen 4

      @Quintin-Giesbrecht We have seen this in the past, though I’ve kind of been out of the loop for some time.

      I believe this is specific to the kernel and the way it deals with paging and block size.

      a63d8062-1d09-43e9-b4de-b5b00b34ef5b-image.png

      While this is a very old image now, This was effectively the problem.

      Basically, what I found back here was that the page_size value being less than the disk size was causing issues by defaulting to anything less than the 4k sector. So if page_size - 1 was less than 4096, default the page size to 4096 to maintain 4k structures.

      Now we may need to revisit this, but i’m not so certain. Even this method could be wrong.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Snapins not deploying: Illegal characters in path.

      @sideone If you’re willing to try the latest pull?

      I’m trying to do it while having the new features of location plugin that were added in dev-branch. I apologize for the many iterations, but I think it should work now as I have failsafes in place too now.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Snapins not deploying: Illegal characters in path.

      @sideone I’ve pushed another fix that I think might help here and it takes a slightly different approach albeit similar.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Snapins not deploying: Illegal characters in path.

      @sideone You use location plugin, correct?

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6.0-beta.2134 - Host won't add automatically

      @sideone I just pushed what I hope might help with this. I cannot guarantee it will fix it, but it should give more forward progress.

      posted in Bug Reports
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6.0-beta.2134 - Host won't add automatically

      @sideone So I see it getting invalid host, then trying to register.

      Is there, by chance, a php-fpm log around the same time?

      Specifically hoping to see an error or even a warning.

      Is there anything after the registration attempt?

      posted in Bug Reports
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6.0-beta.2134 - Host won't add automatically

      @sideone I don’t believe this is a bug in FOG 1.6.0 specifically, I suspect, you’d run into a similar issue using any other version just as much as this 1.6.0

      That said, the issue is Invalid host.

      Are you not seeing this host show up in “pending”? IIt might be one of the mac’s this machine is sending is registered to another machine that’s in a pending status?

      posted in Bug Reports
      Tom ElliottT
      Tom Elliott
    • RE: I am getting stuck on `EFI Stub`

      @RocksAndRolls @Scraggly8046

      Try follow this information please:
      https://forums.fogproject.org/post/155885

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: The image deployment is slower than before

      @Cristian 1000GB a minute? I’ve seen 20gb a minute, and that is really saying something.

      10GB a minute is still well above a typical (generally in my eyes) “normal” speed deployments.

      So i’m not really sure where to go.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: lightdm user detected, wont change hostname

      @AUTH-IT-Center That is correct. That’s what that FOG Settings item is meant to do. If that is checked, on registration it should set that flag on future registrations, but it doesn’t on existing hosts that were registered before it was checked. If after this is checked and a new host registers and this isn’t working, I would believe there to be a bug.

      Though a workaround exists, so while, it would be a bug, it may not be the biggest concern to get fixed immediately over say actual imaging issues.

      posted in Linux Problems
      Tom ElliottT
      Tom Elliott
    • RE: lightdm user detected, wont change hostname

      @AUTH-IT-Center hostEnforce falls under the UI for AD stuff because initially this was thought to only be required for Domain Joins (as hostname, restart, domain join, restart) would generally be the order of things. Then we extended the client to work on Mac OS and Linux. However, we just never moved the “enforce” changes.

      Why? Domain joins for all systems also require reboots, so this “checkbox” is needed for both AD stuff and just baseline Hostname changes.

      posted in Linux Problems
      Tom ElliottT
      Tom Elliott
    • RE: lightdm user detected, wont change hostname

      @pilipp_edv I don’t know. The hosts don’t have that thing checked. Maybe there’s a bug, but I don’t know.

      What I do know is that the individual host is supposed to have it checked. I thought the value there effectively worked as a global toggle.

      posted in Linux Problems
      Tom ElliottT
      Tom Elliott
    • RE: lightdm user detected, wont change hostname

      @pilipp_edv That’s the same thing.

      In the DB the actual name is FOG_ENFORCE_HOST_CHANGES, and for 1.5.x we tried to do some fancy things by replacing _ with and removed the first FOG

      posted in Linux Problems
      Tom ElliottT
      Tom Elliott
    • RE: lightdm user detected, wont change hostname

      @pilipp_edv FOG Configuration Page -> FOG Settings -> FOG_ENFORCE_HOST_CHANGES will set this globally, though for existing hosts it may need to be enabled as well.

      If this is okay for all hosts, just create a group -> add all hosts to the group -> then set up things in the same way from the group to enable this setting for all hosts that already exist.

      posted in Linux Problems
      Tom ElliottT
      Tom Elliott
    • RE: TFTP Problems After Update

      @kenneth-sisco These are the packages installed on a fresh system generally:
      attr bc curl dhcp-server gcc gcc-c++ genisoimage git gzip httpd jq lftp m4 make mariadb mariadb-server mod_ssl mtools net-tools nfs-utils openssl php php-bcmath php-cli php-common php-fpm php-gd php-json php-ldap php-mbstring php-mysqlnd php-pecl-ssh2 php-process syslinux tar tftp-server unzip util-linux-user vsftpd wget xz-devel

      I think the relevant one is tftp-server. Why i tgot removed is a bit strange in my opinion, but hopefully this helps.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Capture UEFI image on hyper-v VM

      @Baessens Unforutnately the EFI stub: Measured initrd data into PCR 9 seems to be hitting us a lot lately and I don’t know why or what’s causing it.

      I have heard mixed results of using older kernels, and sometimes newer ones fix it for the person. Not really sure what will be the right case here.

      From FOG UI you can downgrade the init based kernel by FOG Configuration -> Kernel Update.

      Please try some of them and let us know, if any, which works for you.

      6.1.89 was one (20240430_1) was one that seemed to work for somebody. Maybe there?

      The configs don’t change much between newer version, but we were seeing similar errors using the 6.1.22 version. This leads me to believe something was added to the kernel code, potentially removed, then re-added to it later. Just a suspicion I have.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Number of snapins appears limited in PXE boot environment

      @David-Scott I see what you’re asking, but if you press enter, it will display the next set in the list. If you enter in an ID and then press enter it will go to the next step assuming you wanted whatever value you entered as the id (or ids) associated to the host you’re registering.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Number of snapins appears limited in PXE boot environment

      @David-Scott I’m. Or sure I follow the problem. The max displayed per page is defaulted to 20. Once that cap is hit it says “Press enter to continue or enter the ids you’d like to add” or something like that. Are you unable to hit enter to see the rest of the list?

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • 1
    • 2
    • 6
    • 7
    • 8
    • 9
    • 10
    • 939
    • 940
    • 8 / 940