Multicast timeout?
-
I use FOG 1.2 now and am just going over some of our labs that we use FOG in. For many of them, we seem to be able to multicast fine but for a couple we can’t.
All hosts will sit at the blue screen waiting and nothing happens.
I checked the multicast log and apparently all 31 hosts have timeout notAnswered and notReady and eventually are just all dropped.
[CODE]Udp-sender 20120424
Using mcast address 234.1.63.202
UDP sender for (stdin) at 10.1.63.202 on eth0
Broadcasting control to 224.0.0.1
New connection from 10.9.110.68 (#0) 00000009
New connection from 10.9.110.172 (#1) 00000009
Starting transfer: 00000009
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
…
[/CODE]I’m not really sure where to start but what happened to /opt/fog/service/etc/config.php? I was going to try and increase UDPSENDER_MAXWAIT - but this doesn’t even exist in there. Is there any way to increase the timeout at all somewhere?
Cheers
-
The config for the FOG Services (FOGMulticastManager,FOGScheduler,FOGImageReplicator) fields are now done in /var/www/fog/lib/fog/Config.class.php
The /opt/fog/service/etc/config.php only tells the services where the webroot is for the system.
Hopefully that helps.
That said, the timeout can, at least in SVN and possibly 1.2.0 be set by the database.
-
Ooo, is there a handy link on how to do that?
