• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Intermittent Connection time out error.

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    25
    2.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Tom ElliottT
      Tom Elliott @steharv
      last edited by

      @steharv Once you update the IP Address in the fogsettings file, rerun the installer. I’m also going to guess that you may need to update your storage node information.

      On a secondary note, is your FOG Server providing DHCP as well as your main Router?

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      S 2 Replies Last reply Reply Quote 0
      • S
        steharv @Tom Elliott
        last edited by

        @Tom-Elliott Router is just set to default DHCP setting which is on and when installing FOG I answered yes to use FOG as DHCP server. No storage nodes, I can just reinstall FOG as can go back to a preinstall snapshot on VB.

        Tom ElliottT 1 Reply Last reply Reply Quote 0
        • S
          steharv @Tom Elliott
          last edited by

          @Tom-Elliott Hi Tom, I reinstalled FOG from scratch, I set the FOG server IP to 192.168.1.248 and then DHCP and DNS server the same IP but it still tries to look for 192.168.1.1 when it boots?

          Tom ElliottT 1 Reply Last reply Reply Quote 0
          • Tom ElliottT
            Tom Elliott @steharv
            last edited by

            @steharv Then the problem is you have two DHCP servers on your network. This is why you’re getting access to FOG iPXE menu intermittently. Both DHCP servers are on the same network, and BOTH are issuing IP’s in the same subnet. If FOG hands out faster than the router, you’ll be able to get to FOG iPXE Menu, if not you’ll get an error.

            I’d highly recommend looking into manually updating the information.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            S 1 Reply Last reply Reply Quote 0
            • Tom ElliottT
              Tom Elliott @steharv
              last edited by

              @steharv In your Router you should have a method to set options for Boot IP and Boot file. It’s here I would recommend updating things. In MS DHCP the options are 66/67 (66 being the FOG Server’s IP/67 being the bootfile - ipxe.pxe, undionly.kpxe, etc…)

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              S 2 Replies Last reply Reply Quote 0
              • S
                steharv @Tom Elliott
                last edited by

                @Tom-Elliott So editing the fogsettings file and rerun the installer? Can I edit the file via FTP?

                S 1 Reply Last reply Reply Quote 0
                • S
                  steharv @Tom Elliott
                  last edited by

                  @Tom-Elliott I cannot see any settings in my router for that?

                  1 Reply Last reply Reply Quote 0
                  • S
                    steharv @steharv
                    last edited by

                    @steharv 0_1542123021310_router-dhcp.PNG

                    1 Reply Last reply Reply Quote 0
                    • S
                      steharv @Tom Elliott
                      last edited by

                      @Tom-Elliott Would I be better off just installing DNSMasq?

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by

                        @steharv said in Intermittent Connection time out error.:

                        Would I be better off just installing DNSMasq?

                        You probably would. Follow George’s post here (full config file) and check your dnsmasq version: https://forums.fogproject.org/topic/12133/fog-on-existing-dhcp-server/3

                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                        S 2 Replies Last reply Reply Quote 1
                        • S
                          steharv @Sebastian Roth
                          last edited by

                          @Sebastian-Roth Thank you

                          1 Reply Last reply Reply Quote 0
                          • S
                            steharv @Sebastian Roth
                            last edited by

                            @Sebastian-Roth I have tried restart dnsmasq but get the following error" Job for dnsmasq. service failed because the control process exited with errror code. See "systemctl status dnsmasq.service and “journalctl - xe” for details.

                            1 Reply Last reply Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by

                              @steharv said in Intermittent Connection time out error.:

                              journalctl - xe

                              Then run that command and post output here. As well post your full config here.

                              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                              S 2 Replies Last reply Reply Quote 0
                              • S
                                steharv @Sebastian Roth
                                last edited by

                                @Sebastian-Roth said in Intermittent Connection time out error.:
                                nit dnsmasq.service has begun starting up.

                                Nov 14 12:45:23 ste-VirtualBox dnsmasq[2453]: dnsmasq: syntax check OK.
                                Nov 14 12:45:23 ste-VirtualBox dnsmasq[2454]: dnsmasq: failed to create listenin
                                Nov 14 12:45:23 ste-VirtualBox dnsmasq[2454]: failed to create listening socket
                                Nov 14 12:45:23 ste-VirtualBox dnsmasq[2454]: FAILED to start up
                                Nov 14 12:45:23 ste-VirtualBox systemd[1]: dnsmasq.service: Control process exit
                                Nov 14 12:45:23 ste-VirtualBox systemd[1]: dnsmasq.service: Failed with result ’
                                Nov 14 12:45:23 ste-VirtualBox systemd[1]: Failed to start dnsmasq - A lightweig
                                – Subject: Unit dnsmasq.service has failed
                                – Defined-By: systemd
                                – Support: http://www.ubuntu.com/support

                                – Unit dnsmasq.service has failed.

                                – The result is RESULT.
                                Nov 14 12:45:23 ste-VirtualBox sudo[2447]: pam_unix(sudo:session): session close
                                Nov 14 12:49:44 ste-VirtualBox sudo[2828]: ste : TTY=pts/0 ; PWD=/home/ste
                                Nov 14 12:49:44 ste-VirtualBox sudo[2828]: pam_unix(sudo:session): session opene
                                lines 2203-2225/2225 (END)e

                                1 Reply Last reply Reply Quote 0
                                • S
                                  steharv @Sebastian Roth
                                  last edited by george1421

                                  @Sebastian-Roth

                                  dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
                                  Set the boot file name based on the matching tag from the vendor class (above)
                                  
                                  dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<fog_server_IP>
                                  dhcp-boot=net:UEFI,ipxe.efi,,<fog_server_IP>
                                  dhcp-boot=net:UEFI64,ipxe.efi,,<fog_server_IP>
                                  PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
                                  
                                  pxe-prompt="Booting FOG Client", 1
                                  The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
                                  Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
                                  This option is first and will be the default if there is no input from the user.
                                  
                                  pxe-service=X86PC, "Boot to FOG", undionly.kpxe
                                  pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
                                  pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi
                                  
                                  dhcp-range=192.168.1.248,proxy
                                  

                                  Mod Note: Fixed file formatting -Geo

                                  george1421G 1 Reply Last reply Reply Quote 0
                                  • george1421G
                                    george1421 Moderator @steharv
                                    last edited by

                                    @steharv Be sure to use my example completely and not just edit your ltsp.conf file to match. My config file is known to work correctly.

                                    # Don't function as a DNS server:
                                    port=0
                                    
                                    # Log lots of extra information about DHCP transactions.
                                    log-dhcp
                                    
                                    # Set the root directory for files available via FTP.
                                    tftp-root=/tftpboot
                                    
                                    # The boot filename, Server name, Server Ip Address
                                    dhcp-boot=undionly.kpxe,,<fog_server_IP>
                                    
                                    # Disable re-use of the DHCP servername and filename fields as extra
                                    # option space. That's to avoid confusing some old or broken DHCP clients.
                                    dhcp-no-override
                                    
                                    # inspect the vendor class string and match the text to set the tag
                                    dhcp-vendorclass=BIOS,PXEClient:Arch:00000
                                    dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
                                    dhcp-vendorclass=UEFI,PXEClient:Arch:00007
                                    dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
                                    
                                    # Set the boot file name based on the matching tag from the vendor class (above)
                                    dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<fog_server_IP>
                                    dhcp-boot=net:UEFI,ipxe.efi,,<fog_server_IP>
                                    dhcp-boot=net:UEFI64,ipxe.efi,,<fog_server_IP>
                                    
                                    # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
                                    pxe-prompt="Booting FOG Client", 1
                                    
                                    # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
                                    # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
                                    # This option is first and will be the default if there is no input from the user.
                                    pxe-service=X86PC, "Boot to FOG", undionly.kpxe
                                    pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
                                    pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi
                                    
                                    dhcp-range=<fog_server_ip>,proxy
                                    

                                    Be sure to replace each instance of <fog_server_ip> with the IP address of your fog server. There are several instances of that tag in the config file above.

                                    The last bit is to ensure you have the correct version or later of dnsmasq or the config file will not work. From the linux command prompt key in dnsmasq -v. The version returned should be 2.76 or later. If its earlier than this you will have issues with uefi systems even if you use my config file exactly.

                                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      steharv @george1421
                                      last edited by

                                      @george1421 Thank you thank you!!! that worked you are a legend mate ! Its all running!

                                      1 Reply Last reply Reply Quote 1
                                      • 1
                                      • 2
                                      • 1 / 2
                                      • First post
                                        Last post

                                      146

                                      Online

                                      12.0k

                                      Users

                                      17.3k

                                      Topics

                                      155.2k

                                      Posts
                                      Copyright © 2012-2024 FOG Project