• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Chris Whiteley
    3. Posts
    • Profile
    • Following 2
    • Followers 1
    • Topics 37
    • Posts 173
    • Best 6
    • Controversial 0
    • Groups 0

    Posts made by Chris Whiteley

    • RE: Post Init Script Issues

      @george1421 I already showed you right in the question I asked, but since you want to see it again:

      #!/bin/bash
      ## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
      ## <SCRIPTNAME> should be changed to the script you're planning to use.
      ## Syntax of post init scripts are
      #. ${postinitpath}<SCRIPTNAME>
      . ${postinitpath}patch.fullreg
      
      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Post Init Script Issues

      @george1421 I ended up figuring it out. I had 3 different locations in /images that had the “postinitscripts” folder which I thought was odd. I had it at the root of /images, inside of /images/dev and inside of /images/dev/dev/. I ended up copying the same things into those 2 other folders and now it is working. I am not sure where it is pulling from though.

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Post Init Script Issues

      @Sebastian-Roth The reason I know it’s not being used is because the changes I made are not happening during a full registration and the script “echo’s” are not there. Here is the patch.fullreg

      currfile="/bin/fog.man.reg"
      newfile="${postinitpath}fog.man.reg.fix"
      
      . /usr/share/fog/lib/funcs.sh
      
      echo "Testing path for our fixed file at ${postinitpath}fog.man.reg.fix"
      debugPause
      
      # Test path and run copy if found and matched.
      if [[ -r $newfile ]]; then
          echo "Found file preparing to copy"
          debugPause
          cp -f $newfile $currfile >/dev/null 2>&1
          [[ ! $? -eq 0 ]] && echo "Copy Failed" || echo "Copy Succeeded"
          debugPause
      else
          echo "Failed to find file sorry"
          debugPause
      fi
      

      This was borrowed from Tom Elliot’s post. I tried the very simple one first and that didn’t work, so I tried this one next and the same issue.

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • Post Init Script Issues

      I have FOG Server 1.5.9 and I was trying to customize my FOG reg menu.

      I followed this post: https://forums.fogproject.org/topic/9754/custom-full-host-registration-for-1-3-4 as I wanted to change a few things in my script, namely change the “other user tag #1” and “other user tag #2” to be different questions. I have updated that and created the “patch.fullreg” file in /images/dev/postinitscripts and the fog.man.reg.fix file that I downloaded from github and made my changes. It doesn’t ever look at the file when it goes through even though I have defined it in the “fog.postinit” file like this

      . ${postinitpath}patch.fullreg
      

      I am not quite sure what I am missing here…Is there a different version of the fog.man.reg file?

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Kick off Task by system mac address

      Okay, I will dig into this. Thanks!

      posted in General
      Chris WhiteleyC
      Chris Whiteley
    • Kick off Task by system mac address

      I was curious if there was a way to kick off a task from PDQ Deploy for a FOG image. I know that if you go to http://fogserver.domain.com/fog/management/index.php?node=task&sub=hostdeploy&type=1&id=1 that it should deploy.

      Is there a way to do this by mac address? I am just looking to be able to restart a computer with a command also start a FOG image deploy at the same time.

      Thanks,

      posted in General
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Sebastian-Roth This is not a new branch, just an upgrade and move from Ubuntu to Centos 7 as it is more stable when upgrading. The only thing I can do as far as getting closer is to move this computer into the server room, but since it is a desktop that would be a little cumbersome. These are juniper switches.

      For creating the schools’ base image, I use this same machine to do the work for all of them since it is pretty close to the “golden image” for each one. I am using this Dell Optiplex 7040. I create a legacy image (have some more impoverished districts with old machines) and a UEFI image.

      I have not tried different iPXE binaries and I wasn’t aware that you guys wanted me to do a mirror port. I will try and work on this today if I get some time.

      Thanks for the guidance.

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Sebastian-Roth I will not be able to login to the same switch as the FOG server as it is a VM in our data center. I am 3 switches down from the data center and don’t have issues with the other 5 schools I manage getting this to work. Same setup as this. I have a switch at my desk with multiple VLANs and that is how I get to do imaging for each district. Does that help paint a picture at all?

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Tom-Elliott Same issue with the [Connecting]… going across and failing, rebooting.

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Tom-Elliott I will do this right now and let you know the outcome.

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Tom-Elliott This is all I see

      2020-10-06_9-46-53.png

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Tom-Elliott

      [04-Oct-2020 03:47:02] NOTICE: error log file re-opened
      [04-Oct-2020 15:32:43] NOTICE: [pool www] child 26930 exited with code 0 after 138892.087835 seconds from start
      [04-Oct-2020 15:32:43] NOTICE: [pool www] child 15042 started
      [04-Oct-2020 15:32:50] NOTICE: [pool www] child 26795 exited with code 0 after 138950.201260 seconds from start
      [04-Oct-2020 15:32:50] NOTICE: [pool www] child 15045 started
      [04-Oct-2020 15:35:30] NOTICE: [pool www] child 27071 exited with code 0 after 138908.805085 seconds from start
      [04-Oct-2020 15:35:30] NOTICE: [pool www] child 15194 started
      [04-Oct-2020 15:39:14] NOTICE: [pool www] child 27318 exited with code 0 after 138879.587345 seconds from start
      [04-Oct-2020 15:39:14] NOTICE: [pool www] child 15486 started
      [04-Oct-2020 15:39:42] NOTICE: [pool www] child 27320 exited with code 0 after 138907.167868 seconds from start
      [04-Oct-2020 15:39:42] NOTICE: [pool www] child 15512 started
      [04-Oct-2020 15:41:12] NOTICE: [pool www] child 27405 exited with code 0 after 138913.195601 seconds from start
      [04-Oct-2020 15:41:12] NOTICE: [pool www] child 15600 started
      [04-Oct-2020 16:46:31] NOTICE: [pool www] child 31676 exited with code 0 after 138896.314150 seconds from start
      [04-Oct-2020 16:46:31] NOTICE: [pool www] child 19773 started
      [04-Oct-2020 18:49:32] NOTICE: [pool www] child 7284 exited with code 0 after 138870.684686 seconds from start
      [04-Oct-2020 18:49:32] NOTICE: [pool www] child 27795 started
      [04-Oct-2020 21:13:51] NOTICE: [pool www] child 16588 exited with code 0 after 138930.860352 seconds from start
      [04-Oct-2020 21:13:51] NOTICE: [pool www] child 4701 started
      [05-Oct-2020 08:34:51] NOTICE: Terminating ...
      [05-Oct-2020 08:34:51] NOTICE: exiting, bye-bye!
      [05-Oct-2020 08:35:31] NOTICE: fpm is running, pid 1089
      [05-Oct-2020 08:35:31] NOTICE: ready to handle connections
      [05-Oct-2020 08:35:31] NOTICE: systemd monitor interval set to 10000ms
      [05-Oct-2020 20:25:46] NOTICE: [pool www] child 1813 exited with code 0 after 42614.612041 seconds from start
      [05-Oct-2020 20:25:46] NOTICE: [pool www] child 16127 started
      [05-Oct-2020 20:27:04] NOTICE: [pool www] child 1811 exited with code 0 after 42692.732221 seconds from start
      [05-Oct-2020 20:27:04] NOTICE: [pool www] child 16220 started
      [05-Oct-2020 20:27:47] NOTICE: [pool www] child 3239 exited with code 0 after 42730.396625 seconds from start
      [05-Oct-2020 20:27:47] NOTICE: [pool www] child 16263 started
      [05-Oct-2020 20:27:51] NOTICE: [pool www] child 1812 exited with code 0 after 42740.360500 seconds from start
      [05-Oct-2020 20:27:51] NOTICE: [pool www] child 16273 started
      [05-Oct-2020 20:27:52] NOTICE: [pool www] child 1815 exited with code 0 after 42740.447148 seconds from start
      [05-Oct-2020 20:27:52] NOTICE: [pool www] child 16275 started
      [05-Oct-2020 20:28:04] NOTICE: [pool www] child 1814 exited with code 0 after 42752.756222 seconds from start
      [05-Oct-2020 20:28:04] NOTICE: [pool www] child 16289 started
      [05-Oct-2020 20:29:55] NOTICE: [pool www] child 1939 exited with code 0 after 42862.776461 seconds from start
      [05-Oct-2020 20:29:55] NOTICE: [pool www] child 16407 started
      [06-Oct-2020 07:03:34] NOTICE: Terminating ...
      [06-Oct-2020 07:03:34] NOTICE: exiting, bye-bye!
      [06-Oct-2020 07:03:52] NOTICE: fpm is running, pid 1061
      [06-Oct-2020 07:03:52] NOTICE: ready to handle connections
      [06-Oct-2020 07:03:52] NOTICE: systemd monitor interval set to 10000ms
      
      
      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Sebastian-Roth

      The error on the screen is the same one that I have posted below in this thread. Here are a couple of more pictures about it.

      IMG_0050.JPG
      IMG_0051.JPG

      It is connected through 3 different switches, but I have not had issues with this before. They are also on the same subnet: 192.168.20.1/24.

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Sebastian-Roth It just had a connection thing with my browser. At least that’s what I think it is.

      192.168.20.9 - - [06/Oct/2020:08:43:58 -0700] "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 4350 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"
      
      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Sebastian-Roth This is what I saw:

      192.168.20.41 - - [06/Oct/2020:08:37:18 -0700] "POST /fog/service/ipxe/boot.php HTTP/1.1" 200 652 "-" "iPXE/1.20.1+ (g4bd0)"
      

      192.168.20.41 is the client

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @Sebastian-Roth I just make SELINUX disabled. It was set to permissive. That didn’t make a difference.

      • I tried using a different machine, but all we have are Dells, but I tried 3 different models and encountered an issue where it would sometimes download the bzImage, but then get to init.xz and do the [connecting]… that goes across the screen and then fail.

      • I downloaded the iPXE binaries and that didn’t help either.

      Is there a log I can look at specifically for this issue?

      Thanks for the help!

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @george1421 I just tried that command and got:

      Could not start download: Operation not supported (http://ipxe.org/3c092003)
      
      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @george1421 The bzImage file downloaded when I clicked that link. Yes, the IP is 192.168.20.9.

      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • RE: Fresh Install of 1.5.9 with CentOS 7 issues

      @george1421

      #!ipxe
      set fog-ip 192.168.20.9
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.20.9/fog/ consoleblank=0 rootfstype=ext4 nvme_core.default_ps_max_latency_us=0 mac=18:66:da:4a:79:d9 ftp=192.168.20.9 storage=192.168.20.9:/images/dev/ storageip=192.168.20.9 osid=9 irqpoll hostname=207521-test chkdsk=0 img=Windows10EDU-2004-Template imgType=n imgPartitionType=all imgid=16 imgFormat=5 PIGZ_COMP=-6 adon=1 addomain="******" adou="" aduser="*****" adpass="*****" hostearly=1 pct=5 ignorepg=1 type=up
      imgfetch init_32.xz
      boot
      
      posted in FOG Problems
      Chris WhiteleyC
      Chris Whiteley
    • 1
    • 2
    • 3
    • 4
    • 5
    • 8
    • 9
    • 3 / 9