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

Need help... fog server crashed!

Scheduled Pinned Locked Moved
FOG Problems
3
3
617
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.
  • A
    arnaudrigole
    last edited by Jul 29, 2016, 7:13 AM

    Hello Fog Community!

    I am desperate this morning… Following mishandling with hyper-v snapshots, i totally crashed my fogserver. Can’t reboot it, can’t restore… nothing to do. I used fog 1.3

    Here’s my question, i can’t access to the database to export it…
    I have all my images on a external storage (nfs share), each image directory contains :

    • D1.fixed_size_partitions
    • D1.mbr
    • D1.minimum.partitions
    • D1.original.fstypes
    • D1.original.swauuids
    • D1.partitions
    • D1P1.img
    • D1P2.img
    • D1P3.img
      If i setup a “new” fogserver, how could i reimport it ? setup the nfs storage node and storage group then …? are that images usable and recognized by the “new” fog instance?

    a big thank you in advance to those who will help me

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Jul 29, 2016, 3:36 AM Jul 29, 2016, 9:34 AM

      Yes, if you build a new fog server you can import those files. You would setup the new fog server and connect to the storage node and then manually create the image definition in the new fog server.

      If you still have access to the original (broken) virtual hard drive, you may be able to connect that to your new fog server and glean files off of it. If you installed the trunk build and upgraded it over time to bring you to .3.0-rcX there will be database exports on the disk that you might be able to use.

      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 1
      • W
        Wayne Workman
        last edited by Wayne Workman Jul 29, 2016, 6:32 AM Jul 29, 2016, 12:31 PM

        The most important thing to attempt recovery of (other than images) is the ssl directory. If you have fog clients out in the field running, they will absolutely not trust nor obey any fog server that cannot authenticate. The directory is /opt/fog/snapins/ssl
        There’s a walkthrough here:
        https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

        If you can do that, and then re-use the old IP, then all the existing clients will report in to the server as pending.

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

        253

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project