Re: [Condor-users] IO: Incoming packet header unrecognized

[Richard Hosking <rhos012@xxxxxxxxxxxxxxxxx>]

Ah that seemed to do the trick, added that repository and re installed. 


Thanks for all your help!


On 8/04/2010, at 8:10 AM, Dan Bradley wrote:

> 
> It looks to me like the build of condor you are using does not support SOAP.  It does not look like a build of condor generated by the condor team.  Perhaps it is a stripped-down build that has optional features such as SOAP turned off.
> 
> Perhaps you can benefit from the condor debian repository now being maintained by the condor team:
> 
> http://www.cs.wisc.edu/condor/debian/
> 
> --Dan
> 
> Richard Hosking wrote:
>> Hmm doesnt look like i can wget files, error log shows the same error about the incoming packet header being unrecognized.
>> 
>> The output for condor version is
>> 
>> $CondorVersion: 7.2.4 Aug 22 2009 $
>> $CondorPlatform: I386-LINUX_DEBIAN_UKNOWN $
>> 
>> Thanks,
>> Richad
>> 
>> On 8/04/2010, at 2:13 AM, Dan Bradley wrote:
>> 
>>  
>>> Can you wget files in /usr/web from http://127.0.0.1:8081?
>>> 
>>> If not, what does condor_version say?
>>> 
>>> --Dan
>>> 
>>> Richard Hosking wrote:
>>>    
>>>> Hey Guys,
>>>> 
>>>> Im trying to setup condor and Cloud Scheduler (http://wiki.github.com/hep-gc/cloud-scheduler/). Cloud scheduler tries to connect to the condor scheduling web service but the connection gets reset each time it tries.
>>>> 
>>>> 
>>>> I have these setting in the condor_config file:
>>>> 
>>>> ENABLE_SOAP = TRUE
>>>> ENABLE_WEB_SERVER = TRUE
>>>> WEB_ROOT_DIR = /usr/web
>>>> ALLOW_SOAP = 127.0.0.1
>>>> SCHEDD_ARGS = -p 8081
>>>> 
>>>> And this is the following error messages that are found in the SchedLog:
>>>> 
>>>> IO: Incoming packet header unrecognized
>>>> DaemonCore: Can't receive command request from 127.0.0.1 (perhaps a timeout?)
>>>> 
>>>> 
>>>> There may be something wrong with my configuration of Cloud Scheduler that is causing badly formatted messages (which im looking into), but i was wondering if anyone could suggest reasons why condor could be acting this way, or even ways i can get more information about the reason the packet header is unrecognized.
>>>> 
>>>> Thanks for your time,
>>>> Richard
>>>> _______________________________________________
>>>> 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/
>>  
> _______________________________________________
> 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/