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

FOG Trunk boot loop when PXE booting from storage node.

Scheduled Pinned Locked Moved
FOG Problems
3
9
2.0k
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.
  • B
    BardWood
    last edited by Apr 8, 2016, 12:47 AM

    To be clear, this doesn’t happen if I’m pointing at default master. This is Trunk build 7102. My FOG portal tells me there are newer builds available but this was cloned from git about 2 hours ago. Both default master and the storage node are on the same subnet\VLAN. If I have DHCP hand out the IP of the default master it works great. Pointing to storage node IP results in Chainloading failed:

    0_1460076404990_chainloading_failed_small.jpg

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Apr 7, 2016, 6:59 PM Apr 8, 2016, 12:56 AM

      Just to be clear I think there is a programming error here.

      But please check the storage node configuration. Ensure there an IP Address and a /fog path defined for Web root.

      Also for clarity is the storage node a linux server or some other type of device (like a nas)?

      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 0
      • B
        BardWood
        last edited by Apr 8, 2016, 12:59 AM

        I didn’t customize anything when installing this but did add ‘/fog’ as my Web root so that should be right.

        G 1 Reply Last reply Apr 8, 2016, 1:02 AM Reply Quote 0
        • B
          BardWood
          last edited by Apr 8, 2016, 1:02 AM

          Adding ‘(node IP)/fog’ didn’t make a difference.

          G 1 Reply Last reply Apr 8, 2016, 1:03 AM Reply Quote 0
          • G
            george1421 Moderator @BardWood
            last edited by Apr 8, 2016, 1:02 AM

            @BardWood Is that for the storage node. The master node should already set.

            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 0
            • G
              george1421 Moderator @BardWood
              last edited by george1421 Apr 7, 2016, 7:06 PM Apr 8, 2016, 1:03 AM

              @BardWood said in FOG Trunk boot loop when PXE booting from storage node.:

              Adding ‘(node IP)/fog’ didn’t make a difference.

              As I said this is probably a @Developers issue. But I wanted to make sure you had the web root defined for the storage node, because that is what is missing (outside of the IP address) in the url string.

              edit just looking at the picture again, whats missing is the background image url. So that is why its failing. Can we assume the storage node is 172.16.40.101? /edit

              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!

              T 1 Reply Last reply Apr 8, 2016, 1:59 AM Reply Quote 0
              • T
                Tom Elliott @george1421
                last edited by Apr 8, 2016, 1:59 AM

                @george1421 I don’t think it’s anything much.

                Look at the http://service/ipxe/bg.png. Notice how it’s not got an IP address? My guess is 172.16.40.101 is the main server, and it’s trying to be told to look at the node for data. From what I can see, the only thing I can think of it being is DB settings for this node/server.

                What OS is the main server running? What OS is the node running?

                Assuming (I know I shouldn’t), that the main server IS the mysql server as well, it looks, to me, like it cannot setup the webroot information at all. It’s not connecting the to the Database, at least not properly.

                This can be caused by mismatched user/pass pair for mysql user, or possibly it’s trying to authenticate using an incorrect password checking mechanism (as found in this post: https://forums.fogproject.org/topic/6828/fog-tftp-storge-node-trunk-6455/15#).

                If I had to guess, though, I’d start simple. Just guessing you are running Ubuntu? If so, edit the /etc/mysql/my.cnf file and look for bind-address. Comment it by making that same line start with a #. Save and restart DB with: sudo mysql restart. I think all that’s happening is all requests are being blocked as they’re restricted to connect with anything OTHER than 127.0.0.1 (or whatever address is in there).

                Again, these are all just guesses, so hopefully you can at least start to see what’s going on.

                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
                  Tom Elliott
                  last edited by Apr 8, 2016, 1:59 AM

                  Mind you all the “editing/restarting” of mysql stuff needs to be on the “real” server, not the node.

                  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

                  G 1 Reply Last reply Apr 8, 2016, 2:14 AM Reply Quote 0
                  • G
                    george1421 Moderator @Tom Elliott
                    last edited by Apr 8, 2016, 2:14 AM

                    @Tom-Elliott is there a way to do a qc check on the storage node during the install to ensure it can connect to the master node spl server. That would avoid this type of error?? Just as a suggestion?

                    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 0
                    • 1 / 1
                    1 / 1
                    • First post
                      6/9
                      Last post

                    206

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project