[Spacewalk-list] Clients registered with spacwalk proxy does not pick up scheduled actions
Christian Ejlertsen
ce at lytzenit.dk
Thu Jan 15 10:08:18 UTC 2015
Thank you very much, that did the trick.
And yes our normal procedure is to kickstart the server into the
spacewalk server then when it's ready move the machine and register it
on the proxy server afterwards and now we add removing the
osad-auth.conf to the list :)
Would be great if the osad credentials was wiped when a server is
re-registered with rhnreg_ks to spacewalk.
Maybe it will work if it gets re-registered with a System Activation Key
instead, since it will register with the same id etc. I will give that
try on the next system.
Thank you for the help.
--
---
Med velig hilsen / Kind Regards
Lytzen IT A/S
Christian Ejlertsen
Tlf: +45 96230360
Dir: +45 88328707
On Wed, 2015-01-14 at 16:19 -0600, Matthew Madey wrote:
> When you look at your client in WebUI, does the OSA status say
> "online"? The Spacewalk proxy server runs it's own instance of
> jabberd, and has a jabber database. If your client was previously
> registered directly to the Spacewalk server, it's osad credentials are
> no longer valid. I'd recommend doing the following on the client
> system:
>
>
> service osad stop ; rm -f /etc/sysconfig/rhn/osad-auth.conf ; service
> osad start
>
>
> The osad service will regenerate the osad-auth.conf with a fresh set
> of credentials to authenticate with the jabber server on the Spacewalk
> proxy. If you are still having issues after that, I'd recommend you
> increase the debug verbosity on the client by
> modifying /etc/sysconfig/rhn/osad.conf. Then tail the /var/log/osad
> file on the client to see what is happening.
>
> On Wed, Jan 14, 2015 at 1:31 AM, Christian Ejlertsen <ce at lytzenit.dk>
> wrote:
> Is there anyone that has an idea towards why osad would not
> pickup a
> scheduled task when the client is registered to the proxy?
>
> - Christian
>
> On Sun, 2014-12-21 at 22:14 +0000, Christian Ejlertsen wrote:
> > Hello
> >
> > I have a spacewalk 2.2 system with so far only a few clients
> on it. Any
> > client directly connected to the spacewalk server is working
> perfectly
> > with osad.
> >
> > I have recently added a spacewalk proxy in the dmz and is
> testing it.
> > I can register the clients with the proxy and they appear in
> the
> > management interface as registered with the proxy.
> > The OSA ping does not return online status for the client
> and any action
> > is not picked up automatically before running rhn_check on
> the client
> > registered with the proxy.
> > I've been trying to debug it but I guess my knowledge about
> the osad and
> > jabberd interworkings is lagging. Ports 80,443,5222,5269 are
> all
> > reachable from spacewalk proxy to spacewalk server, names
> resolve on the
> > proxy and the server.
> > Hope someone can share some insight or some places to look
> for the more
> > debug information.
> >
> > Below is the osad output when running it with osad -N -vvvv.
> >
> > 2014-12-21 21:59:01 osad._setup_config: Updating
> configuration
> > 2014-12-21 21:59:01 osad._setup_config: Time drift 0
> > 2014-12-21 21:59:01 osad._setup_config: Client name
> 92db9b8850cfeefc
> > 2014-12-21 21:59:01 osad._setup_config: Shared key
> > a90c0cf93f7764d48290e1cf55c804398dc5ad4d
> > 2014-12-21 21:59:01 jabber_lib.setup_connection: Connecting
> to
> > dmzspacewalkproxy01.anon.com
> > 2014-12-21 21:59:01 jabber_lib._get_jabber_client:
> > 2014-12-21 21:59:01 jabber_lib._get_jabber_client:
> Connecting to
> > dmzspacewalkproxy01.anon.com
> > 2014-12-21 21:59:01 jabber_lib.__init__:
> > 2014-12-21 21:59:01 jabber_lib.__init__:
> > 2014-12-21 21:59:01 jabber_lib.check_cert: Loading cert
> <X509Name object
> > '/C=DK/ST=Nordjylland/L=Hjoerring/O=Anon
> > A/S/OU=spacewalk01.anon.com/CN=spacewalk01.anon.com'>
> > 2014-12-21 21:59:01 jabber_lib.connect:
> > 2014-12-21 21:59:01 jabber_lib.process: 300
> > 2014-12-21 21:59:01 jabber_lib.process: None
> > 2014-12-21 21:59:01 jabber_lib.connect: Preparing for TLS
> handshake
> > 2014-12-21 21:59:01 jabber_lib.process: None
> > 2014-12-21 21:59:01 jabber_lib.process: None
> > 2014-12-21 21:59:01 jabber_lib.setup_connection: Connected
> to jabber
> > server dmzspacewalkproxy01.anon.com
> > 2014-12-21 21:59:01 osad_client.start: osad-1b78d856e7
> > 081485a6b8b4323c0e05 osad
> > 2014-12-21 21:59:01 jabber_lib.auth: osad-1b78d856e7
> > 081485a6b8b4323c0e05 osad 1
> > 2014-12-21 21:59:01 jabber_lib.auth: Sending auth request
> <iq type='get'
> > id='auth-get-a07d88-0'><query xmlns = 'jabber:iq:auth'
> > ><username>osad-1b78d856e7</username></query></iq>
> > 2014-12-21 21:59:01 jabber_lib.process: 59.9999890327
> > 2014-12-21 21:59:01 jabber_lib.dispatch: Unhandled stanza
> <iq
> > type='result' id='auth-get-a07d88-0'><query xmlns =
> 'jabber:iq:auth'
> >
> ><username>osad-1b78d856e7</username><resource /><password /><digest /></query></iq>
> > 2014-12-21 21:59:01 jabber_lib.auth: Auth response <iq
> type='result'
> > id='auth-get-a07d88-0'><query xmlns = 'jabber:iq:auth'
> >
> ><username>osad-1b78d856e7</username><resource /><password /><digest /></query></iq>
> > 2014-12-21 21:59:01 jabber_lib.auth: Sending auth info <iq
> type='set'
> > id='auth-set-a07d88-1'><query xmlns = 'jabber:iq:auth'
> >
> ><username>osad-1b78d856e7</username><resource>osad</resource><digest>ad651bc95e76268883a8ce4fce22ab1584e4769a</digest></query></iq>
> > 2014-12-21 21:59:01 jabber_lib.process: 299.999992132
> > 2014-12-21 21:59:01 jabber_lib.dispatch: Unhandled stanza
> <iq
> > type='result' id='auth-set-a07d88-1' />
> > 2014-12-21 21:59:01 jabber_lib.auth: Authenticated
> > 2014-12-21 21:59:01 jabber_lib.register_callback: <bound
> method
> > Client._roster_callback of <osad.osad_client.Client instance
> at
> > 0x2132998>> iq None None None None
> > 2014-12-21 21:59:01 jabber_lib.process: None
> > 2014-12-21 21:59:01 jabber_lib._roster_callback: Updating
> the roster <iq
> > type='result' id='iq-request-a07d88-2'><query xmlns =
> 'jabber:iq:roster'
> > ><item ask='subscribe'
> jid='rhn-dispatcher-sat at spacewalk01.anon.com'
> > subscription='none' /></query></iq>
> > 2014-12-21 21:59:01 jabber_lib.register_callback: <bound
> method
> > Client._presence_callback of <osad.osad_client.Client
> instance at
> > 0x2132998>> presence None None None None
> > 2014-12-21 21:59:01 jabber_lib.register_callback: <bound
> method
> > Client._message_callback of <osad.osad_client.Client
> instance at
> > 0x2132998>> message None None None None
> > 2014-12-21 21:59:01 jabber_lib.subscribe_to_presence:
> Subscribed to {}
> > 2014-12-21 21:59:01 jabber_lib.subscribe_to_presence:
> Subscribed both {}
> > 2014-12-21 21:59:01 jabber_lib.subscribe_to_presence:
> Subscribed none
> > {'rhn-dispatcher-sat at spacewalk01.anon.com': {'ask':
> u'subscribe', 'jid':
> > 'rhn-dispatcher-sat at spacewalk01.anon.com', 'subscription':
> u'none'}}
> > 2014-12-21 21:59:01 jabber_lib.subscribe_to_presence:
> Subscribed from {}
> > 2014-12-21 21:59:01 jabber_lib.subscribe_to_presence:
> Subscribed none +
> > ask=subscribe
> > 2014-12-21 21:59:01 jabber_lib.send_presence: None None
> > 2014-12-21 21:59:01 jabber_lib.process_forever:
> > 2014-12-21 21:59:01 jabber_lib.process: 180
> >
> >
> > Thank you in advance
> >
> > - Christian Ejlertsen
> >
> > _______________________________________________
> > 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
More information about the Spacewalk-list
mailing list