I would try to investigate, why your clients are losing the connections.
Since I'm using Spacewalk (started with 2.1), I only had one jabber DB
corruption. We currently have >500 servers. Not really that much, but it's
enough.
One difference is that our spacewalk server is NOT also a client to
itself. So I do not have this situation.
Regards,
Robert
Mit freundlichen Grüßen
Robert Paschedag
Netlution GmbH
Landteilstr. 33
68163 Mannheim
im Auftrag des
SWR
Südwestrundfunk
HA IT, Medientechnik und Programmverbreitung
Neckarstraße 230
70190 Stuttgart
Telefon +49 (0)711 /929-12654 oder
Telefon +49 (0)711 /929-13714
paschedag.netlut...@swr.de
swr.de
Von: Daryl Rose <darylr...@outlook.com>
An: "spacewalk-list@redhat.com" <spacewalk-list@redhat.com>
Datum: 03.08.2016 15:26
Betreff: Re: [Spacewalk-list] osad/jabber - Invalid password errors
Gesendet von: spacewalk-list-boun...@redhat.com
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.pasche...@web.de>
Sent: Tuesday, August 2, 2016 11:47 PM
To: Daryl Rose
Cc: spacewalk-list@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 <darylr...@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:
osad/jabber_lib.setup_connection('Connected to jabber server',
'<spacewalk-server.domain.com>')
> 2016/08/02 08:38:25 -05:00 25556 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: 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@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
