[Spacewalk-list] osad/jabber - Invalid password errors

Luzemário Dantas luzemario at gmail.com
Wed Aug 3 19:53:07 UTC 2016


For me, it always says "invalid password" if I start it outside 
spacewalk-services script, but running spacewalk-services start/restart 
gets job done without issues.


Em 03-08-2016 16:06, Daryl Rose escreveu:
>
> I just realized that I've been saying that I am having an issue with 
> osad, when I should be saying that I am having an issue with 
> osa-dispatcher.
>
>
> It just suddenly occurred to me that osad is the process that runs on 
> the client, while osa-dispatcher is running on the server.  This what 
> is causing my "Invalid Password" error.
>
>
> Thank you.
>
>
> Daryl
>
>
>
> ------------------------------------------------------------------------
> *From:* spacewalk-list-bounces at redhat.com 
> <spacewalk-list-bounces at redhat.com> on behalf of Daryl Rose 
> <darylrose at outlook.com>
> *Sent:* Wednesday, August 3, 2016 1:26 PM
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] osad/jabber - Invalid password errors
>
> No, the host name has not changed.
>
>
> Daryl
>
>
>
> ------------------------------------------------------------------------
> *From:* spacewalk-list-bounces at redhat.com 
> <spacewalk-list-bounces at redhat.com> on behalf of Konstantin Raskoshnyi 
> <konrasko at gmail.com>
> *Sent:* Wednesday, August 3, 2016 1:00 PM
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] osad/jabber - Invalid password errors
> Did you change the hostname manually? Usually that's the problem.
>
> On Wed, Aug 3, 2016 at 10:37 AM, Daryl Rose <darylrose at outlook.com 
> <mailto:darylrose at outlook.com>> wrote:
>
>     Thank you for the information.  However, I am confused by a few
>     things.
>
>
>     The error that I am seeing is on the spacewalk server itself, not
>     on the clients.  isn't /etc/sysconfig/rhn/osad-auth.conf only on
>     the clients?    OSAD is failing to start on the server with the
>     invalid password error.  Do I need to remove and recreate the
>     osad-auth.conf file on all of the clients?
>
>
>     Thank you.
>
>
>     Daryl
>
>
>
>
>     ------------------------------------------------------------------------
>     *From:* Dimitri Yioulos <dyioulos at netatlantic.com
>     <mailto:dyioulos at netatlantic.com>>
>     *Sent:* Wednesday, August 3, 2016 10:54 AM
>     *To:* spacewalk-list at redhat.com
>     <mailto:spacewalk-list at redhat.com>; Daryl Rose
>     *Subject:* RE: [Spacewalk-list] osad/jabber - Invalid password errors
>     Robert is correct.  I've had similar issues with osad, and so
>     created a simple Ansible playbook to delete osad-auth.conf against
>     all of my nodes.  If you're running Ansible, here it is:
>
>     ---
>
>     - hosts: all
>       gather_facts: false
>       become: yes
>
>       tasks:
>         - name: stop osad
>           command: /sbin/service osad stop
>         - name: remove osad auth file
>           command: /bin/rm -f /etc/sysconfig/rhn/osad-auth.conf
>         - name: start osad
>           command: /sbin/service osad start
>
>     Dimitri
>
>     -----Original Message-----
>     From: spacewalk-list-bounces at redhat.com
>     <mailto:spacewalk-list-bounces at redhat.com>
>     [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Robert
>     Paschedag
>     Sent: Wednesday, August 03, 2016 11:14 AM
>     To: Daryl Rose <darylrose at outlook.com <mailto:darylrose at outlook.com>>
>     Cc: spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com>
>     Subject: Re: [Spacewalk-list] osad/jabber - Invalid password errors
>
>     You should have configuration files for osad in
>     /etc/sysconfig/rhn. An osad.conf and osad-auth.conf.
>
>     I think, if you remove the osad-auth.conf file and restart osad,
>     it should re-register. I think!
>
>     Regards
>     Robert
>     Am 03.08.2016 15:38 schrieb Daryl Rose <darylrose at outlook.com
>     <mailto:darylrose at outlook.com>>:
>     >
>     > Hmmm....Wonder how that happened?  I didn't press send, at least
>     not that I'm aware of.
>     >
>     >
>     > Anyway, before I was rudely interrupted by my email client, I was
>     > asking if there is a password in the jabberd database or
>     authreg.db file that could be an issue?  Since I am no longer
>     completely clearing out the database files, perhaps something got
>     stuck at some point?  Would clearing out the database files rest
>     the password?
>     >
>     >
>     > But again, I'm wondering what the invalid password is?  What is
>     osad
>     > logging into?
>     >
>     >
>     > Thank you.
>     >
>     >
>     > Daryl
>     >
>     >
>     >
>     >
>     > ________________________________
>     > From: spacewalk-list-bounces at redhat.com
>     <mailto:spacewalk-list-bounces at redhat.com>
>     > <spacewalk-list-bounces at redhat.com
>     <mailto:spacewalk-list-bounces at redhat.com>> on behalf of Daryl Rose
>     > <darylrose at outlook.com <mailto:darylrose at outlook.com>>
>     > Sent: Wednesday, August 3, 2016 8:15 AM
>     > To: spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com>
>     > Subject: Re: [Spacewalk-list] osad/jabber - Invalid password errors
>     >
>     >
>     > I have some additional information that I think that I should share.
>     >
>     >
>     > Because of specific issues experienced with SW, I used
>     to completely remove jabberd database and log files.  I used to
>     stop SW, cd to /var/lib/jabberd/db and remove the entire contents
>     then restart SW.  But, I started experience problems with OSAD not
>     picking up packages, and after so research, I learned that the way
>     that I used to do things was not a good idea.
>     >
>     >
>     > I think that it was a posting here that told me by removing at
>     database files and the authreg.db it was causing the clients from
>     losing connection with the SW server.  In the SW documentation, I
>     learned that its better to delete only the logs that are not
>     required.  These are the steps that I now use:
>     >
>     >
>     > /usr/bin/db_checkpoint -1 -h /var/lib/jabberd/db/ ## mark logs for
>     > deletion /usr/bin/db_archive -d -h /var/lib/jabberd/db/  ## delete
>     > logs /usr/sbin/spacewalk-service restart  ## stop/start spacewalk
>     >
>     > I have this setup in a crontab that runs on a daily schedule.  I
>     set
>     > this up about two months ago.
>     >
>     >
>     > I'm not sure when the invalid password issue started.  But it
>     was some
>     > point after implementing these steps that the invalid password
>     issue
>     > started.  Is there a password
>     >
>     >
>     >
>     >
>     >
>     >
>     > ________________________________
>     > From: Robert Paschedag <robert.paschedag at web.de
>     <mailto:robert.paschedag at web.de>>
>     > Sent: Tuesday, August 2, 2016 11:47 PM
>     > To: Daryl Rose
>     > Cc: spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com>
>     > Subject: Re: [Spacewalk-list] osad/jabber - Invalid password errors
>     >
>     > Hi Daryl,
>     >
>     > the password fire jabber is stored in
>     /etc/sysconfig/rhn/osad.auth, if I remember right.
>     >
>     > The other thing is not enough permissions to delete the PID file.
>     >
>     > Are you running osad as a non-root user?
>     >
>     > Regards
>     > Robert
>     > Am 02.08.2016 16:24 schrieb Daryl Rose <darylrose at outlook.com
>     <mailto:darylrose at outlook.com>>:
>     > >
>     > > OSAD has not been working, and I finally had a moment to look
>     into it.  The osa-dispatcher.log has the following error:
>     > >
>     > >
>     > > 2016/08/02 08:38:25 -05:00 25556 0.0.0.0 <http://0.0.0.0>:
>     > > osad/jabber_lib.setup_connection('Connected to jabber server',
>     > > '<spacewalk-server.domain.com
>     <http://spacewalk-server.domain.com>>')
>     > > 2016/08/02 08:38:25 -05:00 25556 0.0.0.0 <http://0.0.0.0>:
>     > > osad/jabber_lib.register('ERROR', 'Invalid password')
>     > >
>     > > What password would be invalid?  I am using a customized
>     > > certificate, and its still valid for another two years. I can
>     register servers just fine.  I can use rhn_check
>     to retrieve updates, so I'm sure that the certificate is fine.
>     > >
>     > >
>     > > There is another error that I see:
>     > >
>     > >
>     > > 2016/08/01 09:36:22 -05:00 1552 0.0.0.0 <http://0.0.0.0>:
>     > > osad/jabber_lib.main('ERROR', 'Traceback (most recent call
>     last):\n
>     > > File "/usr/share/rhn/osad/jabber_lib.py", line 119, in main\n
>        c =
>     > > self.setup_connection(no_fork=no_fork)\n  File
>     > > "/usr/share/rhn/osad/jabber_lib.py", line 283, in
>     setup_connection\n
>     > > self.push_to_background()\n  File
>     > > "/usr/share/rhn/osad/jabber_lib.py", line 213, in
>     > > push_to_background\n  os.unlink(pid_file)\nOSError: [Errno 13]
>     > > Permission denied: \'/var/run/osa-dispatcher.pid\'\n')
>     > >
>     > > Anyone have any suggestions?
>     > >
>     > > Thank you
>     > >
>     > > Daryl
>     > >
>     > >
>     > >
>
>     _______________________________________________
>     Spacewalk-list mailing list
>     Spacewalk-list at redhat.com <mailto:Spacewalk-list at redhat.com>
>     https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>     _______________________________________________
>     Spacewalk-list mailing list
>     Spacewalk-list at redhat.com <mailto: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/20160803/bcb1cab3/attachment.htm>


More information about the Spacewalk-list mailing list