@Tom-Elliott

03-04-16 7:27:25 am] Interface Ready with IP Address: 10.72.3.50 [03-04-16 7:27:25 am] Interface Ready with IP Address: 168.216.10.20 [03-04-16 7:27:25 am] Interface Ready with IP Address: adamstnel.s201.c33.k12.wv.us [03-04-16 7:27:25 am] Interface Ready with IP Address: fog-server [03-04-16 7:27:25 am] * Starting SnapinReplicator Service [03-04-16 7:27:25 am] * Checking for new items every 600 seconds [03-04-16 7:27:25 am] * Starting service loop [03-04-16 7:27:25 am] * Starting Snapin Replication. [03-04-16 7:27:25 am] * We are group ID: #1 [03-04-16 7:27:25 am] | We are group name: Office [03-04-16 7:27:25 am] * We have node ID: #1 [03-04-16 7:27:25 am] | We are node name: Fog-Server [03-04-16 7:27:25 am] * Found Snapin to transfer to 4 group(s) [03-04-16 7:27:25 am] | Snapin name: HP-SDM [03-04-16 7:27:26 am] | Local File: /opt/fog/snapins/HpSDM.bat [03-04-16 7:27:26 am] | Remote File: /opt/fog/snapins [03-04-16 7:27:26 am] | Local File size: 145 [03-04-16 7:27:26 am] | Remote File size: 4096 [03-04-16 7:27:26 am] | Files do not match [03-04-16 7:27:26 am] * Deleting remote file: /opt/fog/snapins

that’s it

@Sebastian-Roth Lol it’s not me, tom confirms it’s the code this time.

EDIT
I misinterpreted. It is apparently somehow my fault lol.

EDIT 2
Tom found the typo. Missing a ) Wasn’t my fault! 🙂

@Quazz I know it’s not a nice bit of info, but this isn’t something I can fix within the code base, unfortunately.

The “trick” i do to keep the GUI functional is simply not enough. The trick, btw, is basically if the image has no storage group associated, get the first created group (smallest ID in the database) and use that for representation.

While it works to keep the GUI functional, it simply CANNOT work for replication. I imagine the same feat could be replicated on Snapins.

@g-chanaud Sorry for digging this out. But it seams like we have this problem still in current trunk version! Not sure if you still have this setup (Dell Utility partition is a major part of the problem). Let me know if you are interested to get this fixed?!

@Fernando-Gietz Thanks for testing and reporting! Marking this solved now but please keep on testing an let us know if you find another issue with this - as we usually don’t have the setup to test multidisk stuff all the time!

Confirmed fixed in r6505

I added some preliminary checking to try to figure out if a file is the same. If it isn’t, it deletes it on the remote side, and then continues checking the other files. This means lftp should always start a fresh file.

Actually, only / got expanded using all that is available on the drive… the /home partition did not get expanded.

That’s OK though - I can work with that at least.

@Wayne-Workman Done.

I’ve patched this up in a suggested pull request. see here for details: https://forums.fogproject.org/topic/6732/install-update-your-database-blank-white-page

@pmonstad https://forums.fogproject.org/topic/6738/not-possible-to-delete-active-tasks/2#

It clearly says all tasks were active tasks. Which is it?

Added checking code to remove any package that can no longer be found.

See my post here please: https://forums.fogproject.org/topic/6781/php5-gettext

Only needs to have the -c argument once, after that it should work continuously.

@Matthieu-Jacquart Told ya.

Confirmed working. the CA ssl folders can now be separated from the snap-ins folder

@Wayne-Workman while I realize this is very old, I feel I must add, the legacy clients Config files always defaulted force reboot to off. It is this I imagine is the meaning of lazy mode.

@Sebastian-Roth I’m marking it as solved. I cannot replicate.

I set multiple systems up for ONLY All Snapin Tasks.

@Tom-Elliott Yes the settings apply through the group to the hosts in the group.

Found, confirmed, and fixed plus a little.

Snapin associations weren’t being deleted for whatever reason, so I’ve added code to ensure it will do so now.

To fix the systems that currently believe it’s already broken, we do the same thing.

I check the associations, check the valid ID’s, and delete associations that are no longer valid when compared to the two primary tables.