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

    040ee119 error on boot

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    26
    101
    86.1k
    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.
    • W
      Wolfbane8653 Developer
      last edited by

      Hmmm…so I downloaded the undionly.kpxe directly from ipxe.org and threw it up on my /tftpboot folder. Renamed it to wolf.kpxe and changed my dhcp 67 to wolf.kpxe. I embedded nothing. Guess what error message I get for most of my machines?

      0x040ee119

      So there is nothing wrong with your embeded scripts! its all ipxe

      The infamous pxelinux.0 may need to come out of retirement.

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

        One more try everybody:

        [url]https://mastacontrola.com/undionly_ROM.kpxe[/url]

        Please try it, hopefully more success?

        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

        1 Reply Last reply Reply Quote 0
        • W
          Wolfbane8653 Developer
          last edited by

          FOR ME I get these results with undionly_ROM.kpxe

          Attempt(s) ==> Configuring (net0 xx:xx:xx:xx) …

          After: Initializing …ok ==> different machines show a bit of a different output

          Dell D610’s, Dell D630’s, HP DC5700’s read:
          Waiting for linkup …ok
          Configuring (net0 xx:xx:xx:xx) …

          Dell E6410’s and HP DC7800 read:
          Configuring (net0 xx:xx:xx:xx) …

          [B]Round 1: (1st boot)[/B]
          VM --> over 20 attempt(s) didn’t get to the “Fog Menu”
          Dell D610 --> 1 attempt(s) to get to “Fog Menu”
          Dell D630 --> 2 attempt(s) to get to “Fog Menu”
          Dell E6410 --> 1 attempt(s) to get to “Fog Menu”
          HP DC5700 --> 1 attempt(s) to get to “Fog Menu”
          HP DC7800 --> 1 attempt(s) to get to “Fog Menu”

          [B]Round 2: (2nd boot)[/B]
          VM --> over 20 attempt(s) didn’t get to the “Fog Menu”
          Dell D610 --> 3 attempt(s) to get to “Fog Menu”
          Dell D630 --> 1 attempt(s) to get to “Fog Menu”
          Dell E6410 --> 7 attempt(s) to get to “Fog Menu”
          HP DC5700 --> 1 attempt(s) to get to “Fog Menu”
          HP DC7800 --> 5 attempt(s) to get to “Fog Menu”

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

            All,

            It seems there may be two options available. Until I can get a solid fix for things with ipxe, please try:

            [url]https://mastacontrola.com/ipxe.pxe[/url] in place of undionly.kpxe This may not work on all systems, but should work on newer and medium aged systems.

            If that doesn’t work, please give a go with this command:

            [code]wget -O /tftpboot/undionly.kpxe https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/code]

            This one is from svn revision 1312 and seems to work on numerous systems. I have issues with VirtualBox, but that’s fine if our “real” systems work in a more consistent manner.

            Hopefully this makes sense until I can get information from ipxe devs.

            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

            1 Reply Last reply Reply Quote 0
            • W
              Wolfbane8653 Developer
              last edited by

              undionly.kpxe–r1312 --> GOLD STAR!..at least on all my machines

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

                One for go, while the above link should help out all those having issues: if you’re daring enough, please give a try to svn rev 1704.

                I’m working on a theory right now, so I understand the hesitation:

                Please try the file in rev 1312 with the commands as above and let us know if this is working for you.

                Then, if you can, please try the latest undionly.kpxe as well:

                [code]wget -O /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe[/code]

                I’m trying something out and am in hope that this one will also receive a gold star.

                Thank you,

                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

                1 Reply Last reply Reply Quote 0
                • D
                  DanielR
                  last edited by

                  Having the same issue with one type of laptop in our fleet. The acer aspire 1830T

                  I have tried every single file mentioned in this thread without success. Did you have any luck Justin P?

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

                    [quote=“DanielR, post: 27398, member: 17896”]Having the same issue with one type of laptop in our fleet. The acer aspire 1830T

                    I have tried every single file mentioned in this thread without success. Did you have any luck Justin P?[/quote]

                    Can you be more specific on which files you’ve used? I’ve got quite a few for testing and would just like to know which you’ve tried.

                    For example, have you tried the undionly.kpxe in [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe?[/url]

                    Have you tried the undionly.kpxe from revision 1312? Which can be found with the command:
                    [code]wget -O /tftpboot/undionly.kpxe https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/code]

                    Is there any more information you can provide for the error(s) you’re seeing?
                    What I mean by this, are you getting the 040ee119 error or some other message?

                    Are you getting this message on multiple systems or just this Acer? What’s the NIC on that system? Has ipxe ever worked for this system?

                    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

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

                      Anybody got any news on this?

                      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

                      1 Reply Last reply Reply Quote 0
                      • Jaymes DriverJ
                        Jaymes Driver Developer
                        last edited by

                        your latest revision

                        [quote=“Tom Elliott, post: 27370, member: 7271”]One for go, while the above link should help out all those having issues: if you’re daring enough, please give a try to svn rev 1704.

                        I’m working on a theory right now, so I understand the hesitation:

                        Please try the file in rev 1312 with the commands as above and let us know if this is working for you.

                        Then, if you can, please try the latest undionly.kpxe as well:

                        [code]wget -O /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe[/code]

                        I’m trying something out and am in hope that this one will also receive a gold star.

                        Thank you,[/quote]

                        seems to work decently well, I still see a number of these errors but I am not stuck waiting 5 minutes anymore.

                        WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

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

                          All,

                          Currently in trunk there are two files dealing with undionly.kpxe.

                          The first one (undionly.kpxe) is the exact one from revision 1312. Please test this one as a potential fix for now.

                          If you are able, the second one (undionly.kpxe.INTEL) is a more recent git pull with the “older” intel drivers that I suspect was/is causing the issues we’re seeing presenting us all with this error. I have not seen any errors with this file, but all I have is VirtualBox, and it works perfectly for me.

                          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

                          1 Reply Last reply Reply Quote 0
                          • D
                            DanielR
                            last edited by

                            [quote=“Tom Elliott, post: 27420, member: 7271”]Can you be more specific on which files you’ve used? I’ve got quite a few for testing and would just like to know which you’ve tried.

                            For example, have you tried the undionly.kpxe in [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe?[/url]

                            Have you tried the undionly.kpxe from revision 1312? Which can be found with the command:
                            [code]wget -O /tftpboot/undionly.kpxe https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/code]

                            Is there any more information you can provide for the error(s) you’re seeing?
                            What I mean by this, are you getting the 040ee119 error or some other message?

                            Are you getting this message on multiple systems or just this Acer? What’s the NIC on that system? Has ipxe ever worked for this system?[/quote]

                            Hi Tom,

                            [B]I have tried the following:[/B]
                            [url]https://mastacontrola.com/undionly_ROM.kpxe[/url]
                            [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe[/url]
                            [url]https://sourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/undionly.kpxe?format=raw[/url]

                            [B]I will try these two now:[/B]
                            [url]https://mastacontrola.com/ipxe.kkkpxe[/url]
                            [url]https://mastacontrola.com/ipxe.kkpxe[/url]

                            [B]Is there any more information you can provide for the error(s) you’re seeing?[/B]
                            I’m getting the 040ee119 error (0x040ee119)

                            [B]Are you getting this message on multiple systems or just this Acer? What’s the NIC on that system? Has ipxe ever worked for this system?[/B]
                            First time trying ipxe with this system, only just created a new server to try out the latest version of FOG. The NIC is the Atheros AR8131

                            The acer TravelMate B113 models in our fleet work flawlessly with iPXE.

                            My setup is Ubuntu 14.04, Fog 1.0.1 on an Isolated Network.

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

                              [quote=“DanielR, post: 27537, member: 17896”]Hi Tom,
                              [B]Are you getting this message on multiple systems or just this Acer? What’s the NIC on that system? Has ipxe ever worked for this system?[/B]
                              First time trying ipxe with this system, only just created a new server to try out the latest version of FOG. The NIC is the Atheros AR8131

                              The acer TravelMate B113 models in our fleet work flawlessly with iPXE.

                              My setup is Ubuntu 14.04, Fog 1.0.1 on an Isolated Network.[/quote]

                              The NIC (Atheros AR8131) is referring to your fog server or the client NIC that is failing?

                              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

                              1 Reply Last reply Reply Quote 0
                              • D
                                DanielR
                                last edited by

                                [quote=“Tom Elliott, post: 27550, member: 7271”]The NIC (Atheros AR8131) is referring to your fog server or the client NIC that is failing?[/quote]
                                It is the NIC on the client, not the server. Sorry for the confusion.

                                1 Reply Last reply Reply Quote 0
                                • P
                                  pmonstad
                                  last edited by

                                  The install/upgrade script fails on CentOS: Starting FOG Multicast Management Server…Failed!

                                  It is possible to start the service manualle by running “service FOGMulticastManager start”. Trying to stop it with “service FOGMulticastManager start” returns an error FAILED.

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

                                    [quote=“pmonstad, post: 27646, member: 17422”]The install/upgrade script fails on CentOS: Starting FOG Multicast Management Server…Failed!

                                    It is possible to start the service manualle by running “service FOGMulticastManager start”. Trying to stop it with “service FOGMulticastManager start” returns an error FAILED.[/quote]

                                    This, by chance, needs to be in a forum by itself. Your message reported here has NOTHING to do with the 040ee119 error.

                                    On the topic of this posting,

                                    I’m already aware of this issue AND how to fix it. Why it’s failing you ask? Because there’s a schema update needed to be performed. The FOG Service files can’t access the database because something needs to direct it where to go. The workaround, for now, is to open a browser to:
                                    [url]http://<FOGSERVERIP>/fog/management[/url] and apply the schema update. Then perform the install script again, it should succeed. The reason why you see a FAILED message with “service FOGMulticastManager [b]stop[/b]” is because it’s not running, even if you get a successful “start” message.

                                    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

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

                                      Hi tom,

                                      I’m getting “could not start download, operation not supported” error as well after upgrading.

                                      PC: HP DC 7900s w/ onboard Intel 82567LM-3
                                      Fog Server: VMware, running Ubuntu 12.04LTS & Fog 1.0.1

                                      Files tried: Stock, 1312, & IPXE.pxe

                                      Apache error log

                                      [CODE]
                                      [Wed May 21 09:13:39 2014] [error] [client 10.99.0.75] PHP Warning: mysql_real_escape_string(): A link to the server could not be established in /var/www/fog/lib/db/MySQL.class.php on line 253
                                      [Wed May 21 09:13:39 2014] [error] [client 10.99.0.75] PHP Warning: mysql_query() expects parameter 2 to be resource, boolean given in /var/www/fog/lib/db/MySQL.class.php on line 95
                                      [Wed May 21 09:13:39 2014] [error] [client 10.50.0.52] PHP Warning: mysql_query() expects parameter 2 to be resource, boolean given in /var/www/fog/lib/db/MySQL.class.php on line 95
                                      [Wed May 21 09:13:39 2014] [error] [client 10.50.0.52] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /var/www/fog/lib/db/MySQL.class.php on line 156
                                      [Wed May 21 09:13:39 2014] [error] [client 10.50.0.52] PHP Warning: mysql_real_escape_string(): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2) in /var/www/fog/lib/db/MySQL.class.php on line 253
                                      [/CODE]

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        Jordon Rapp
                                        last edited by

                                        Hi Tom,

                                        I’ve followed this thread and have eliminated many problems that I was having. Now I get the FOG GUI and then it quickly disappears and loads Windows.

                                        I’m running FOG 1.0.1 on Ubuntu 14.04

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

                                          All with this issue:

                                          Per suggestion from one of our Project Leads: Chuck Syperski,

                                          I’ve rebuilt the undionly.kpxe and ipxe.kpxe with the ipxescript set as:
                                          [code]#!ipxe
                                          dhcp || reboot
                                          chain default.ipxe[/code]

                                          Please try both if possible.

                                          They are located at:
                                          [url]https://mastacontrola.com/ipxe.kpxe[/url]
                                          [url]https://mastacontrola.com/undionly.kpxe[/url]

                                          I’d recommend using the undionly.kpxe first, if that doesn’t work try the ipxe.kpxe AS your undionly.kpxe.

                                          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

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            DanielR
                                            last edited by

                                            [quote=“Tom Elliott, post: 27969, member: 7271”]All with this issue:

                                            Per suggestion from one of our Project Leads: Chuck Syperski,

                                            I’ve rebuilt the undionly.kpxe and ipxe.kpxe with the ipxescript set as:
                                            [code]#!ipxe
                                            dhcp || reboot
                                            chain default.ipxe[/code]

                                            Please try both if possible.

                                            They are located at:
                                            [url]https://mastacontrola.com/ipxe.kpxe[/url]
                                            [url]https://mastacontrola.com/undionly.kpxe[/url]

                                            I’d recommend using the undionly.kpxe first, if that doesn’t work try the ipxe.kpxe AS your undionly.kpxe.[/quote]

                                            Sadly, both produce the same error only this time the client restarts after it fails.

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

                                            146

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project