From fedecentrico at gmail.com Thu Nov 9 04:17:01 2017 From: fedecentrico at gmail.com (Federico Cerminara) Date: Thu, 9 Nov 2017 10:17:01 +0100 Subject: [Aerogear-users] A question about unifiedpush crashed tables Message-ID: 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 From dpassos at redhat.com Tue Nov 21 07:31:53 2017 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 21 Nov 2017 10:31:53 -0200 Subject: [Aerogear-users] [aerogear-dev] AeroGear Android Offline In-Reply-To: References: Message-ID: I have added a note on this and archived[1] the repo [1] https://github.com/blog/2460-archiving-repositories On Tue, Oct 31, 2017 at 7:14 AM, Matthias Wessendorf wrote: > adding a notice is fine, IMO - deleting not needed ... > > On Mon, Oct 30, 2017 at 1:00 PM, Daniel Passos wrote: > >> A long time ago we try to draft an offline library, we have created an >> aerogear-android-offline GH repo, but we did not work too much on it there >> and never released it. >> >> Should we delete this repo or only add a notice on the README >> >> -- >> -- Passos >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20171121/10438a5a/attachment-0001.html From xfdeng at hotmail.com Mon Nov 27 10:37:20 2017 From: xfdeng at hotmail.com (jeff01) Date: Mon, 27 Nov 2017 08:37:20 -0700 (MST) Subject: [Aerogear-users] Push Problem on 1.1.1.Final Push In-Reply-To: <144EA958C5BCB144849B6DF3DD05867C2730CA8C@EXMB1EU21.za.if.atcsg.net> References: <144EA958C5BCB144849B6DF3DD05867C2730CA8C@EXMB1EU21.za.if.atcsg.net> Message-ID: <1511797040306-0.post@n5.nabble.com> Usually error 8 indicates that you are using a development device token on the production APN service, or vise versa. See if you mixed APNS DEV and PRO certs. Install PRO/distribution cert for example, tick Production in Aerogear admin console when you install it, did you accuidentally tick Development? https://stackoverflow.com/questions/29406840/apns-notification-fails-to-be-delivered-error-code-8 -- Sent from: http://aerogear-users.1116366.n5.nabble.com/