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

FOG "Reattempting to update database...Failed", broken after update

Scheduled Pinned Locked Moved Unsolved
FOG Problems
2
2
99
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.
  • S
    Sab
    last edited by Sep 12, 2024, 7:08 AM

    We have a rather complex issue with FOG, we are a team of people who were using this solution, but it wasnt us who built it.

    our setup is the next: we have a laptop running as fog server, and a virtual machine on a NAS as a storage node. We have both Legacy and UEFI computers in the building.

    The whole issue began at updating the FOG Server (1.5.10.1593)(DefaultMember FOG Version), the computers were unable to capture or deploy after that. Its really weird, the same computer was okay with deploying, which wasnt okay with it at yesterday (We didnt change anything.)

    The errors are mostly: “Reattempting to update database…Failed”
    "Unable to locate image store (/bin/fog.download)
    “ServerName” was not set, we tried to set it to the FOG servers ip but the GUI basically died
    Then we have refind too, which because of, some computers are unable to boot currently. The storage node is version 1.5.9(nodes, FOG Version)

    What we tried already: DHCP settings, in windows server, thats where they get DHCP
    -changing option 67 to different values, to check compatibility
    -checking logs, trying to solve them

    We will try to answer ASAP to every suggestion, thanks.

    G 1 Reply Last reply Sep 12, 2024, 9:51 AM Reply Quote 0
    • G
      george1421 Moderator @Sab
      last edited by Sep 12, 2024, 9:51 AM

      @Sab First I would have to say both fog server and fog storage node have to be on the same version. The fog storage node doesn’t have its own database, it uses the fog server’s database. There could be schema changes in the database between 1.5.10 and 1.5.9.

      Unless you change the storage group around, its not possible to capture to a storage node (in the default configuration). Only the master node in a storage group captures the image, then it replicates the captured image to all storage nodes. Both the master node and storage node can deploy images.

      If I had to guess, I would think that in the storage group the nas fog server is not defined as the master node. If I think I understand what you did to configure this setup.

      On the fog error screen it should print out the kernel parameters sent to the FOS imaging engine. There should be a filed marked storage or storage_ip, that will point to the fog server it will try to get the image from. Make sure that is correct for your configuration.

      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
      • 1 / 1
      1 / 1
      • First post
        2/2
        Last post

      206

      Online

      12.0k

      Users

      17.3k

      Topics

      155.2k

      Posts
      Copyright © 2012-2024 FOG Project