Bug 784722 - 500 internal server error on deploy
Summary: 500 internal server error on deploy
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OKD
Classification: Red Hat
Component: oc
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Alex Boone
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 22:37 UTC by Nam Duong
Modified: 2015-05-15 01:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-25 22:57:35 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Nam Duong 2012-01-25 22:37:26 UTC
Description of problem:
We currently have this KB article:
https://www.redhat.com/openshift/community/kb/kb-e1026-i-get-a-500-internal-server-error-when-deploying-my-app

Could we offload this debugging step from the user with better error handling?

KB article:
Code: 
KB-E1026
Applies to: 
OpenShift Express
Issue: 

When deploying my application, I get a 500 internal server error in my browser
Resolution: 

The reason for this could be many different things. The best way to find out what might be going on is to run 'rhc-tail-files -a app_name' while you are receiving this error. Running this command in a terminal window and then visiting your application in a browser window should output meaningful information in the terminal.

Also take a look at the result of 'git push' -- make sure there are no errors there too.

If you are unable to resolve the problem yourself, please visit us in the forums or in IRC (#openshift on irc.freenode.net) or email openshift at redhat dot com. Please try and include as much log data as possible.

Comment 1 Nam Duong 2012-01-25 22:57:35 UTC
Misunderstood the use case.  The use case described in the KB is an error the user gets when accessing the application, not from an rhc* command.  Nothing we can do there but to debug the app/git logs


Note You need to log in before you can comment on or make changes to this bug.