@cnkpadobi

You might want to switch to the working branch.

FOG Install instructions on wiki

Here you will see instructions on how to install Git and switch to working branch. Hope this helps.

@Wayne-Workman @Tom-Elliott I just imaged one computer with the empty storage group in the location plug in and it pulled the image from the slave node. I’m going to leave it like that for now and when we go to image the lab later today, I will report. Like I said before, it is strange that the storage group is not visually represented on the location management page but once you click on the location, you can see that the storage group is defined.

@sebastian-roth

@Tom-Elliott
I tried to test this as well. I’m on SVN 6080 and when creating a group and hitting create, it takes me to a separate page with this message

{“msg”:“Successfully added selected hosts to the group!”}

When I hit the back button, then go to groups, the group is there along with random clients I did not check to add into this group. Really strange. Also forgot to mention that when I tried to delete the group, it also does not delete the clients in that group.

@george1421 @Tom-Elliott I will go ahead and restore the fog.postinit script back to its intended use. Call the patch.fullreg script to reflect exactly what we are trying to do, that is to copy our custom script and replace /bin/fog.man.reg That way as @george1421 has said to prevent any updates from replacing the script by accident.

@dpotesta50

looks like your FTP credentials are not matching properly. The error is not on the Windows 10 machine but on the fog server ftp credentials.

@joe-gill We need more tabs!!!

@george1421

I will check tomorrow and place the results here.

@klkwarrior May I suggest the following:

1. If your project of imaging lots of machines are on the same network, maybe image as a group based on the model computers? Or are the computers at various sites?

2. Not sure if latest working branch has this but I know that 1.6 does have the deploy image option from the client which just basically allows for you to choose the image to deploy rather than defining anything. That I think is what is probably going to accomplish for you and you don’t have to do anything on the web UI in the sense of adding additional functions. Just define the image, upload, and then begin imaging.

@sebastian-roth

Sweet. The default setting for the loglevel is 4. Taking it down to 3 no longer produces those USB errors. Thank you. The computer does register and I can image but those USB errors were extremely annoying. Seems like this will suppress those messages and works just fine now.

@Sebastian-Roth So I went ahead and switched to dev-branch and upgrade nodes along with fog server. Seems like it’s working fine and the storage group info is now displayed. Thank you again for your help in this.

@Sebastian-Roth Fair enough. I will switch over to the dev-branch on nodes and fog server once we’re done with these projects. I should be able to do it prior to our winter break. Thank you again for your help on this.

@Sebastian-Roth Cool. We have several projects in the mix right now but once it slows down, I plan on upgrading to 1.5.5 since i haven’t had a chance to do so. Would that fix happen to be in the working branch by any chance or should i stay on the dev branch?

@Tom-Elliott @Wayne-Workman Worked like a charm. The lab imaged with 20 going on at once with both nodes active and remaining clients were placed in line to wait until slots opened up. Thank you both for all your help.

Looks like it works. Here are my logs. Once upload completed, took about 15 minutes for replicator to begin. Once it pushed files to slave, I did a FOGImageReplicator restart and looks good.

