@Wayne-Workman It depends on the image. For the ones linked to the storage node, i.e the middle school group we have, it says Middle School. But the checkbox isn’t checked, should it be? Thats all thats in there though
Posts made by K.Hays
-
RE: Fog: multicasting across subnets
-
RE: Fog: multicasting across subnets
Well here is the updated situation. As you know not too long ago we set up a fog server that could unicast and do all that across subnets no problem. Theoretically it should have been able to multicast (since we had a fog server up and running before which was able to do so, but it is currently and permanently inaccessible) but it would pause at the partclone screen. Then we decided to try storage nodes, as making modifications to the switches may be complicated at the moment. So we set up two different storage nodes in two different buildings, both with trunk and both set up AS storage nodes. They were loaded correctly and were also able to unicast too and from them, the images were physically stored on them also. When we tried to multicast though, it stopped again at the partclone screen. I’m assuming this is most likely a network issue, which we will be more able to solve this summer, as during the school year it gets complicated. But i just wanted to check to see if there is another solution, or possibly something that I am not doing correctly. Sorry for the influx of questions but it would be great if this was ready by the time we started summer maintenance.
-
RE: Fog: multicasting across subnets
@Wayne-Workman I found another log for multicast manager and it says “unable to locate udp sender”
-
RE: Fog: multicasting across subnets
@Wayne-Workman It says the image file was not found. Which is weird because we were able to unicast using that file.
specifically it said the task was found but it failed to execute because the image was not found. -
RE: Fog: multicasting across subnets
@Wayne-Workman When i try to enable FOGMulticastManager it tells me it fails.
Edit: Never mind, i stopped it then restarted it and now it says it’s running. -
RE: Fog: multicasting across subnets
@Wayne-Workman yeah i watched it but i didnt check the storage node itseld to see if it actually saved there. I cant see why it wouldnt have though unless its a problem some people have. I think it was set up correctly. We were able to image to and from it.
-
RE: Fog: multicasting across subnets
@Wayne-Workman yes,yes,and yes. We made sure of all that.
-
RE: Fog: multicasting across subnets
@K.Hays it will do the same thing as before, and it just stops at the partclone screen.
-
RE: Fog: multicasting across subnets
@Wayne-Workman We got the node setup but multicast still doesnt work. We can unicast no problem.
-
RE: Fog: multicasting across subnets
How do I set up this storage node? Sorry for the dumb question but we loaded fog as a storage node and we think we put it on the fog server correctly but apparently not.
-
RE: Fog: multicasting across subnets
@Tom-Elliott We’re about to test setting up a storage node right now. How exactly does this make multicast able? Does the storage node just act like a segway from the server to the Vlan then?
-
Fog: multicasting across subnets
So I’ve looked into this a bit and I’ve figured there are two ways to do this. One is to just have the switches configured to do such a thing, which were working on to no avail yet. We are able to ping other computers from different Vlans on our internal network so this should be possible. The second option would be to have a storage node in each Vlan. Which would be better and more functional to use, and how would one set this up? it would be ideal to be able to just use the one server, but either option is viable. Im running Ubuntu 14.04 with Fog Trunk.
-
RE: PXE-E32 error, unable to boot to fog from pxe
@Wayne-Workman True, but the reason i posted this was not solved by reloading. In fact reloading hadn’t helped with it at all before posting this, because i did have 14.04 + Trunk at one point and was still getting this error. The issue behind the original post was PXE-E32 error which was solved by changing option 66 and 67 for not only just the dhcp servers, but all of the ip pools also, which is something we hadn’t thought to check until wireshark showed somewhere it was set to the old fog server. But, we now have fog up and running regardless, so thanks everyone! You’re all great!
-
RE: PXE-E32 error, unable to boot to fog from pxe
So, i reinstalled ubuntu 14.04 and downloaded the trunk version of FOG, and it works! Haven’t tried to imaging anything yet as i am out of time but i will soon. Thanks to everyone who helped out with this problem, i appreciate it!
edit: Just started to upload an image successfully, thanks again for all the help! ill update this as soon as i know it completed without error. -
RE: PXE-E32 error, unable to boot to fog from pxe
So, whats the consensus here. What do i need to do to get this setup.
-
RE: PXE-E32 error, unable to boot to fog from pxe
@Tom-Elliott should i just reboot?
-
RE: PXE-E32 error, unable to boot to fog from pxe
@Wayne-Workman now i got this
Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully- Stopping FOG Computer Imaging Solution: FOGMulticastManager
…done. - Stopping FOG Computer Imaging Solution: FOGImageReplicator
…done. - Stopping FOG Computer Imaging Solution: FOGScheduler
…done.
mysql stop/waiting
mysql start/running, process 25428 - Stopping web server apache2
- There are processes named ‘apache2’ running which do not match your pid file which are left untouched in the name of safety, Please review the situation by hand.
is this because i had my web gui open?
- Stopping FOG Computer Imaging Solution: FOGMulticastManager
-
RE: PXE-E32 error, unable to boot to fog from pxe
@Wayne-Workman Errors were encountered while processing:
/var/cache/apt/archives/apache2-bin_2.4.16-4+deb.sury.org~precise+4_i386.deb
/var/cache/apt/archives/apache2-data_2.4.16-4+deb.sury.org~precise+4_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
thats whats at the bottom sorry not 7084