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

    database update failed after capture

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    6
    37
    9.9k
    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.
    • george1421G
      george1421 Moderator @alansopro
      last edited by george1421

      @alansopro You can’t pxe boot for a known or unknown device?

      If its either than please post the results of this url
      http://<fog_server_ip>/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00

      Please post the results in the forum. But it sounds like your fog sql password is now a mismatch. Your fog (linux) and fog (sql) passwords are not linked by design. Its strange that both would get out of sync when you upgraded. I know that the fog (linux) password gets reset sometimes during the upgrade.

      Also it might be interesting to tail the apache error log to see if apache threw an error when you tried to boot.

      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!

      A 1 Reply Last reply Reply Quote 0
      • Q
        Quazz Moderator @alansopro
        last edited by

        @alansopro Is Secure Boot enabled per chance?

        A 1 Reply Last reply Reply Quote 0
        • A
          alansopro @Quazz
          last edited by

          @Quazz No just regular PXE boot.

          @george1421 I updated a field in the file .fogsettings called ‘password’. I will login to mysql and set them all the same and try again before going into more detail.

          1 Reply Last reply Reply Quote 0
          • A
            alansopro @george1421
            last edited by

            @george1421 i went to the address you said and the page reads out as…

            #!ipxe
            set fog-ip <server ip>
            set fog-webroot fog
            set boot-url http://$(fog-ip)/$(fog-webroot)

            I’ve updated the passwords for MySQL and also changed them in the .fogsettings. Still giving me the I/O error. I’m wondering if it’s the PC itself. I’m going to try plugging in another one.

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

              @alansopro Please check the apache error log in /var/log/http/error_log or where ever ubuntu puts it in error.log This will give more details on what is wrong.

              In the case of the output from boot.php I’m going to say the fog sql password is wrong. You should be able to see this user id and password from the web gui too. Then try to login to mysql with something like, mysql -u fog -p fog and then enter the fog (sql) password.

              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
              • A
                alansopro @alansopro
                last edited by

                @george1421

                I did just realize there was a newer version of FOG out. RC5. I was upgrading to it and at the end it did give me a failed message when starting up the NFS server.

                ‘Setting up and starting NFS server: Failed!’

                Could this be cuasing my I/O error and how would I go about resolving this one?

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

                  @alansopro No you are not that far yet. It still may be an issue, but not in this case. FOG uses mysql data to build out the reset of the boot.php page. There is a bunch of text missing from what you posted.

                  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!

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    alansopro @george1421
                    last edited by

                    @george1421 The only users I have listed in my MySQL is fogstorage and root. I have no fog user. I looked in the web config directory where the login is defined and the DB is fog using the login root and the password.

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

                      @alansopro Ok then we need the error message from apache error log.

                      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!

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

                        I’m oh so very lost in what’s happening here.

                        @alansopro, you’ve gone through the FTP steps, and NOW the pxe boot doesn’t work? How isn’t it working? Is there an error message, or something we can help you troubleshoot further?

                        That said, resetting your password would have 0 impact on the booting capability of PXE. So unless there’s something seriously misconfigured we need a lot more information please.

                        Preferrably, Apache error logs, Installation Error logs, pictures, and more details than “I did this, now that ain’t working”.

                        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

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

                          @Tom-Elliott Tom, in this post https://forums.fogproject.org/topic/8236/database-update-failed-after-capture/11 FOG is only filling out the top section of the iPXE menu when boot.php is called directly. My guess is that something is wrong with access the msql server, but that is only a guess.

                          The OP does have 2 issues. One was resolved with correcting the ftp (linux) user password.

                          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
                          • A
                            alansopro @george1421
                            last edited by

                            @george1421 The problem was the actual computer. I plugged in another one and it PXE boots fine but now the NFS server isn’t starting so i can’t capture image due to that. 😕

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

                              @alansopro ?? Was the target computer ??, Um ok.

                              As for the nfs service, have you rebooted your FOG server since the upgrade.

                              You can check the status of nfs with the following command: showmount -e 127.0.0.1 That should list the exported shares from /etc/exports.

                              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!

                              A 1 Reply Last reply Reply Quote 0
                              • P
                                phishphan
                                last edited by

                                I received the same error message on 1.3.0 RC5. Right when the image was just about to finish it said Update Database Failed and then rebooted. This thread is somewhat confusing. Was there a fix posted for this?

                                george1421G Wayne WorkmanW 2 Replies Last reply Reply Quote 0
                                • george1421G
                                  george1421 Moderator @phishphan
                                  last edited by

                                  @phishphan You are correct the OP seems to have several issues, but in your case please follow the suggestion by @Quazz https://forums.fogproject.org/topic/8236/database-update-failed-after-capture/5 and see if your issue is the FTP user account

                                  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!

                                  Wayne WorkmanW 1 Reply Last reply Reply Quote 1
                                  • Wayne WorkmanW
                                    Wayne Workman @george1421
                                    last edited by

                                    @george1421 it is an ftp issue. the storage management pass was changed, and a gui user wasn’t defined in .fogsettings, and the wrong pass defined in there too.

                                    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!
                                    Daily Clean Installation Results:
                                    https://fogtesting.fogproject.us/
                                    FOG Reporting:
                                    https://fog-external-reporting-results.fogproject.us/

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

                                      @Wayne-Workman said in database update failed after capture:

                                      @george1421 it is an ftp issue. the storage management pass was changed, and a gui user wasn’t defined in .fogsettings, and the wrong pass defined in there too.

                                      Is this a systemic issue with the 1.3.0-rcX upgrade script? We’ve seen quite a few of these exact issues in the last few days??

                                      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!

                                      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                                      • Wayne WorkmanW
                                        Wayne Workman @george1421
                                        last edited by

                                        @george1421 said in database update failed after capture:

                                        Is this a systemic issue with the 1.3.0-rcX upgrade script? We’ve seen quite a few of these exact issues in the last few days??

                                        It’s systemic only because people don’t know that they really should define fog web ui user and pass inside of /opt/fog/.fogsettings exactly like the installer says. Additionally, people are changing the Storage Management DefaultMember password without realizing that they must too change the password setting in .fogsettings, and re-run the installer, or do it all manually.

                                        You know what I think?
                                        @Tom-Elliott I think if people change the Storage Management password, that the new password should be tried against that node before being stored in the DB. If an FTP connection fails with the new credentials, show a big fat message saying the credentials are bad and won’t be stored, and to first update .fogsettings and re-run the installer, and that they ought to have web ui credentials defined too so the installer can auto-update the node’s password FOR them.

                                        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!
                                        Daily Clean Installation Results:
                                        https://fogtesting.fogproject.us/
                                        FOG Reporting:
                                        https://fog-external-reporting-results.fogproject.us/

                                        1 Reply Last reply Reply Quote 1
                                        • Wayne WorkmanW
                                          Wayne Workman
                                          last edited by

                                          IMHO, even requiring ui credentials inside .fogsettings creates an unnecessary complexity for fog. When I setup this initially using just BASH, it didn’t require any such ui credentials, but only access to the DB, which the main already has, and a remote node has because the user has to enter the fogstorage credentials. The new way Tom has it setup is php based, and requires valid web interface credentials.

                                          I’ve discussed this with Tom at great length several times, he feels differently.

                                          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!
                                          Daily Clean Installation Results:
                                          https://fogtesting.fogproject.us/
                                          FOG Reporting:
                                          https://fog-external-reporting-results.fogproject.us/

                                          1 Reply Last reply Reply Quote 0
                                          • A
                                            alansopro @george1421
                                            last edited by

                                            @george1421 When running the showmount -e 127.0.0.1 in SSH it gives me a Port mapper failure - timed out error.

                                            I did reboot the system but I mounted the external drive back using mount --bind /media/EXT /images/EXT

                                            Tom ElliottT 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            145

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project