RESOLVED
Log messages from jabber during the conflict failure:
Sep 12 03:32:41 spacewalk jabberd/c2s[12995]: [12] [SUBNET1.92, port=36942]
connect
Sep 12 03:32:41 spacewalk jabberd/c2s[12995]: [12] traditional.digest
authentication succeeded: rhn-dispatcher-sat@/superclient SUBNET1.92:36942 TLS
Hello,
anyone can now contribute to spacewalk wiki (
https://github.com/spacewalkproject/spacewalk/wiki) by submitting Pull
requests to https://github.com/spacewalkproject/spacewalk-wiki repository.
More details about this process can be found on
https://github.com/spacewalkproject/spacewalk/wiki
Am 12. September 2017 05:13:36 MESZ schrieb Andrew Bergman
:
>I just removed the jabber RPM, reinstalled with a clean slate, ran
>spacewalk-setup-jabberd
>
>Jabberd runs fine using the SSL cert I provided built with the FQDN,
>but again, osa-dispatcher fails with same error.
>
>Maybe I should rein
Hello,
I'll try to reproduce the issue as it looks like a bug in our code,
especially if someone else could confirm that after upgrade to 2.6 this
can be seen consistently on any machine.
The changes in commit 95345b58a86b134084bcc5a8c07ae452f1574670 are not
causing this as the change is about
Hello,
do you see any errors in /var/log/tomcat*/catalina.out* ?
Tomas
On 09/12/2017 08:26 AM, Olivier FONT wrote:
Hello,
I just installed a new Spacewalk 2.6 server and, when I try to
connect, I face a blank page.
The installation is a PostgreSQL embeded one, according this HowTo:
https://
Olivier FONT:
> Hello,
>
> I just installed a new Spacewalk 2.6 server and, when I try to connect, I
> face a blank page.
> The installation is a PostgreSQL embeded one, according this HowTo:
> https://github.com/spacewalkproject/spacewalk/wiki/HowToInstall
>
> I can't find in wich folder the Doc
