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

snapin issues - loop client reboot

Scheduled Pinned Locked Moved
FOG Problems
3
9
2.8k
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.
  • R
    robza
    last edited by Sep 22, 2015, 7:16 AM

    Hello,
    my conf:
    fedora 22 64b
    fog: svn 4730
    I have problems with sending snapins to client. When trying send all sanpins to client get this message Fog_message.png
    after reboot nothing happened - I mean no snapin installation. PC goes in loop, it’s reboot until remove “Active Tasks” and “Active Snapin Tasks”
    Help needed.
    Regards

    P 1 Reply Last reply Sep 22, 2015, 11:44 AM Reply Quote 0
    • P
      plegrand @robza
      last edited by plegrand Sep 22, 2015, 5:48 AM Sep 22, 2015, 11:44 AM

      @robza Same problem here
      In fact i havent same version … idont really understand versionning
      when i do svn up it says 4044
      And on fog, in the cloud at the top of the page it says 4700

      T 1 Reply Last reply Sep 22, 2015, 11:54 AM Reply Quote 0
      • T
        Tom Elliott @plegrand
        last edited by Sep 22, 2015, 11:54 AM

        @plegrand You’re not running it properly if your fog version is showing as 4700. My guess is you moved the /var/www/html/fog to /var/www/fog and this is what you’re seeing?

        When you run the svn up where, exactly, are you in the directory structure?

        For example, if you’re in /opt/svn/trunk/bin and you run svn up, you are not updating the whole tree, you’re only updating the bin directory.

        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

        P 1 Reply Last reply Sep 22, 2015, 12:07 PM Reply Quote 0
        • P
          plegrand @Tom Elliott
          last edited by Sep 22, 2015, 12:07 PM

          @Tom-Elliott i’m going to make a new install with the good path and i come back to tell you.
          But i’ve got the same problem than robza about loop reboot with snapins task

          1 Reply Last reply Reply Quote 0
          • T
            Tom Elliott
            last edited by Sep 22, 2015, 12:09 PM

            This is now fixed, please update first, then try again.

            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

            R P 2 Replies Last reply Sep 22, 2015, 12:55 PM Reply Quote 1
            • R
              robza @Tom Elliott
              last edited by Sep 22, 2015, 12:55 PM

              @Tom-Elliott
              after update svn works like a charm.
              But I still don’t get how to understand versioning.
              For example I have svn in root directory. This is what I do to update svn.
              cd /root/svn/trunk
              svn up
              cd bin
              ./installfog.sh
              And on fog website I see version 4738 but on console when type svn info have 4048.
              Regards

              T 1 Reply Last reply Sep 22, 2015, 1:13 PM Reply Quote 0
              • P
                plegrand @Tom Elliott
                last edited by Sep 22, 2015, 1:06 PM

                @Tom-Elliott
                Here is what i’ve donne

                cd /home
                mkdir svn
                cd svn
                svn checkout https://svn.code.sf.net/p/freeghost/code/trunk
                at the end i’ve got this information : Révision 4048 extraite.
                cd /home/svn/trunk/bin
                ./installfog.sh

                At the end of installation i’ve got this message :
                You still need to install/update your database schema.
                This can be done by opening a web browser and going to:

                  http://192.168.39.243/fog/management
                

                Press [Enter] key when database is updated/installed.

                On the serveur fog is installed in /var/fog

                I go on the web page, and in the cloud : 4738

                To update (run svn up) i’ve got to go into /home/svn/trunk then ?

                For the snapins problem it works fine

                Just in the hosts list, for my machine test, i’ve got “No response” with an exclamtion point in a red circle
                as fog didnt see the host .
                Nevertheless i can see the host add snapins etc…

                Then thanks again for your help and for this great application

                1 Reply Last reply Reply Quote 0
                • T
                  Tom Elliott @robza
                  last edited by Sep 22, 2015, 1:13 PM

                  @robza versioning is now done based on the number of commits to the github repo after svn version 3510. This was done because sourceforge had a major malfunction and I needed to keep things Updated. Initially when sf went down there was no versioning the cloud which makes it very difficult to narrow down where a bug is. When sourceforge came back I didn’t feel it was necessary to keep using svn revision number as the version as to many people it would’ve looked as if they went backwards. Hopefully this helps clarify?

                  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

                  R 1 Reply Last reply Sep 23, 2015, 5:24 AM Reply Quote 0
                  • R
                    robza @Tom Elliott
                    last edited by Sep 23, 2015, 5:24 AM

                    @Tom-Elliott
                    thanks for explanation.
                    Regards

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    1 / 1
                    • First post
                      6/9
                      Last post

                    212

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project