Re: Problem with up2date after upgrade

Could you check and make SURE you have 1.0.6? 


On Wed, 2002-10-30 at 16:47, Krell, Mike wrote:
>   We have a beta environment, running current-1.0.6-1 and hosting a channel
> for redhat 7.1.  I've upgraded from up2date-2.7.61-7.x.1 to
> up2date-2.8.39-1.7.1 on the servers subscribing to the 7.1 channel, and have
> started getting the following messages:
> 
> __________________
> From the local box:
> [root@betaminidb1 /root]# up2date -l
> 
> Fetching package list for channel: redhat-i386-7.1...
> ########################################
> 
> Fetching Obsoletes list for channel: redhat-i386-7.1...
> There was a fatal error communicating with the server.  The message was:
> 400: "Function getObsoletes not recognized" while attempting to get 
> $RHN/redhat-i386-7.1/getObsoletes/2002102818154
> [root@betaminidb1 /root]# 
> 
> From /var/log/current.log on the current server:  (repeats several times)
> Oct 30 15:34:56 ERROR: New function called: module up2date, function
> getObsoletes
> Oct 30 15:34:56   params were: [{'client_address': ('127.0.0.1', 45957),
>   'command': 'GET',
>   'headers': <mimetools.Message instance at 81e5b50>,
>   'path':
> 'https://10.2.2.200:8091/XMLRPC/$RHN/redhat-i386-7.1/getObsoletes/2002102818
> 1546',
>   'version': ''},
>  'redhat-i386-7.1',
>  '20021028181546']
> __________________
> 
> Any ideas on this?  Will most likely try downgrading to the former up2date
> version after posting this, just curious if anyone else has seen this kind
> of problem before.  Thanks!
> 
> -Mike
> 
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> 
-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.