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

Fog Boot Menu only works once

Scheduled Pinned Locked Moved Solved
FOG Problems
5
18
4.3k
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.
  • T
    TomBagley
    last edited by May 9, 2016, 11:05 AM

    Hi,
    Firstly, just want to say a huge thank you for such a brilliant piece of kit.

    I have Fog Trunk 7492 running on CentOS 07.

    I am using the kitchen sink config with kernel 4.5.3

    I have two machines to image the Dell OptiPlex 7010 and the OptiPlex 3020.

    The OptiPlex 7010 boots to the Fog menu perfectly and works with multiple reboots.

    The issue I am having is with the OptiPlex 3020. It boots to the Fog Menu once and then if I reboot the machine it hangs at ‘Please enter tftp server:’ if I enter the address it does not boot to the fog menu.

    If I reboot the FogServer the 3020 will boot fine first time and then fail the second time again. Could you possibly offer any guidance?

    If you need any information let me know,
    Thanks,
    Tom

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by May 9, 2016, 11:26 AM

      Did you build the kernel yourself?

      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

      1 Reply Last reply Reply Quote 0
      • G
        george1421 Moderator
        last edited by May 9, 2016, 11:56 AM

        Is the fog server functioning as the DHCP server for the 3020?

        Without putting too much thought into this, it sounds like a networking issue. But its not clear yet why rebooting the fog server fixes the issue (once). We will need more information before we can narrow down the problem.

        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!

        1 Reply Last reply Reply Quote 1
        • W
          Wayne Workman
          last edited by May 9, 2016, 2:15 PM

          It does sound like a networking issue - but it could possibly be something else. We do need more details as George said.

          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!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          1 Reply Last reply Reply Quote 0
          • T
            Tom Elliott
            last edited by May 9, 2016, 2:21 PM

            To me this sounds like SELinux is the issue.

            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

            1 Reply Last reply Reply Quote 1
            • T
              TomBagley
              last edited by May 9, 2016, 2:36 PM

              Hi,
              Thanks all for the replies. The Fog Server is indeed functioning as the DHCP server and I did build the Kernel myself however I found the same issue with the original kernel and have tried several different ones all with the same effect!

              Thanks,
              Tom

              T 1 Reply Last reply May 9, 2016, 2:37 PM Reply Quote 0
              • T
                Tom Elliott @TomBagley
                last edited by May 9, 2016, 2:37 PM

                @TomBagley What’s the output of sestatus? What about iptables -L -n?

                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

                1 Reply Last reply Reply Quote 0
                • T
                  TomBagley
                  last edited by Sebastian Roth May 9, 2016, 9:24 AM May 9, 2016, 2:54 PM

                  Hi Tom,

                  sestatus:

                  SELinux status:                 enabled
                  SELinuxfs mount:                /sys/fs/selinux
                  SELinux root directory:         /etc/selinux
                  Loaded policy name:             targeted
                  Current mode:                   permissive
                  Mode from config file:          permissive
                  Policy MLS status:              enabled
                  Policy deny_unknown status:     allowed
                  Max kernel policy version:      28
                  

                  Output of iptables -L -n:

                  Chain INPUT (policy ACCEPT)
                  target     prot opt source               destination
                  ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
                  ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
                  INPUT_direct  all  --  0.0.0.0/0            0.0.0.0/0
                  INPUT_ZONES_SOURCE  all  --  0.0.0.0/0            0.0.0.0/0
                  INPUT_ZONES  all  --  0.0.0.0/0            0.0.0.0/0
                  ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
                  REJECT     all  --  0.0.0.0/0            0.0.0.0/0            reject-with icmp-host-prohibited
                  
                  Chain FORWARD (policy ACCEPT)
                  target     prot opt source               destination
                  ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
                  ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
                  FORWARD_direct  all  --  0.0.0.0/0            0.0.0.0/0
                  FORWARD_IN_ZONES_SOURCE  all  --  0.0.0.0/0            0.0.0.0/0
                  FORWARD_IN_ZONES  all  --  0.0.0.0/0            0.0.0.0/0
                  FORWARD_OUT_ZONES_SOURCE  all  --  0.0.0.0/0            0.0.0.0/0
                  FORWARD_OUT_ZONES  all  --  0.0.0.0/0            0.0.0.0/0
                  ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
                  REJECT     all  --  0.0.0.0/0            0.0.0.0/0            reject-with icmp-host-prohibited
                  
                  Chain OUTPUT (policy ACCEPT)
                  target     prot opt source               destination
                  OUTPUT_direct  all  --  0.0.0.0/0            0.0.0.0/0
                  
                  Chain FORWARD_IN_ZONES (1 references)
                  target     prot opt source               destination
                  FWDI_public  all  --  0.0.0.0/0            0.0.0.0/0           [goto]
                  FWDI_public  all  --  0.0.0.0/0            0.0.0.0/0           [goto]
                  
                  Chain FORWARD_IN_ZONES_SOURCE (1 references)
                  target     prot opt source               destination
                  
                  Chain FORWARD_OUT_ZONES (1 references)
                  target     prot opt source               destination
                  FWDO_public  all  --  0.0.0.0/0            0.0.0.0/0           [goto]
                  FWDO_public  all  --  0.0.0.0/0            0.0.0.0/0           [goto]
                  
                  Chain FORWARD_OUT_ZONES_SOURCE (1 references)
                  target     prot opt source               destination
                  
                  Chain FORWARD_direct (1 references)
                  target     prot opt source               destination
                  
                  Chain FWDI_public (2 references)
                  target     prot opt source               destination
                  FWDI_public_log  all  --  0.0.0.0/0            0.0.0.0/0
                  FWDI_public_deny  all  --  0.0.0.0/0            0.0.0.0/0
                  FWDI_public_allow  all  --  0.0.0.0/0            0.0.0.0/0
                  
                  Chain FWDI_public_allow (1 references)
                  target     prot opt source               destination
                  
                  Chain FWDI_public_deny (1 references)
                  target     prot opt source               destination
                  
                  Chain FWDI_public_log (1 references)
                  target     prot opt source               destination
                  
                  Chain FWDO_public (2 references)
                  target     prot opt source               destination
                  FWDO_public_log  all  --  0.0.0.0/0            0.0.0.0/0
                  FWDO_public_deny  all  --  0.0.0.0/0            0.0.0.0/0
                  FWDO_public_allow  all  --  0.0.0.0/0            0.0.0.0/0
                  
                  Chain FWDO_public_allow (1 references)
                  target     prot opt source               destination
                  
                  Chain FWDO_public_deny (1 references)
                  target     prot opt source               destination
                  
                  Chain FWDO_public_log (1 references)
                  target     prot opt source               destination
                  
                  Chain INPUT_ZONES (1 references)
                  target     prot opt source               destination
                  IN_public  all  --  0.0.0.0/0            0.0.0.0/0           [goto]
                  IN_public  all  --  0.0.0.0/0            0.0.0.0/0           [goto]
                  
                  Chain INPUT_ZONES_SOURCE (1 references)
                  target     prot opt source               destination
                  
                  Chain INPUT_direct (1 references)
                  target     prot opt source               destination
                  
                  Chain IN_public (2 references)
                  target     prot opt source               destination
                  IN_public_log  all  --  0.0.0.0/0            0.0.0.0/0
                  IN_public_deny  all  --  0.0.0.0/0            0.0.0.0/0
                  IN_public_allow  all  --  0.0.0.0/0            0.0.0.0/0
                  
                  Chain IN_public_allow (1 references)
                  target     prot opt source               destination
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:21 ctstate NEW
                  ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:137 ctstate NEW
                  ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:138 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:139 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:445 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:80 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:443 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:111 ctstate NEW
                  ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:111 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:20048 ctstate NEW
                  ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:20048 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:2049 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:22 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:53 ctstate NEW
                  ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:53 ctstate NEW
                  ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:3306 ctstate NEW
                  ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:67 ctstate NEW
                  ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:69 ctstate NEW
                  ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:4011 ctstate NEW
                  
                  Chain IN_public_deny (1 references)
                  target     prot opt source               destination
                  
                  Chain IN_public_log (1 references)
                  target     prot opt source               destination
                  
                  Chain OUTPUT_direct (1 references)
                  target     prot opt source               destination
                  

                  Thanks,
                  Tom

                  Q 1 Reply Last reply May 9, 2016, 2:56 PM Reply Quote 0
                  • Q
                    Quazz Moderator @TomBagley
                    last edited by May 9, 2016, 2:56 PM

                    @TomBagley Considering you have to enter tftp server address, it is likely you have another DHCP server on your network (likely your modem), which might be interfering.

                    T W 2 Replies Last reply May 9, 2016, 3:51 PM Reply Quote 3
                    • T
                      TomBagley @Quazz
                      last edited by May 9, 2016, 3:51 PM

                      @Quazz said in Fog Boot Menu only works once:

                      @TomBagley Considering you have to enter tftp server address, it is likely you have another DHCP server on your network (likely your modem), which might be interfering.

                      I understand your thoughts Quazz and although I do have another DHCP server I wouldn’t have expected it to not work so consistently if that was the case. I’d expect intermittent issues rather than it always working the first time and not the second.

                      Tom

                      Q W 2 Replies Last reply May 9, 2016, 3:54 PM Reply Quote 0
                      • Q
                        Quazz Moderator @TomBagley
                        last edited by May 9, 2016, 3:54 PM

                        @TomBagley This will most likely be due to the dhcp leases that are handed out allowing the other DHCP server to reach it before FOG has a chance.

                        T 1 Reply Last reply May 9, 2016, 3:58 PM Reply Quote 2
                        • W
                          Wayne Workman @TomBagley
                          last edited by May 9, 2016, 3:58 PM

                          I understand your thoughts Quazz and although I do have another DHCP server I wouldn’t have expected it to not work so consistently if that was the case. I’d expect intermittent issues rather than it always working the first time and not the second.

                          Tom

                          Depends on your network setup. with IP Helpers - you wouldn’t notice any issues at all. If one DHCP server is set as authoritative and another is not, you wouldn’t notice any issues at all. And it too could be that the other DHCP server is just able to reply faster, consistently.

                          If two co-existing DHCP servers within the same broadcast domain are not properly configured to work with another present, it’ll only cause you issues.

                          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!
                          Daily Clean Installation Results:
                          https://fogtesting.fogproject.us/
                          FOG Reporting:
                          https://fog-external-reporting-results.fogproject.us/

                          1 Reply Last reply Reply Quote 1
                          • T
                            TomBagley @Quazz
                            last edited by May 9, 2016, 3:58 PM

                            @Quazz said in Fog Boot Menu only works once:

                            @TomBagley This will most likely be due to the dhcp leases that are handed out allowing the other DHCP server to reach it before FOG has a chance.

                            My networking manager has explained that the Fog Server and clients are on a Vlan completely separate from the rest of the network. Could this still be interfering?

                            Thanks Quazz,
                            Tom

                            W 1 Reply Last reply May 9, 2016, 3:59 PM Reply Quote 0
                            • W
                              Wayne Workman @TomBagley
                              last edited by May 9, 2016, 3:59 PM

                              @TomBagley said in Fog Boot Menu only works once:

                              @Quazz said in Fog Boot Menu only works once:

                              @TomBagley This will most likely be due to the dhcp leases that are handed out allowing the other DHCP server to reach it before FOG has a chance.

                              My networking manager has explained that the Fog Server and clients are on a Vlan completely separate from the rest of the network. Could this still be interfering?

                              Thanks Quazz,
                              Tom

                              Depends on if the totally seperated vlan is being served DHCP or not.

                              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!
                              Daily Clean Installation Results:
                              https://fogtesting.fogproject.us/
                              FOG Reporting:
                              https://fog-external-reporting-results.fogproject.us/

                              T 1 Reply Last reply May 9, 2016, 4:06 PM Reply Quote 0
                              • T
                                TomBagley @Wayne Workman
                                last edited by May 9, 2016, 4:06 PM

                                @Wayne-Workman said in Fog Boot Menu only works once:

                                @TomBagley said in Fog Boot Menu only works once:

                                @Quazz said in Fog Boot Menu only works once:

                                @TomBagley This will most likely be due to the dhcp leases that are handed out allowing the other DHCP server to reach it before FOG has a chance.

                                My networking manager has explained that the Fog Server and clients are on a Vlan completely separate from the rest of the network. Could this still be interfering?

                                Thanks Quazz,
                                Tom

                                Depends on if the totally seperated vlan is being served DHCP or not.

                                Got you thanks all for the rapid response it is much appreciated. Going to turn the Fog off and see how the client behaves. Will let you know how I get on.

                                Tom

                                T 1 Reply Last reply May 9, 2016, 4:46 PM Reply Quote 0
                                • T
                                  TomBagley @TomBagley
                                  last edited by May 9, 2016, 4:46 PM

                                  @TomBagley said in Fog Boot Menu only works once:

                                  @Wayne-Workman said in Fog Boot Menu only works once:

                                  @TomBagley said in Fog Boot Menu only works once:

                                  @Quazz said in Fog Boot Menu only works once:

                                  @TomBagley This will most likely be due to the dhcp leases that are handed out allowing the other DHCP server to reach it before FOG has a chance.

                                  My networking manager has explained that the Fog Server and clients are on a Vlan completely separate from the rest of the network. Could this still be interfering?

                                  Thanks Quazz,
                                  Tom

                                  Depends on if the totally seperated vlan is being served DHCP or not.

                                  That’s done it - solved! Thank you ever so much! Time to slap my network manager for not blocking the DHCP 🙂

                                  Have a nice evening guys.

                                  Tom

                                  W 1 Reply Last reply May 9, 2016, 5:12 PM Reply Quote 1
                                  • W
                                    Wayne Workman @TomBagley
                                    last edited by May 9, 2016, 5:12 PM

                                    @TomBagley You could ask him to modify it to support fog. We have very detailed guides in the wiki. Please pass these two links to your network manager:

                                    https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG

                                    https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

                                    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!
                                    Daily Clean Installation Results:
                                    https://fogtesting.fogproject.us/
                                    FOG Reporting:
                                    https://fog-external-reporting-results.fogproject.us/

                                    1 Reply Last reply Reply Quote 1
                                    • W
                                      Wayne Workman @Quazz
                                      last edited by May 9, 2016, 5:16 PM

                                      @Quazz Kudos to you for knowing what the issue was.

                                      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!
                                      Daily Clean Installation Results:
                                      https://fogtesting.fogproject.us/
                                      FOG Reporting:
                                      https://fog-external-reporting-results.fogproject.us/

                                      1 Reply Last reply Reply Quote 0
                                      • 1 / 1
                                      1 / 1
                                      • First post
                                        14/18
                                        Last post

                                      198

                                      Online

                                      12.0k

                                      Users

                                      17.3k

                                      Topics

                                      155.2k

                                      Posts
                                      Copyright © 2012-2024 FOG Project