Two things…
The following command listed above:
cp -R /new/new/ssl/ /opt/fog/snappins is misspelled here. I ran the correct spelling…
Secondly, I checked the /opt/fog/snapins directory and it appears the permissions were not set correctly. I adjusted that and am re-running the fog installer.
I’ll keep you posted!
Cheers,
Joe
Hi all,
I just finished migrating our old Ubuntu box over to a new VM running Debian 8.8. I followed the wiki – https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG. Everything seems to have worked very smoothly. I moved our images off of our old physical server to a Windows box along with the SSL directory and database info. Then I copied all of that over to the new physical server running our VMs. All of this went fairly well.
The new server is up and running. FOG is installed. The database is migrated. I just tried to remotely wipe a few machines and noticed that the PXE was not activating WOL.
I did copy over the entire SSL directory. Than I followed this as per the WIKI…
@Wayne-Workman The wiki was a little unclear on the part listed below. I was a little confused how the new SSL settings were supposed to make it to the new server based on the commands. Please correct me if I’m misinterpreting things. 
Thanks!
rm -rf /opt/fog/snapins/ssl
# mv /images/dev/ssl /opt/fog/snapins -- I replaced this to my needs. I ran the below command instead... <<<<<
cp -R /new/new/ssl/ /opt/fog/snappins
#Debian, Ubuntu, and Ubuntu variant users should use this command to set permissions:
chown -R fog:www-data /opt/fog/snapins/ssl
The only step that I had to modify in my project was that I copied all of my files to a directory I created on the new server entitled new. Then when I moved all of my files over they were in a directory entitled new as well. So my directory structure is this : /new/new/ssl/. See the above code…
Also, I did re-run the fog installer after I completed moving the SSL directory…
Anyhow, if you all have any suggestions please let me know!
Thanks!!!
Cheers,
Joe Gill
Townsend K-12 Schools
@Tom-Elliott
Thanks Tom! I’ll check that out. That sounds like it could be the issue!
I’m rebuilding the FOG Server today!
Everything is set to go. I backed up all of my images locally. We migrated to a new physical server. So this is a brand new install. I’m going with Debian.
The machine sleep settings I have tried adjusting are the settings in Power Options within the OS.
I have noticed that as of about 6 months ago I started having random machines on our network log off the user despite what the machine sleep settings are set to. I have tried adjusting the power settings, looking at the settings for the graphics cards ect.
Has anyone ever had anything similar to this happen before?
Thanks!
Joe Gill
Townsend K12 Schools
The resolution here was the following…
My image WAS corrupt. It DID image just fine with UniCast. I remade my image and all is happy. I also made an adjustment to the resize option on my image. I set it to be resizeable.
I’m all going good now. All is happy.
Just in time for my server upgrade!! I’ll be installing Debian here in the next couple days…
Cheers!!!
Joe Gill
Townsend K-12 Schools
Thanks for helping me on this one!!
I finally got it!!! I made those adjustments… BOOM! It worked!
Received the following error message when MultiCasting…
I will post the particlone.log file as well when I get to a different PC.
Any advice is appreciated! I thought I had this thing licked… Apparently, I still have problems!!
Thanks!!
Joe Gill
Townsend K-12 Schools
Well, the image I pushed via the server works just fine unicast.
Now, that said, I make a pre-sysprep image (one prior to running sysprep when it’s in audit stage) and one post-sysprep prior to reboot. The pre-sysprep image is stable and pushes via multicast. The post-sysprep image fails. SO… I’m going to re-capture my image and try again. Ugh… Glad to hopefully resolve this one.
Thanks for making me think, as usual.
Cheers,
Joe
@Tom-Elliott
So I created a new storage group with my storage node on it and nothing else. I set the image that I was having issue with multicasting to that storage group. Then I pushed the image via UniCast and things worked fine from the storage node.
I will re-push this same image and change the storage group back to the server and see what happens…
Joe
@Tom-Elliott
So I can see it’s pulling the image from the Master Node on at least one occasion that was successful. Let me see if I can push an image from the node.
@george1421
The MAC address from my captured target machine is there.
The images seem to push fine via unicast. I’m still having problems with MultiCast.
I have tried pushing to multiple labs, just to make sure their isn’t any underlying problem with a switch, and I’m still having the same issue. The image appears to push, but when you start the machine, you get the message below.
Any ideas of what to try would be helpful… Thanks!
I did check the /images directory from the terminal and it shows no directory created. Just a file with the images name…
@Tom-Elliott
@Developers
@george1421
Apparently yesterday I made two images that were empty. The GUI shows that one has data and the other has nothing in it. Everything appeared to finish normal. I’m at a loss on this one.
I’m going to try and capture a new image and see what the heck is going on.
The other images pushes fine from uni-cast just not fine on multi-cast… don’t know what the heck is going on.
Any advice is appreciated as I’m dead in the water.
I figured out that issue… Going to retry the new image and see if the other issue comes back.
@Tom-Elliott
@Developers
Just updated to FOG 1.4.2…
Re-ran multicast on machine that bombed earlier… Same problem.
I created a new image on a different machine type and thought I’d try and push it… Got a new issue…
How do we resolve this one? Maybe they are connected… Ugh…
@Tom-Elliott said in Multicasting -- Image Fails After Completion:
You’re 100% sure the same machine and same image works with unicast but fails with multicast?
I’m 100% Positive! In fact I Uni-casted to one of the 5 that failed last night and verified it was working this morning. Then this morning I tried multicasting just to 1 of the 5 test machines and it failed with the screenshot posted here.
Are their any other logs you might need?
@Developers
@george1421
@Tom-Elliott
Well I thought I was in the clear… Long story short… Uni-cast is working fine, multicast finishes but leaves me with Windows errors.
Here is my multicast log from a test I did with 1 machine this morning. Below that is the screenshot of what the error I am getting when I start that machine. Like I said, I can uni-cast the same image and things run great.
I also have a screen shot of the successful uni-cast deployment. It appears to be pulling the image from the server. I was concerned about errors from my image transfer from the other thread I had posted… But that appears to not be an issue here.
[06-14-17 1:16:54 pm] | Task (48) Multi-Cast Task is new!
[06-14-17 1:16:54 pm] | Task (48) Multi-Cast Task has been cleaned.
[06-14-17 1:16:54 pm] | Task (48) /images/3020BaseImage image file found.
[06-14-17 1:16:54 pm] | Task (48) Multi-Cast Task 1 client found.
[06-14-17 1:16:54 pm] | Task (48) Multi-Cast Task sending on base port: 64006.
[06-14-17 1:16:54 pm] | Command: /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 600 --portbase 64006 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/3020BaseImage/d1p1.img;/usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 10 --portbase 64006 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/3020BaseImage/d1p2.img;
[06-14-17 1:16:54 pm] | Task (48) Multi-Cast Task has started!
[06-14-17 1:17:04 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:17:14 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:17:24 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:17:34 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:17:44 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:17:54 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:18:04 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:18:14 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:18:24 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:18:34 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:18:44 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:18:54 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:19:04 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:19:14 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:19:24 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:19:34 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:19:44 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:19:54 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:20:04 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:20:14 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:20:24 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:20:34 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:20:44 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:20:54 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:21:04 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:21:14 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:21:24 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:21:34 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:21:45 pm] | Task (48) Multi-Cast Task is already running with pid: 19373.
[06-14-17 1:21:55 pm] | Task (48) Multi-Cast Task is no longer running.
[06-14-17 1:21:55 pm] | Task (48) Multi-Cast Task has been completed.
[06-14-17 1:22:05 pm] * No tasks found!
Let me know if you need any other log files. I will be working in the lab all day so if anyone would like to remote in and take a peek, let me know. Thanks!!
Cheers,
Joe Gill
Townsend K-12 Schools
@george1421
The image transfer is complete!
I had to touch the .mntcheck file to the /images and /images/dev directory. But other than that, I’m up and rolling again! Woo Whooo!
I can’t wait to start fresh with Debian and clean up my server a bit. That’ll be next month’s project!!
Thanks everyone who’s contributed!! I appreciate all the advice! 
Cheers,
Joe Gill
Townsend K-12 Schools