[mdlug] Centralized package management tools *update*
Michael ORourke
mrorourke at earthlink.net
Mon Dec 15 14:51:59 EST 2008
Greg,
Any success yet?
I did notice something in the docs... they suggested creating an activation key and assign it to a base channel. Which I did, and it worked. However, I did a "--force" when I joined the base channel with the new key and it created a duplicate system entry in the spacewalk database. Also, I installed and configured the osad client to enable remote activities to be scheduled immediately. Having duplicate server names did not initially cause a problem until I deleted one. Which evidently was the one that was using some unique identifier that allowed osad to funtion properly. After updating the server id on the client, I was able to get osad working again.
-Mike
----- Original Message -----
From: Wojtak, Greg
To: MDLUG's Main discussion list
Sent: Thursday, December 11, 2008 2:31 PM
Subject: Re: [mdlug] Centralized package management tools *update*
Same results - one thing I did notice in the logs was:
rhnException: ('Could not initialize Oracle database connection',
'exceptions.RuntimeError', 'Unable to acquire Oracle environment
handle')
RHN 14734 2008/12/11 14:26:56 -04:00: ("DATABASE CONNECTION TO 'xe'
LOST", "Exception information: 'NoneType' object has no attribute
'cursor'")
This is from /etc/rhn/satellite-httpd/logs/error_log
Are you seeing the same thing?
Greg
-----Original Message-----
From: mdlug-bounces at mdlug.org [mailto:mdlug-bounces at mdlug.org] On Behalf
Of Michael ORourke
Sent: Thursday, December 11, 2008 8:32 AM
To: MDLUG's Main discussion
Subject: Re: [mdlug] Centralized package management tools *update*
Okay... here is what I did thus far.
1. Standard install, followed directions on the Wiki.
2. Created a new 'activation key' within Spacewalk GUI.
Systems --> Activation Keys --> Create new key
Using these values...
Description: Default Key
Key: <blank>
Usage: <blank>
Base Channels: Spacewalk Default
Add-On Entitlements: <nothing checked>
Universal Default: Checked
3. Created software channel using python script
Example:
create_channel.py --label "centos-5.2-i386" --name "CentOS 5.2
32-bit" --summary "32-bit CentOS 5.2 channel"
4. Attempt to join a client to spacewalk (failed)
Example:
rhnreg_ks --verbose --force --activationkey="<default key created
with
spacewalk GUI " --serverUrl http://myspacewalk.server.local/XMLRPC
5. Disabled firewall on spacewalk server.
6. Retry the join (failed)
7. Admin --> Spacewalk Configuration --> Restart (takes about 5 minutes
on
our system)
8. Verify spacewalk is up and running, then retry join (Success!)
-Mike
----- Original Message -----
From: Michael ORourke
To: MDLUG's Main discussion list
Sent: Tuesday, December 09, 2008 5:00 PM
Subject: Re: [mdlug] Centralized package management tools
I'm currently doing a reinstall, and I plan on taking better notes this
time.
Strange thing, I was able to register a system with my spacewalk server,
but
I was not able to join any channels. Until I created a channel manually
with that script. Were you able to register a client with your
spacewalk
server?
I don't remember the exact steps I took to be able to register and join
the
channel, but I did have it working. This time around, I should have
some
better notes that I can share regarding the proceedure. Hopefully I can
get
it working again! :-)
-Mike
----- Original Message -----
From: Wojtak, Greg
To: MDLUG's Main discussion list
Sent: Tuesday, December 09, 2008 2:04 PM
Subject: Re: [mdlug] Centralized package management tools
It sounds like we are having the same problems. I can't get a channel
created - when I click on the Manage Entitlement Channels link it
takes
me to the Overview page, so I had to use the python script to create
the
channel manually. Still no go, I can't get a client registered. I
asked about it on the Spacewalk list but haven't heard back about that
particular issue. How did you get a client registered?
-----Original Message-----
From: mdlug-bounces at mdlug.org [mailto:mdlug-bounces at mdlug.org] On
Behalf
Of Michael ORourke
Sent: Tuesday, December 09, 2008 1:33 PM
To: MDLUG's Main discussion list
Subject: Re: [mdlug] Centralized package management tools
Greg,
You have any luck with Spacewalk?
It is not an easy tool to install and configure, that's for sure..
Also, the wiki docs seem a bit disorganized. It took me several
attempts to get it installed and working. Then I had trouble with the
channels. Mainly adding clients to a channel. I was finally able to
add a client to a channel, populate it with a few RPMs, and push the
RPMs to the client. Also, I noticed that the rhnsd client daemon
wakes
up every 240 minutes (default) and checks the spacewalk server for any
actions. I had initially thought that was 240 seconds. So an "apply
now" action could really be hours later.
-Mike
----- Original Message -----
From: Wojtak, Greg
To: MDLUG's Main discussion list
Sent: Monday, December 01, 2008 9:38 AM
Subject: Re: [mdlug] Centralized package management tools
Ah, the holy grail for CentOS/RHEL systems (aside from paying Red
Hat
$13,000 a year for a satellite server!).
I am looking for the same thing (and I'm sure any other Linux
Sysadmin
is) for years. I'm still using the strategy of "install updates on
dev
server, keep the rpm's that were downloaded, move them to test, then
production, and pray to God that the same packages are in sync
across
all environments."
Not very efficient. I've been looking into building a yum server
and
configuring the yum-updatesd to download the packages that I roll
out.
A little better than using cron, but not by much.
I'd be interested to hear if you find anything.
Greg Wojtak
-----Original Message-----
From: mdlug-bounces at mdlug.org [mailto:mdlug-bounces at mdlug.org] On
Behalf
Of Michael ORourke
Sent: Monday, December 01, 2008 9:29 AM
To: MDLUG's main mailing list
Subject: [mdlug] Centralized package management tools
Lug nuts,
I'm looking for some recommendations, specifically for the CentOS
5.2
distribution, for a centralized package management system or tools.
I've
spent some time doing vaious Google searches, but haven't found what
I
was
looking for aside from basic tools such as 'yum' and 'up2date',
which
are
designed to run on a single host. I was hoping that I would stumble
upon
some existing tools that could be leveraged in an existing
environment.
What I would really like is:
* Gui tools (browser based).
* Internal centralized server (package repository).
* Centralized management (for development, QA, & production).
* Ability to schedule updates and manually push updates.
* Auditing capabilities (which servers have what packages
installed).
* Ability to manage servers by group (e.g. Dev App servers).
Running 'yum -update' from cron on each server isn't a good
strategy,
especially when it comes to production systems. I would like to
have
the
capability to pull down patches to a centralized server, then push
the
patches/updates to the development/QA environment, and finally out
to
the
production systems after testing is completed.
Is that too much to ask for. :-)
Any suggestions/recommendations/ideas?
Thanks,
Mike
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug
------------------------------------------------------------------------
------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.12/1822 - Release Date:
12/1/2008 8:23 AM
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug
------------------------------------------------------------------------
------
Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.14/1829 - Release Date:
12/4/2008
2:59 PM
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug
Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.14/1829 - Release Date:
12/4/2008
2:59 PM
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug
More information about the mdlug
mailing list