Hi Daryl,
please, just to be sure. Tell, in which logfile you find the error and past the error you get. You say, that you have the problem with osa-dispatcher? This is on the server.
So what do you get, when you restart the spacewalk services "spacewalk-service restart"? Does the osa-di
Dang, This is the second time today that this has happened to me. I'm right
in the middle of writing the reply, I hit a key combination that "sends" the
message before I'm ready.
Anyway. I was explaining how I registered servers to SuSE in order to access
the repositories.
I hope that my
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 s
Jineesh,
In order to get SLES repositories setup in Spacewalk, you need to first
register one server per service pack with SuSE. For example, I have servers
that are on both SLES 11 SP3 and SLES 11 SP4. I built two servers specifically
just to register to SuSE. One was registered to the SLE
Hi Daryl,
It would be helpful, if you could share the details.
Thanks & Regards,
Jineesh K
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Daryl Rose
Sent: Tuesday, August 02, 2016 7:36 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-li
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 causin
No, the host name has not changed.
Daryl
From: spacewalk-list-boun...@redhat.com on
behalf of Konstantin Raskoshnyi
Sent: Wednesday, August 3, 2016 1:00 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osad/jabber - Invalid password errors
Did
Did you change the hostname manually? Usually that's the problem.
On Wed, Aug 3, 2016 at 10:37 AM, Daryl Rose 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/sys
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
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/ser
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 :
>
> HmmmWonder how that happened? I
Osad is logging into jabber. The client into the server. Just as rhnsd.
Am 03.08.2016 15:38 schrieb Daryl Rose :
>
> HmmmWonder 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
HmmmWonder 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 o
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
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 experien
Robert,
This error is on the SW server itself. (Sorry that I did not say that in my
original post.) I'm using SW 2.3.
I don't see a osad.auth file in /etc/sysconfig/rhn. I'm assuming that is
because this is the server that I am dealing with.
Also, OSAD is being ran as root.
Thank you.
16 matches
Mail list logo
