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

    database update issues following image capture

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    27
    4.0k
    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.
    • E
      epatterson @george1421
      last edited by

      @george1421
      So, saving the image from the machine to a new image in FOG worked. Could we have a database issue?
      It’s very odd that we can save a new image capture, but not a capture from an updated, established, image.

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

        @epatterson So from the same machine do a back to back capture. The first time it will be a new image and the second time same machine, same relative time frame will be a replace image capture. See if your logic holds.

        Are you running any other applications on your fog server that might make php-fpm slow to respond to apache? What does top show us?

        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!

        E 1 Reply Last reply Reply Quote 0
        • E
          epatterson @george1421
          last edited by

          @george1421
          The machine I was working with had to be sent out for the user. So, I imaged another machine, with the build I had created, updated the build, and imaged back. It worked w/o issue.
          Our FOG server only runs the FOG processes. We aren’t using it for anything else.
          Another thought. Because our machine is an older desktop and using the original hard drive, we have to make use of secondary attached storage. In doing so, we move images back and forth as needed. Could that be causing an issue with the images, or how the database “sees” them? Should we alter the image path to the attached storage, working all processes from there, instead of moving them back and forth?

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

            @epatterson said in database update issues following image capture:

            we have to make use of secondary attached storage

            What method are you using to do this? Is it external DAS storage, NFS, or iSCSI?

            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!

            E 1 Reply Last reply Reply Quote 0
            • E
              epatterson @george1421
              last edited by

              @george1421
              We are using a USB, directly, attached MyBook storage unit. I then just run a move between the storage and the main machine.

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

                @epatterson So moving the images may be the problem.

                FWIW if you have DAS attached storage you can / could add a second hard drive to this computer, or if the USB hard drive is attached via USB3.0 you could image directly from that.

                In fog you would just setup a second primary storage node in a new storage group. You would use all of the same settings as your default storage node. You do not want to add this alternate hard drive as a secondary storage node in your default storage group because then fog will just replicate from the internal hard drive to the usb hard drive. But if the usb hard drive is setup as a master node in its own storage group then FOG will be happy and you won’t have to fiddle with moving image files.

                Is there an option to add a second physical hard drive to the existing fog server? I realize you use a usb attached drive for this today.

                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!

                E 1 Reply Last reply Reply Quote 0
                • E
                  epatterson @george1421
                  last edited by

                  @george1421
                  I’ll shut the machine down and do some checking. I’ll let you know. Thanks.

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

                  178

                  Online

                  12.1k

                  Users

                  17.3k

                  Topics

                  155.4k

                  Posts
                  Copyright © 2012-2024 FOG Project