http:///service/ipxe/bg.png Error 0x3e11613b / Fog UI Stuck in Loop

TomBagley · Jul 29, 2016, 2:56 PM

@Tom-Elliott No trouble Tom have done. Same symptom when running quick registration. Eventually I get:
*Attempting to register host… Failed
An error has been detected!
Cannot register host. (/bin/fog.auto.reg)
Args Passed:
Computer will reboot in 1 minute.

Thanks,
Tom

TomBagley · Aug 1, 2016, 8:16 AM

@Tom-Elliott Just as a further note I am able to perform a full registration of host. I can also image the client after registering this way.

Not sure whether this helps or offers any guidance.
Tom

Wayne Workman · Aug 2, 2016, 3:25 PM

@TomBagley Did you change the fog server’s IP? Have you tried updating to the latest RC5 ?

TomBagley · Aug 2, 2016, 9:27 AM

@Wayne-Workman Hi Wayne, I haven’t changed the IP and have just upgraded to RC5 and the symptoms remain the same unfortunately.

Wayne Workman · Aug 6, 2016, 9:38 PM

@TomBagley said in http:///service/ipxe/bg.png Error 0x3e11613b / Fog UI Stuck in Loop:

http://service/ipxe/bg.png… Error 0x3e11613b (http://ipxe.org/3e11613b)

I just noticed that line is missing both the IP and fog. It should be this:
http://192.168.150.10/fog/service/ipxe/bg.png

My first advice would be to check in Storage Management, look at all node’s Web root field. This should (generally) be /fog

Then look inside of FOG Configuration -> FOG Settings -> Web Server -> FOG_WEB_HOST and FOG_WEB_ROOT.

Web host should be the fog IP address. web root should be /fog/

TomBagley · Aug 8, 2016, 9:45 AM

This post is deleted!

TomBagley · Aug 8, 2016, 3:48 PM

@Wayne-Workman Have checked and all values are as you state them to be.

Quazz · Aug 8, 2016, 3:56 PM

@TomBagley What’s the output of http://192.168.150.10/fog/service/ipxe/boot.php ?

Wayne Workman · Aug 8, 2016, 3:57 PM

@TomBagley I can see the deleted post, your root directory is about full? that would cause serious issues.

TomBagley · Aug 8, 2016, 4:05 PM

@Wayne-Workman Yes, very nearly. I deleted because I was able to access the FOG UI eventually. How do I know what I can/can’t delete? Or should I be looking to rebuild onto a VM with more space?

TomBagley · Aug 8, 2016, 4:08 PM

@Quazz

#!ipxe
set fog-ip 192.168.150.10
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.150.10/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 3000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.150.10/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
imgfetch init_32.xz
boot || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.150.10/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
imgfetch init_32.xz
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.150.10/fog/ consoleblank=0 rootfstype=ext4 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.150.10/fog/ consoleblank=0 rootfstype=ext4 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.150.10/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://192.168.150.10/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

Wayne Workman · Aug 8, 2016, 5:07 PM

@TomBagley said in http:///service/ipxe/bg.png Error 0x3e11613b / Fog UI Stuck in Loop:

@Wayne-Workman Yes, very nearly. I deleted because I was able to access the FOG UI eventually. How do I know what I can/can’t delete? Or should I be looking to rebuild onto a VM with more space?

I’d first start by looking for snapins that are in /opt/fog/snapins but are not in the web interface snapins management area, and delete the ones that shouldn’t be there.

There are some linux commands you can run to list all files sorted by size, I’ll see if I can find them.

TomBagley · Aug 9, 2016, 10:30 AM

@Wayne-Workman Thanks Wayne there was quite a lot not required so that’s got the root back to 20% available. The UI and Fog boot menu are more stable now but I am back to being stuck at ‘attempting to register host…’

Quazz · Aug 9, 2016, 10:32 AM

@TomBagley Could you make a new thread for that issue? Sounds like a different issue entirely, screenshots would be helpful as well

TomBagley · Aug 9, 2016, 10:32 AM

@Quazz Sure! Thanks for your help thus far.

Wayne Workman · Aug 9, 2016, 11:10 PM

@TomBagley What is the output of du -sh /var/log/httpd and the output of ls -laht /var/log/httpd/error_log

TomBagley · Aug 10, 2016, 1:34 PM

@Wayne-Workman

15G     /var/log/httpd


-rwxr-xr-x. 1 root root 1.3G Aug 10 14:32 /var/log/httpd/error_log

Thanks

Tom Elliott · Aug 10, 2016, 1:34 PM

@TomBagley Clean up the error log a bit.

Run: cat /dev/null > /var/log/httpd/error_log

Wayne Workman · Aug 10, 2016, 1:34 PM

@TomBagley There’s where your space is going. What is the output of ls -laht /var/log/httpd

TomBagley · Aug 10, 2016, 1:44 PM

@Tom-Elliott Have done, thanks for the tip.

@Wayne-Workman said in http:///service/ipxe/bg.png Error 0x3e11613b / Fog UI Stuck in Loop:

ls -laht /var/log/httpd

total 14G
-rwxr-xr-x. 1 root root  26M Aug 10 14:42 access_log
-rwxr-xr-x. 1 root root    0 Aug 10 14:42 error_log
-rwxr-xr-x. 1 root root 3.7G Aug  7 03:33 error_log-20160807
drwxr-xr-x. 9 root root 4.0K Aug  7 03:33 ..
drwxr-xr-x. 2 root root 4.0K Aug  7 03:33 .
-rwxr-xr-x. 1 root root 118M Aug  7 03:33 access_log-20160807
-rwxr-xr-x. 1 root root 9.2G Jul 31 03:09 error_log-20160731
-rwxr-xr-x. 1 root root 152M Jul 31 03:09 access_log-20160731
-rwxr-xr-x. 1 root root  992 Jul 25 03:36 error_log-20160725
-rwxr-xr-x. 1 root root 158M Jul 25 03:36 access_log-20160725
-rwxr-xr-x. 1 root root 1.3K Jul 17 03:37 error_log-20160717
-rwxr-xr-x. 1 root root 129M Jul 17 03:37 access_log-20160717
-rwxr-xr-x. 1 root root    0 May  6 09:18 ssl_access_log
-rwxr-xr-x. 1 root root    0 May  6 09:18 ssl_error_log
-rwxr-xr-x. 1 root root    0 May  6 09:18 ssl_request_log
[root@localhost ~]#

http:///service/ipxe/bg.png Error 0x3e11613b / Fog UI Stuck in Loop

210

12.1k

17.3k

155.4k