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

    FOG ubuntu image fails to update database

    Scheduled Pinned Locked Moved Unsolved FOG Problems
    23 Posts 4 Posters 288 Views
    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.
    • M
      mashina @Tom Elliott
      last edited by

      @Tom-Elliott

      FOG version: working-1.6
      commit: f61a90d97

      The history of the days we noticed the issue. One thing I want to point out is that unicasting doesn’t throw that error.

      | 2119 | [2026-03-05 09:22:52] Task ID:  Name: Multiple Snapin -- orig Single has failed to save. Error: Required database field is empty: hostID    | iina     | 2026-03-05 09:22:52 | 10.24.193.157  |
| 2120 | [2026-03-05 09:23:03] Task ID: 3714 NAME: Wake-Up Task - 6037-GOLD 2026-03-05 09:23:03 has been successfully updated.                       | fog      | 2026-03-05 09:23:03 | 172.28.172.92  |
| 2122 | [2026-03-05 09:23:04] Task ID: 3714 NAME: Wake-Up Task - 6037-GOLD 2026-03-05 09:23:03 has been successfully updated.                       | fog      | 2026-03-05 09:23:04 | 172.28.172.92  |
| 2123 | [2026-03-05 09:23:54] Task ID:  Name: Multiple Snapin -- orig Single has failed to save. Error: Required database field is empty: hostID    | iina     | 2026-03-05 09:23:54 | 10.24.193.157  |
| 2124 | [2026-03-05 10:27:19] ScheduledTask ID: 4 NAME: Multi-Cast Task has been successfully updated.                                              | le.do    | 2026-03-05 10:27:19 | 10.24.193.251  |
| 2125 | [2026-03-05 10:34:39] ScheduledTask ID: 5 NAME: Multi-Cast Task has been successfully updated.                                              | le.do    | 2026-03-05 10:34:39 | 10.24.193.251  |
| 2126 | [2026-03-05 14:26:47] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | fog      | 2026-03-05 14:26:47 | 172.28.171.22  |
| 2127 | [2026-03-05 14:27:16] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | fog      | 2026-03-05 14:27:16 | 172.28.171.22  |
| 2128 | [2026-03-05 14:58:43] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | le.do    | 2026-03-05 14:58:43 | 10.24.193.251  |
| 2129 | [2026-03-05 15:04:36] ScheduledTask ID: 10 NAME: Multi-Cast Task has been successfully updated.                                             | le.do    | 2026-03-05 15:04:36 | 10.24.193.251  |
| 2130 | [2026-03-05 15:08:03] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | le.do    | 2026-03-05 15:08:03 | 10.24.193.251  |
| 2131 | [2026-03-05 15:08:39] ScheduledTask ID: 11 NAME: Multi-Cast Task has been successfully updated.                                             | le.do    | 2026-03-05 15:08:39 | 10.24.193.251  |
| 2132 | [2026-03-05 15:13:38] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | le.do    | 2026-03-05 15:13:38 | 10.24.193.251  |
| 2133 | [2026-03-05 15:15:50] ScheduledTask ID: 12 NAME: Multi-Cast Task has been successfully updated.                                             | le.do    | 2026-03-05 15:15:50 | 10.24.193.251  |
| 2134 | [2026-03-05 15:49:11] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | fog      | 2026-03-05 15:49:11 | 172.28.172.92  |
| 2135 | [2026-03-05 16:13:34] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | fog      | 2026-03-05 16:13:34 | 172.28.171.193 |
| 2136 | [2026-03-05 16:13:47] MulticastSession ID: 141 NAME: Multi-Cast Task - sysprep-test-5004 2026-03-05 16:13:46 has been successfully updated. | fog      | 2026-03-05 16:13:47 | 172.28.171.193 |
| 2137 | [2026-03-06 09:15:12] Group ID: 41 NAME: Le.Do (api-test) has been successfully updated.                                                    | le.do    | 2026-03-06 09:15:12 | 10.24.193.251  |
| 2138 | [2026-03-06 09:15:27] ScheduledTask ID: 14 NAME: Multi-Cast Task has been successfully updated.                                             | le.do    | 2026-03-06 09:15:27 | 10.24.193.251  |
| 2139 | [2026-03-06 09:18:47] ScheduledTask ID: 15 NAME: Multi-Cast Task has been successfully updated.                                             | le.do    | 2026-03-06 09:18:47 | 10.24.193.251  |
| 2140 | [2026-03-06 09:45:04] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | fog      | 2026-03-06 09:45:04 | 172.28.172.92  |
| 2141 | [2026-03-06 09:45:21] MulticastSession ID: 142 NAME: Multi-Cast Task - sysprep-test-5004 2026-03-06 09:45:21 has been successfully updated. | fog      | 2026-03-06 09:45:21 | 172.28.172.92  |
| 2142 | [2026-03-06 10:37:18] Group ID: 41 NAME: Le.Do (api-test) has been successfully updated.                                                    | le.do    | 2026-03-06 10:37:18 | 10.24.193.251  |
| 2143 | [2026-03-06 10:37:32] ScheduledTask ID: 16 NAME: Multi-Cast Task has been successfully updated.                                             | le.do    | 2026-03-06 10:37:32 | 10.24.193.251  |
| 2144 | [2026-03-06 11:11:22] ScheduledTask ID: 17 NAME: Multi-Cast Task has been successfully updated.                                             | fog      | 2026-03-06 11:11:22 | 172.28.172.92  |
| 2145 | [2026-03-06 12:10:27] ScheduledTask ID: 18 NAME: Multi-Cast Task has been successfully updated.                                             | fog      | 2026-03-06 12:10:27 | 172.28.172.92  |
| 2146 | [2026-03-06 12:20:58] ScheduledTask ID: 19 NAME: Multi-Cast Task has been successfully updated.                                             | fog      | 2026-03-06 12:20:58 | 172.28.172.92  |
| 2147 | [2026-03-06 12:39:43] Group ID: 42 NAME: sysprep-test-5004 has been successfully updated.                                                   | fog      | 2026-03-06 12:39:43 | 172.28.171.193 |
| 2148 | [2026-03-06 12:39:59] MulticastSession ID: 145 NAME: Multi-Cast Task - sysprep-test-5004 2026-03-06 12:39:58 has been successfully updated. | fog      | 2026-03-06 12:39:59 | 172.28.171.193 |
| 2149 | [2026-03-06 15:50:17] ScheduledTask ID: 20 NAME: Multi-Cast Task has been successfully updated.                                             | le.do    | 2026-03-06 15:50:17 | 10.24.193.251  |
| 2150 | [2026-03-06 16:21:15] ScheduledTask ID: 22 NAME: Multi-Cast Task has been successfully updated.                                             | le.do    | 2026-03-06 16:21:15 | 10.24.193.251  |
| 2151 | [2026-03-09 09:19:06] Task ID:  Name: Multiple Snapin -- orig Single has failed to save. Error: Required database field is empty: hostID    | iina     | 2026-03-09 09:19:06 | 10.24.193.58   |
| 2152 | [2026-03-09 09:19:14] Host ID: 66 NAME: 6037-GOLD has been successfully updated.                                                            | iina     | 2026-03-09 09:19:14 | 10.24.193.58   |
| 2153 | [2026-03-09 09:19:25] Task ID:  Name: Multiple Snapin -- orig Single has failed to save. Error: Required database field is empty: hostID    | iina     | 2026-03-09 09:19:25 | 10.24.193.58   |
+------+---------------------------------------------------------------------------------------------------------------------------------------------+----------+---------------------+----------------+
      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @mashina
        last edited by

        @mashina The history table issue’s I’m seeing appear to be legitimate:

        You wouldn’t be able to deploy snapins to a host if the snapin isn’t associated to a host. That said, I don’t know exactly what deploy type, nor what actual “version”

        while I can checkout the commit hash, it’s just a hash and not somethign I readily memorize.

        your exact version of FOG would show on the bottom right of the UI when you login.

        I believe your commit hash relates to working-1.6-beta.2273 or something like that.

        That’s within 2 of the actual “current” but also notably it is within the save function rewrite. Which we definitely see in the history writing.

        It appears like you’re trying to do a Multiple Snapin Task and this 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

        M 3 Replies Last reply Reply Quote 0
        • M
          mashina @Tom Elliott
          last edited by

          This post is deleted!
          Tom ElliottT 1 Reply Last reply Reply Quote 0
          • M
            mashina @Tom Elliott
            last edited by

            @Tom-Elliott

            FOG version: 1.6.0-beta.2273

            Let’s ignore the Snapin errors for now. The error is thrown at the end of the Multicasting image.

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

              @mashina Okay so just so I fully understand:

              The database is successfully updating, but for some reason it’s not returning the exit code correctly.

              I don’t know why (I do want to fix the error you’re seeing but it doesn’t appear to be causing a true “problem” just causes the machine to appear like there is a problem when after the reboot actually occurs), however all is perfectly fine just it might take a minute or 2 longer to actually get into a bootable/workable system?

              So your issue is not at all related though the messaging is similar (Failed to update database) but its failing because it believes the task no longer exists (which indeed is true although only in the context that it is successfully completing the task, but not sending the expected code FOS is waiting for.)

              (I know I’m seeming to ramble, just trying to get my thoughts out and help steer the issue toward whats actually wrong so we know where to look to hopefully fix it.)

              The database is updated, but because FOS doesn’t get the code it expects, it thinks it needs to retry. The retry has nothing to associate to any more (Hence the no active task.)

              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

              Tom ElliottT M 2 Replies Last reply Reply Quote 0
              • Tom ElliottT
                Tom Elliott @Tom Elliott
                last edited by

                @mashina I have made an update after being able to replicate the problem you described.

                Issue it seems was an error 500 occuring on line 329 of the taskingelement.class.php element because it couldn’t find a relevant imaging log.

                I’ve added code that seems to be able to address this though not sure what is actually wrong otherwise. WIth the patch I made things seem to complete okay so I think it’d work good for uni and multicast tasks if you’d be willing to update and test?

                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

                M 1 Reply Last reply Reply Quote 0
                • JGeearJ
                  JGeear @Tom Elliott
                  last edited by

                  This post is deleted!
                  JGeearJ 1 Reply Last reply Reply Quote 0
                  • JGeearJ
                    JGeear @JGeear
                    last edited by

                    @JGeear It appears there is a issue with the UI after all. I tried updating the password there are extra characters added.
                    0c70256a-d51e-4528-a705-d517772f320d-image.png

                    JGeearJ 1 Reply Last reply Reply Quote 0
                    • JGeearJ
                      JGeear @JGeear
                      last edited by

                      @JGeear Updating the password of the storage node fixed the issue. Still I would like to know how these passwords were changed??

                      1 Reply Last reply Reply Quote 0
                      • M
                        mashina @Tom Elliott
                        last edited by mashina

                        @Tom-Elliott

                        Yes, it looks like multicast is working correctly. Thank you for the support.

                        I also want to add a few details to clarify our setup.

                        A few months ago, I was running version 1.15.10. Since we are developing an API-based solution, we decided to upgrade to the latest development branch.

                        During the upgrade, I noticed that when the message appeared telling me to visit /fog/management to update the database, no database update actually took place. Instead, the web interface took me straight to the FOG login page.

                        If I understood that correctly, it suggests there were no database schema changes between 1.15.10 and 1.6. However, that later led me to question my understanding, because several issues arose afterward, including the one mentioned in this post: “Database Update: Failed.”

                        I will add the other issues to the forum soon and link them here.

                        1 Reply Last reply Reply Quote 0
                        • M
                          mashina @Tom Elliott
                          last edited by

                          @Tom-Elliott Absolutely. I will get back to you in a few hours.

                          1 Reply Last reply Reply Quote 0
                          • M
                            mashina @Tom Elliott
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • 1
                            • 2
                            • 2 / 2
                            • First post
                              Last post

                            171

                            Online

                            12.6k

                            Users

                            17.5k

                            Topics

                            156.3k

                            Posts
                            Copyright © 2012-2026 FOG Project