On 01/21/2011 12:08 AM, James Hogarth wrote:
On 20 January 2011 18:07, Tomas Lestach<tlest...@redhat.com> wrote:
Hey James,
I investigated your problem. You're right, there's such a problem on
Spacewalk 1.2. It was caused by changes regarding postgreSql port.
The problem has been fixed in nightly in November.
I've set up scratch builds in koji for you with the fix for spacewalk 1.2.
Not sure, when koji builds them, because it's pretty busy right now. :-)
But as soon as the builds finish, try to download and test the new packages.
RHEL5:
http://koji.spacewalkproject.org/koji/taskinfo?taskID=58614
F12:
http://koji.spacewalkproject.org/koji/taskinfo?taskID=58616
F13:
http://koji.spacewalkproject.org/koji/taskinfo?taskID=58617
Just make sure, you update all:
* spacewalk-java
* spacewalk-java-config
* spacewalk-java-lib
* spacewalk-java-oracle or spacewalk-java-postgresql depending on what DB
you use
* spacewalk-taskomatic
Let me know, if it works for you.
Regards,
Tomas
Btw. the traceback you've attached is too short - there's no valuable
information in there. Next time, please attach the whole traceback. :-)
Hi Tomas,
Thanks for taking a look. Have a long weekend for a birthday present
from the office so back in on Tuesday ;)
Oh, enjoy!
That was the whole traceback from rhn_web_api.log...
Ah, the java log is available in /var/log/tomcat[56]/catalina.out
didn't have time
to check more than that due to an excess of meetings today.
Once the new rpms are up (earliest Tuesday of course) I'll pop them on
our spacewalk instance and report back.
The rpms are available and they work for me. :-)
Regards,
Tomas
--
Tomas Lestach
RHN Satellite Engineering, Red Hat
Have a good weekend,
James
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
