I got this error recently on my OBS appliance exactly 1 year after I installed it! Turned out the self signed certificates in the Cert direct of OBS had expired. I deleted them (and copies in /etc/pki from memory), restarted, and OBS recreated new certs. Once I copied them back to the /etc/pki directory every thing was back to normal. Maybe the OBS devs can increase the validity of the self signed certs to 5(?) years? Sent from my iPhone

On 5 Jun, 2014, at 3:46 pm, "Adrian Schr?ter" wrote:

On Mittwoch, 4. Juni 2014, 13:54:21 wrote Andrew Melo:

...

On Wed, Jun 4, 2014 at 1:14 PM, Smith, Kenneth wrote:

...

Hello,

My OBS webui installation has become inoperable. I was logged in and browsing when I clicked a link on the ui and got "Application error 500". I restarted the obs services, no change. I rebooted the server. No change. I get the same error from another user's machine.

webui production.log shows this:

[INFO |# 2980] Started GET "/" for 192.168.1.60 at 2014-06-04 17:45:11 +0000 [INFO |# 2980] Processing by MainController#index as HTML [INFO |# 2980] Anonymous request to / [INFO |# 2980] Completed 500 Internal Server Error in 6ms

[FATAL|# 2980] OpenSSL::SSL::SSLError (SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read server certificate B: certificate verify failed): lib/activexml/transport.rb:350:in `http_do' lib/activexml/transport.rb:227:in `direct_http' app/controllers/application_controller.rb:361:in `block in require_configuration' app/controllers/application_controller.rb:359:in `require_configuration'

I'm not sure why I'm suddenly getting ssl errors, when I wasn't before. I'm not sure where to start in fixing this.

I'm not sure if it's related, but:

I just moved my OBS instance to one hypervisor to another and instead of moving the whole disk image,I started from a scratch hypervisor image from the OBS website and then rsynced over the /srv tree from the old machine. When I try to log in, I get:

OpenSSL::SSL::SSLError (SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol):

unknown protocol sounds like you do not talk to a SSL connection.

or ruby stack does not accept the certificate and throws wrong error ...

...

/usr/lib64/ruby/2.0.0/net/http.rb:918:in `connect' /usr/lib64/ruby/2.0.0/net/http.rb:918:in `block in connect' /usr/lib64/ruby/2.0.0/timeout.rb:52:in `timeout'

--

Adrian Schroeter email: adrian@suse.de

SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendrffer, HRB 21284 (AG Nrnberg) Maxfeldstrae 5 90409 Nrnberg Germany

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org