[Spacewalk-list] Unknown Error for OSA-DISPATCHER - No Resolution yet

[Matt Moldvan]

If you've changed the back end multiple times it's possible the password
for your master in the rhnpushdispatcher table of your Spacewalk database
is now incorrect.  Try deleting the entries in the rhnpushdispatcher table
and restarting osa-dispatcher.  That service fails on a somewhat regular
basis in 2.5, unfortunately with very limited debug output and reason (I've
gone as far as adding debug output to the Python code directly, without
much luck), so I've had to script something to check the service status and
hammer it into submission when it does crash.

Here is my script, it may or may not help you also... has some CentOS 6 and
SQLite specific parts but should be easily adaptable.

Hope it helps... I was also in the same boat as you, wrangling with it to
make it work, about a year and a half ago.

#!/bin/bash
PATH=/sbin:/usr/bin:/bin
LOGFILE=/var/log/$(basename $0).out
if [ ! -f "${LOGFILE}" ]; then
        echo "osa-dispatcher and jabberd have been restarted 0 times since
$(date); last restart was on " >> "${LOGFILE}"
fi
service jabberd status && service osa-dispatcher status
if [ $? -ne 0 ]; then
        service osa-dispatcher stop
        service jabberd stop
        echo "delete from rhnpushdispatcher where
jabber_id='rhn-dispatcher-sat@$(uname -n)/superclient';" | spacewalk-sql -i
        sqlite3 /var/lib/jabberd/db/sqlite.db < /usr/local/etc/fixjabber.sql
        service jabberd start
        service osa-dispatcher start
        oldnum=$(cut -d ' ' -f7 ${LOGFILE})
        newnum=$(expr $oldnum + 1)
        sed -i "s/$oldnum times/$newnum times/g;s/last restart was
on.*$/last restart was on $(date +'%F @ %H:%M:%S')/g" ${LOGFILE}
fi

and the content of fixjabber.sql is:
[me at work ~]$ cat /usr/local/etc/fixjabber.sql
delete from authreg where username = 'rhn-dispatcher-sat';
delete from "roster-items" where "collection-owner" = 'rhn-dispatcher-sat@
<replacethis>';
delete from status where "collection-owner" = 'rhn-dispatcher-sat@
<replacethis>';
delete from active where "collection-owner" = 'rhn-dispatcher-sat@
<replacethis>';


On Fri, Jan 12, 2018 at 10:18 AM Wilkinson, Matthew <
MatthewWilkinson at alliantenergy.com> wrote:

> Vipul this looks like a network issue not a DB issue. Or could also be a
> cert issue. Is your /etc/jabberd/server.pem correct?
>
>
>
> --Matthew Wilkinson
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Vipul Sharma (DevOps)
> *Sent:* Friday, January 12, 2018 02:05
> *To:* spacewalk-list at redhat.com
> *Subject:* [Spacewalk-list] Unknown Error for OSA-DISPATCHER - No
> Resolution yet
>
>
>
> [This is an external email. Be cautious with links, attachments and
> responses.]
> ------------------------------
>
> Hi Team,
>
> I have tested spacewalk on different DB's & been stuck on this issue for
> at least a month.
>
> *Same issue with - Postgresql*
>
> *Same issue with - Sqlite*
>
> *Same issue with - Jabberd*
>
>
>
>
>
>
> *Jan 12 07:55:25 spacewalk systemd: Starting OSA Dispatcher daemon... Jan
> 12 07:55:25 spacewalk jabberd/c2s[30837]: [7] [::ffff:10.240.0.21,
> port=38390] connect Jan 12 07:55:25 spacewalk jabberd/c2s[30837]: [7]
> traditional.digest authentication failed:
> rhn-dispatcher-sat at spacewalk/superclient ::ffff:*.*.*.*:38390 TLS Jan 12
> 07:55:25 spacewalk systemd: Started OSA Dispatcher daemon. Jan 12 07:55:25
> spacewalk jabberd/c2s[30837]: [7] traditional authentication failed:
> rhn-dispatcher-sat at spacewalk/superclient ::ffff:*.*.*.*:38390 TLS*
>
>
>
>
>
> If there is a resolution for this - Please suggest me, I have been through
> various forums - Didn't find a solution for this issue -
>
>
>
> I am standing at a point wherein either we have to completely remove
> spacewalk or Find a viable solution-
>
>
>
> Please do suggest if anyone have some ideas/suggestions.
>
>
>
> Thanks
>
> Vipul
>
>
>
>
>
> Please consider the environment before printing this email.
> *********************************************************************
> This communication may contain information which is confidential, personal
> and/or privileged. It is for the exclusive use of the intended recipient(s).
> If you are not the intended recipient(s), please note that any
> distribution, forwarding, copying or use of this communication or the
> information in it is strictly prohibited. If you have received it in error
> please contact the sender immediately by return e-mail. Please then delete
> the e-mail and any copies of it and do not use or disclose its contents to
> any person.
> Any personal views expressed in this e-mail are those of the individual
> sender and the company does not endorse or accept responsibility for them.
> Prior to taking any action based upon this e-mail message, you should seek
> appropriate confirmation of its authenticity.
> This message has been checked for viruses on behalf of the company.
> *********************************************************************
> _______________________________________________
> 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/20180112/f7672b1d/attachment.htm>