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

    Was working prior to update, Image deployment

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    49
    17.2k
    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.
    • Tom ElliottT
      Tom Elliott @EAHarvey
      last edited by

      @EAHarvey Yes.

      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

      E 2 Replies Last reply Reply Quote 0
      • E
        EAHarvey @Tom Elliott
        last edited by

        @Tom-Elliott Moved the kernal back to 4.4.2 and same result. Going to double check a different image real quick.

        1 Reply Last reply Reply Quote 0
        • E
          EAHarvey @Tom Elliott
          last edited by

          @Tom-Elliott Tried a different older image with same result.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth

            @EAHarvey I am still wondering if there is something wrong with the inits. Can you please run a debug deploy for this client (normal deploy but tick “Schedule task as a debug task” just before you hit the button “CREATE DEPLOY TASK FOR …”). When you get to the shell run head -n 642 /usr/share/fog/lib/funcs.sh | tail -n 3 Please take a picture of what you see on the screen and post it here.

            Then you can run the debug deploy job using the command fog. Now you need top step through hitting ENTER. When things go wrong you might fall back to the shell (or try getting back to the shell with Ctrl+c). Take a look at the logfile by cat /tmp/status.fog

            This is not going to solve anything. I am just trying to gather more information on what could be causing the broken pipe… my understanding is that the pigz (parallel gzip) is crashing and therefore not delivering data to the pipe anymore. Just a guess though.

            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

            E 1 Reply Last reply Reply Quote 0
            • E
              EAHarvey @Sebastian Roth
              last edited by

              @Sebastian-Roth 0_1456934762988_fogdebug.jpg

              When I try and cat that /tmp/status it says no directory.

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by

                @EAHarvey Thanks for the picture. Seams like your inits are fine. Not sure why it says line 641 (maybe the beginning of that function although this does not make sense to me…)?!

                When I try and cat that /tmp/status it says no directory.

                Tried after partimage crashed?

                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

                E 1 Reply Last reply Reply Quote 0
                • E
                  EAHarvey @Sebastian Roth
                  last edited by

                  @Sebastian-Roth yes. right after i got the error I ctrl-c and ran the command. So is there a way to svn back down to the previous version or is it just step forward?

                  1 Reply Last reply Reply Quote 0
                  • E
                    EAHarvey
                    last edited by

                    After working with @Sebastian-Roth we discovered it was the latest init files that were causing my problem. I was able to copy the init files from a backup folder and all is working correctly. I am going to test the other backup builds to see where the error starts. I will post back here with what I find.

                    1 Reply Last reply Reply Quote 3
                    • E
                      EAHarvey
                      last edited by

                      Just wanted to update. I have been busy here at work so I have not been able to do anymore testing on the init files. So sorry for the delay.

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

                      276

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project