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

Standalone

Scheduled Pinned Locked Moved
Tutorials
4
56
21.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.
  • F
    fredlwal
    last edited by Apr 20, 2015, 6:03 PM

    I did the check box but where to go next?

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Apr 20, 2015, 6:07 PM

      [quote=“fredlwal, post: 45831, member: 26766”]I did the check box but where to go next?[/quote]

      I was sort of intending for you to read through that entire thread. I don’t believe you need the check-box for image-type.

      Further in the thread, there is talk about what needs done to get the images to show up.

      1 Reply Last reply Reply Quote 0
      • F
        fredlwal
        last edited by Apr 20, 2015, 6:21 PM

        I wasn’t going from an old version of fog i’m coping images that are from 1.2.0 to the same version.

        1 Reply Last reply Reply Quote 0
        • F
          fredlwal
          last edited by Apr 20, 2015, 6:33 PM

          I ran the chmod 777, but how do I know its working when I can’t PXE into the server from a client?

          1 Reply Last reply Reply Quote 0
          • W
            Wayne Workman
            last edited by Apr 20, 2015, 6:45 PM

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • W
              Wayne Workman
              last edited by Apr 20, 2015, 6:46 PM

              You just need to create those images inside Image Management using the correct paths.

              [url=“/_imported_xf_attachments/1/1899_ImageNames.png?:”]ImageNames.png[/url]

              1 Reply Last reply Reply Quote 0
              • W
                Wayne Workman
                last edited by Apr 20, 2015, 6:50 PM

                You can troubleshoot PXE booting using this tutorial, it’s really through: [url]http://fogproject.org/wiki/index.php/Troubleshoot_TFTP[/url]

                1 Reply Last reply Reply Quote 0
                • F
                  fredlwal
                  last edited by Apr 20, 2015, 8:10 PM

                  is there a log file that I can send about the pxe boot issue?

                  1 Reply Last reply Reply Quote 0
                  • W
                    Wayne Workman
                    last edited by Apr 20, 2015, 8:25 PM

                    Sort of… there’s a script that’s still under development that you could try. It produces a log file that has lots of important configuration in it… It’s attached, along with sample output. The sample output is no use to you, it just shows what the output might look like.

                    Also, you might be better off just giving us screen-shots of the errors you’re seeing. Maybe a TCPDump of the communications, too: [url]http://fogproject.org/wiki/index.php/TCPDump[/url]

                    For more info on the troubleshooting script, look through this thread. And keep in mind, it’s still a very new thing.
                    This script doesn’t change anything, either. It just collects information. [url]http://fogproject.org/forum/threads/lets-make-scripts.12551/[/url]

                    [url=“/_imported_xf_attachments/1/1900_FogScript.zip?:”]FogScript.zip[/url]

                    1 Reply Last reply Reply Quote 0
                    • F
                      fredlwal
                      last edited by Apr 21, 2015, 12:21 PM

                      this is what I get when I run the script.

                      t_tiger@fogsrv1:~/Downloads$ ./TroubleshootFog.sh
                      status: Unknown job: tftpd-hpa
                      status: Unknown job: isc-dhcp-server
                      status: Unknown job: rpcbind
                      status: Unknown job: vsftpd
                      modprobe: ERROR: could not insert ‘ip_tables’: Operation not permitted
                      iptables v1.4.21: can’t initialize iptables table `filter’: Table does not exist (do you need to insmod?)
                      Perhaps iptables or your kernel needs to be upgraded.
                      ./TroubleshootFog.sh: line 92: sestatus: command not found
                      cat: /etc/dnsmasq.d/ltsp.conf: No such file or directory

                      1 Reply Last reply Reply Quote 0
                      • W
                        Wayne Workman
                        last edited by Apr 21, 2015, 12:38 PM

                        Try this one, instead please.

                        It will create a text file in the location that it was run in. Post that file.

                        [url=“/_imported_xf_attachments/1/1905_troubleshoot.zip?:”]troubleshoot.zip[/url]

                        1 Reply Last reply Reply Quote 0
                        • F
                          fredlwal
                          last edited by Apr 21, 2015, 3:33 PM

                          Where does it store the log file at, that you would need to look at?

                          1 Reply Last reply Reply Quote 0
                          • W
                            Wayne Workman
                            last edited by Apr 21, 2015, 3:34 PM

                            This particular script stores the log in the place where the script is run from.

                            1 Reply Last reply Reply Quote 0
                            • F
                              fredlwal
                              last edited by Apr 21, 2015, 3:46 PM

                              here u go

                              [url=“/_imported_xf_attachments/1/1908_DebianFog.txt?:”]DebianFog.txt[/url]

                              1 Reply Last reply Reply Quote 0
                              • W
                                Wayne Workman
                                last edited by Apr 21, 2015, 4:47 PM

                                Can you post a screen shot of the error you’re seeing?

                                1 Reply Last reply Reply Quote 0
                                • W
                                  Wayne Workman
                                  last edited by Apr 21, 2015, 4:55 PM

                                  [quote=“Joseph Hales, post: 45708, member: 18131”]
                                  [COLOR=#333333][FONT=Arial]/etc/default/isc-dhcp-server[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Arial]We want to serve DHCP only on eth1 interface to we need to configure it that way. Edit the file and save it.[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Courier New]sudo vim /etc/default/isc-dhcp-server[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Arial]The line will look like this before you change it[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Courier New]INTERFACES=“”[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Arial]And after you change it, it will look like this:[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Courier New]INTERFACES=“eth1”[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Arial]Now you should stop and start the DHCP server.[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Courier New]sudo service isc-dhcp-server stop[/FONT][/COLOR][COLOR=#555555][FONT=Arial] (if the service is already running; skip if it’s not running)[/FONT][/COLOR]
                                  [COLOR=#555555][FONT=Courier New]sudo service isc-dhcp-server start[/FONT][/COLOR][/quote]

                                  Going off of what Mr. Hales posted, you might also want to restrict DHCP to your eth0 interface. I see in the log file you provided that there are several interfaces on this machine.

                                  1 Reply Last reply Reply Quote 0
                                  • F
                                    fredlwal
                                    last edited by Apr 21, 2015, 6:19 PM

                                    t_tiger@fogsrv1:~/Downloads$ ./troubleshoot.sh
                                    status: Unknown job: tftpd-hpa
                                    status: Unknown job: isc-dhcp-server
                                    status: Unknown job: rpcbind
                                    status: Unknown job: vsftpd
                                    modprobe: ERROR: could not insert ‘ip_tables’: Operation not permitted
                                    iptables v1.4.21: can’t initialize iptables table `filter’: Table does not exist (do you need to insmod?)
                                    Perhaps iptables or your kernel needs to be upgraded.
                                    ./troubleshoot.sh: line 92: sestatus: command not found
                                    cat: /etc/dnsmasq.d/ltsp.conf: No such file or directory
                                    t_tiger@fogsrv1:~/Downloads$

                                    1 Reply Last reply Reply Quote 0
                                    • W
                                      Wayne Workman
                                      last edited by Apr 21, 2015, 6:56 PM

                                      I’m sorry, I should have been more clear.

                                      Can you take a picture with a camera of the errors you see when you try to network-boot a computer ?

                                      1 Reply Last reply Reply Quote 0
                                      • W
                                        Wayne Workman
                                        last edited by Apr 21, 2015, 7:39 PM

                                        I’ve viewed a picture that fredlwal sent me.
                                        The target host isn’t receiving DHCP. “No DHCP or proxyDHCP offers were received”

                                        We should check the status of the DHCP service.
                                        What is the output of this?
                                        [CODE]sudo service isc-dhcp-server status[/CODE]

                                        After that, try restarting the service:
                                        [CODE]sudo service isc-dhcp-server restart[/CODE]

                                        1 Reply Last reply Reply Quote 0
                                        • F
                                          fredlwal
                                          last edited by Apr 21, 2015, 8:24 PM

                                          DOING THE RESTART COMMAND WORKED!!! Your the greatest!!

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

                                          149

                                          Online

                                          12.1k

                                          Users

                                          17.3k

                                          Topics

                                          155.3k

                                          Posts
                                          Copyright © 2012-2024 FOG Project