soundscape-community
Backend Appears to be Offline
I sent this message through the feedback yesterday, but since it hasn't been resolved yet, I'm opening this as an issue. Soundscape's backend appears to be offline. I checked my app, and the settings are alright. Location Services is on, and it is set to "While Using". Also the app was still up and running last Friday, and I haven't changed any phone settings or downloaded new IOS updates since then. I reset the tile server URL in Troubleshooting, but that didn't fix it either. I used alternative Soundscape apps as a control, and all the alternatives are working fine. Thanks.
Oops so it is. I'm out but I'll try to get it back up if it's an easy fix. Might just restart the server for now and examine the logs later.
looks like a hardware problem. I'm bringing up a temporary It will take several hours to import the OSM data.
Since you said it could be faulty hardware, does that mean that the main server will need to be replaced,?
It's been over half a day since the temp was put up. Does it take at least a day for the OSM data to fill up? My copy of the app is still working offline.
Everything seems to be working again. Once you get the other server fixed, you can close this issue, or you can close it right now, it doesn't matter.
That's the Hetzner server back up. There was some kind of issue causing memory corruption.
The backup server still hasn't completed importing the OSM data; I drastically underestimated how long that would take.
I am continuing to investigate and will report this to Hetzner, although I will hopefully get the backup server going before they look at it so we don't have any more downtime.
Leaving this open until the issue is definitely resolved fully.
On a related note, after the database was reloaded, it looks like the backend is using an earlier version rather than the latest changes from Open Street Map. I deleted and changed a couple of places in my town the Sunday before the temp server was put up, and those changes haven't been reflected.
@JJGatchalian Possibly because of data corruption, but since then it has done a full import so should be reasonably up to date.
You can try clear stored map data in settings -> trouble shooting to force it to download new data.
I did the "Clear Stored Map Data" command yesterday, and I also reset the tile server. I just added a brand new change to OSM before I received your comment right now. Maybe this new change won't show up in the update yet, but that's alright. Anyway, I did another "Clear Stored Map Data" command just before getting on Github right now, but it still shows the places I deleted last Sunday. The best thing to do is just wait and see.
It looks like the data corruption may be within OSM itself. Using the alternative versions of Soundscape after clearing stored map data doesn't reflect my latest changes, even the apps that say they update the database weekly. All we can do is wait for OSM to fix it on their end.
The OSM updates seem to be working fine now. I found the changes I made a couple weeks ago, but I'm still waiting for the change I made this morning. Since it took about two and a half weeks to update, if all goes well, then my latest changes should appear in Soundscape around the second week of November.
It looks like the OSM data for the Soundscape Community backend is outdated again. Since my previous comment on October 23, all the alternative versions of Soundscape already reflect the changes I made, but they still don't show up in the default backend. I switched over to an alternative backend through the "Tile Server URL" setting in "Troubleshooting" just to get the latest database until the default backend gets updated. BTW, is there an exact timeframe when the tile server updates for Soundscape Community?
apologies, after the server hardware issue I deliberately didn't start the osm ingestion service, intending to start it once I knew the server was stable. unfortunately I forgot to start it until just now.
Not sure how long it takes, but it should be updated by later today or tomorrow.
There's a delay of about 2 weeks between updates at the moment. It could definitely be improved, currently the update involves a complete download of the osm data and database import from scratch.
we Could certainly change it to weekly though.
Ok, I'll change the URL back on my own copy in a cupple of days. The weekly suggestion sounds fine because it looks like the alternative backend I'm using already updated it to a weekly schedule. Even though you started the ingestion again, have you gotten word that the server issue has been fixed yet? This backup server seems stable right now, but what about the original?