I’m not able to check the cpu usage at this moment, but I did try to multicast the image first to 2 computers and that worked fine.
I rejoyced and tried them all again but the issue came back.

I then tried to send it to 25 computers and that worked but it wanted to use 6-7 hours on it and the image would send out around 100-200MB and then freeze for around a minute and then send more… The computer I house fog on is rather old and if it’s a cpu heavy job for the fog server to multicast then your theory might indeed fit what I saw.

For the fun of it I’m going to get some new fresh hardware and try it on that to see what results that yields.

Unicasting the image went fine btw

Hello.

I’m having a problem with multicasting on fog 0.32, CentOS 5.6 (final) and windows 7 machines (Dell Optiplex gx620).

It’s a rather strange problem where I’m trying to multicast 145 machines and it’s all fine with the first small partition, it multicasts that one just fine, but when it’s about to start the second partition it just sits and wait on the “please wait” screen.

[B]Now the log in /opt/fog/log/ show’s the following:[/B]
[SIZE=2]([COLOR=#ff0000]This is the multicast.log.udpcast.28 log and not the one called only “multicast.log”[/COLOR]) [/SIZE]

Udp-sender 2007-12-28
Using mcast address 236.21.238.31
UDP sender for (stdin) at 172.21.238.31 on eth0
Broadcasting control to 224.0.0.1
New connection from 172.21.238.123 (#0) 00000009
New connection from 172.21.238.156 (#1) 00000009
New connection from 172.21.238.152 (#2) 00000009
New connection from 172.21.238.151 (#3) 00000009
New connection from 172.21.238.136 (#4) 00000009 etc etc…

[B]The it show’s:[/B]

Starting transfer: 00000009
bytes= 97 552 re-xmits=0000001 ( 1.4%) slice=0066 73 709 551 615 - 132
bytes= 193 648 re-xmits=0000001 ( 0.7%) slice=0066 73 709 551 615 - 131
bytes= 289 744 re-xmits=0000001 ( 0.5%) slice=0066 73 709 551 615 - 131
bytes= 385 840 re-xmits=0000001 ( 0.3%) slice=0066 73 709 551 615 - 131
bytes= 481 936 re-xmits=0000001 ( 0.3%) slice=0066 73 709 551 615 - 131
bytes= 578 032 re-xmits=0000001 ( 0.2%) slice=0066 73 709 551 615 - 131
bytes= 674 128 re-xmits=0000001 ( 0.2%) slice=0066 73 709 551 615 - 130 etc etc…

[B]And then the interesting bits happen:[/B]

bytes= 25 370 800 re-xmits=0000001 ( 0.0%) slice=0066 73 709 551 615 - 130
bytes= 25 375 168 re-xmits=0000001 ( 0.0%) slice=0066 73 709 551 615 - 133
bytes= 25 375 612 re-xmits=0000001 ( 0.0%) slice=0066 73 709 551 615 - 132
Timeout notAnswered=[2,4,7,8,10,13,14,15,18,19,20,21,63,106,110,111,114,115,118,119,120,121,122,124,127,128,129,131,133,134,135,136,138,139,140,142,143,145] nrAns=108 nrRead=108 nrPart=146 avg=3661
Disconnecting #24 (172.21.239.10)
Disconnecting #89 (172.21.238.240)
Disconnecting #78 (172.21.238.143)
Disconnecting #28 (172.21.238.100)
Disconnecting #23 (172.21.238.227)
Disconnecting #31 (172.21.238.132)
Disconnecting #25 (172.21.238.111)
Disconnecting #22 (172.21.238.226) etc etc…

[B]And then follows:[/B]

Disconnecting #126 (172.21.238.174)
Disconnecting #130 (172.21.238.119)
Disconnecting #131 (172.21.238.194)
Bad command 0300
Bad command 0300
Bad command 0300
Bad command 0300
Bad command 0300
Bad command 0300 etc etc…

[B]After that I’m getting:[/B]

Dropping client #2 because of timeout
Disconnecting #2 (172.21.238.152)
Dropping client #4 because of timeout
Disconnecting #4 (172.21.238.136)
Dropping client #7 because of timeout
Disconnecting #7 (172.21.238.149)
Dropping client #8 because of timeout
Disconnecting #8 (172.21.238.138)
Dropping client #10 because of timeout
Disconnecting #10 (172.21.238.205)
Dropping client #13 because of timeout
Disconnecting #13 (172.21.238.104) etc etc…

[B]Almost at the end it says:[/B]

Dropping client #142 because of timeout
Disconnecting #142 (172.21.238.120)
Dropping client #145 because of timeout
Disconnecting #145 (172.21.238.173)
Transfer complete.^G
Disconnecting #0 (172.21.238.123)
Disconnecting #1 (172.21.238.156)
Disconnecting #3 (172.21.238.151)
Disconnecting #5 (172.21.238.140)
Disconnecting #6 (172.21.238.129)
Disconnecting #9 (172.21.238.130)
Disconnecting #12 (172.21.238.207)
Disconnecting #16 (172.21.238.211)
Disconnecting #27 (172.21.239.8)

[B]And then finally:[/B]

Udp-sender 2007-12-28
Using mcast address 236.21.238.31
UDP sender for (stdin) at 172.21.238.31 on eth0
Broadcasting control to 224.0.0.1

Any idea’s what can be wrong? It complains about timeout altho the machines all started up within 20 minutes from the first to the last and looking at [URL=‘http://fogproject.org/forum/threads/multicast-timeout.529/’]this[/URL] post I’ve also checked the Config.php --> UPDSENDER_MAXWAIT setting and I see that it’s on 0 (so I guess that means it will wait forever and not timeout anything).

The size of the image I’m trying to deploy is 3.7Gb so it’s the right size.

Hello.

First I’m going to copy over the history from the old forums, so you can see/read what’s already been done:

Original post [URL=‘https://sourceforge.net/projects/freeghost/forums/forum/716419/topic/4794903/index/page/1’]here[/URL]

balticsea

2011-11-05 01:05:00 PDT

Cloning with FOG is new for me.
I´ve got a good general computer-experience (DOS, Windows, dBase, Ghost, etc.).
So it was easy to understand, how to install and work with FOG.

I´m teacher at a german school and have to update 75 equal computers.
The clients: eeepc-netbooks (1000H) with Windows XP sp3.
Partitions: C-drive NTFS (80GB, system), d-drive NTFS (70 GB, nearly empty) and an EFI partition (40MB).
After uploading a master-image I can find the 4 single image-files in a correct size on the server.

The problem:
When I deploy an image, everything seems to work well, but after 45 seconds the total imaging-process is complete: After “restoring the mbr = ok”, there are 4 short imaging-runs which finish with “ok” after 5% complete.
I can´t read the scrolling text after this, it disappears to fast.
(Is there a report anywhere?)
When I do this on a client with an empty hd, the machine won´t start afterwards: “Error reading disk”
When I upload an image from one of my clients and now make some modifications on its C- and D-drive, the result after deploying on the same machine is: The C-drive is not written over, the D-drive is the old one again (written over from the image).

---

Fog-server: Windows XP sp3 with vmplayer and Ubuntu 8.04 / FOG 0.32
[The problem was the same with a real Ubuntu 11.04 and FOG 0.32]

hellslayr

2011-12-20 05:31:52 PST

Hi.

I’m experiencing the very same problem that is described above with the exact same netbook model (Asus 1000H)
I’ve successfully fogged these machines before but that was when I formated the disk and put in Win XP pro on them.

Now after 3 years in service we’re selling the machines so I fiddle out the recovery dvd and ghosts them back to Windows XP Home edition… The Ghost makes the 3 partition mentioned by balticsea in his post.
Uploading the image goes fine, but when I try to deploy it stops at around 70-90MB fogged data (2ish %) and then goes on to say “restore mbr”… The message do go away quite fast, but I did see it reporting this: “The image contains and unclean file 0 1”… Googeling that made me no wiser sadly.

I then tried (using Gparted) to resize the partitions and make one partition and then use the “Single partition - NTFS Only Resizable” option but I had the same issue there as well.

Since I don’t have access to a windows xp home edition dvd I can’t format the machine either and build the image from scratch, I have to use the recovery dvd and that will make the 3 partitions regardless.

Any ideas?

Ps: Tried two different fog servers as well (Both 0.32 release of fog tho)

itismike

2011-12-20 06:07:56 PST

Hi HellslayeR. Try posting this on the new FOG fourms:
[url]http://fogproject.org/forum/[/url]

An “unclean disk” usually means it wasn’t shut down cleanly and the NTFS journal is out-of-sync. If you have a bootable machine, run a disk cleanup, a defrag, chkdsk /x, then cleanly shut down the PC and try imaging it again.

Don’t follow up here - go to the new FOG forums:
[url]http://fogproject.org/forum/[/url]

So I now tried to do as you suggested itsmike and I did a cleanup, defrag and chkdsk /x and uploaded then deployed a new image, but sadly the error is still there.

I’m kinda blank at this point, but are there any log files anywhere that I could look at? Or do you have any other ideas as to what might be wrong?

Thanks for the replies so far