--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/32bdc815-65c0-4dc0-bf6e-89385304f778%40googlegroups.com.
Hi Dirk
Windows Version: WIN 10mac version for phoneSubsurface Version: 4.9.4 (PC)277 dive on pc 255 on web and phone
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/DC601FE2-C69F-4C9B-8611-E5749FE82DDA%40hohndel.org.
--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/DC601FE2-C69F-4C9B-8611-E5749FE82DDA%40hohndel.org.
--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/DC601FE2-C69F-4C9B-8611-E5749FE82DDA%40hohndel.org.
On 6 Jun 2020, at 20:03, Dirk Hohndel <di...@hohndel.org> wrote:
Yeah, so let's talk about what really happened and how these things are related.
Two weeks ago someone decided to attack the cloud server. Not to hack into it, but to disrupt the service and to create pain for me.Since that person is a complete moron, it was very easy to identify who it was. But since the infrastructure wasn't designed to be resilient against such attacks, they were spectacularly successful in causing me pain.The VM that was running the main cloud storage instance crashed because the attacker managed to fill all disk space (and create a noticeable uptick in my AWS bill for last month).The hot standby that took over had three distinct mistakes in its configuration. Since all this happened over a holiday weekend it took me longer than it should have to address those (especially, embarrassingly, for the most impactful one, a permission error that only affected newly created accounts). Because of that, about 25 accounts were incorrectly initialized which caused a number of very odd error cases for those users. You were one of those. And since the last eleven days I have spent time trying to help the black community and engaging in a number of events and activities, my response to some of those emails was slower than usual. I mean, obviously, a free service like this damn well better have a 24x7 SLA with sub 12h response time OR ELSE...Oh, yeah, plus massive stress induced migraines and headaches because, yay, why not.Subsurface-mobile is designed to not confuse the user with too many error messages and to recover when it couldn't reach the cloud server. In this unforeseen scenario, that ended up making things worse because it lead people to believe that they had successfully synced when in fact they had not.For those people who reached out to me and actually worked with me and did the things I asked them to do, to the best of my knowledge no one lost data.In the same two weeks more than 4000 distinct accounts have accessed cloud data (impressive how many of you are back diving, I guess), all but those about 25 accounts without issues (except for the downtime that all of this caused).I have now spent about 50 hours on cleaning up this mess, responding to angry users, having people yell at me, having people tell me that I am incompetent, rude and <censored>. Explaining my own infrastructure to me (without being limited in their explanations by actually understanding how any of this does, in fact, work). Etc.Phases like this remind me why I love doing open source and why I love providing a free service to the users. It's the people. It's so rewarding to see their responses.Anyway, tl;dr: you can absolutely download dives on your mobile device and sync them with the cloud. I have added a couple of failsafes and a couple of hacks to make it easier to recover from the next asshole who wants to show me how they much they appreciate all the work this community spends on Subsurface.In the meantime, if anyone out there still has problem with their cloud storage, please just reach out directly in email. Happy to help.Enjoy your weekend
/D
On Jun 6, 2020, at 10:47 AM, Max Schlager wrote:
Hi Dirk, maybe it is helpful for you to get feedback.First of all, everything is working again. Thank you for your support and time you spent, helping me.The cloud account only worked after I changed the password for my subsurface application on my computer. Web access via https://cloud.subsurface-divelog.org/ did allow login, but did not show any synced dives. Sync of the local stored dives on my computer was not possible and failed with a local cache error. Thus I created a new account with a different email address. This worked fine instantly, for all endpoints (computer, Android app and web access (browser)).As I'm always curious, I took a closer look at the error with the "old" account credentials. The error message in the bottom of Subsurface stated that the folder (respectively the data) with the local dives, were moved to "a53f07d2724a11b6.1". Anyway, after closing the app there was no such folder. I took a look at the existing folders and compared them. Both seemed to be equal. I renamed the possible faulty folder to "folder_old" and tried to login to the cloud service again.. voila... The folder was created again and sync to cloud, Android app and web access did work again... now I have two working accounts..I don't know what actually happened, I can say, that the issue started after I successfully did a sync between my DC (Suunto Cobra 1) and my Android mobile Samsung S20+ with the most current Subsurface Android app via OTG. The new dives did show up on my mobile phone and after that I did a manual sync to the cloud. From that point of time cloud access via web browser, and sync computer to cloud did not work anymore.To avoid this in future I will use my mobile to view dives only... ;)
--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/468090CB-8EE7-46A2-ABB3-55BCEFFC8663%40hohndel.org.