昨日、自分のHPがいきなり表示されなくなったので調べたところ、このScriptで利用しているDBがエラーになっていました。
サーバーの管理会社に確認したところコネクションが正しく切断されず、「sleep」となっているプロセスが多数発生しているのでエラーになっていると言われました。
Scriptを最新のバージョンにしていないので、もしこの問題が解決していたら申し訳ないですが上記の問題があったことだけ報告します。
かなり致命的なバグだと思うので改善お願いします。
評価
50
翻訳 / 英語
- 2014/06/10 13:21:02に投稿されました
As I have encountered a problem with my HP not shoing properly, I conducted an investigation. The problem is the DB error which is used for this Script.
According to the server administration company, it was due to the connection not being ended correctly, which resulted numerous processes in "speep" status.
As the latest version has not been installed yet, please accept my apologies in case this issue is already resolved. But I am reporting the aforementioned issue anyway.
This is a critical bug, so please resolve the issue.
kikkaaさんはこの翻訳を気に入りました
According to the server administration company, it was due to the connection not being ended correctly, which resulted numerous processes in "speep" status.
As the latest version has not been installed yet, please accept my apologies in case this issue is already resolved. But I am reporting the aforementioned issue anyway.
This is a critical bug, so please resolve the issue.
評価
50
翻訳 / 英語
- 2014/06/10 13:20:21に投稿されました
Since my HP suddenly stopped being displayed yesterday, I examined and found that DB you are using in this script became an error.
I called the management company of the server and was told that it has been error because the connection was not cut out correctly and there are so many processes that have been "sleep".
I haven't updated the Script to the latest version, so I'm sorry if you have already resolved this problem, but I'm going to report the above issue anyway.
I think it's a fairly critical bug, so please improve.
kikkaaさんはこの翻訳を気に入りました
I called the management company of the server and was told that it has been error because the connection was not cut out correctly and there are so many processes that have been "sleep".
I haven't updated the Script to the latest version, so I'm sorry if you have already resolved this problem, but I'm going to report the above issue anyway.
I think it's a fairly critical bug, so please improve.
★★★☆☆ 3.0/1
評価
52
翻訳 / 英語
- 2014/06/10 13:22:25に投稿されました
As It began suddenly that my homepage can not be displayed yesterday, I have checked and found out DB error that is used in Script.
I immediately checked the server provider and they told me that they found several cases of process error in which the connection had not disconnected and turned int sleep.
This problem might have been already fixed as it might be the reason that Script is not at the latest version, but just in case I am reporting this to you.
I assume this is a critical bug, and hope it will be solved as soon as possible.
kikkaaさんはこの翻訳を気に入りました
I immediately checked the server provider and they told me that they found several cases of process error in which the connection had not disconnected and turned int sleep.
This problem might have been already fixed as it might be the reason that Script is not at the latest version, but just in case I am reporting this to you.
I assume this is a critical bug, and hope it will be solved as soon as possible.
評価
57
翻訳 / 英語
- 2014/06/10 13:48:32に投稿されました
I checked and found the DB error used in this script out since my home page wasn't displayed all of the sudden yesterday.
As I checked with the web hosting server, they said the error had occured because the connection wasn't shut off properly and there were so many process on "sleep" mode. I'd just like to report you that we had this problem occured, even though it might be already solved since we didn't update the script to newest version yet. Please take care of this problem since I think that's pretty fatal bug.
As I checked with the web hosting server, they said the error had occured because the connection wasn't shut off properly and there were so many process on "sleep" mode. I'd just like to report you that we had this problem occured, even though it might be already solved since we didn't update the script to newest version yet. Please take care of this problem since I think that's pretty fatal bug.
評価
52
翻訳 / 英語
- 2014/06/10 13:32:31に投稿されました
I examined yesterday,because of my HP longer appears suddenly, DB that I'm using in this Script had an error.
It was said to have been in error for a process because connection is not cut correctly, the process that has become a "sleep" have been occurred in process after a review of the management company of the server, " Because of the large number generation.
If this problem has been resolved, I'm sorry.
Because I do not have an up-to-date version of Script, it reports only that there is a problem of the above
Improve ask because I think it's a critical bug fairly, thank you.
kikkaaさんはこの翻訳を気に入りました
It was said to have been in error for a process because connection is not cut correctly, the process that has become a "sleep" have been occurred in process after a review of the management company of the server, " Because of the large number generation.
If this problem has been resolved, I'm sorry.
Because I do not have an up-to-date version of Script, it reports only that there is a problem of the above
Improve ask because I think it's a critical bug fairly, thank you.
評価
60
ネイティブ
翻訳 / 英語
- 2014/06/10 13:20:48に投稿されました
Yesterday, my own hompage was not displaying and when I checked it the database using this script was causing an error.
When I checked with my server company, the connection was not shutting off, there were multiple [sleep] instances and they said that lead to the error.
I have not upgraded to the latest version of the script, I'm sorry if this problem has already been solved, but I thought I would report the above problem just in case.
It is quite a serious bug I think, please can you organize a fix for it.
kikkaaさんはこの翻訳を気に入りました
When I checked with my server company, the connection was not shutting off, there were multiple [sleep] instances and they said that lead to the error.
I have not upgraded to the latest version of the script, I'm sorry if this problem has already been solved, but I thought I would report the above problem just in case.
It is quite a serious bug I think, please can you organize a fix for it.
