SOLVED 040ee119 error on boot
I may have found a fix, thanks in great part to those understanding it was timing, not a pxe problem itself.
I worked most of my evening trying to get this figured out by playing with the source files. However, it was so simple and I’m sorry I missed it. Thank you Junkhacker for the code piece to help me.
This seems to fix the issue with Virtualbox as well, though I wasn’t seeing the reported issues on hardware boxes. I’m almost certain this will fix the issue.
I retagged the svn 1.0.1 branch to contain this fix.
For those experiencing this problem, please use the following command as the root user on your FOG Server.
[code]mv /tftpboot/undionly.kpxe /tftpboot/undionly.kpxe.BROKEN
wget http://svn.code.sf.net/p/freeghost/code/tags/1.0.1/packages/tftp/undionly.kpxe -O /tftpboot/undionly.kpxe[/code]
Please let me know of any other issues as you encounter them.
Same issue with Dell Precision T7610. Error 040ee119. Tried everything including chainloading[SIZE=2]. Dell T3500s and other 100 machines are good. Any ideas what else I can check ? Fog 1.2.0[/SIZE]
How long is it taking for systems to get DHCP address?
yeah fixed it, i restarted mysql service, now opens the webpage…
But error 0x040ee119 is still there after chainloading
what does this mean, it is part of file init.database.php in /var/www/fog/common
die(_(‘Unable to connect to Database’));
[quote=“Tom Elliott, post: 29508, member: 7271”]If you’re still having issues with that try this:
I have tried chainloading , and now i am unable to open webpage,
webpage is saying unable to connect to database
FWIW, I spent a couple of hours trying the different binaries in this thread which solved nothing up until i stumbled upon this from the wiki and I got it to work in 10 minutes, big workaround sure but I was merely concerned with getting it up and running:
0x040EE119 error in all clients i’ve tried (VirtualBox, Linux/KVM/qemu, HP Laptop/Intel chipset, HP Desktop/Intel chipset). Juniper Netscreen DHCP server, FOG 1.2.0, Ubuntu 12.04LTS.
I am having the exact same problem as DanielR - Getting error 0x040ee119 on our Acer 1830 fleet, however both our Acer B113 & Acer 3830 fleets are working fine.
If DanielR is still around, did you fix the issue?
We have tested the default files with Fog 1.1.2, as well as the files available on Tom’s site under both “Latest 5Jun” and “e0478 3Jun”.
[url="/_imported_xf_attachments/1/1170_Fog 03 kpxe.jpg?:"]Fog 03 kpxe.jpg[/url]
Did I miss where the 0x040ee119 error final solution was? I am trying on an HP 15T. I have tried the “latest” and “default good” on the mastacontroler page, tried the symlink ln -s pxelinux.0.old undionly.kpxe method. None have worked.
My Fog box is working. I can connect with Dell Optiplex, Lenvova E545 no problem, upload/download images, just can’t boot to pxe with the HP 15T.
[quote=“Tribble, post: 29689, member: 17221”]Finally managed to get around to looking at those switches. Disabled Spanning Tree Protocol, and they now boot correctly.
Just poking fun.
[quote=“Wolfbane8653, post: 29152, member: 3362”]Tribble check out this: [url]http://fogproject.org/forum/threads/nothing-is-working.10598/page-2#post-28305[/url]
I’m sure that the Dell Powerconnects have Spanning Tree Protocol (STP) enabled by default. Please confirm that these have be disabled.
Also there seems to be a portfast function as well. With portfast being disabled it would interfere with iPXE and not PXE[/quote]
Finally managed to get around to looking at those switches. Disabled Spanning Tree Protocol, and they now boot correctly.
We’ve messed up totally, we’ve started reinstall completly the OS (Debian) + FOG in 1.0.1.
You can delete my post, we’ll see that next Thurdsay (Week-end + day off + 2 days of meetings)
Thanks for your help !!
K3nnyfr, change the boot exit style from sanboot to exit or grub and let me know if that helps you out.
Just did that fix, having now “booting from san device 0x00” then nothing happens…
If you’re still having issues with that try this:
If you want to give this a shot!
Thank you I will try this in the morning. Getting late now. I will let you know.
Hi guys, as a quick workaround till the iPXE issues are working I posted this in another post.
Might help a few people?
The above was off a dell 390. Just tested them all on hp 8300 elite:
unidonly.pxe - - puts it into a boot loop
All others = operation not supported.
Just tested them all as well. undionly.pxe throws it in a boot loop (but still gets error (op not sup)- flashes really fast). ipxe.pxe does something new (see image below). The rest just did the operation not supported. The ipxe.pxe error doesn’t make a lot of sense though as seen in second pic the path is correct.