Posts made by Mark Shelton

It was a problem with a formula in the coding. I changed it to work on 0.32. Now with 1.2 I can only get bandwidth info for the master node…storage node info does not appear at all.

Hi all,
I had FOG 0.32 st up with a couple of remote storage nodes, which were tied back to the master. Images would replicate (slowly) over the internet, and I could monitor where the data was going via the bandwidth graph which showed the nodes transmission/reception as well as the master. This seems to be missing in FOG 1.2. The image attached shows bandwidth display with master node and one remote storage node under FOG 0.32. I cannot get the storage node bandwidth info to appear with 1.2. Only bandwidth info for the master node appears. Anyone have an answer or idea remote node info is missing or have I missed a step? FYI, I can switch between storage locations in the disk space pie chart, so that part works fine.
Thanks in advance.[ATTACH=full]1434[/ATTACH]

[url=“/_imported_xf_attachments/1/1434_bandwidth graph.jpg?:”]bandwidth graph.jpg[/url]

That works well chad-bisd, thanks. It appears to transfer with a maximum combined bandwidth of about 1Mbit/s. So transferring one file at a time or two in parallel will most likely take a similar overall time. Not sure what regulates this rate, can’t see any config in my IPSec tunnel to adjust speed. It appears that the other issue of the replication process “quitting” has gone, before I used your modified file. Perhaps it was a Ubuntu 12.04 update that fixed that. Thanks again.

That sounds great Chad-bisd! Just what is needed for remote sites. Sorry for not replying sooner, I’ve had other things happening. I’ll try this code next week and let you know the results.

Hi,
A request…
We have 3 FOG servers, 1 local and 2 remote accessed over WAN through modem/fireall via IpPSec tunnel.
There are unique PC’s at the remote sites, and when deploying everything is fine as the nodes are all synchronised with images from the master.
The issue arises when updates or changes are made to these PC’s. We use SteadyState with scripts to keep the PC’s locked down and yet have antivirus/windows updates done automatically overnight.
When I make changes I usually deploy the image(which does not have Steady State Disk Protection activated) to the PC , make the changes then upload back to the master node. This is fin locally, but this cannot be done at the remote sites, as the upload would take many hours to go back to the master, THEN would be sync’d back to the remote node.
It would be great if the Master Node allowed image uploading from remote hosts to the local (remote from master) node first then sync back to itself overnight or whenever.

Hope this is a clear explanation. Thanks, Mark

Thanks chad-bisd.
Parallel syncing would be great, even if the process still times out it will have replicated both sites first.
Mark

Hi,
We have 3 Fogservers: 1 master node located locally, and 2 located remotely. They are connected over the WAN (via modems and firewalls) using IPSec. Our OS is Ubuntu 12.04, and FOG version 0.32.
When uploading an image from the host, the replicator begins transferring shortly afer the upload to the first remote node. It takes many hours as it only transfers at less than 1Mbit/sec. When it completes, the replicator process stops and does not restart. It also will not transfer to the second remote node. Both IPsec tunnels are set with the same parameters, and I have had them working in the past. It appears to be sonething that has changed since 12.04 upgrade, but I can’t be certain of this.

Log output below:
[url]http://tinypic.com/r/i2itqb/6[/url]

Any help on this or similar experiences would be appreciated.
Thanks, Mark

Hi again Lee,

Just found the answer that worked for me.
See this thread:
[url]http://fogproject.org/forum/threads/systems-not-shutting-down-after-upload-or-deploy.989/[/url]

Regards
Mark

Hi Lee,

I have the same issue, have been trying for a while to solve. Some PC’s work, others dont, even with the sane hardware! It’s bizarre.

Some forums say by setting different restart options in /etc/default/grub.cfg file this will solve the issue, but I think this is only for the host machine, not the Fog clients.
[url]http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/[/url]

I’ve tried these but it doesnt fix my issues. Earlier kernels work, but then there are different issues, like some machines not imaging.
This is a pain, especilly with remote site as it prevents completing remote rebiulds.

[B]Can anyone else shed some light on this, are there any reboot options available with the host imaging script?[/B]

Thanks in advance, Mark