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

Cannot image/register

Scheduled Pinned Locked Moved
FOG Problems
3
8
1.6k
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
    Scott Adams
    last edited by Feb 22, 2016, 2:29 PM

    Up until Feb. 12th, imaging/registering devices was working fine. We had recently updated to SVN 6124 in order to get imaging working with Surface Pro 3s.

    However, starting Friday 19th, this issue occurred. It doesn’t matter the device (Surface or existing computer), but get the following screen when trying to do a quick image:![0_1456151324277_20160222_084256_resized.jpg](Uploading 100%)

    S 1 Reply Last reply Feb 22, 2016, 2:32 PM Reply Quote 0
    • S
      Scott Adams @Scott Adams
      last edited by Feb 22, 2016, 2:32 PM

      0_1456151436077_20160222_084256_resized_1.jpg

      I should also say that I am running Ubuntu 14.04.4, SVN 6124

      I currently am having to swap the boot file that my DCHP is assigned when imaging Surfaces and legacy computers. I know that is not the issue as I have made sure theat file has been swapped back.

      1 Reply Last reply Reply Quote 0
      • G
        george1421 Moderator
        last edited by george1421 Feb 22, 2016, 8:49 AM Feb 22, 2016, 2:47 PM

        Well this error is in the FOS (Fog client OS) its not finding your network adapter in the target computer. For clarity, what is the make and model of the computer (specifically) that is throwing this error?

        FWIW: The latest release is (r6371) as shown in the cloud on the management console.

        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!

        S 1 Reply Last reply Feb 22, 2016, 2:50 PM Reply Quote 0
        • S
          Scott Adams @george1421
          last edited by Feb 22, 2016, 2:50 PM

          @george1421 Thanks for the response. This is a Dell Latitude 3550. We have imaged several of these particular laptops since our upgrade to 6124.

          G 1 Reply Last reply Feb 22, 2016, 3:06 PM Reply Quote 0
          • G
            george1421 Moderator @Scott Adams
            last edited by Feb 22, 2016, 3:06 PM

            @Scott-Adams Interesting, these were working under r6124 (you did nothing to fog) and now they are not working. Did something change in the environment (i.e. network)? Are these one the same network switch where the image worked before? I have seen spanning tree do something similar, where it take a few seconds for the port to go into a forwarding state once the link is dropped and established (as transitioning from ipxe to FOS kernels). Usually this happens on the ipxe side first.

            Just to fill my curiosity, could you go on the fog server into /var/www/html/fog/service/ipxe and key in file bzImage and report the version and build date of the kernel?

            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!

            S 1 Reply Last reply Feb 23, 2016, 3:55 PM Reply Quote 0
            • S
              Scott Adams @george1421
              last edited by Feb 23, 2016, 3:55 PM

              @george1421 I have a few different kernel version. By default, we use 4.4.0. I have also downloaded 4.4.1, and a few different 4.3.x.

              Good news is, it is all of a sudden working today. No idea what the deal is, but I was able to image my laptop.

              Seeings how I am the FOG admin and the network admin, not sure what is different as I have not changed anything, but at least it works now. Thanks!

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Feb 23, 2016, 8:42 PM

                @Scott-Adams said:

                not sure what is different as I have not changed anything, but at least it works now. Thanks!

                I really hope that this will not hit back again in a unsuitable moment. Keep us posted if you see this again.

                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

                1 Reply Last reply Reply Quote 2
                • S
                  Scott Adams
                  last edited by Feb 24, 2016, 1:04 PM

                  Thanks for all your help. I hope so as well.

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

                  151

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project