FOG Project

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

    Unsolved snapin : problem with hash

    FOG Problems
    2
    6
    1197
    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
      Ric41 last edited by

      Server
      • FOG Version: Version 1.3.1-RC-5 SVN 6052
      • OS: debian 8.6
      Client
      • OS: windows 7
      Description

      Hi,
      When i create a snapin, if I use an existant file, the hash is not calculated. Can you modify that ? It seems it is necesary to deploy a snapin with the new client.

      1 Reply Last reply Reply Quote 0
      • Wayne Workman
        Wayne Workman @Ric41 last edited by Wayne Workman

        @Ric41 What other services appear? What’s OK?

        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
        • R
          Ric41 last edited by

          it’s weird, but the others services appear withou any action. It’s all okay, thanks.

          Wayne Workman 1 Reply Last reply Reply Quote 0
          • Wayne Workman
            Wayne Workman last edited by Wayne Workman

            I’ve just setup a Debian 8.7 VM at home and installed FOG 1.3.4 on it. Everything installed fine, and the FOGSnapinHash service exists. So something is wrong with yours setup.

            0_1485913616629_Screenshot from 2017-01-31 19-46-42.png

            My first recommendation is to update everything on your server with the below line.

            apt-get -y update;apt-get -y upgrade;apt-get -y dist-upgrade
            

            Next, update to the latest fog. I don’t know how you got fog originally, but the easiest way to stay updated is via the git method. Details on that are located here:
            https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

            Finally, check to see if the service files are marked as executable with the below command:
            ls -la /opt/fog/service/FOGSnapinHash/
            Output should look like this:

            total 12
            drwxr-xr-x  2 root root 4096 Jan 31 19:44 .
            drwxr-xr-x 10 root root 4096 Jan 31 19:40 ..
            -rwxr-xr-x  1 root root 1135 Jan 31 19:40 FOGSnapinHash
            
            

            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
            • R
              Ric41 last edited by

              Thanks for your answer. I don’t have this service. Only the followings : FOGImageReplicator FOGMulticastManager FOGScheduler

              I’ll see to update

              1 Reply Last reply Reply Quote 0
              • Wayne Workman
                Wayne Workman last edited by Wayne Workman

                I would first recommend moving to FOG 1.3.4, it’s the latest release. What you’re on is a developmental version, which is not officially branded ‘stable’ nor would I recommend an older RC over a newer release.

                Second, make sure that FOGSnapinHash is running. This service is what’s supposed to keep stuff like your problem from happening.
                service FOGSnapinHash.service status
                or
                systemctl status FOGSnapinHash.service

                This service defaults to running every 30 minutes, and it’s supposed to generate hashes for any snapin that doesn’t have hashes already. Of course upon snapin file upload/creation a hash is made right then and there, but for picking existing files that were uploaded in older versions of fog, this service is supposed to take care of those.

                If you don’t want to wait for the sleep time (default is 30 minutes), you can kick things into action by restarting the service:
                service FOGSnapinHash.service restart
                or
                systemctl restart FOGSnapinHash.service

                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

                254
                Online

                10.2k
                Users

                16.3k
                Topics

                149.9k
                Posts

                Copyright © 2012-2020 FOG Project