Re: [Condor-users] incomplete udp for command 0 / command 2

[Dan Bradley <dan@xxxxxxxxxxxx>]

rob@xxxxxxxxxxxxxxxxxx wrote:

> Hello,
>
> Unfortunately, upgrading to condor version 6.8.8 doesn't seem to have 
> solved the problem. The upgraded client is once again sending incomplete
> master updates. I haven't yet seen any broken updates coming from the
> 6.8.6 client since I applied the D_NETWORK logging delay workaround.
>
> Has UDP handling been changed between 6.8.8 and 7.0.0?
>  

No.  I would not expect any UDP problems in 6.8.8 to be fixed by 
upgrading to 7.0.0.

If the logging delay continues to work, then that gives us a pretty good 
clue.

--Dan

> Thanks,
>
> Rob de Graaf
>
> On Fri, 1 Feb 2008, Rob de Graaf wrote:
>
>  
>
> > Hi,
> >
> > Thank you all for your suggestions. I will upgrade one client to 6.8.8,
> > set D_NETWORK on the other, and leave tcpdump running over the weekend.
> >
> > Hopefully both will behave!
> >
> > Thanks,
> >
> > Rob de Graaf
> >
> > Dan Bradley wrote:
> >    
> >
> > > Daniel Forrest wrote:
> > >
> > >      
> > >
> > > > This is a problem with UDP under Windows, it considers a packet "sent"
> > > > when the sendto() call is made, not when the packet has actually hit
> > > > the wire.  So if sendto() is called too rapidly (e.g. when collector
> > > > update packets are split) you can lose the previous UDP packet if it
> > > > hasn't really been sent yet.
> > > >
> > > > What we did was add "D_NETWORK" to the MASTER_DEBUG and STARTD_DEBUG
> > > > flags in the config file.  The added delay of logging the UDP packets
> > > > seems to be enough to keep this from happening.
> > > >
> > > > You can alternatively use "UPDATE_COLLECTOR_WITH_TCP = True" and avoid
> > > > UDP entirely.
> > > >
> > > >
> > > >        
> > > A patch for this problem that Dan Forrest is referring to was released
> > > in 6.8.7, but some mistake was made, because no note of this was made in
> > > the 6.8.7 version history.
> > >
> > > Rob, can you please try 6.8.8 or 7.0.0 and see if this solves your problem?
> > >
> > > --Dan
> > >
> > > _______________________________________________
> > > Condor-users mailing list
> > > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> > > subject: Unsubscribe
> > > You can also unsubscribe by visiting
> > > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > >
> > > The archives can be found at:
> > > https://lists.cs.wisc.edu/archive/condor-users/
> > >      
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
> > The archives can be found at:
> > https://lists.cs.wisc.edu/archive/condor-users/
> >
> >    
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at: 
> https://lists.cs.wisc.edu/archive/condor-users/
>