Re: [Spacewalk-list] Spacewalk gui irresponsive

2017-07-06 Thread Konstantin Raskoshnyi
Completely from spacewalk On Thu, Jul 6, 2017 at 10:29 PM Robert Paschedag wrote: > Am 7. Juli 2017 00:12:07 MESZ schrieb Konstantin Raskoshnyi < > konra...@gmail.com>: > >I have 7 version of java on board so it should be compatible with > >tomcat6 > > > >Where can I find db.prperties? > > > >O

Re: [Spacewalk-list] Spacewalk gui irresponsive

2017-07-06 Thread Robert Paschedag
Am 7. Juli 2017 00:12:07 MESZ schrieb Konstantin Raskoshnyi : >I have 7 version of java on board so it should be compatible with >tomcat6 > >Where can I find db.prperties? > >On Thu, Jul 6, 2017 at 2:14 PM Vipul Sharma (GDC) > >wrote: > >> Any catalina errors - What about the version of Java, Can

Re: [Spacewalk-list] Spacewalk gui irresponsive

2017-07-06 Thread Konstantin Raskoshnyi
I have 7 version of java on board so it should be compatible with tomcat6 Where can I find db.prperties? On Thu, Jul 6, 2017 at 2:14 PM Vipul Sharma (GDC) wrote: > Any catalina errors - What about the version of Java, Can you check the > compatibility with Tomcat. > > Your connection settings l

Re: [Spacewalk-list] Spacewalk gui irresponsive

2017-07-06 Thread Vipul Sharma (GDC)
Any catalina errors - What about the version of Java, Can you check the compatibility with Tomcat. Your connection settings looks fine for Tomcat, Please verify your db.properties files for postgres. Thanks Vipul DevOps On Fri, Jul 7, 2017 at 1:37 AM, Konstantin Raskoshnyi wrote: > Hi guys, af

[Spacewalk-list] Spacewalk gui irresponsive

2017-07-06 Thread Konstantin Raskoshnyi
Hi guys, after upgrade to 2.6, when I try to remove more than 10 packages spacewalk become irresponsive. Server config 24Gb or ram, 24 cores. I did some tuning of tomcat and pg It used to work fine, no any error in the logs though. Here's my settings: DB: autovacuum on default_statistics_targe

Re: [Spacewalk-list] up2date A protocol error occurred: Internal Server Error

2017-07-06 Thread Daryl Rose
The magic of posting online resolved the error. As soon as posted my last reply, I was able to get it working. I think the final issue was the FQDN in /etc/hostname. I had added the FQDN previously, but I kept rolling back the snapshot while working out other issues. Once I got everything

Re: [Spacewalk-list] up2date A protocol error occurred: Internal Server Error

2017-07-06 Thread Daryl Rose
I disabled selinux previously, so I don't think that is the issue. Where did you see the HttpProtocolOptions Unsafe error? Thank you Daryl From: spacewalk-list-boun...@redhat.com on behalf of Coffman, Anthony J Sent: Thursday, July 6, 2017 11:50 AM To: sp

Re: [Spacewalk-list] up2date A protocol error occurred: Internal Server Error

2017-07-06 Thread Coffman, Anthony J
I ran into something similar with a newly deployed CentOS 7 / Spacewalk Proxy 2.5 today. Selinux was denying access to several things. I guess this may not be fixed in Proxy 2.6? Check the audit.log and see if you may be running into the same thing. Anyway - this may save you some time, right

[Spacewalk-list] up2date A protocol error occurred: Internal Server Error

2017-07-06 Thread Daryl Rose
I recently rebuilt my proxy server to v2.6.I'm able to get clients to register, but I can't patch or install packages via the proxy server. I use a signed certificate and I believe that everything with the certificate is working correctly. However, I get the following errors: Registratio