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

Client not booting

Scheduled Pinned Locked Moved
Linux Problems
3
9
3.9k
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.
  • P
    Peter Fraser
    last edited by Jun 13, 2014, 10:04 PM

    Hi All
    I have install Fog 1.1.0 on Ubuntu desktop 14 and the install went well and I was able to log in.

    I run ISC-DHCP on FreeBSD and set the following options in DHCPD.CONF according to what I read

    host tfptclient {
    hardware ethernet 00:24:43:C3:A4:DC;
    next-server 192.168.0.19;
    fixed-address 192.168.0.210;
    }

    I also set option bootfile-name “pxeboot.0”; in the Global section.
    and restarted the service.

    However, the client will not boot. It’s a Dell GX 280 by the way. On the client screen I see No entry found in database for device.

    Any ideas on what’s causing this?

    Thanks for any help.

    1 Reply Last reply Reply Quote 0
    • I
      ianabc Testers
      last edited by Jun 14, 2014, 12:17 AM

      How far PXE boot does it get?, do you see the iPXE stuff? Also, I think the filename you need in option 67 is “undionly.kpxe” not “pxeboot.0”. Fog 0.32 used “pxeboot.0” but I don’t think fog > 1.0 does so your stanza might look like

      [CODE]
      host tfptclient {
      hardware ethernet 00:24:43:C3:A4:DC;
      next-server 192.168.0.19;
      filename: “undionly.kpxe”;
      fixed-address 192.168.0.210;
      }
      [/CODE]

      I got caught out by the name change as well.

      1 Reply Last reply Reply Quote 0
      • I
        ianabc Testers
        last edited by Jun 14, 2014, 12:17 AM

        Oops, there shouldn’t be a colon at filename
        [CODE]host tfptclient {
        hardware ethernet 00:24:43:C3:A4:DC;
        next-server 192.168.0.19;
        filename “undionly.kpxe”;
        fixed-address 192.168.0.210;
        }[/CODE]

        1 Reply Last reply Reply Quote 0
        • T
          Tom Elliott
          last edited by Jun 15, 2014, 11:47 AM

          I don’t know what’s wrong, or if this is fixed now, but just correction to pxeboot.0. pxelinux.0 was the usual boot filename. At least for 0.32 and below. In 1.x.x its recommended to use undionly.kpxe.

          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
          • P
            Peter Fraser
            last edited by Jun 16, 2014, 3:48 PM

            I have corrected the filename to undionly.kpxe but I am still getting the same error: “No entry found in database for device”
            Yes I have checked the wiki and google but only saw where some else asked the same thing but didn’t see a response. Link Below.

            [url]http://fogproject.org/forum/threads/pxe-booting-no-entry-found-in-database-for-device.4019/[/url]

            As you suggested, I checked the fog install logs and the install completed without error. The apache logs error.log showed no errors either.
            As I mentioned above, I have install Fog 1.1.0 on Ubuntu desktop 14. Actually I have now upgraded it to 1.1.1

            1 Reply Last reply Reply Quote 0
            • T
              Tom Elliott
              last edited by Jun 16, 2014, 3:54 PM

              [url]http://www.itninja.com/question/no-entry-found-in-database-for-device-error-while-booting-from-pxe[/url]

              Do you have a citrix server passing out PXE 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

              1 Reply Last reply Reply Quote 0
              • P
                Peter Fraser
                last edited by Jun 16, 2014, 4:00 PM

                I am attaching the fog install file just in case you may notice something I don’t.

                1 Reply Last reply Reply Quote 0
                • P
                  Peter Fraser
                  last edited by Jun 16, 2014, 5:00 PM

                  I checked and the Citrix Servers are not running the Citrix PVS PXE service.

                  1 Reply Last reply Reply Quote 0
                  • I
                    ianabc Testers
                    last edited by Jun 17, 2014, 12:45 AM

                    It sounds like the problem is with the DHCP service rather than Fog. Your Fog install could be fine, but if there is a problem with DHCP your clients won’t even try to talk to fog.

                    One thing to try might be sniffing out some of the DHCP traffic on your network to confirm that it looks it should. Wireshark should help there. My hunch from what you say above is that your Citrix setup might have a DHCP service somewhere which is handing out DHCP leases in competition with your FreeBSD box. If that is the case, and your client gets it’s lease from that other DHCP server then it wont work.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    1 / 1
                    • First post
                      4/9
                      Last post

                    149

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project