[11-13-18 10:22:26 am]  | Image Name: BCS-Velocity
[11-13-18 10:22:27 am]   # BCS-Velocity: No need to sync d1.fixed_size_partitions (BCS-Slave)
[11-13-18 10:22:27 am]   # BCS-Velocity: No need to sync d1.mbr (BCS-Slave)
[11-13-18 10:22:28 am]   # BCS-Velocity: No need to sync d1.minimum.partitions (BCS-Slave)
[11-13-18 10:22:28 am]   # BCS-Velocity: No need to sync d1.original.fstypes (BCS-Slave)
[11-13-18 10:22:28 am]   # BCS-Velocity: No need to sync d1.original.swapuuids (BCS-Slave)
[11-13-18 10:22:28 am]   # BCS-Velocity: No need to sync d1.partitions (BCS-Slave)
[11-13-18 10:22:29 am]   # BCS-Velocity: No need to sync d1p1.img (BCS-Slave)
[11-13-18 10:22:30 am]   # BCS-Velocity: No need to sync d1p2.img (BCS-Slave)
[11-13-18 10:22:30 am]  * All files synced for this item.
[11-13-18 1:22:11 pm]  * Starting Image Replication.
[11-13-18 1:22:11 pm]  * We are group ID: 6. We are group name: BCS
[11-13-18 1:22:11 pm]  * We are node ID: 9. We are node name: BCS-Master
[11-13-18 1:22:11 pm]  * Attempting to perform Group -> Group image replication.
[11-13-18 1:22:11 pm]  | Replicating postdownloadscripts
[11-13-18 1:22:12 pm]  * Found Image to transfer to 1 node
[11-13-18 1:22:12 pm]  | File Name: postdownloadscripts
[11-13-18 1:22:13 pm]   # postdownloadscripts: No need to sync fog.postdownload (BCS-Slave)
[11-13-18 1:22:13 pm]  * All files synced for this item.
[11-13-18 1:22:13 pm]  | Replicating postinitscripts
[11-13-18 1:22:15 pm]  * Found Image to transfer to 1 node
[11-13-18 1:22:15 pm]  | File Name: dev/postinitscripts
[11-13-18 1:22:16 pm]   # dev/postinitscripts: No need to sync fog.postinit (BCS-Slave)
[11-13-18 1:22:16 pm]  * All files synced for this item.
[11-13-18 1:22:16 pm]  | Not syncing Image: 32-Dell-790
[11-13-18 1:22:16 pm]  | This is not the primary group.
[11-13-18 1:22:16 pm]  | Not syncing Image: 64-Dell-790
[11-13-18 1:22:16 pm]  | This is not the primary group.
[11-13-18 1:22:17 pm]  * Not syncing Image between groups
[11-13-18 1:22:17 pm]  | Image Name: BCS-Velocity
[11-13-18 1:22:17 pm]  | There are no other members to sync to.
[11-13-18 1:22:17 pm]  * Attempting to perform Group -> Nodes image replication.
[11-13-18 1:22:18 pm]  * Found Image to transfer to 1 node
[11-13-18 1:22:18 pm]  | Image Name: 32-Dell-790
[11-13-18 1:22:19 pm]   # 32-Dell-790: No need to sync d1.fixed_size_partitions (BCS-Slave)
[11-13-18 1:22:20 pm]   # 32-Dell-790: No need to sync d1.mbr (BCS-Slave)
[11-13-18 1:22:20 pm]   # 32-Dell-790: No need to sync d1.minimum.partitions (BCS-Slave)
[11-13-18 1:22:20 pm]   # 32-Dell-790: No need to sync d1.original.fstypes (BCS-Slave)
[11-13-18 1:22:20 pm]   # 32-Dell-790: No need to sync d1.original.swapuuids (BCS-Slave)
[11-13-18 1:22:20 pm]   # 32-Dell-790: No need to sync d1.partitions (BCS-Slave)
[11-13-18 1:22:21 pm]   # 32-Dell-790: No need to sync d1p1.img (BCS-Slave)
[11-13-18 1:22:23 pm]   # 32-Dell-790: No need to sync d1p2.img (BCS-Slave)
[11-13-18 1:22:23 pm]  * All files synced for this item.
[11-13-18 1:22:24 pm]  * Found Image to transfer to 1 node
[11-13-18 1:22:24 pm]  | Image Name: 64-Dell-790
[11-13-18 1:22:25 pm]   # 64-Dell-790: No need to sync d1.fixed_size_partitions (BCS-Slave)
[11-13-18 1:22:25 pm]   # 64-Dell-790: No need to sync d1.mbr (BCS-Slave)
[11-13-18 1:22:26 pm]   # 64-Dell-790: No need to sync d1.minimum.partitions (BCS-Slave)
[11-13-18 1:22:26 pm]   # 64-Dell-790: No need to sync d1.original.fstypes (BCS-Slave)
[11-13-18 1:22:26 pm]   # 64-Dell-790: No need to sync d1.original.swapuuids (BCS-Slave)
[11-13-18 1:22:26 pm]   # 64-Dell-790: No need to sync d1.partitions (BCS-Slave)
[11-13-18 1:22:27 pm]   # 64-Dell-790: No need to sync d1p1.img (BCS-Slave)
[11-13-18 1:22:28 pm]   # 64-Dell-790: No need to sync d1p2.img (BCS-Slave)
[11-13-18 1:22:28 pm]  * All files synced for this item.
[11-13-18 1:22:29 pm]  * Found Image to transfer to 1 node
[11-13-18 1:22:29 pm]  | Image Name: BCS-Velocity
[11-13-18 1:22:30 pm]   # BCS-Velocity: No need to sync d1.fixed_size_partitions (BCS-Slave)
[11-13-18 1:22:30 pm]   # BCS-Velocity: File hash mismatch - d1.mbr: 89b972e8f6585f2606a6658d58b9f66d57957ac7d57fc2f7fd7d8882a12d8722 != 341041528cb53b70422e1c39270490452de62ad764c72541e4f6eb1890f3365d
[11-13-18 1:22:30 pm]   # BCS-Velocity: Deleting remote file d1.mbr
[11-13-18 1:22:30 pm]   # BCS-Velocity: File hash mismatch - d1.minimum.partitions: 23b505385e9008070c65c42d950dff96d5cf39e99478b6b81c7a867e8bcadb02 != 899d69e652f3c9683d83deeec82f231bba2f4df0a01d706b5acbba9992a10861
[11-13-18 1:22:30 pm]   # BCS-Velocity: Deleting remote file d1.minimum.partitions
[11-13-18 1:22:31 pm]   # BCS-Velocity: No need to sync d1.original.fstypes (BCS-Slave)
[11-13-18 1:22:31 pm]   # BCS-Velocity: No need to sync d1.original.swapuuids (BCS-Slave)
[11-13-18 1:22:31 pm]   # BCS-Velocity: File hash mismatch - d1.partitions: ac70ba6fe1d57bf4a8ba01459f85f075f3df10bdcbd99a368ec1523078b8fde6 != ff0c6a27b7627ad4416fa46da7f57d2c4b0f4a621d2e7ca5414fa2faa5d43a96
[11-13-18 1:22:31 pm]   # BCS-Velocity: Deleting remote file d1.partitions
[11-13-18 1:22:31 pm]   # BCS-Velocity: File size mismatch - d1p1.img: 8699649 != 8696814
[11-13-18 1:22:31 pm]   # BCS-Velocity: Deleting remote file d1p1.img
[11-13-18 1:22:31 pm]   # BCS-Velocity: File size mismatch - d1p2.img: 36002135558 != 41888768241
[11-13-18 1:22:31 pm]   # BCS-Velocity: Deleting remote file d1p2.img
[11-13-18 1:22:32 pm]  | CMD: lftp -e 'set xfer:log 1; set xfer:log-file "/opt/fog/log/fogreplicator.BCS-Velocity.transfer.BCS-Slave.log";set ftp:list-options -a;set net:max-retries 10;set net:timeout 30;  mirror -c --parallel=20 -R --ignore-time -vvv --exclude ".srvprivate" "/images/BCS-Velocity" "/images/BCS-Velocity"; exit' -u fog,[Protected] 10.210.100.62
[11-13-18 1:22:32 pm]  | Started sync for Image BCS-Velocity - Resource id #20268
[11-13-18 1:29:35 pm]  | Sync finished - Resource id #20268

