[Aerogear-users] A question about unifiedpush crashed tables

[Federico Cerminara]

Hi,
we are recognizing internally a strange behaviour with push notifications.
Aerogear server seems to be no more reachable and looking in jboss
(wildfly) logs for some explanations, we founds some ups database table are
crashed and "need" to be repaired.
Have you ever experienced this scenario and eventually could you suggest me
an approach to solve it? Googling about the error messages, someone suggest
to repair tables using a specific command; otherwise i could drop the
crashed tabled and creating them using the sql creation code from another
running installation of unified push database. Crashed tables seem to be
variant_metric_info and push_message_info.

Thanks anyway for your important support and for the time you'll spend
reading this mail.
Federico.

08:51:26,167 WARN  [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB
default - 1) SQL Error: 126, SQLState: HY000



08:51:26,214 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB
default - 1) Incorrect key file for table
'.\unifiedpush\variant_metric_info.MYI'; try to repair it



08:51:26,230 WARN  [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB
default - 1) Table 'variant_metric_info' is marked as crashed and should be
repaired



Caused by: java.sql.SQLException: Incorrect key file for table
'.\unifiedpush\variant_metric_info.MYI'; try to repair it

Here about reparing tables:

https://stackoverflow.com/questions/4357270/table-is-marked-as-crashed-and-should-be-repaired
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20171109/917593b0/attachment.html