[Spacewalk-list] osa-dispatcher Error Caught

[Konstantin Raskoshnyi]

I guess the main problem was caused by machines with login: osad-85cdcd1a3e
<osad-85cdcd1a3e at ncias-p1466-v.nci.nih.gov>

I recommend to move from berkley to pgsql db

On Thu, Mar 30, 2017 at 9:49 AM, Camp, Neil (NIH/NCI) [C] <neil.camp at nih.gov
> wrote:

> I was able to connect to the database and select one row. I deleted the
> row in rhnpushdispatcher and stopped jabberd. I removed
> /var/lib/jabberd/db/* and started jabberd. I waited for jabberd to start up
> and then started osa-dispatcher. It is staying up and I checked a host and
> it is showing as online for OSA status. Thank you for your help!
>
>
>
> *From: *<spacewalk-list-bounces at redhat.com> on behalf of Matt Moldvan <
> matt at moldvan.com>
> *Reply-To: *"spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
> *Date: *Thursday, March 30, 2017 at 11:37 AM
> *To: *"spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
> *Subject: *Re: [Spacewalk-list] osa-dispatcher Error Caught
>
>
>
> This message was identified as a phishing
> <http://aka.ms/LearnAboutPhishing> scam.
>
> Feedback <http://aka.ms/SafetyTipsFeedback>
>
> Looks like osa-dispatcher is having trouble connecting to your database...
> have you tried running "spacewalk-sql -i" from your master (or the same
> system you're seeing that error from) to get a n idea of the connectivity
> from that system to your database?
>
>
>
> Once you have that tested take a look at the rhnpushdispatcher table in
> the database.  You can remove any entry there, osa-dispatcher will recreate
> it when you restart...
>
>
>
> On Thu, Mar 30, 2017 at 10:47 AM Camp, Neil (NIH/NCI) [C] <
> neil.camp at nih.gov> wrote:
>
> Hello,
>
>
>
> Osa-dispatcher starts, but dies after a few seconds. I have been digging
> through the archives and searching but have not found a solution.
>
>
>
> 2017/03/30 10:35:25 -04:00 10622 0.0.0.0: osad/jabber_lib.subscribe_to_presence('Subscribed
> from', {})
>
> 2017/03/30 10:35:25 -04:00 10622 0.0.0.0: osad/jabber_lib.subscribe_to_
> presence('osad-85cdcd1a3e at ncias-p1466-v.nci.nih.gov',)
>
> 2017/03/30 10:35:25 -04:00 10622 0.0.0.0: rhnSQL/driver_postgresql._execute_wrapper('Executing
> SQL: "select * from rhnPushClient where jabber_id = %(p1)s" with bind
> params: {p1: osad-85cdcd1a3e at hostname/osad}',)
>
> 2017/03/30 10:35:26 -04:00 10622 0.0.0.0: osad/jabber_lib.main('ERROR',
> 'Error caught:')
>
>
>
> I have turned debugging up to 5 for osa-dispatcher and have the last 4
> lines posted above. Jabberd appears to be running correctly. I see
> connections coming in from clients. It does have one error (SASL callback
> for non-existing host: spacewalk.fqdn). Does anyone have a suggestion as to
> what could be causing the error for osa-dispatcher?
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20170330/8efb3b76/attachment.htm>