I am having a similar problem. Were you able to resolve this?
Posts made by TRSD
-
RE: Aditionnal storage node problem
-
RE: Image path not the same in log as it is storage node.
I have determined the image path this storage node is using is the path from another storage group Master node. I have 2 storage groups and each have a Master node. Why would this be looking at the other storage group? I have verify the storage group is correct on the image.
-
RE: Change storage node, won't download image
This is similar to the problem I am having. Any solutions?
-
RE: Image path not the same in log as it is storage node.
I have removed glusterfs from the new storage node and I am still getting “image not found” when trying to multicast. Unicast works fine to that server for both upload and download. I have also changed the IP address of the new storage node on the fog server so it should be setup as a normal storage node. What else can I check here?
-
RE: Image path not the same in log as it is storage node.
Thanks. So is it possible to have 2 different mounts on a server that point to the /image directories remote servers?
For example, the current situation is:
If my fog server is 10.10.10.1 and I have /images mounted on 10.10.10.2:/images and /ivimages mounted on 10.10.10.3:/images
I then have storage_node_1 with IP of 10.10.10.1 and image_path /images and storage_node_2 with IP of 10.10.10.1 and image_path /ivimages
Is there a different way to do this with mounts to remote servers via glusterfs?
-
RE: Image path not the same in log as it is storage node.
Also, If I try image a machine via Unicast I get “mounting 10.x.x.x:/ivimages/ on /images failed: Permission Denied”
ivimages is already mounted and accessible via glusterfs. -
RE: Image path not the same in log as it is storage node.
Why is it looking in /images instead of /ivimages when it produces the error if my image path is set to /ivimages?
-
RE: Image path not the same in log as it is storage node.
/ivimages is already created and it is mounted on a remote server to the /images folder on that server. I can change directories to it and the privileges look good.
We already have /images mounted to another remote server so I was hoping to use another storage node for the second storage server.
-
Image path not the same in log as it is storage node.
I have changed the image path in a storage node to /ivimages but I am getting the following error in the multicast.log file:
Multicast Group Quick Deploy failed to execute, image file:/images/IVWin7Room4 not found!
I have double checked the image is using the correct storage node.
What am I missing?
-
RE: FOG 1.2.0 multicast issues
It looks like we have resolved this issue by installing Ubuntu 14.04 on both our FOG server and image server and then installing the GlusterFS as per Tom’s advice. Thank you Tom for all of your help.
-
RE: FOG 1.2.0 multicast issues
I have done a fresh install of Ubuntu 14.04 LTS and SVN and restored database.
Now the multicast process doesn’t stop but it still doesn’t multicast.
Here is the log:[07-24-14 1:55:48 pm] * No tasks found!
[07-24-14 1:55:58 pm] | Task (1) Multicast Group Quick Deploy is new!
[07-24-14 1:55:58 pm] | Task (1) /images/PeteTest image file found.
[07-24-14 1:55:58 pm] | Task (1) 2 client(s) found.
[07-24-14 1:55:58 pm] | Task (1) Multicast Group Quick Deploy sending on base port: 58570
[07-24-14 1:55:58 pm] CMD: cat /images/PeteTest/rec.img.|/usr/local/sbin/udp-sender --min-receivers 2 --portbase 58570 --interface eth0 --full-duplex --ttl 32 --nokbd;cat /images/PeteTest/sys.img.|/usr/local/sbin/udp-sender --min-receivers 2 --portbase 58570 --interface eth0 --full-duplex --ttl 32 --nokbd;
[07-24-14 1:55:58 pm] | Task (1) Multicast Group Quick Deploy has started.
[07-24-14 1:56:08 pm] | Task (1) Multicast Group Quick Deploy is already running PID 2520
[07-24-14 1:56:18 pm] | Task (1) Multicast Group Quick Deploy is already running PID 2520I have checked all of the options we have previously gone through in this thread and omping does work for multicast. Any ideas since we can get this far?
-
RE: FOG 1.2.0 multicast issues
Also, why wouldn’t I change the /etc/exports folder on the fog server to match the image box:?
/images *(rw,sync,no_wdelay,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure) -
RE: FOG 1.2.0 multicast issues
Would it make sense to change the owner of PeteTest to www-data for testing purposes?
-
RE: FOG 1.2.0 multicast issues
Unfortunately, we did run out of space on this so we can’t test on the one server. Do you think permissions would be an issue since unicast imaging does work?
-
RE: FOG 1.2.0 multicast issues
This says it will take about 18 minutes. I will leave it running but I have to leave the office now. I really appreciate your help with this and will report back in the morning with a status.
Thank you very much.
-
RE: FOG 1.2.0 multicast issues
touch: cannot touch `/images/dev/.mntcheck’: No such file or directory
-
RE: FOG 1.2.0 multicast issues
done. restarted nfs kernel servers and FOGMulticastManager and still not working
-
RE: FOG 1.2.0 multicast issues
They both match. Which should I change, fog server or image box?
-
RE: FOG 1.2.0 multicast issues
That is from the box where the images are stored.