07-02-2019, 08:20 PM
Still empty cdbUsers table for me...
To ";" or not to ";" that is the question
|
User auth not working
|
07-02-2019, 08:30 PM
(This post was last modified: 07-02-2019, 08:31 PM by WhenInSpace.)
OK, Mark just emailed that outdated caching indexes seem to be the problem. So once they get that sorted everyone should be fine again.
07-02-2019, 09:39 PM
some more info.
I can log in just fine. But, when I want to view another table's data I get this error: (2019-07-02 13:21:05.846): Error: Failed API Key Authentication (2019-07-02 13:21:05.846): Could not read record from cloud. so, the API seems to forget my logon info. 
07-03-2019, 12:29 PM
(This post was last modified: 07-03-2019, 02:09 PM by simon.schvartzman.
Edit Reason: new info
)
Hi LiveCloud team, where are we with the fix, can you please update?
I'm happy my App has not been deployed yet but not sure about moving forward with LiveCloud as my DB cloud server of choice... UPDATE 1: I was able to recreate new user and recreate a user that was already there originally. Is this what is to be expected to happen? I'd really like an explanation from the LiveCloud team as what happened, what kind of actions are being taken in order to avoid this to happen again in the future and any suggestions about what can we (users) do in order to protect our App to face a situation like this. Many thanks in advance UPDATE 2: (2019-07-03 11:00:03.226): Error: Failed API Key Authentication
To ";" or not to ";" that is the question
07-03-2019, 08:08 PM
Hello everyone. Thank you for your patience while we worked through the issue with this update. For a short time, authentication was not working. Next, a handful of developer accounts could not access the cdb_Users table. The table appeared empty. The table was accepting changes and new users. These same developers could not see the changes though. We were affected by this issue as well.
I am happy to say that we have corrected the problem. Here is a post mortem for you. Yesterday, we pushed an update to LiveCloud Manager. A single but necessary behavior file was accidentally not pushed to our auto-update system. The result was that LCM could not authenticate on any region. The forgotten was found and pushed. We thought we had it all going well. But, the San Franciso Region had one more issue. The User instance that manages this region's user data had corrupted data in its config file. It took us a while to realize this corruption was there. The corrupted data has been cleared out. The instance is running and working well. Please restart your LCM to ensure you have the latest update. Try accessing your User table. We appreciate everyone's patience while we worked through this. A more detailed post is coming that details what the update contains.
07-04-2019, 01:30 AM
Hi, many thanks for the update. Still having problems to get it working...
After restarting LCM here is my situation: 1- the pre-crash records were not restored in cdbUsers 2- I was able to create new users 3- When I start my App I get : (2019-07-03 22:14:43.593): Completed apiKey portion of auth 4- When I try to create a new record I get : (2019-07-03 22:19:28.413): Error: Failed API Key Authentication (2019-07-03 22:19:28.414): Could not create record in cloud. Is there something else I have to do besides restoring LCM? p.s.: more than 24 hours out of service for me
To ";" or not to ";" that is the question
07-04-2019, 08:52 PM
(This post was last modified: 07-04-2019, 08:54 PM by clarencemartin.)
I have the LCM seemingly working just fine.
I am having to review my code to look for coding problems that seem to be problematic. I am sure that any problems that I am finding are in my code. My problems seem to be associated with the Login code that I copied into my application. I am spending the day analyzing my code for these problems. Thank you to the LiveCloud team for your work in correcting the problem. As a note: My previous version of my application still seemed to work, even without my recoding things. other users need to be aware that some changes may need to be made if there are conflicts with an imported Login code. I was experiencing a situation that looked like authentication conflicts where the system seemed to think that there was some kind of authentication duplication.
07-04-2019, 10:38 PM
(07-04-2019, 01:30 AM)simon.schvartzman Wrote: Hi, many thanks for the update. Still having problems to get it working... The main thing to do is to make sure you have all the updates to LCM. You get this by restarting the app while connected to the internet. It will auto download your updates and install them. There is a log file in the folder structure that will allow you to see your update process. In the log, you will find details about updates that are needed and the status of the updates. The Mac path is: /Applications/LiveCloudManager.app/Contents/Resources/_MacOS/spicekit/log.txt The Windows path will not have the first few folders that are in the Mac path. Let us know what you find out in there.
07-04-2019, 10:49 PM
I have another question:
I noticed a HardwareID in the keys of the cdbUsers table. What is this the Key used for? I assume it is generated when a new user is created and Identifies the machine the user was created on.
07-05-2019, 12:45 AM
(07-04-2019, 10:38 PM)mark_talluto Wrote:(07-04-2019, 01:30 AM)simon.schvartzman Wrote: Hi, many thanks for the update. Still having problems to get it working... Hi Mark, thanks for your reply, please find below the log for today 2019-07-04 09:38:38.012: ########## STARTER RUNNING... 2019-07-04 09:38:38.014: Showing splash... 2019-07-04 09:38:38.324: Splash shown. 2019-07-04 09:38:38.325: Build number: 508.3 2019-07-04 09:38:38.325: Build date: Mon, 20 Feb 2017 16:49:10 -0800 2019-07-04 09:38:38.326: Build engine: 9.0.5-rc-1 2019-07-04 09:38:38.326: Current OS: MacOS 10.14.5 2019-07-04 09:38:38.341: Engine Location: /Applications/LiveCloudManager.app/Contents/MacOS/LiveCloudManager 2019-07-04 09:38:38.345: >>> Resetting the proxy to none by default 2019-07-04 09:38:38.345: Running sk_CheckInternetStatus... 2019-07-04 09:38:39.181: First internet check PASSED after: 834ms 2019-07-04 09:38:39.183: Second internet check PASSED after: 836ms 2019-07-04 09:38:39.597: Third internet check SKIPPED with: out of range 2019-07-04 09:38:39.597: INTERNET STATUS: true 2019-07-04 09:38:39.599: Fetching the SERVER INDEX FILE... 2019-07-04 09:38:39.733: The download of the SERVER INDEX FILE was SUCCESSFUL. 2019-07-04 09:38:39.734: Processing the ON-DISK INDEX FILE. 2019-07-04 09:38:39.749: Local index was NOT MODIFIED. 2019-07-04 09:38:39.751: Update status for this execution: TRUE 2019-07-04 09:38:39.752: Starter complete, switching to PREUPDATER... 2019-07-04 09:38:39.793: ########## PRE UPDATER RUNNING... 2019-07-04 09:38:39.810: Build number: 310.24 2019-07-04 09:38:39.823: Build date: Thu, 25 Feb 2016 09:41:06 -0800 2019-07-04 09:38:39.862: INTERNET STATUS: true 2019-07-04 09:38:39.882: Loading Spicekit LIBRARY... 2019-07-04 09:38:40.067: Registration complete, switching to UPDATER... 2019-07-04 09:38:40.083: ########## UPDATER RUNNING... 2019-07-04 09:38:40.084: Build number: 310.13 2019-07-04 09:38:40.084: Build date: Fri, 12 Feb 2016 16:45:22 -0800 2019-07-04 09:38:40.084: INTERNET STATUS: true 2019-07-04 09:38:40.093: Total updates REQUIRED: 0 2019-07-04 09:38:40.094: Update process COMPLETE. 2019-07-04 09:38:40.228: Submitting system information... 2019-07-04 09:38:40.229: Critical system information is missing or corrupt. 2019-07-04 09:38:40.230: Launching LiveCloudManager... Please let me know what else can I do
To ";" or not to ";" that is the question
|
Users browsing this thread: 5 Guest(s)