Here is log after ImageReplicator restart occured.

[11-13-18 1:31:02 pm] Interface Ready with IP Address: 10.210.100.61
[11-13-18 1:31:02 pm] Interface Ready with IP Address: 127.0.0.1
[11-13-18 1:31:02 pm] Interface Ready with IP Address: 127.0.1.1
[11-13-18 1:31:02 pm]  * Starting ImageReplicator Service
[11-13-18 1:31:02 pm]  * Checking for new items every 10800 seconds
[11-13-18 1:31:02 pm]  * Starting service loop
[11-13-18 1:31:05 pm]  * Starting Image Replication.
[11-13-18 1:31:05 pm]  * We are group ID: 6. We are group name: BCS
[11-13-18 1:31:05 pm]  * We are node ID: 9. We are node name: BCS-Master
[11-13-18 1:31:06 pm]  * Attempting to perform Group -> Group image replication.
[11-13-18 1:31:06 pm]  | Replicating postdownloadscripts
[11-13-18 1:31:08 pm]  * Found Image to transfer to 1 node
[11-13-18 1:31:08 pm]  | File Name: postdownloadscripts
[11-13-18 1:31:09 pm]   # postdownloadscripts: No need to sync fog.postdownload (BCS-Slave)
[11-13-18 1:31:10 pm]  * All files synced for this item.
[11-13-18 1:31:10 pm]  | Replicating postinitscripts
[11-13-18 1:31:11 pm]  * Found Image to transfer to 1 node
[11-13-18 1:31:11 pm]  | File Name: dev/postinitscripts
[11-13-18 1:31:12 pm]   # dev/postinitscripts: No need to sync fog.postinit (BCS-Slave)
[11-13-18 1:31:12 pm]  * All files synced for this item.
[11-13-18 1:31:12 pm]  | Not syncing Image: 32-Dell-790
[11-13-18 1:31:12 pm]  | This is not the primary group.
[11-13-18 1:31:12 pm]  | Not syncing Image: 64-Dell-790
[11-13-18 1:31:12 pm]  | This is not the primary group.
[11-13-18 1:31:13 pm]  * Not syncing Image between groups
[11-13-18 1:31:13 pm]  | Image Name: BCS-Velocity
[11-13-18 1:31:13 pm]  | There are no other members to sync to.
[11-13-18 1:31:13 pm]  * Attempting to perform Group -> Nodes image replication.
[11-13-18 1:31:14 pm]  * Found Image to transfer to 1 node
[11-13-18 1:31:14 pm]  | Image Name: 32-Dell-790
[11-13-18 1:31:16 pm]   # 32-Dell-790: No need to sync d1.fixed_size_partitions (BCS-Slave)
[11-13-18 1:31:16 pm]   # 32-Dell-790: No need to sync d1.mbr (BCS-Slave)
[11-13-18 1:31:16 pm]   # 32-Dell-790: No need to sync d1.minimum.partitions (BCS-Slave)
[11-13-18 1:31:16 pm]   # 32-Dell-790: No need to sync d1.original.fstypes (BCS-Slave)
[11-13-18 1:31:17 pm]   # 32-Dell-790: No need to sync d1.original.swapuuids (BCS-Slave)
[11-13-18 1:31:17 pm]   # 32-Dell-790: No need to sync d1.partitions (BCS-Slave)
[11-13-18 1:31:18 pm]   # 32-Dell-790: No need to sync d1p1.img (BCS-Slave)
[11-13-18 1:31:19 pm]   # 32-Dell-790: No need to sync d1p2.img (BCS-Slave)
[11-13-18 1:31:19 pm]  * All files synced for this item.
[11-13-18 1:31:20 pm]  * Found Image to transfer to 1 node
[11-13-18 1:31:20 pm]  | Image Name: 64-Dell-790
[11-13-18 1:31:21 pm]   # 64-Dell-790: No need to sync d1.fixed_size_partitions (BCS-Slave)
[11-13-18 1:31:22 pm]   # 64-Dell-790: No need to sync d1.mbr (BCS-Slave)
[11-13-18 1:31:22 pm]   # 64-Dell-790: No need to sync d1.minimum.partitions (BCS-Slave)
[11-13-18 1:31:22 pm]   # 64-Dell-790: No need to sync d1.original.fstypes (BCS-Slave)
[11-13-18 1:31:22 pm]   # 64-Dell-790: No need to sync d1.original.swapuuids (BCS-Slave)
[11-13-18 1:31:23 pm]   # 64-Dell-790: No need to sync d1.partitions (BCS-Slave)
[11-13-18 1:31:23 pm]   # 64-Dell-790: No need to sync d1p1.img (BCS-Slave)
[11-13-18 1:31:24 pm]   # 64-Dell-790: No need to sync d1p2.img (BCS-Slave)
[11-13-18 1:31:24 pm]  * All files synced for this item.
[11-13-18 1:31:26 pm]  * Found Image to transfer to 1 node
[11-13-18 1:31:26 pm]  | Image Name: BCS-Velocity
[11-13-18 1:31:27 pm]   # BCS-Velocity: No need to sync d1.fixed_size_partitions (BCS-Slave)
[11-13-18 1:31:27 pm]   # BCS-Velocity: No need to sync d1.mbr (BCS-Slave)
[11-13-18 1:31:27 pm]   # BCS-Velocity: No need to sync d1.minimum.partitions (BCS-Slave)
[11-13-18 1:31:28 pm]   # BCS-Velocity: No need to sync d1.original.fstypes (BCS-Slave)
[11-13-18 1:31:28 pm]   # BCS-Velocity: No need to sync d1.original.swapuuids (BCS-Slave)
[11-13-18 1:31:28 pm]   # BCS-Velocity: No need to sync d1.partitions (BCS-Slave)
[11-13-18 1:31:29 pm]   # BCS-Velocity: No need to sync d1p1.img (BCS-Slave)
[11-13-18 1:31:30 pm]   # BCS-Velocity: No need to sync d1p2.img (BCS-Slave)
[11-13-18 1:31:30 pm]  * All files synced for this item.

@Sebastian-Roth Yup. I read earlier about that. Followed your instructions and all nodes and fog server are updated with the replication branch. I’m currently uploading updated image to an image that exists currently. Awaiting for it to finish uploading and tailing the replication log.

@Wayne-Workman @Tom-Elliott I just imaged one computer with the empty storage group in the location plug in and it pulled the image from the slave node. I’m going to leave it like that for now and when we go to image the lab later today, I will report. Like I said before, it is strange that the storage group is not visually represented on the location management page but once you click on the location, you can see that the storage group is defined.

@Sebastian-Roth What I meant to say is after I upload an updated image to a master node, with the changes in the replication branch, should I let the replication service run on it’s own? OR should I force the replication by restarting the replication service? I figured that by restarting the replication service will speed things up to check the logs after I successfully upload the updated image.

@Wayne-Workman Interesting bug I think may exist. So I went into the location plug in and set the ‘node’ field to exactly what you said ‘please select an option’ and hit update then going to the location management page I no longer see a storage group set for the location. The strange thing is that going into the location it does show a storage group defined. It’s just when I go to the location management page that it doesn’t show. So by setting the ‘node’ field to blank, it appears that no storage group is defined at least according to the main menu of the location plug in.

Here is what it looks like. Hopefully you understand what I’m trying to describe.

@Sebastian-Roth I will be updating a image definition this week. I ran into an issue with imaging a lab with storage nodes. I’m testing the solution out today and then I will be updating image to storage group that has storage nodes. Should I force the replication or let it run on it’s own? I’m curious if it matters how to let the replication start.