Description of problem: Do not restart app C:\Ruby200\bin>rhc app-start -a sfssoft -d DL is deprecated, please use Fiddle DEBUG: Authenticating with RHC::Auth::Token DEBUG: Connecting to https://openshift.redhat.com/broker/rest/api DEBUG: Getting all domains DEBUG: Request GET https://openshift.redhat.com/broker/rest/api DEBUG: code 200 9019 ms DEBUG: Request GET https://openshift.redhat.com/broker/rest/api DEBUG: code 200 4913 ms DEBUG: Request GET https://openshift.redhat.com/broker/rest/domains DEBUG: code 200 4798 ms DEBUG: Getting all domains DEBUG: Request GET https://openshift.redhat.com/broker/rest/domains/sfsuser/appl ications/sfssoft DEBUG: code 200 1416 ms DEBUG: Starting application sfssoft DEBUG: Request POST https://openshift.redhat.com/broker/rest/domains/sfsuser/app lications/sfssoft/events DEBUG: code 500 2853 ms Unable to complete the requested operation due to: Failed to correctly execute all parallel operations. Reference ID: 5a34595aaab2b4ad402044d0cb92d306
http://posts-sfsuser.rhcloud.com/
http://posts-sfsuser.rhcloud.com/ C:\Ruby200\bin>rhc app-force-stop -a posts DL is deprecated, please use Fiddle RESULT: posts force stopped C:\Ruby200\bin>rhc app-start -a posts -d DL is deprecated, please use Fiddle DEBUG: Authenticating with RHC::Auth::Token DEBUG: Connecting to https://openshift.redhat.com/broker/rest/api DEBUG: Getting all domains DEBUG: Request GET https://openshift.redhat.com/broker/rest/api DEBUG: code 200 7747 ms DEBUG: Request GET https://openshift.redhat.com/broker/rest/api DEBUG: code 200 3699 ms DEBUG: Request GET https://openshift.redhat.com/broker/rest/domains DEBUG: code 200 3609 ms DEBUG: Getting all domains DEBUG: Request GET https://openshift.redhat.com/broker/rest/domains/sfsuser/appl ications/posts DEBUG: code 200 1781 ms DEBUG: Starting application posts DEBUG: Request POST https://openshift.redhat.com/broker/rest/domains/sfsuser/app lications/posts/events DEBUG: code 500 3488 ms Unable to complete the requested operation due to: Failed to correctly execute all parallel operations. Reference ID: bf467fdcb224800283d4b24816acc417
DEBUG: server results: Failed to execute: 'control restart' for /var/lib/openshift/51efb9485004460cf9000b68/php DEBUG: server results: Restarting PHP cartridge DEBUG: server results: httpd not running, trying to start DEBUG: server results: DEBUG: server results: Syntax error on line 7 of /var/lib/openshift/51efb9485004460cf9000b68/php/configuration/etc/conf.d/openshift.conf: DEBUG: server results: Invalid command 'CustomLog', perhaps misspelled or defined by a module not included in the server configuration DEBUG: server results: Failed to execute: 'control restart' for /var/lib/openshift/51efb9485004460cf9000b68/phpmyadmin DEBUG: server results: Restarting PHPMyAdmin cartridge DEBUG: server results: httpd not running, trying to start DEBUG: server results: DEBUG: server results: Syntax error on line 1 of /var/lib/openshift/51efb9485004460cf9000b68/phpmyadmin/conf.d/disabled_pages.conf: DEBUG: server results: Invalid command 'Alias', perhaps misspelled or defined by a module not included in the server configuration
Refer comment above. That is the response received from mcollective for each of the start/restart attempts.
Discussed with Mrunal and he believe this might be related to bug 969098
> Invalid command 'CustomLog', > Invalid command 'Alias', Interesting, seems like the Apache couldn't load some of it's modules: > LoadModule log_config_module modules/mod_log_config.so > LoadModule authn_alias_module modules/mod_authn_alias.so > etc. This must be caused by corruption of either of the following Apache config files: > $OPENSHIFT_PHP_DIR/configuration/etc/conf/httpd_nolog.conf > $OPENSHIFT_PHPMYADMIN_DIR/conf/httpd_nolog.conf
I confirm that this could have been actually caused by bug 969098. However, the Sprint 33 migration should fix this issue by copying the new config files on setup.
I checked the provided URL from comment 1 and the app is running correctly. Thus I assume the bug was fixed during the last upgrade, as described in comment 7. @Samael, feel free to reopen this bz if the issue still exists. Thanks. *** This bug has been marked as a duplicate of bug 969098 ***