重新启动Openshift MySQL墨盒时出错 [英] Error restarting Openshift MySQL cartridge

查看:111
本文介绍了重新启动Openshift MySQL墨盒时出错的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个不可扩展的OpenShift应用程序,该应用程序具有 Tomcat 7 MySQL 5.5 ,并且该应用程序上仅运行了一个小型Java应用程序.该应用程序运行了好几个月,但是从上周开始它停止工作了.当我尝试使用OpenShift仪表板重新启动应用程序时,出现以下错误消息:

I have a non-scalable OpenShift application with Tomcat 7 and MySQL 5.5 and this application has only one small Java application running on it. This application was running fine for a couple of months but since last week it stopped working. When I try to restart the application using the OpenShift dashboard I get the following error message:

Starting MySQL 5.5 cartridge
MySQL server failed to start:
140305 07:01:47 mysqld_safe Logging to '/var/lib/openshift/53104e375973cad496000022/mysql//log/mysql_error.log'.
140305 07:01:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/openshift/53104e375973cad496000022/mysql/data/
140305 07:01:52 mysqld_safe mysqld from pid file /var/lib/openshift/53104e375973cad496000022/mysql/pid/mysql.pid ended
140305 07:01:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/openshift/53104e375973cad496000022/mysql/data/
140305  7:01:49 [Note] Plugin 'FEDERATED' is disabled.
140305  7:01:49 InnoDB: The InnoDB memory heap is disabled
140305  7:01:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140305  7:01:49 InnoDB: Compressed tables use zlib 1.2.3
140305  7:01:49 InnoDB: Using Linux native AIO
140305  7:01:49  InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
140305  7:01:52  InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
140305  7:01:52 InnoDB: Fatal error: cannot initialize AIO sub-system
140305  7:01:52 [ERROR] Plugin 'InnoDB' init function returned error.
140305  7:01:52 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140305  7:01:52 [ERROR] Unknown/unsupported storage engine: InnoDB
140305  7:01:52 [ERROR] Aborting

140305  7:01:52 [Note] /opt/rh/mysql55/root/usr/libexec/mysqld: Shutdown complete

140305 07:01:52 mysqld_safe mysqld from pid file /var/lib/openshift/53104e375973cad496000022/mysql/pid/mysql.pid ended
Failed to execute: 'control restart' for /var/lib/openshift/53104e375973cad496000022/mysql

显然,MySQL盒式服务器无法以某种方式重新启动,但是我没有更改Java应用程序或齿轮配置中的任何内容.

Apparently the MySQL cartridge is failing to restart somehow, but I didn't change anything in my Java application or the gear configuration.

有人知道为什么会这样吗?我不想简单地删除MySQL并再次添加它,因为如果我不确定根本原因,将来可能会再次发生此问题.

Does anybody know why this is happening? I don't want to simply remove MySQL and add it again because this problem may happen again in the future if I don't identify the root cause.

谢谢.

推荐答案

我建议检查您的配额,以查看您是否已达到限额.尝试摆弄齿轮并运行以下quota -s.如果已达到配额,则可以在本地计算机上使用rhc tidy命令清理齿轮.

I would suggest checking your quota to see if you've reached your limit. Try ssh'ing into your gear and running the following quota -s. If you've reached your quota then you can use the rhc tidy command on your local machine to clean up the gear.

经过更多研究后,我会说您受此错误影响 https://bugzilla.redhat.com/show_bug.cgi?id=1061926 .在过去的几天中,我们经历了一些停机时间,并产生了一些残留影响.请放心,我们正在积极努力,以彻底解决这一问题.

After a little more research I would say that you were affected by this bug https://bugzilla.redhat.com/show_bug.cgi?id=1061926. In the last few days we experienced some outage time with some residual effects. Rest assured we are actively working getting this fully resolved.

这篇关于重新启动Openshift MySQL墨盒时出错的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