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

    Seems that TFTP was not prepared by installer

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    42
    10.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.
    • Tom ElliottT
      Tom Elliott @Tywyn
      last edited by

      @Tywyn Did you install as server or storage 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

      T 1 Reply Last reply Reply Quote 0
      • Q
        Quazz Moderator @Tywyn
        last edited by

        @Tywyn There’s an error_logs folder in the fogproject/bin folder (where you extracted the download). There will be a log file of the most recent installation, there’s probably some more detailed information in there.

        T 1 Reply Last reply Reply Quote 0
        • T
          Tywyn @Tom Elliott
          last edited by

          @Tom-Elliott
          Normal Server

          1 Reply Last reply Reply Quote 0
          • T
            Tywyn @Quazz
            last edited by Tywyn

            @Quazz
            Hm hm … thought over to reinstall about an hour ago but aborted the reinstall. It seems, that this try overwrote the log-files from the last install. So I have none from my orignal installation.

            Maybe I should do another, clean reinstallation.
            Is it just the sudo ./installscript.sh? Or do I have to remove some files/databases?

            Do I have to set router address for DHCP-Server to 192.168.100.1 ?

            Are those settings then correct:

             * Here are the settings FOG will use:
             * Base Linux: Debian
             * Detected Linux Distribution: Debian GNU/Linux
             * Server IP Address: 192.168.100.1
             * Server Subnet Mask: 255.255.255.0
             * Interface: enp3s1
             * Installation Type: Normal Server
             * Internationalization: 0
             * Image Storage Location: /images
             * Using FOG DHCP: Yes
             * DHCP router Address: 192.168.100.1
            
            

            Interface enp3s1 is the one, which listens to 192.168.100.1

            Q 1 Reply Last reply Reply Quote 0
            • Q
              Quazz Moderator @Tywyn
              last edited by

              @Tywyn The router address should be the address of the router, it’s unlikely to be the FOG server. This is information used by the DHCP server (which will run on the FOG server in your case it seems) to inform DHCP clients of where the router is they should use.

              You can change this information in /opt/fog/.fogsettings

              george1421G T 2 Replies Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @Quazz
                last edited by

                @Quazz said in Seems that TFTP was not prepared by installer:

                You can change this information in /opt/fog/.fogsettings

                Just a small amendment to Quazz’s post.

                You can / fix change this information in /opt/fog/.fogsettings and then just rerun the installer. No need to do a clean install

                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
                • T
                  Tywyn @Quazz
                  last edited by

                  @Quazz

                  Hm … seems I have no /opt/fog/.fogsettings:

                  # ls -la /opt/fog
                  insgesamt 12
                  drwxr-xr-x 3 root root 4096 Jul 11 12:31 .
                  drwxr-xr-x 3 root root 4096 Jul 10 13:48 ..
                  drwxr-xr-x 3 root root 4096 Jul 10 13:48 snapins
                  -rw-r--r-- 1 root root    0 Jul 11 12:31 undionly.kpxe
                  
                  george1421G 1 Reply Last reply Reply Quote 0
                  • george1421G
                    george1421 Moderator @Tywyn
                    last edited by

                    @Tywyn said in Seems that TFTP was not prepared by installer:

                    no /opt/fog/.fogsettings == no installer finish.

                    I have done that a few times where I use putty for installation and want to copy the url out of the putty window and I hit crtl-c to copy (which is the wrong keystroke for linux and the installer aborts).

                    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!

                    Q T 2 Replies Last reply Reply Quote 1
                    • T
                      Tywyn
                      last edited by

                      Additional info about installing on debian 9.0.0: It seems, that /sbin/ifconfig is not installed by default anymore, but the installer looks for it.
                      So you have to install net-tools.

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

                        @Tywyn it only uses ifconfig if needed. We try ip addr too

                        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

                        T 1 Reply Last reply Reply Quote 1
                        • T
                          Tywyn @Tom Elliott
                          last edited by

                          @Tom-Elliott said in Seems that TFTP was not prepared by installer:

                          @Tywyn it only uses ifconfig if needed. We try ip addr too

                          Thought I saw an error message there …

                          1 Reply Last reply Reply Quote 0
                          • Q
                            Quazz Moderator @george1421
                            last edited by

                            @george1421 More specifically CTRL+C tries to abort the current command/script in terminal, this is also true on Windows. (making it one of the more confusing key strokes)

                            1 Reply Last reply Reply Quote 1
                            • T
                              Tywyn @george1421
                              last edited by

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0
                              • Q
                                Quazz Moderator
                                last edited by

                                I’m guessing you deleted your message because you found the .fogsettings file after all.

                                As for your DHCP concerns, this might be because your router is also handing out DHCP information.

                                If you cannot modify your router’s DHCP settings to hand out TFTP/PXE bootfiles and if you cannot turn it off, then you should like into using ProxyDHCP

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  Tywyn @Quazz
                                  last edited by Tywyn

                                  @Quazz You are right. I was looking in /etc/fog (for what reason ever :))
                                  There is no router involved.
                                  I have the fog-server connected to a switch (cisco SF100D-05) and my test-client connected to the same switch.
                                  Strange thing is: in the beginning I got ip-adresses on pxe boot via dhcp.
                                  Now not anymore. But: starting Windows and setting network to use dhcp immediatly gets an ip address.
                                  dhcp-Server is the fog-server

                                  Q 1 Reply Last reply Reply Quote 0
                                  • Q
                                    Quazz Moderator @Tywyn
                                    last edited by

                                    @Tywyn Would it be possible to provide a screenshot of the client failing to get an IP?

                                    T 1 Reply Last reply Reply Quote 1
                                    • T
                                      Tywyn @Quazz
                                      last edited by

                                      @Quazz
                                      Cannot do a screenshot, but will type in, what it says

                                      Intel UNDI, PXE-2.1 (build 082)
                                      Copyright (C) 1997-2000 Inten Corporation
                                      
                                      For Realtek RTL8111B/8111C Gigbit Ethernet Controller v2.08 (070827)
                                      
                                      CLIENT MAC ADDR: 00 25 11 31 B6 07 GUID: 00251131-B607-2009-0621-034515000000
                                      PXE-E51: No DHCP or proxyDHCP offers were received.
                                      
                                      PXE-M0F: Exiting PXE ROM.
                                      

                                      After booting windows now, it does not offer an IP-Address either anymore, although it did 20 Minutes ago:

                                      # /etc/init.d/isc-dhcp-server status
                                      ● isc-dhcp-server.service - LSB: DHCP server
                                         Loaded: loaded (/etc/init.d/isc-dhcp-server; generated; vendor preset: enabled)
                                         Active: active (running) since Wed 2017-07-12 10:59:47 CEST; 32min ago
                                           Docs: man:systemd-sysv-generator(8)
                                          Tasks: 1 (limit: 4915)
                                         CGroup: /system.slice/isc-dhcp-server.service
                                                 └─7977 /usr/sbin/dhcpd -4 -q -cf /etc/dhcp/dhcpd.conf enp3s1
                                      
                                      Jul 12 11:18:00 debian-linux dhcpd[7977]: reuse_lease: lease age 5006 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.100.10
                                      Jul 12 11:18:00 debian-linux dhcpd[7977]: DHCPDISCOVER from 00:25:11:31:b7:42 (409TN06) via enp3s1
                                      Jul 12 11:18:00 debian-linux dhcpd[7977]: DHCPOFFER on 192.168.100.10 to 00:25:11:31:b7:42 (409TN06) via enp3s1
                                      Jul 12 11:18:00 debian-linux dhcpd[7977]: reuse_lease: lease age 5006 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.100.10
                                      Jul 12 11:18:00 debian-linux dhcpd[7977]: DHCPDISCOVER from 00:25:11:31:b7:42 (409TN06) via enp3s1
                                      Jul 12 11:18:00 debian-linux dhcpd[7977]: DHCPOFFER on 192.168.100.10 to 00:25:11:31:b7:42 (409TN06) via enp3s1
                                      Jul 12 11:18:00 debian-linux dhcpd[7977]: DHCPDISCOVER from 00:25:11:31:b7:42 via enp3s1
                                      Jul 12 11:18:00 debian-linux dhcpd[7977]: DHCPDISCOVER from 00:25:11:31:b6:07 via enp3s1
                                      Jul 12 11:18:01 debian-linux dhcpd[7977]: DHCPOFFER on 192.168.100.12 to 00:25:11:31:b7:42 via enp3s1
                                      Jul 12 11:18:01 debian-linux dhcpd[7977]: DHCPOFFER on 192.168.100.13 to 00:25:11:31:b6:07 via enp3s1
                                      
                                      Q 1 Reply Last reply Reply Quote 0
                                      • Q
                                        Quazz Moderator @Tywyn
                                        last edited by Quazz

                                        @Tywyn This might be relevant for your situation:

                                        https://wiki.fogproject.org/wiki/index.php/Not_passing_PXE,_or_ProxyDHCP...NO_PROBLEM_Cisco

                                        Either that, or try and get a “dumb” switch and see if that works.

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          Tywyn
                                          last edited by

                                          Replaced the cicso switch by an tp-link switch (Easy Smart Switch TL-SG108E).

                                          Same thing. No ip-Addresses anymore …

                                          Q 1 Reply Last reply Reply Quote 0
                                          • Q
                                            Quazz Moderator @Tywyn
                                            last edited by

                                            @Tywyn Can you communicate from the client to the server? (ping and ftp for example)

                                            Another possibility for why it’s not working might be the firewall on debian. You could turn it off for testing.

                                            https://forums.fogproject.org/topic/6162/firewall-configuration

                                            Explains a bit how to set it up so you can still use it.

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

                                            211

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project