any updates on how long it will take? Thanks
In the email notices we sent out, we identified the following maintenance window:
8:00 to 13:00 GMT0 (3:00 AM to 8:00 AM EST)
yes I know, I was wondering if you think we might be done earlier (I think we are 2 hours in now?). Thx
I cannot make any predictions now. The team is working on it and we will update everyone in our Slack channel when the migration is done.
ok thanks, please let me know here as well as we do not use slack. Appreciate it.
The migration has been completed. Thank you for your patience.
Regards,
Mark
1 Like
great news, thank you Mark for all the support and input during this migration
@mark-piller @olhadanylova we have an issue post-migration, we cannot access a table anymore and this blocks several functionalities.
Please look into this ASAP, it is the “LapOnline” table, if you query it, it all gets stuck (from the web but also from console, so probably you can verify the issue from console).
I could capture only this which does not seem to be any use, but I can query all other tables, this one not.
App ID: 9088AF67-1648-1726-FF09-A51862BF1A00
From the web app (not the console) I get this on google chrome developer tools (only when trying to access the LapOnline table, which of course I access in the exact same I way I access all other tables, and was working before the migration). The message shows up after a very long time of hanging there (like minutes):
Let me know if you need any additional information
We are investigating the issue.
Regards,
Mark
1 Like
The problem has been resolved. Could you please check and confirm?
Regards,
Mark
thanks Mark, I confirm that it is working.
hi @mark-piller, something else to check.
I had this reported by an user (first time I see it):
I have searched the forum and found this: "app not properly configured" error on Registration, facebook login, forgot password
But even after going to the email settings, and resetting it, when I test I still get the error:
I see users are able to register, so I am not sure why this happened and how frequent it is, but if you could look into it, that would be great, thank you.
App ID: 9088AF67-1648-1726-FF09-A51862BF1A00
We have identified and fixed the problem. It should be working now. Could you please check and confirm?
Regards,
Mark
thank you, can this have impacted others? I am asking because we had many reports of people that could not see their data online after Sunday, they could use our app (as it can be used also offline), but then the initialization of backendless or login of the user somehow would not work as they could not see their data on the web service, which of course works only if the app writes to backendless correctly.
Do you think this could be due to the issue you just resolved? This happened only for some users in a sort of not-systematic way, hence we are struggling to sort it out (having users to login again solved it for most of them).
Thank you for your input / support
(I confirm that if I tap “test” the email now gives me “test passed”)
The issue we just resolved was strictly with sending out email.
For the users who could not see their data, how was the problem resolved? Did they reload the app? Or by some other means?
basically we do not normally have login/logout in the app, but only with a fresh install. This has never been a problem as in our experience once they login the first time, then they are logged in forever (like years), and the data is always pushed correctly.
After sunday however data was not pushed for some users, the ones using this Pro web service noticed (or coaches working with athletes via the web service, as the regular user of the app cannot see the issue since locally it is all working normally).
Hence we added a login button in the app, to see if by logging in they could then get their data synched, and this seems to do the trick.
It seems like if with the migration some users were logged out but then when opening the app the system does not detect it the way it normally would (so the user can proceed using the app without having to login again, which normally would be the case when we detect that the user is online but logged out - rare situation based on what I mentioned above)
I am sorry but I am not really able to provide more useful information as I cannot replicate this on our devices where every phone stayed logged in even after the migration, so this is a best guess based on what has been reported by users.
hi Olha, I still experience this issue (it is a problem as I need to be able to export the data, otherwise I am stuck here without access). Here is the error I see:
1 07:21:54 EXPORT Export started
2 07:21:54 EXPORT Exporting table: BackendlessFile
3 07:21:54 EXPORT Exporting table: PurchaseOrderTest
4 07:21:54 EXPORT Exporting table: DailySummaryNoCoreData
5 07:24:49 EXPORT Exporting table DailySummaryNoCoreData failed Exception:com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Application was streaming results when the connection failed. Consider raising value of ‘net_write_timeout’ on the server.
6
7 sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
8 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
9 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
10 java.lang.reflect.Constructor.newInstance(Constructor.java:423)
11 com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
12 com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:983)
13 com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3457)
14 com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3357)
15 com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3797)
16 com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:871)
17 com.mysql.jdbc.MysqlIO.nextRow(MysqlIO.java:1963)
18 com.mysql.jdbc.RowDataDynamic.nextRecord(RowDataDynamic.java:375)
19 com.mysql.jdbc.RowDataDynamic.next(RowDataDynamic.java:355)
20 com.mysql.jdbc.ResultSetImpl.next(ResultSetImpl.java:6344)
21 org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:191)
22 com.backendless.tasks.impex.DataTableExporter.execute(DataTableExporter.java:96)
23 com.backendless.tasks.impex.ExportTask.export(ExportTask.java:154)
24 com.backendless.tasks.impex.ExportTask.execute(ExportTask.java:108)
25 com.backendless.taskman.Task.run(Task.java:123)
26 java.lang.Thread.run(Thread.java:748)
27 Caused by: java.io.EOFException: Can not read response from server. Expected to read 1,081 bytes, read 211 bytes before connection was unexpectedly lost.
28
29 com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2949)
30 com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3417)
31 com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3357)
32 com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3797)
33 com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:871)
34 com.mysql.jdbc.MysqlIO.nextRow(MysqlIO.java:1963)
35 com.mysql.jdbc.RowDataDynamic.nextRecord(RowDataDynamic.java:375)
36 com.mysql.jdbc.RowDataDynamic.next(RowDataDynamic.java:355)
37 com.mysql.jdbc.ResultSetImpl.next(ResultSetImpl.java:6344)
38 org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:191)
39 com.backendless.tasks.impex.DataTableExporter.execute(DataTableExporter.java:96)
40 com.backendless.tasks.impex.ExportTask.export(ExportTask.java:154)
41 com.backendless.tasks.impex.ExportTask.execute(ExportTask.java:108)
42 com.backendless.taskman.Task.run(Task.java:123)
43 java.lang.Thread.run(Thread.java:748)
44 07:24:49 EXPORT Exporting table: CoachNoCoreData
45 07:24:50 EXPORT Exporting table: CoachRequestNoCoreData
46 07:24:50 EXPORT Exporting table: LapOnline
47 07:25:15 EXPORT Exporting table: ReferralCode
48 07:25:15 EXPORT Exporting table: PPGOnline
49 07:25:16 EXPORT Exporting table: CustomPlan
50 07:25:16 EXPORT Exporting table: DailySummary
51 07:25:19 EXPORT Exporting table: Loggers
52 07:25:19 EXPORT Exporting table: Users
53 07:25:21 EXPORT Exporting table: RROnline
54 07:25:22 EXPORT Exporting table: PlanningDailySummary
55 07:25:23 EXPORT Exporting table: PurchaseOrder
56 07:25:23 EXPORT Exporting table: PlanningOverview
57 07:25:23 EXPORT Exporting table: SubscriptionNoCoreData
58 07:25:23 EXPORT Exporting table: UserUpdateNoCoreData
59 07:25:24 EXPORT Generating export.zip
60 07:27:43 EXPORT Uploading export.zip to File Service
61 07:27:45 EXPORT Export finished
Thank you for your help
Thank you for your patience. We worked quite hard to get this problem resolved. It should be working now. Please check. Also, it would be quite beneficial for the continued smooth operation to keep the file storage of your app as clean as possible (removing older unused large files).
Regards,
Mark
1 Like
thank you Mark, this is really appreciated. I hope you and your team are doing well in these challenging times.