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

Uni-cast deployment problem

Scheduled Pinned Locked Moved Solved
FOG Problems
4
13
4.4k
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.
  • T
    TheeGrizzly
    last edited by Aug 21, 2013, 12:29 PM

    please help

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Aug 21, 2013, 12:33 PM

      It sounds like the file /images/780/d1p2.img.001 does not exist? Can you very if this is indeed there?

      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

      1 Reply Last reply Reply Quote 0
      • A
        afmrick
        last edited by Jun 2, 2015, 11:36 PM

        We started having the same problem today on 0.32. There’s a “d1.mbr” and a “d1p1.img” but, not a “d1p1.img.001” for any image in their directories.

        -rwxrwxrwx 1 root root 512 Jun 2 13:16 d1.mbr
        -rwxrwxrwx 1 root root 77976571904 Jun 2 14:30 d1p1.img

        If I re-type the path into the error box, omitting the “.001” part, it’ll finish imaging and boot normally. …We can’t do that several hundred times though.

        W 1 Reply Last reply Jun 3, 2015, 1:53 AM Reply Quote 0
        • W
          Wayne Workman @afmrick
          last edited by Wayne Workman Jun 2, 2015, 7:59 PM Jun 3, 2015, 1:53 AM

          @afmrick

          That’s very interesting. Another guy is having the exact same issue (I think), but he’s found another work around (equally unacceptable in nature though).

          Try making a simbolic link to /images/780/d1p2.img.001, pointing at the actual files… I bet it’d work.

          [CODE]ln -s /images/780/d1p2.img /images/780/d1p2.img.001[/CODE]

          Then ensure the sym-link has the right permissions:
          [CODE]chmod 777 /images/780/d1p2.img.001[/CODE]

          If that works for you, we can build a script that can do this for all of your images in mere seconds.

          Let us know, I’m very interested.

          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 1
          • T
            Tom Elliott
            last edited by Jun 3, 2015, 8:22 AM

            To my knowledge, 1.2 and trunk versions of fog do not have this type of bug. I’more partial towards trunk only because it is what I’m developing on and has many bugs and improvements over 1.2. That said, I think if you were able to update to 1.2, you’d find any of these weirdness issues would be gone.

            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

            1 Reply Last reply Reply Quote 1
            • W
              Wayne Workman
              last edited by Jun 3, 2015, 11:01 AM

              I agree with Tom.

              I’d recommend upgrading, too. I was just very curious about the issue you were seeing.

              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
              • A
                afmrick
                last edited by Jun 3, 2015, 10:09 PM

                Oooh, the symbolic link would be a pretty neat work around! Thanks Wayne!

                Sadly and/or stupidly I finally noticed that our partition for the FOG images was full and that appears to have been causing the problem. …So many clues.
                I’ll know for sure in a few hours.

                1 Reply Last reply Reply Quote 1
                • A
                  afmrick
                  last edited by Jun 3, 2015, 10:11 PM

                  Oh and the upgrade to the current version is in the pipeline. We just did so much customization on 0.32 that we’re moving a little slow on upgrading.

                  W 2 Replies Last reply Jun 3, 2015, 10:16 PM Reply Quote 0
                  • W
                    Wayne Workman @afmrick
                    last edited by Wayne Workman Jun 3, 2015, 4:23 PM Jun 3, 2015, 10:16 PM

                    @afmrick said:

                    Oh and the upgrade to the current version is in the pipeline. We just did so much customization on 0.32 that we’re moving a little slow on upgrading.

                    If you want support for open source projects that have limited volunteers / developers,

                    Customization is a no no, unless you really know your stuff lol. Try to stay the beaten path, do things the way others have done it.

                    I.E. no crazy distros that nobody has heard of, No crazy “multi-purpose” linux servers that do a million other things besides FOG… gah…

                    And have backups of your images and your database… regularly.

                    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
                    • W
                      Wayne Workman @afmrick
                      last edited by Jun 3, 2015, 11:54 PM

                      @afmrick

                      So, you’re not going to worry about this problem anymore because the disk is full and you’re upgrading Distro and FOG ?

                      Is it ok for me to mark this solved?

                      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
                      • A
                        afmrick
                        last edited by Jun 5, 2015, 5:17 PM

                        Well, I’m all good. ThreeGrizzly originally posted the problem. 🙂

                        1 Reply Last reply Reply Quote 0
                        • W
                          Wayne Workman
                          last edited by Jun 5, 2015, 5:31 PM

                          Well with FOG 0.32, the answer is to upgrade to 1.2.0.

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

                          210

                          Online

                          12.1k

                          Users

                          17.3k

                          Topics

                          155.3k

                          Posts
                          Copyright © 2012-2024 FOG Project