@fl0pp Synology NAS have different NFS and FTP paths. NFS starts in the exported directory, in your case that’s /images but the FTP path is likely /something/images
I’m not sure if this will solve your issue, but this is something you have to set on Synology NAS for them to work 100% correctly with transferring images from /dev to /images, for FTP Image Size, and for replication too probably
@Albertus At this time there is no defined release date for 1.3.0 stable. The developers are working hard to get the trunk version to the stable level.
The situation is the more people we can get into the trunk version to find the bugs, the quicker the bugs can be identified and resolved. If people not upgrade waiting for the stable release the longer it will take to find the bugs. So the best situation is to get as many people as possible into the trunk stream to identify issues faster. This will make the 1.3.0 release come faster too.
Understand when I say bugs, the trunk is not unstable today. There are many updates to fog per week as the code is fine tuned for best performance. So you will need to update your fog code frequently to take advantage of the performance improvements.
@Tom-Elliott yessir, sorry so long to get back to you, but that was it, and client registers normally now. I guess that’s the only interface I didn’t check for in database…Loopback I guess
@moses found the type hinting, really kind of wish the secondary bits would’ve been put in a separate posting, but all in all everything should be functional again.
@Hanz Seems as though there are a few hosts with competing clients…that is the newer version installed and then the older is getting installed via gpo.
@Wayne-Workman Thank you, Wayne. That really does clear things up. It sounds like the easiest thing to do (short of upgrading to trunk) is what I’ve been doing. Do a round of image updates and assign them to default. Clear ‘is master’ from all other storage nodes and move them to default group. Watch the logs for the sync to complete, move them back to their respective groups, recheck ‘is master’ on SNs since I only have a single SN per group. I only update these images a few times per year so that’s really not that painful. I could manage rsync scripts or a manual process but I’d rather let FOG do it especially if 1.3.0 will be along sometime in the not too distant future. Much appreciated!
While I said multicasting would not work, I should clarify that multicasting will only work on one interface of your consolidated FOG server.
I’m thinking that if he maintains separate Storage Groups per interface, and make each one a master, it would work. images can be shared across storage groups. But all replication only happens from the original storage group to the others, and not the other way around.
I still don’t understand why the OP is even doing what he’s doing though. Albeit I’ve not given this thread hardly any thought.
