[tools] up2date client config

Johan Booysen johan at matrix-data.co.uk
Fri Jun 8 20:13:02 CEST 2007 

Whoohoo!!

I had a look at mrepo's options, and noticed the -f option to force
generation of metadata.

So I did:

# mrepo -gfvv

rhel3es-i386: Create (old-style) yum repository for os
Digesting rpms 100 % complete:
kernel-smp-unsupported-2.4.21-40.EL.athlon.rpm   pm
   Total: 1159
   Used: 1159
   Src: 0

Writing header.info file
rhel3es-i386: Create (old-style) yum repository for other
Digesting rpms 100 % complete: pygtk2-python24-2.6.0-2_6.el3.at.i386.rpm
   Total: 4
   Used: 4
   Src: 0

Writing header.info file
rhel3es-i386: Create (old-style) yum repository for updates
Digesting rpms 100 % complete:
kernel-unsupported-2.4.21-47.0.1.EL.athlon.rpm   pmm
   Total: 1249
   Used: 1249
   Src: 0

Writing header.info file

And now the client updates happily!

Thanks very much for your suggestions and pointing me in the right
direction!

Johan

-----Original Message-----
From: tools-bounces at lists.rpmforge.net
[mailto:tools-bounces at lists.rpmforge.net] On Behalf Of Johan Booysen
Sent: 08 June 2007 18:54
To: djonas at vitalwerks.com
Cc: tools at lists.rpmforge.net
Subject: RE: [tools] up2date client config

Ah - good point!

Ok - now that the client RHEL3 machine has a valid systemid, it doesn't
complain about registration.

'up2date --nox -u' now yields:

Fetching package list for channel: rhel-i386-es-3...
########################################

Fetching package list for channel: base...

Fetching
http://pofadder/mrepo/rhel3es-i386/RPMS.os/headers/header.info...
There was some sort of I/O error: HTTP Error 404: Not Found

And I don't seem to have a headers directory on the mrepo server.  Could
mean that the yum metadata is in fact not generated at all?

Johan
 

-----Original Message-----
From: David Jonas [mailto:djonas at vitalwerks.com]
Sent: 08 June 2007 18:22
To: Johan Booysen
Cc: tools at lists.rpmforge.net
Subject: Re: [tools] up2date client config

Johan Booysen wrote:
> Hi David,
> 
> Many thanks for your reply.
> 
> In the meantime I've installed yum on the mrepo server and changed 
> mrepo.conf to specify that yum metadata should be generated:
> 'metadata = yum'.  Then ran the command 'mrepo -ugvv' but this didn't 
> yield anything related to whether or not it actually generated yum
metadata.
> Is it possible to somehow confirm what metadata was or wasn't created?
> 
> On the client I commented out the "up2date default" entry and added 
> the following to the sources file:
> 
> yum base http://pofadder/mrepo/rhel3es-i386/RPMS.os
> yum updates http://pofadder/mrepo/rhel3es-i386/RPMS.updates
> yum other http://pofadder/mrepo/rhel3es-i386/RPMS.other
> 
> But, the client still seems to be connecting to the RHN server and not

> to the mrepo one.  It's a virtual RHEL3 server that was previously 
> registered with RHN, and now, when running up2date, it complains about

> needing to reregister with RHN.

I am no authority on this, and in fact I know just enough to make our
system work, but I believe our RHEL3 boxes needed to be registered with
RHN before they would update against any repo.

Perhaps look at gensystemid in the mrepo package. Maybe if the box has a
proper systemid it will ignore registration and just try the sources.

Maybe someone else can comment more on how this works? I'd be curious
myself.

> Maybe it's the version of yum I'm using (yum-2.0.8-0.1.el3.rf), 
> although the documentation states that yum < 2.4 should be ok for 
> generating yum metadata.
> 
> If you have any advice I will greatly appreciate it.
> 
> Thanks.
> 
> Johan
> 
> -----Original Message-----
> From: David Jonas [mailto:djonas at vitalwerks.com]
> Sent: 08 June 2007 17:20
> To: Johan Booysen
> Cc: tools at lists.rpmforge.net
> Subject: Re: [tools] up2date client config
> 
> Johan Booysen wrote:
>> Hi,
>>  
>> I've just set up mrepo, and it looks very much like what we need.  
>> Great piece of work!
>>  
>> However, can anyone please tell me how I "point" up2date on Red Hat
>> EL3 clients at mrepo?
> 
> Depends a little on what metadata you're generating. We use apt, so 
> our line looks like this:
> 
> apt all http://mrepo.localnet rhel4es-i386 os extras updates local
> 
> Back in March there was a post that included a few yum lines:
> 
> yum rhel4os http://hostname/mrepo/rhel4es-i386/RPMS.os/
> yum rhel4updates http://hostname/mrepo/rhel4es-i386/RPMS.updates/
> yum local http://hostname/mrepo/rhel4es-i386/RPMS.local/
> 
>> I've found any number of instructions on how to use yum, but I want 
>> to
> 
>> be able to use up2date on the clients.
>>  
>> Most information about this simply says you need to modify 
>> /etc/sysconfig/rhn/sources to point at mrepo, but I can't find an 
>> example for doing that with up2date anywhere...so I've fiddled with 
>> the sources file but don't seem to be getting anywhere.
> 
> This instructions for the sources file should really get into 
> http://svn.rpmforge.net/svn/trunk/tools/mrepo/docs/redhat-network.txt
> 
>> I also tried using up2date-config to get up the gui and modified 
>> "..Server to use" to be 
>> http://pofadder/mrepo/rhel3es-i386/RPMS.updates/ (and variants of 
>> that
> 
>> url), but no luck.
>>  
>> Thanks in advance.
>>  
>> Johan
>>
>>
>> ---------------------------------------------------------------------
>> -
>> --
>>
>> _______________________________________________
>> tools mailing list
>> tools at lists.rpmforge.net
>> http://lists.rpmforge.net/mailman/listinfo/tools
> 

-- 

Vitalwerks, LLC / No-IP.com
_______________________________________________
tools mailing list
tools at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/tools

More information about the tools mailing list