Bug 1400960

Summary:	Cannot log in to softwarecollections.org
Product:	[Community] softwarecollections.org	Reporter:	Honza Horak <hhorak>
Component:	Other	Assignee:	Jakub Dorňák <jakub.dornak>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	hhorak, jakub.dornak, msuchy, pkovar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-03 17:16:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Honza Horak 2016-12-02 12:26:22 UTC

When trying to log in to the web admin, I see:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at jdornak to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Comment 1 Honza Horak 2016-12-14 09:58:53 UTC

ping

Comment 2 Jakub Dorňák 2016-12-14 11:33:06 UTC

Memcache was not running there (also softwarecollections-rsyncd).
I have created softwarecollections-services-setup script to ensure that all services are enabled and running.
It is built in Copr (https://copr.fedorainfracloud.org/coprs/jdornak/SoftwareCollections/build/489005/) and installed on softwarecollections.org.

The last step is to pull the changes into sclorg/softwarecollections repository.
(https://github.com/sclorg/softwarecollections/pull/95)

Comment 3 Jakub Dorňák 2016-12-14 11:45:11 UTC

By the way, is there a way to watch product softwarecollections.org in bugzilla? I hadn't known about this issue until Honza created the issue in GitHub.

Comment 4 Petr Kovar 2016-12-14 18:25:39 UTC

I think you can start watching the default assignee for this component, whoever that is.

Comment 5 Honza Horak 2016-12-19 18:47:49 UTC

Hey Kubo, thank you very much for fixing this!!