Possible Image and Snapin Replication Problem w/ Working Branch
-
@wayne-workman while quality assurance is always a good thing, the code I added would not have broken what is being reported here. I added a simple check to find out if it can reach the server on port 21, the ftp port. If it cannot communicate it will report it cannot. If it does communicate it will perform replication tasks.
-
-
@Moderators @Testers Is anyone able to replicate this issue?
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
-
@sebastian-roth I have plans (in my head) to build automated functional testing for this, I’m not setup to test replication at the moment.
-
I just wanted to let the FOG team know that I have just completed the build of a new FOG server using v1.5.0 RC9, Dev Branch, with associated storage nodes. We created storage groups and storage nodes, after uploading images. Installed the Locations Plugin and set locations. We moved our images and snapins to the new FOG installation…
And we’ve reproduced the same problem we’ve had on FOG system on which this original posting was based. We have no replication of images or snapin, even though the storage nodes are working as expected.
We’ve written a bash script to replicate both snapins and images from the main fog server to the storage nodes, so our installation works, but based on my experience, it’s very easy to reproduce this replications problem - just do an installation on fresh servera and the problems ensue.
Thanks,
Jim
-
@jim-graczyk Can you try on working branch please? There was an issue with implementation of finding “isAvailable” nodes which I’m pretty sure has been corrected for.
-
Tom,
I’m using the working branch on my lab set up. I’ll pull it there.
I’m also OK trying the working branch on my new installation, as long as I can switch back to the Dev branch after pulling the current Working version.
Is it just a matter of changing the git checkout back to dev branch?
FYI - My new installation is showing SVN 6079 while the lab is showing SVN 6080 - if that helps any.
thanks,
Jim
-
@jim-graczyk Switching to dev-branch is as easy as
git checkout dev-branch(re-run installer of course too).However, reinstalling would put it back into state where it isn’t working properly again. I don’t expect the current working to remain working for too much longer though. Probably by end of this week I’ll make it into RC-10.
-
Updated Lab to v52. Can no longer check replications logs.
Fog Configuration / Log Viewer gives me a Files: pulldown that is now empty.
Jim
-
-
@jim-graczyk I’ll fix that later. Sorry that’s a missed thing in jquery call. The logs are still ‘working’, you just can’t view them currently from the GUI.
-
@Jim-Graczyk Try
less /opt/fog/log/fogreplicator.logon the FOG server command line. -
Working should fix the GUI not displaying the logs for you now too.
-
Fantastic …
Updated the lab and replication is working to the Storage Nodes, Group to Group, as it should be AND the Replication Log UI is not only working but provides much more detail.
Please consider this issue Solved…
Just an FYI - since we have a script working in the new system, we may or may not move to it to the Working branch. It’ll depend on how much pain our script causes us as we add Locations and Storage Nodes v fear of instability this is part and parcel to using the Working branch. Our lab will stay up to date on the working branch. At this point, we think we can hold out for the Dev release of RC10.
Thanks very much.
Jim
-
I have been keeping an eye out on this issue with replication myself, im running V52 of working branch, should I wait until RC10 to come out to update? So far I think everything is functioning normally for replication but figured I could wait until RC10.
