• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. george1421
    3. Posts
    • Profile
    • Following 1
    • Followers 64
    • Topics 113
    • Posts 15,330
    • Best 2,777
    • Controversial 0
    • Groups 2

    Posts made by george1421

    • RE: FOG Registration; Host not registered

      @natsufiree said in FOG Registration; Host not registered:

      I see a conflict in what you say. I think we may have a language translation problem. So we will go slow.

      First you say your router does not support dhcp

      my router does not support dhcp.

      Then you say it is

      I am using the router for dhcp ip addresses.

      OK I understand (I think) your router is your dhcp server but you can not change anything on your router. FOG does have an option to work with a dhcp server you can not modify. You can load dnsmasq on your fog server to supply the missing dhcp pxe boot options. This works very well and will not change your dhcp router at all. The dnsmasq service will just hear the dhcp request from the client and add in the pxe boot information.

      We do have another option to usb boot into fog, but you will loose some features of fog. This is an option when you can not pxe boot your computers at all.

      posted in FOG Problems
      george1421G
      george1421
    • RE: FOG Registration; Host not registered

      @natsufiree OK, let me say you started wrong. But no worries we can get you pointed correctly again.

      Do you have a dhcp server on your network or are you using your router for dhcp ip address?

      If you are using your router for dhcp; does your router support optional dhcp settings like option 66 and option 67 or support pxe booting? If you don’t know can you tell me the model of your router?

      posted in FOG Problems
      george1421G
      george1421
    • RE: FOG Registration; Host not registered

      Ok lets start with your very fist picture.

      That is not a standard FOG ipxe boot.

      1. Where are you getting this iPXE ISO boot image from?
      2. ipxe.kern is not the right boot file.
      3. How do you have your network setup?
      4. Are you attempting to pxe boot this system?

      What do you have configured for dhcp options 66 {next-server} and dhcp options 67 {boot-file}?

      posted in FOG Problems
      george1421G
      george1421
    • RE: Can php-fpm make fog web-gui fast

      This is a continuation of this thread. This time I added memcache to store apache/php session data in ram instead of on the filesystem.

      1. Install memcache from the remi (repo added during fog installation)
        yum install memcached
      2. Edit the memcache config file
        vi /etc/sysconfig/memcached
      3. Add in -l 127.0.0.1 into the options parameter. We only want memcache to be available to the local system.
      PORT="11211"
      USER="memcached"
      MAXCONN="1024"
      CACHESIZE="64"
      OPTIONS="-l 127.0.0.1"
      
      1. Enable the memcached service to auto start
        systemctl enable memcached
      2. Start the memcached service
        systemctl start memcached
      3. Check to ensure memcached service is running in memory
        ps aux|grep memcached
      4. Check to see if memcached service is bound to the loopback adapter
        netstat -an|grep 11211
      5. Install memcache for php [note: many instructions on the internet say to compile php-memcache using pecl. I found that remi already has a package so compiling it was not necessary. I can’t say this will be the case for all distros]
        yum install php-pecl-memcache
      6. Update the fog php-fpm config file to tell php-fpm to use memcache to store session data.
        vi /etc/php-fpm.d/fog.conf
      7. Find these lines at the end of the config file and comment them out
      php_value[session.save_handler] = files
      php_value[session.save_path]    = /var/lib/php/session
      
      1. Uncomment these lines
      ;php_value[session.save_handler] = memcached
      ;php_value[session.save_path]    = "127.0.0.1:11211"
      
      1. Save and exit the php-fpm config file
      2. Stop and restart apache and php-fpm
      systemctl stop httpd
      systemctl stop php-fpm
      # wait a few seconds for the dust to settle
      systemctl start php-fpm
      systemctl start httpd
      
      1. Done
      posted in General Problems
      george1421G
      george1421
    • Can php-fpm make fog web-gui fast

      Note this is more of a document blog than a question. Its intended to be as basis of the configuration required to enable php-fpm to speed up php code processing.
      Note: This post is only about looking into options to speed up the fog web-gui front end and will have NO IMPACT on FOG imaging. I have another thread on what is required to make FOG Imaging faster.

      For this post I’m focusing on Centos 7, but I suspect the configuration will be similar for Debian variants.

      By default the fog installer installs php-fpm, but the fog installer doesn’t activate apache to use it. The follow steps are what I did to enable php-fpm to see if it would speed up the FOG web-gui. This speed up is not so much for interacting with the web-gui, but for the backend fog client that will check into the web master server every XX minutes to look for new tasks. If you have 1000 computers checking in every 5 minutes (fog default) then you will have (if averaged out) every second you will have 1.3 check ins. But we know that this check in time will be randomized where you might have 20 check ins within one second and nothing for 3 seconds then a flood again for the next.

      1. Edit the mpm configuration file to tell the apache mpm module to use events and not pre-fork
        vi /etc/httpd/conf.modules.d/00-mpm.conf
      2. Comment out
        #LoadModule mpm_prefork_module modules/mod_mpm_prefork.so
      3. Uncomment
        LoadModule mpm_event_module modules/mod_mpm_event.so
      4. Save and exit from 00-mpm.conf
      5. Change to the apache configuration directory
        /etc/httpd/conf.d
      6. Copy the standard php.conf file to create a new php-fpm.conf file
        cp /etc/httpd/conf.d/php.conf /etc/httpd/conf.d/php-fpm.conf
      7. Rename the original php.conf file so that apache won’t see it during startup
        mv /etc/httpd/conf.d/php.conf /etc/httpd/conf.d/php.conf.disabled
      8. Edit the copied php-fpm.conf file
        vi /etc/httpd/conf.d/php-fpm.conf
      9. Comment out the following line
        #SetHandler application/x-httpd-php
      10. Insert the following line just below the commented out line
        SetHandler "proxy:fcgi://127.0.0.1:9000"
      11. Save and exit the php-fpm.conf file
      12. Change to the php-fpm directory
        cd /etc/php-fpm.d
      13. Remove the default www.conf in the php-fpm.d directory (this file is created by the fog installer and not used in this setup)
        rm /etc/php-fpm.d/www.conf
      14. Create a new file called fog.conf
        vi /etc/php-fpm.d/fog.conf
      15. Paste in the following
      [fog]
      user = apache
      group = apache
      
      listen = 127.0.0.1:9000
      
      ;listen.owner = apache
      ;listen.group = apache
      ;listen.mode = 0660
      ;listen.acl_users = apache
      ;listen.acl_groups =
      
      listen.allowed_clients = 127.0.0.1
      
      pm = dynamic
      pm.max_children = 50
      pm.start_servers = 5
      pm.min_spare_servers = 5
      pm.max_spare_servers = 35
      ;pm.process_idle_timeout = 10s;
      pm.max_requests = 500
      ;pm.status_path = /status
      ;ping.path = /ping
      ;ping.response = pong
       
      access.log = /var/log/php-fpm/$pool.access.log
      ;access.format = "%R - %u %t \"%m %r%Q%q\" %s %f %{mili}d %{kilo}M %C%%"
      slowlog = /var/log/php-fpm/$pool-slow.log
      
      ;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f www@my.domain.com
      ;php_flag[display_errors] = off
      php_admin_value[error_log] = /var/log/php-fpm/fog-error.log
      php_admin_flag[log_errors] = on
      ;php_admin_value[memory_limit] = 128M
      php_value[session.save_handler] = files
      php_value[session.save_path]    = /var/lib/php/session
      
      ; we will use these settings when memcache (d) is configured.
      ;php_value[session.save_handler] = memcached
      ;php_value[session.save_path] = "127.0.0.1:11211"
      
      php_value[soap.wsdl_cache_dir]  = /var/lib/php/wsdlcache
      
      1. Save and exit fog.conf
      2. Create a php information page in the web root
        vi /var/www/html/info.php
      3. Paste in the following
      <html>
      <body>
      
      <?php
       phpinfo();
      ?>
      
      </body>
      </html>
      
      1. Save and exit info.php page.
      2. Change the owner of that page to apache
        chown apache:apache /var/www/html/info.php
      3. From a web browser call the info page with http://<fog_server_ip>/info.php. The page should look similar to below
        <insert_info_page_image>
      4. Now lets restart both apache and php-fpm
        systemctl restart php-fpm
        systemctl restart httpd
      5. Give it a few seconds for both services to initialize.
      6. Now call the same info.php page. The page should look similar to below. NOTE: that the Server API variable is now ‘FPM/FastCGI’
        <insert_info_page_image>
      7. Now access the FOG management page console
      8. Access a few of the managment pages, you will note that after a few page clicks the pages will respond faster to your page selections.
      9. To confirm that php-fpm is working you can inspect the logs files being created in /var/log/php-fpm directory. The php errors will now be listed there instead of the default apache error log (because php-fpm is now handling the php code).
      10. You may remove the info.php page in the apache root directory. Its no longer needed.
      11. Done (for now, I’m currently looking into the memcache option. But more on that later).

      With these updates we have now handed off php code execution to a dedicated php engine and we are no longer relying on apache to execute both web pages management and php code execution. Will this help the sites that have hundreds of clients? I hope so.

      Next steps installing memcache

      posted in General Problems
      george1421G
      george1421
    • RE: FOG 1.20 on Ubuntu 16.04 web interface http 500 error on multiple servers

      While I also agree with the others you should update to take advantage of the enhancements like, deployment speed, nvme disks, gpt format, native win10, new hardware, and… and…

      In your case since you have ubuntu and one day fog was working perfectly and the next day it was broken you might want to read over this post: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy This is something that should impact FOG 1.2.0 as well as the current release of fog.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Postdownload Script Issue

      looking at your sed call, it doesn’t look suffient. You might want to review my tutorial here: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/6

      More specifically my sed command to rename a host.

      sed -i -e "s#<ComputerName>\([^<][^<]*\)</ComputerName>#<ComputerName>$hostname</ComputerName>#gi" $unatendfile 
      

      The other thing is there is no warning if the unattend file doesn’t exist. The check just silently fails by design.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Postdownload Script Issue

      If the scripts have a mod of 755 then they should run.

      There are ways to debug these scripts. What you would do is add liberal echo statements to the scipts, then setup a debug deploy (check the debug box when you schedule the task). PXE boot a target computer and on the target computer it will display a few screens of commands. After a few enter key presses you will be dropped to a linux command prompt on the target computer. Key in fog and you can single step through a deployment. When you get just after the images have been pushed to the disk it should call your post download scripts. You can press crtl-C and exit out of the deployment scripts and then test your script.

      Its a bit of a back art debugging the scripts but you can get to what you need this way.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Host seems reachable by fog, but is not reaching PXE fog menu

      @thebrennan47 Well without the location plugin FOG sees all storage nodes at the same location. So it will try to load balance between the storage nodes. So its possible that you might have a client at site D trying to pxe boot and image from Site A. Because as far as FOG is concerned they are at the same location. With the location plugin, you assign storage nodes to locations and then when you register clients, you assign clients to a location so they know what storage node to use.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Host seems reachable by fog, but is not reaching PXE fog menu

      @thebrennan47 Well I would start looking through your storage node configurations.

      Slightly off topic, but along the same lines. Do you have the location plugin installed? And do you have your storage nodes assigned to a location?

      posted in FOG Problems
      george1421G
      george1421
    • RE: Realtek 8111\8168 & undionly.kpxe -> hangs on Initialising Devices...

      @eroneree What version of fog are you running? I understand the mechanics behind why that worked, but 3 years later those (pita) Realtek nics should be working correctly.

      posted in Hardware Compatibility
      george1421G
      george1421
    • RE: incorrect IPs in IPXE

      After reviewing the pcap file we found there IS a second dhcp server on the OP’s network. The OP is currently addressing the second dhcp server issue.

      posted in FOG Problems
      george1421G
      george1421
    • RE: incorrect IPs in IPXE

      If you follow these instructions and capture a pcap of the pxe booting process we can tell what is going down the wire. For this test your dhcp server, fog server, and pxe booting client should be on the same subnet so that we can see the entire pxe booting conversation. Capture the pcap and post to a google drive or dropbox. Either post the link here or send me an IM and I will take a look at it and tell you what is going on.

      https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

      posted in FOG Problems
      george1421G
      george1421
    • RE: incorrect IPs in IPXE

      It really sounds like you have two or more dhcp servers in your broadcast domain .

      posted in FOG Problems
      george1421G
      george1421
    • RE: Can't capture image, looks like permissions, but can't see how it could be

      Just for something abstract, is 10.2.0.87 your FOG master node server?

      Oh, what the hell is that?? image name =v2Office365-SymFix/18 Why is that forward slash ( / ) in the file name? What you have done is allowed in FOG, but I don’t think that is what you really intended here. By putting the forward slash in there FOG will look for a directory called v2Office365-SymFix and place the image in a image directory named 18 This allows for grouping of like Images. If this isn’t what you intended, replace the forward slash with something other than a special character.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Host seems reachable by fog, but is not reaching PXE fog menu

      @thebrennan47 Boy, you are just full of good news.

      OK what is 10.2.102.49? You keep throwing new IP addresses at this poor pxe booting client?

      posted in FOG Problems
      george1421G
      george1421
    • RE: Host seems reachable by fog, but is not reaching PXE fog menu

      @thebrennan47 It might help if you updated your picture with IP addresses but I’m going to guess what I see.

      The FOG server management console is 10.0.80.49??

      I could understand if 192.168.1.1 is on the deployment LAN for a storage node. Because dhcp would tell it to get the iPXE file from 192.168.1.1. The file its getting is default.ipxe. Inside the storage node 192.168.1.1 there is a file called /tftpboot/default.ipxe and it should point to the fog master server. That is where the boot.php is coming from. boot.php will determine what storage node to boot bzImage from. That is where its falling down.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Host seems reachable by fog, but is not reaching PXE fog menu

      @thebrennan47 Well now after looking at that picture my neck hurts…

      There is a whole bunch of craziness in that picture.

      What is host 192.168.1.1?
      What is host 10.0.80.49?
      And the last issue is the line with http///fog/service/ipxe in it. That should have an ip address

      I see it tftp booting from 192.168.1.1 then connecting to 10.0.80.49 (which might be a fog server) but then the 10.0.80.49 gives it bad IP address. That should be the IP address of a fog server or a storage node and not be blank.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Set Host Product Key no logger works

      @lebrun78 So the problem is the fog client crashed and once the computer was restarted it completed the activation? Do I understand correctly?

      posted in Windows Problems
      george1421G
      george1421
    • RE: Set Host Product Key no logger works

      @lebrun78 Other than the client machine not working, is there an error message you can show us where it tells us the activation failed?

      This might be in the fog client log or in the windows event viewer. What I want to see is if we can see where the MS VLK key is being used to check to see if it matches what you have configured in the FOG GUI.

      posted in Windows Problems
      george1421G
      george1421
    • 1
    • 2
    • 491
    • 492
    • 493
    • 494
    • 495
    • 766
    • 767
    • 493 / 767