Bug 985641

What is the status of the mysql cartridge?

Can you stop and start the cartridge?

Not sure about the status of the mysql cartridge, how do I find out?
I can start and stop the cartridge from command line and the web interface and that preceded by another push fixes the problem momentarily.

To see the cartridge status:

rhc cartridge status mysql -a walrussoup

Are you saying that you can start and stop the cartridge without a problem and that 'git push' works for a while, but after a while the problem returns?

Since it is not possible to control the DB cartridge on the console, I assume you mean starting/stopping the application.

You said "that preceded", which doesn't seem to fit with the rest of what you are saying.

I'm saying I can start/stop the application from the console without a problem. I should have read your post more carefully since you asked me to start/stop the cartridge not the application but someone was talking to me when I was writing the reply hence the slightly odd wording. Apologies.

For now the cartridge status reports the following:
$ rhc cartridge status mysql-5.1 -a walrussoup

RESULT:
MySQL is running

Can you stop the cartridge with this?

rhc cartridge stop mysql-5.1 -a walrussoup


What happens if you restart your application (instead of the cartridge)? You indicated that `git push` would work for a while after that, correct? (Also, how long is "a while"? Could you be more precise?) And `git push` stops working at some point, yes?

When `git push` is failing, can you ssh to the gear, and see if you can connect to the database?

rhc app ssh walrussoup

mysql

Also, what would 'ps -ef' show at that time?

Also, do you have any action hook for this app defined?

$ rhc cartridge stop mysql-5.1 -a walrussoup

Unable to complete the requested operation due to: Failed to correctly execute
all parallel operations - --DEBUG--

--RESULT--

--MESSAGE--

--ERROR--

--APP INFO--

--CART COMMANDS--

--CART PROPERTIES--
{}
--DATA--

--EXIT CODE--

--USER ACTIONABLE--
false
.
Reference ID: d311ec68d9e12c2ba7b40db37855c5d8


Restarting the app instead of the cartridge works fine, git push doesn't work for "a while"( I may have worded that badly, again - apologies). It's more that it gets that one particular push through and where it needs to be, sometimes an indeterminate number of pushes afterwards succeed, sometimes not.

Next time gish push failed I will ssh to the gear and do that - I'm about to start work on my application again so I'll bear this in mind.

I don't have any action hooks defined for the app as far as I'm aware (I didn't define any anyway).

Has this recurred? Were you able to determine what sort of state mysql was in while you can't stop mysql? Does $OPENSHIFT_MYSQL_DIR/pid/mysql.pid exist? If so, does it match with match the mysql PID?

In $OPENSHIFT_MYSQL_DIR/bin/control, the stop() function will be invoked when you run 'rhc cartridge stop mysql-5.1 -a walrussoup'. You can invoke this manually, and get a little more debugging information:

bash -x $OPENSHIFT_MYSQL_DIR/bin/control stop

Hi there

I currently having company staying so I haven't been able to do much development on my app. Hoping to make another push in the near future though and see if it happens again.

The bug is sometimes producible in devenv_3641. Specifically, when I pushed changes to a ruby-1.9 app with a MySQL-5.1 cart added via Git, the errors were:

[zhe@fedora rb9]$ git add . && git commit -amp && git push
[master 2e5ceb6] p
 1 file changed, 1 insertion(+), 1 deletion(-)
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 284 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Stopping Ruby cart
remote: Waiting for stop to finish
remote: An error occurred executing 'gear prereceive' (exit code: 1)
remote: Error message: Failed to execute: 'control stop' for /var/lib/openshift/5209b1384a6aa70997000002/mysql
remote: 
remote: For more details about the problem, try running the command again with the '--trace' option.
To ssh://5209b1384a6aa70997000002.rhcloud.com/~/git/rb9.git/
 ! [remote rejected] master -> master (pre-receive hook declined)

(In reply to Zhe Wang from comment #10)
> The bug is sometimes producible in devenv_3641. Specifically, when I pushed
> changes to a ruby-1.9 app with a MySQL-5.1 cart added via Git, the errors
> were:
> 
> [zhe@fedora rb9]$ git add . && git commit -amp && git push
> [master 2e5ceb6] p
>  1 file changed, 1 insertion(+), 1 deletion(-)
> Counting objects: 5, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (3/3), done.
> Writing objects: 100% (3/3), 284 bytes, done.
> Total 3 (delta 2), reused 0 (delta 0)
> remote: Stopping Ruby cart
> remote: Waiting for stop to finish
> remote: An error occurred executing 'gear prereceive' (exit code: 1)
> remote: Error message: Failed to execute: 'control stop' for
> /var/lib/openshift/5209b1384a6aa70997000002/mysql
> remote: 
> remote: For more details about the problem, try running the command again
> with the '--trace' option.
> To
> ssh://5209b1384a6aa70997000002.rhcloud.com/~/git/rb9.git/
>  ! [remote rejected] master -> master (pre-receive hook declined)

Was this app created with 'app create' without '--from-code' but added 'rails' to Gemfile (and Gemfile.lock) later? If so, this error might be a result of the problem with pre-build function in https://github.com/openshift/origin-server/commit/6400c02.

This was fixed by https://github.com/openshift/origin-server/commit/b46b39c, which will be in devenv_3642.

Hi, Hiro,

The app referred in Comment#10 was a raw one, without building from any code. I simply created a ruby-1.9 app and then added a MySQL cartridge to it. After that, I changed the title of the Welcome page (in config.ru) a bit, and pushed the change via Git.

Hope this info helps.

Thanks,
Zhe Wang

Zhe, I believe the bare application is working now on devenv. If you see a problem, please open a separate ticket, since it's most likely a separate issue.

Let us now wait for further input from Robert.

Hi, Robert,

Is there any progress here?

I'm closing this for now. If there is anything we can do to investigate further, do let us know.

Any chance I could stop getting emails about this since the bug is closed?