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

    Cannot deploy images

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    39
    9.7k
    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
      Tom @george1421
      last edited by george1421

      @george1421

      #!ipxe
set fog-ip 192.168.2.196
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://192.168.2.196/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 10000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://192.168.2.196/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot
      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @george1421
        last edited by

        @george1421 So far we found in the pcap that the client is trying to download bzImage412 and the fog server is replying with file not found.

        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
        • george1421G
          george1421 Moderator @Tom
          last edited by george1421

          @tom Well that wasn’t what I expected (it looks good).

          Lets try one more URL call: http://<fog_server_ip>/fog/service/ipxe/boot.php?mac=<mac_address_of_target_computer>

          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!

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

            @george1421 Just for clarity this is what we see in the pcap

            0_1504734327912_bzImage412.png

            Note that packet 56 asking for bzImage412 and then in packet 58 the FOG server says 302 not found.

            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
            • T
              Tom @george1421
              last edited by george1421

              @george1421

              #!ipxe
set fog-ip 192.168.2.196
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://192.168.2.196/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 10000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.2.196/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.2.196:/images/ storageip=192.168.2.196 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://192.168.2.196/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot
              george1421G 1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @Tom
                last edited by george1421

                @tom OK this isn’t getting us to the answer. Not your fault, I think “fog” is helping us by hiding the answer.

                Can you go to the FOG webgui and look at the FOG Configuration->FOG Settings. Then in FOG Settings look at these values:
                FOG_TFTP_PXE_KERNEL (suspect is wrong) should be bzImage
                FOG_TFTP_PXE_KERNEL_32 (probably right)

                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 Reply Quote 0
                • T
                  Tom @george1421
                  last edited by

                  @george1421
                  0_1504735036772_Capture.JPG

                  george1421G 1 Reply Last reply Reply Quote 0
                  • george1421G
                    george1421 Moderator @Tom
                    last edited by george1421

                    @tom Well as they say… There you go. You found the smoking gun.

                    Did someone try to create a custom kernel for some reason?

                    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 Reply Quote 0
                    • T
                      Tom @george1421
                      last edited by

                      @george1421
                      Not that I am aware of. I was on vacation.
                      So, what are the changes I need to make?

                      Thanks,
                      Tom

                      george1421G 1 Reply Last reply Reply Quote 0
                      • george1421G
                        george1421 Moderator @Tom
                        last edited by

                        @tom Well I would start out by changing that value of bzImage412 in FOG_TFTP_PXE_KERNEL back to the default of bzImage. Then reboot your target computer and see if you can register it.

                        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 Reply Quote 0
                        • T
                          Tom @george1421
                          last edited by

                          @george1421
                          I will tested in the morning and provide feedback.

                          Thanks for all the help.

                          Tom

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

                            Changed the entry to bzimage4123 and it seems to be working fine.
                            Thank you for all your help.

                            You guys ROCK!

                            Tom

                            1 Reply Last reply Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by

                              @Tom Why the heck you using bzimage4123 now or was this just a typo?

                              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
                              • T
                                Tom @Sebastian Roth
                                last edited by

                                @sebastian-roth

                                I cannot say how it was changed. I never touch the settings, unless it is a fresh install which was not the case.

                                Tom

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Sebastian Roth Moderator
                                  last edited by Sebastian Roth

                                  Nevermind, though this is definitely not something FOG did by itself… case closed.

                                  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
                                  • 1
                                  • 2
                                  • 2 / 2
                                  • First post
                                    Last post

                                  297

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project