kawstov / missed-call-otp

Automatically exported from code.google.com/p/missed-call-otp
0 stars 0 forks source link

MOTP Service Down #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The response I get is 

<br />
<b>Fatal error</b>:  Call to undefined function mysqli_connect_Exception() in 
<b>/home/rmtechbi/public_html/mOTP_API/Framework/Controller/Handler.Classes.motp
</b> on line <b>24</b><br />

Please please dont break like this! I have started using this service!

Original issue reported on code.google.com by kinshuk1...@gmail.com on 16 Feb 2014 at 10:47

GoogleCodeExporter commented 9 years ago
Hi there,

We are aware of a temporary issue affecting MySQL caused by a software update 
to MySQL v5.6 , we are fixing this issue now and MySQL will be back in 30 
minutes or less.

Please let us know if there is anything further we can do for you.

Best Regards,
On behalf of Team MOtp,
Dial2verify Support

Original comment by rahc...@gmail.com on 16 Feb 2014 at 11:20

GoogleCodeExporter commented 9 years ago
current status: 
Issue has been resolved.

Original comment by rahc...@gmail.com on 16 Feb 2014 at 11:21

GoogleCodeExporter commented 9 years ago
No, It isnt, still I get

mOTP  Response : {
"Status":"Exception",
"Result":"mOTP Exception: Please contact support."
}

Original comment by kinshuk1...@gmail.com on 16 Feb 2014 at 12:38

GoogleCodeExporter commented 9 years ago
Hello,

Apologies,
Yes, the DB sync operation is in progress. It is expected to be over within an 
hour.

We understand it is affecting your applications and we are sincerely sorry for 
this downtime. With this, we also assure you to have a backup DB server ready 
for mOTP API.

Original comment by rahc...@gmail.com on 16 Feb 2014 at 12:46

GoogleCodeExporter commented 9 years ago
Exception Changed to : 

 mOTP Exception: (Got error -1 from storage engine) Please contact support.

Original comment by kinshuk1...@gmail.com on 16 Feb 2014 at 1:25

GoogleCodeExporter commented 9 years ago
Hello,

Yes, This is because innodb databases are syncronizing on our server. It would 
take some time to get over with the process.

Original comment by team.m...@gmail.com on 16 Feb 2014 at 1:29

GoogleCodeExporter commented 9 years ago
Hello,

We are happy to announce the services are restored but at the same time are 
equally sad to see this downtime happened. 

Unfortunately, for a mOTP DB server, we were relying on Single Point Of Failure 
architecture, and a little mistake in the DB upgrade caused the downtime.

We would take this forward as a learning and would make sure to implement 
multiple points of failures to avoid such incidents in future.

Thanks for your cooperation and support.

Team mOTP

Original comment by team.m...@gmail.com on 16 Feb 2014 at 1:59