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

    Snapins do not replicate to storage node

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    2
    2
    923
    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.
    • dolfD
      dolf
      last edited by

      Using the latest FOG server (8540) and client (0.11.3). One storage group with two nodes: the main server and one slave.

      On the client, in C:\fog.log:

      ------------------------------------------------------------------------------
      ---------------------------------SnapinClient---------------------------------
      ------------------------------------------------------------------------------
       2016/07/13 09:18 PM Client-Info Client Version: 0.11.3
       2016/07/13 09:18 PM Client-Info Client OS:      Windows
       2016/07/13 09:18 PM Client-Info Server Version: 8540
       2016/07/13 09:18 PM Middleware::Response Success
       2016/07/13 09:18 PM SnapinClient Snapin Found:
       2016/07/13 09:18 PM SnapinClient     ID: -1
       2016/07/13 09:18 PM SnapinClient     Name: 
       2016/07/13 09:18 PM SnapinClient     Created: -1
       2016/07/13 09:18 PM SnapinClient     Action: 
       2016/07/13 09:18 PM SnapinClient     Hide: False
       2016/07/13 09:18 PM SnapinClient     TimeOut: -1
       2016/07/13 09:18 PM SnapinClient     RunWith: 
       2016/07/13 09:18 PM SnapinClient     RunWithArgs: 
       2016/07/13 09:18 PM SnapinClient     File: 
       2016/07/13 09:18 PM SnapinClient     Args: 
       2016/07/13 09:18 PM SnapinClient ERROR: Snapin hash does not exist
      ------------------------------------------------------------------------------
      

      The ID is NOT -1 in the database. In my experience, error messages relating to FOG are usually confusing or misinforming, which is unfortunate. However, after reading this, I started investigating:

      http://mymainserver/fog/status/getsnapinhash.php?filepath=/opt/fog/snapins/res1360x768.ps1 returns a hash, but http://mystoragenode/fog/status/getsnapinhash.php?filepath=/opt/fog/snapins/res1360x768.ps1 returns 0.

      There were no files in /opt/fog/snapins/ on the storage node. The Snapin Replicator log reported:

      [07-13-16 10:18:36 pm] * Starting Sync Actions
      [07-13-16 10:18:36 pm] | CMD:
      			lftp -e 'set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c -R -i res1360x768.ps1 --ignore-time -vvv --exclude 'dev/' --exclude 'ssl/' --exclude 'CA/' --delete-first /opt/fog/snapins /opt/fog/snapins; exit' -u fog,[Protected] ip.ip.ip.ip
      [07-13-16 10:18:36 pm] * Started sync for Snapin Resolution 1360x768
      mirror: Access failed: 553 Could not create file. (res1360x768.ps1)
      

      Then I read this and tried:

      # chown -R fog:root /opt/fog/snapins
      

      So it works now.

      BUT: This was on a fresh install of the latest trunk on a brand new Debian Jessie machine, following the installation instructions and “best practices” (sudo -i and what not) as best I could. So maybe that chown command should go in the installer?

      1 Reply Last reply Reply Quote 1
      • Tom ElliottT
        Tom Elliott
        last edited by

        I’m pretty sure it does fall on the installer already.

        I’ll double check just to be sure:

           1 configureSnapins() {                                                                         
           2     dots "Setting up FOG Snapins"                                                            
           3     mkdir -p $snapindir >>$workingdir/error_logs/fog_error_${version}.log 2>&1               
           4     if [[ -d $snapindir ]]; then                                                             
           5         chmod -R 775 $snapindir                                                              
           6         chown -R fog:$apacheuser $snapindir                                                  
           7     fi                                                                                       
           8     errorStat $?                                                                             
           9 } 
        

        That’s the script portion in the installer’s functions.sh file.

        I see what’s wrong now. Thanks for leading me to it. Yes, Servers were getting the information set, but plain nodes were not. Should be fixed in latest. Thanks for reporting. Also fixed a few minor issues while I was 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 1
        • 1 / 1
        • First post
          Last post

        163

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project