Created attachment 817054 [details]
full log file

Description of problem:

Create rubyonrails and redmine application with ruby-1.9 and mysql-5.1 cartridges on old env, after migration, the rubyonrails and redmine application return 503 error, found the following result for rubyonrails applications:

"upgrade_script_ruby": {
                "status": "incomplete",
                "errors": [
                   
                ],

"start_gear": {
                "status": "complete",
                "errors": [
                   
                ],
                "context": {
                    "warning": "Start gear failed with an exception: Failed to execute: 'control start' for /var/lib/openshift/526f55f145ed468e39000036/ruby"
                }
            },
            "validate_gear": {
                "status": "complete",
                "errors": [
                   
                ],
                "context": {
                    "preupgrade_state": "started",
                    "postupgrade_response_code": "503",
                    "postupgrade_status": "Cart status for ruby [PROBLEM]: CLIENT_RESULT: Application is either stopped or inaccessible\n\nCart status for mysql [OK]: CLIENT_RESULT: MySQL is running\n\n"
                }
            }
        },

Version-Release number of selected component (if applicable):
devenv_3960

How reproducible:
always

Steps to Reproduce:
1.Create rubyonrails or redmine application on devenv-stage_528
2.Migrate to devenv_3960
3.Check the rubyonrails and redmine application

Actual results:

The rubyonrails and redmine application both return 503 error, full log please see in attachment.

Expected results:

The rubyonrails and redmine application should work correctly after migration.

Additional info: