• 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,783
    • Best 2,568
    • Controversial 0
    • Groups 0

    Posts made by Tom Elliott

    • RE: Can't search client list

      When you’re searching it’s attempting to find the reference data in the images, inventory, and hostOS field. If those fields are blank, I’d imaging it would be rather tough to find all that data.

      You could attempt a manual search to see if you find any data.

      Look in the file {fogwebdir}/lib/HostManager.class.php for the search function. It will display the sql you need to test first.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      r1150 released.

      Should truly fix inventory deploy bug.

      Was awaiting ##@GO but being sent ##. All the other scripts referencing the Post_Wipe.php file were requesting ##, so made the change to the script (fog.auto.reg) and updated the init.gz

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Can't search client list

      It sounds like data isn’t where it should be.

      Do all systems have OSID, ImageID, Inventory, the correct MAC’s, etc…?

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Can't search client list

      What version of fog?

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Failed to mount NFS Volume.

      locate nfs-common if you have locate and updatedb ready.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Dell Optiplex 755

      My guess is your trying to image using MBR, but the Drives are partitioned through GPT. Just saying, check it out.

      posted in Hardware Compatibility
      Tom ElliottT
      Tom Elliott
    • RE: Problem with separate NFS Server

      It looks like you only allow the ip listed there to access the NFS can you try changing the ip to a * and restart the Nfs service?

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      r1149 released.

      Should fix issue with ntfsresize once upload is complete.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      What revision are you on?

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      r1147 released.

      Fixes an issue in fog.upload where I was supposed to check if sector 63 is not the case, but actually but if sector 63 is the case.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      r1146 should fix these issues. As always, if you notice anything else, please let me know.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      Found the issue with deployed inventory update.

      fog.auto.reg was trying to send a variable ${mac_deployed} if the fog script is deployed from the FOG GUI, the inventory appears to update appropriately, but the scripts, if deployed, tries to send an unset variable. Added to the fog.auto.reg script now is the mac_deployed variable.

      Now I found another bug doing this. When the inventory is performed, it performs it like it’s a new host. This means it actually resets, to an invalid, hostID and hostname.

      I’m testing once again to make sure this works as expected as we speak.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      FOG_PIGZ_COMP is now included in the FOG Web GUI as a range input field. The range is from 0 to 9.

      0 means worst compression, and should mean the fastest upload speed with the largest amount of disk space in use.
      9 Means the best compression, but slower upload speed.

      I don’t want to remove the field as the FOG Upload Scripts rely pretty heavily on it.

      I don’t know what’s causing the FTP issue you’re seeing as I’ve not yet seen the error myself. Maybe provide some more information about the type of image it is. Specifically if it’s Multi-Part, raw, or Resizable.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      I’m starting to think it’s because the mac address is sent during image task creation. Meaning the mac being set within a script isn’t working properly. Specifically, the inventory task from the gui starts the fog.auto.reg script. I’m thinking the mac variable within that command isn’t working properly. If I go to debug and run this script, all seems perfectly fine. Can you try the same?

      Boot your client into Debug mode (no tasks).

      Once at the command prompt type:
      fog.auto.reg and press enter.

      Does it still fail?

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      I’m guessing this mac thing is to be expected. The inventory.php file uses the base64_decode for the MAC Address. It appears the bas64 command being sent for one of these jobs is not working properly. I don’t know why yet though. Maybe because it’s expecting something else for the mac address?

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      r1145 released.

      Fixes an issue where if the state of the multicast task is in-progress, it will kill the task, but not remove it. We don’t want that, so this has been corrected. If it’s complete, or canceled, the task gets killed properly.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      fog.download found an issue with multicast. I stored the command in a variable and needed to eval it first.

      r1144 released as a fix for multicast download. MPS is working now. Haven’t fully tested SDR. MPA isn’t tested either as it’s usually taken care of and only has one extra step but is basically the same as MPS.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      r1143 released.

      With it comes a notice:
      [B]FOG SCRIPTS ARE IN ALPHA/BETA TESTING ONCE AGAIN.[/B]

      init.gz is perfectly fine by itself but I’ve rewritten the main fog script. Three new files (besides fog.bkup2 which is the original fog script) are included to help me with managing what goes wrong where.

      fog.checkin performs checkin tasks for download, upload, and multicast. I Have test this and it works for download/upload, haven’t yet tested with multicast checkin, though it should work as it’s a part of the download checkin anyway.

      fog.upload, I’ve tested single disk resize and single disk multi-part functions. It should work as well. I’ve also dabbled, a little bit, with the raw upload at it too seems to work fine.

      fog.download, I’ve tested single disk resize download and a minor single disk multi-part test. Don’t know if mps (single disk multi-part) is working properly though I haven’t seen any major issues thus far. I’ve not tested anything dealing with multicast yet.

      As a side note, it appears the fstype is working as expected now, though I haven’t had a proper chance to verify this is the case.

      As I test various things and notice issues, as always, I’ll update and figure out a fix. If you haven’t noticed by now, I’m working in a progressive aggressive pattern now. I find an element that is “broken/borked” and work it out until I have a fix in place.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Latest FOG 0.33b

      I’m working on a fix for this issue as I’m well aware of it already. My fix is basically rewritting the fog scripts and adding an upload and download script, to separate the code base slightly for easier management. I’m still testing it.

      In the mean-time, Find the lines that deal with setting the fstype variable in the FOG Scripts, and make sure they’re using double quotes rather than single quotes, I don’t think Shell scripts like single quotes to identify strings the same way php does, which may be what’s causing the issue.

      @VincentJ,

      Does your system have multiple MAC’s? You can check what’s being sent to the inventory.php service file from your access log file. Chances are, I’m only guessing, is it’s sending the data as something like:
      inventory.php?mac=00:01:ab:2c:3f:1b%7C00:01:ab:ac:af:ff which would explain why it’s not liking the MAC Format.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Unable to find bypass.gz file

      I don’t have the file directly, but it’s on the wiki:
      [url]http://fogproject.org/wiki/index.php/Bypass_Host_Registration[/url]

      posted in General
      Tom ElliottT
      Tom Elliott
    • 1 / 1