[Spacewalk-list] Interesting OSAD Problem
Waldirio Manhães Pinheiro
waldirio at gmail.com
Tue Dec 9 04:28:31 UTC 2014
Hello friends, good morning
Let'me try to explain, but by points
- osad
The osad daemon normally works fine and the timeout is relatively low, the
response time is very good because jabber works with broadcast, according
the size of your network can delay, but maybe ..., 5, ... 10 seconds, btw
to work the client need to be registered, with the same ssl key and is
mandatory the client see the server by fqdn (in general), because the
certificate is generated using fqdn. To do this, you can use a dns or you
can register in the /etc/hosts.
So, if your server is spacewalk.info.net, you client should response when
you try "ping spacewalk.info.net" or "ping spacewalk".
At least, check all logs in /var/log/rhn/*, looking for errors or warnings,
for sure, they will help you!
Use rhn_check in crontab will works :-), but use osad is a little bit more
"recommended". :-))
- register the client
You can sign your new centos machine for example in a spacewalk repo client
(http://yum.spacewalkproject.org/2.2/RHEL/6/x86_64/), now you can install
the packages to register your client in the SW server. If you need
additional files/packages, probably you need add a epel repo.
- kickstart
To create a kickstart from SW you need before prepare the environment, so
create a tree of your distro, configure in your SW, add some additional
packages that will support kickstart environment .., asap I'll prepare a
post about it, but for now, probably if we send to you a ks file to you use
in your environment, will not work to register automatically in SW. My
recommendation is, install a machine, add a repo, install necessary
packages to add in SW and enjoy.
I believe be only this, I'm preparing a new SW environment to test debian
packages and another things., asap I'll come back with news.
Have a wonderful night.
______________
Atenciosamente
Waldirio
msn: waldirio at gmail.com
Skype: waldirio
Site: www.waldirio.com.br
Blog: blog.waldirio.com.br
LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
PGP: www.waldirio.com.br/public.html
On Mon, Dec 8, 2014 at 10:12 PM, Nick Tailor <HTailor at bclc.com> wrote:
> Also the osad package… I think is only available in the child channel
> (network-tools) If you don’t have that child channel available on the key,
> it wont pull the package down from spacewalk J
>
>
>
> Did you add the child-channel to your activation key?
>
>
>
> Nick Tailor
>
> http://www.nicktailor.com
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Zinny
> *Sent:* December-08-14 3:01 PM
> *To:* ATH KEBEI; spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] Interesting OSAD Problem
>
>
>
> ATH,
>
>
>
> I have tried what you suggested and yet still getting the same error but
> unfortunately the clients I kickstarted from the SW server does not have
> osad service installed and there's no way to installed them since the
> packages are not showing unless alternatively I copy the package from SW
> server and then use rpm to install it.
>
>
>
>
>
> Sent from my iPhone
>
>
> On Dec 8, 2014, at 2:58 PM, ATH KEBEI <kebei at yahoo.com> wrote:
>
> yum repolist (KEYword here is REPO, not packages) will not list
> packages but will list your repos which are in /etc/yum.repos.d
>
>
>
> First, remove all the default repos on all SW clients that came when you
> did the installation. You do not need this again. You need the repos that
> belong to the software channels your system is registered to on your SW
> server. Do the following
>
>
>
> Try to remove yum cache on each client and then make a new cache:
>
> cd /etc/yum.repos.d
>
> mkdir /old
>
> mv * /old # This moves all the default repos into the old directory
>
>
>
> rm -rf /var/cache/yum # This removes yum cache
>
> yum clean all
>
> yum makecache # This makes a new cache
>
> yum update # rhn-check -vvvv will only work if the repos
> of your software channels are on each client
>
>
>
> If it doesn't work, unregister each client and then re-register them again:
>
>
>
> rhnreg_ks --serverUrl=https://IP or FQDN/XMLRPC
> --activationkey=1-a81b573814336d70a007c39f6f2b7f3 --force
>
>
>
>
>
> FOR OSAD:
>
> Did you do the following on each client:
>
> rpm -Uvh https://ip or fqdn of SW server/pub/RHN-ORG-TRUSTED-SSL-CERT
> <https://spacewalker1.waselinux.net/pub/RHN-ORG-TRUSTED-SSL-CERT>
>
> yum install osad
> vim /etc/sysconfig/rhn/osad.conf
>
> change the line starting with osa_ssl_cert to:
>
> osa_ssl_cert = /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
>
>
>
>
>
>
>
> *Oh yes, you can make today a great day! Thanks.*
>
>
> * Very Respectfully, A. C. Kebei*
>
>
> * Always, Very Committed to Excellence and the fair treatment of all.*
>
>
> ------------------------------
>
> *From:* ezinne ibeagbazi <eibeagbazi at gmail.com>
> *To:* stuart.green at doccentrics.com; "spacewalk-list at redhat.com" <
> spacewalk-list at redhat.com>
> *Sent:* Monday, December 8, 2014 2:11 PM
> *Subject:* Re: [Spacewalk-list] Interesting OSAD Problem
>
>
>
> Here is the output when I run the rhn_check -vvv command.
>
>
>
>
>
> [root at child ~]# rhn_check -vvv
>
> D: opening db environment /var/lib/rpm cdb:mpool:joinenv
>
> D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
>
> D: locked db index /var/lib/rpm/Packages
>
> D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
>
> D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
>
> D: loading keyring from rpmdb
>
> D: opening db index /var/lib/rpm/Name rdonly mode=0x0
>
> D: added key gpg-pubkey-fd431d51-4ae0493b to keyring
>
> D: added key gpg-pubkey-2fa658e0-45700c69 to keyring
>
> D: Using legacy gpg-pubkey(s) from rpmdb
>
> D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
>
> D: do_call packages.checkNeedUpdate('rhnsd=1',){}
>
> D: opening db environment /var/lib/rpm cdb:mpool:joinenv
>
> D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
>
> D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
>
> D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
>
> D: loading keyring from rpmdb
>
> D: opening db index /var/lib/rpm/Name rdonly mode=0x0
>
> D: added key gpg-pubkey-fd431d51-4ae0493b to keyring
>
> D: added key gpg-pubkey-2fa658e0-45700c69 to keyring
>
> D: Using legacy gpg-pubkey(s) from rpmdb
>
> D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
>
> D: closed db index /var/lib/rpm/Providename
>
> D: closed db index /var/lib/rpm/Name
>
> D: closed db index /var/lib/rpm/Packages
>
> D: closed db environment /var/lib/rpm
>
> Loaded plugins: product-id, rhnplugin
>
> Config time: 0.423
>
> D: login(forceUpdate=False) invoked
>
> D: readCachedLogin invoked
>
> D: Checking pickled loginInfo, currentTime=1418061265.49,
> createTime=1418058632.07, expire-offset=3600.0
>
> D: readCachedLogin(): using pickled loginInfo set to expire at
> 1418062232.07
>
> D: rpcServer: Calling XMLRPC up2date.listChannels
>
> This system is receiving updates from RHN Classic or RHN Satellite.
>
> Setting up Package Sacks
>
> updateLoginInfo() login info
>
> D: login(forceUpdate=True) invoked
>
> logging into up2date server
>
> D: rpcServer: Calling XMLRPC up2date.login
>
> D: writeCachedLogin() invoked
>
> D: Wrote pickled loginInfo at 1418061275.67 with expiration of
> 1418064875.67 seconds.
>
> successfully retrieved authentication token from up2date server
>
> D: logininfo:{'X-RHN-Server-Id': 1000010003, 'X-RHN-Auth-Server-Time':
> '1418063315.26', 'X-RHN-Auth-Channels': [['centos6', '20141204103056', '1',
> '1']], 'X-RHN-Auth': '4i2mZWbybU6Y9udbCEc2uA==', 'X-RHN-Auth-User-Id': '',
> 'X-RHN-Auth-Expire-Offset': '3600.0'}
>
> updateLoginInfo() login info
>
> D: login(forceUpdate=True) invoked
>
> logging into up2date server
>
> D: rpcServer: Calling XMLRPC up2date.login
>
> D: writeCachedLogin() invoked
>
> D: Wrote pickled loginInfo at 1418061280.78 with expiration of
> 1418064880.78 seconds.
>
> successfully retrieved authentication token from up2date server
>
> D: logininfo:{'X-RHN-Server-Id': 1000010003, 'X-RHN-Auth-Server-Time':
> '1418063320.32', 'X-RHN-Auth-Channels': [['centos6', '20141204103056', '1',
> '1']], 'X-RHN-Auth': 'F7sKe7ONjWcMSsr2x/2Ysw==', 'X-RHN-Auth-User-Id': '',
> 'X-RHN-Auth-Expire-Offset': '3600.0'}
>
> updateLoginInfo() login info
>
> D: login(forceUpdate=True) invoked
>
> logging into up2date server
>
> D: rpcServer: Calling XMLRPC up2date.login
>
> D: writeCachedLogin() invoked
>
> D: Wrote pickled loginInfo at 1418061285.97 with expiration of
> 1418064885.97 seconds.
>
> successfully retrieved authentication token from up2date server
>
> D: logininfo:{'X-RHN-Server-Id': 1000010003, 'X-RHN-Auth-Server-Time':
> '1418063325.44', 'X-RHN-Auth-Channels': [['centos6', '20141204103056', '1',
> '1']], 'X-RHN-Auth': 'k2kAqHa5P1bhFQV3hX0cJA==', 'X-RHN-Auth-User-Id': '',
> 'X-RHN-Auth-Expire-Offset': '3600.0'}
>
> D: local action status: ((6,), 'Fatal error in Python code occured', {})
>
> D: rpcServer: Calling XMLRPC registration.welcome_message
>
> D: closed db index /var/lib/rpm/Providename
>
> D: closed db index /var/lib/rpm/Name
>
> D: closed db index /var/lib/rpm/Packages
>
> D: closed db environment /var/lib/rpm
>
>
>
> [root at child ~]# yum repolist
>
> Loaded plugins: product-id, rhnplugin, security, subscription-manager
>
> This system is not registered to Red Hat Subscription Management. You can
> use subscription-manager to register.
>
> This system is receiving updates from RHN Classic or RHN Satellite.
>
> repo id repo name
> status
>
> centos6
> centOS6.6-Minimal-x86_64 0
>
> repolist: 0
>
>
>
>
>
>
>
> On Mon, Dec 8, 2014 at 9:40 AM, Stuart Green <stuart.green at doccentrics.com>
> wrote:
>
> Hi,
>
>
> On 08/12/2014 14:31, ezinne ibeagbazi wrote:
> > Hi All,
> >
> > Can someone tell me why all my client server can not get packages from
> the
> > SW server, this is the same case for all the machines I kickstart from
> the
> > SW server and physical machine that I added as client to the SW server.
> >
> There's many issues that could cause this(not necessarily this bug),
> have you checked the relevant logs?
>
> If you run the command: rhn_check -vvv on the client machine, does it
> receive the packages?
>
>
> > When I run yum repolist, it list all the repos but no packages. Please
> how
> > can I solve this issue.
>
> AFAIK, thats what 'yum repolist' is meant to do.
>
>
>
> > Thanks
> >
> >
> > On Mon, Dec 8, 2014 at 3:17 AM, Patrick Hurrelmann <
> > patrick.hurrelmann at lobster.de> wrote:
> >
> >> On 02.12.2014 19:27, Glennie, Jonathan - 0443 - MITLL wrote:
> >>> Hello All-
> >>>
> >>>
> >>>
> >>> I’m having an interesting osad problem… osa-dispatcher starts fine on
> >>> the server, but from a client, attempting to do a “service osad start”
> >>> generates the “Unable to connect to jabber servers” log messages.
> >>> However, if I manually launch osad from the command line, either by
> >>> running “osad _N –v –v –v –v” or simply typing “osad”, everything
> >>> launches just fine… I see the connection on the server side and I can
> >>> successfully ping/push commands to it from the GUI.
> >>>
> >>>
> >>>
> >>> What could be causing he difference in behavior? I’ve checked and no
> >>> matter what way the service is launched, it runs as root so I wouldn’t
> >>> think it’s a permissions issue… Thanks for any help.
> >>>
> >>>
> >>>
> >>> -Jon
> >>
> >> This should be fixed by RHBA-2014-1964 [1]. Waiting for the CentOS
> >> rebuild to verify.
> >>
> >> Regards
> >> Patrick
> >>
> >> [1] https://rhn.redhat.com/errata/RHBA-2014-1964.html
> >>
> >> --
> >> Lobster SCM GmbH, Hindenburgstraße 15, D-82343 Pöcking
> >> HRB 178831, Amtsgericht München
> >> Geschäftsführer: Dr. Martin Fischer, Rolf Henrich
> >>
> >> _______________________________________________
> >> Spacewalk-list mailing list
> >> Spacewalk-list at redhat.com
> >> https://www.redhat.com/mailman/listinfo/spacewalk-list
> >>
> >
> >
> >
> >
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
> >
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
>
>
> --
>
> Ezinne M Ibeagbazi, Bsc, RHCE, RHCSA,VCA-Cloud, VCA-DCA, A+
>
> Linux Systems Engineer
>
> VINDS INC,
>
> Landover, MD
>
> 301-364-7694
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> ------------------------------
> This email is intended only for the addressee. It may contain confidential
> or proprietary information that cannot be disclosed without BCLC's
> permission. If you have received this email in error, please notify the
> sender immediately and delete the email.
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141209/523b5f15/attachment.htm>
More information about the Spacewalk-list
mailing list