Database no longer available? #3
Comments
|
I haven't touched this for years, so not totally surprised if Heroku
changes created difficulties. Will recheck it shortly, see if there's any
obvious fix.
Have any deadlines for this? Any Bus gonna go soon? Just out of curiosity.
…On Sun, Nov 22, 2020, 12:42 Steven Beeckman ***@***.***> wrote:
After upgrading Heroku to the heroku-20 stack the app was redeployed and
it turns out the DB is no longer available.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAJPT2T22BWAKDWYRL7GCTSREBLHANCNFSM4T6OQXPQ>
.
|
|
No rush needed as I already upgraded to the Heroku stack, just saw the
database timeouts in the logs after redeploy to the new stack.
Op zo 22 nov. 2020 om 13:57 schreef Gergely Imreh <notifications@github.com>
… I haven't touched this for years, so not totally surprised if Heroku
changes created difficulties. Will recheck it shortly, see if there's any
obvious fix.
Have any deadlines for this? Any Bus gonna go soon? Just out of curiosity.
On Sun, Nov 22, 2020, 12:42 Steven Beeckman ***@***.***>
wrote:
> After upgrading Heroku to the heroku-20 stack the app was redeployed and
> it turns out the DB is no longer available.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#3>, or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAAJPT2T22BWAKDWYRL7GCTSREBLHANCNFSM4T6OQXPQ
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADBQAABRRCBEWLGYYK7JN3SREDDFANCNFSM4T6OQXPQ>
.
|
|
I'm not sure who owned the DB this app was writing to and reading from. I have a MySQL server running for my own projects, I can point this Heroku app to my own server. But what about the history of all the bus location logs? |
|
Isn’t it possible to see where it was trying to connect to in the source of these files?
If it was MySQL it was for sure not on Heroku as I remember at one point all the trouble we had to do trying to get WordPress up and running with PostgreSQL since the StartupBus website needed to run on Heroku and MySQL wasn’t supported.
…--
Sent from my pocket calculator. I am a mobile nomad, please excuse brevity and typos.
On 22 Nov 2020, 16:39 +0100, Steven Beeckman ***@***.***>, wrote:
I'm not sure who owned the DB this app was writing to and reading from.
I have a MySQL server running for my own projects, I can point this Heroku app to my own server. But what about the history of all the bus location logs?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
The connection details are stored in environment variables on Heroku. It’s
a MySQL on a Dutch server, hence my guess. ;-)
I’ll post the details later tonight.
Op zo 22 nov. 2020 om 19:52 schreef Hans van Gent <notifications@github.com>
… Isn’t it possible to see where it was trying to connect to in the source
of these files?
If it was MySQL it was for sure not on Heroku as I remember at one point
all the trouble we had to do trying to get WordPress up and running with
PostgreSQL since the StartupBus website needed to run on Heroku and MySQL
wasn’t supported.
--
Sent from my pocket calculator. I am a mobile nomad, please excuse brevity
and typos.
On 22 Nov 2020, 16:39 +0100, Steven Beeckman ***@***.***>,
wrote:
> I'm not sure who owned the DB this app was writing to and reading from.
> I have a MySQL server running for my own projects, I can point this
Heroku app to my own server. But what about the history of all the bus
location logs?
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADBQAA76WRQRMO3ZS4WKRTSRFMVLANCNFSM4T6OQXPQ>
.
|
|
Found the Heroku deployment, just looking at it now. And indeed it's a Dutch server :) |
|
There was one issue, that I seem to have deleted the previous Google Maps API key, so the map didn't work. That is now fixed, and the maps shows.
|
|
I think it's the database server that is gone/not responding, not related to the new Heroku deploy. I've invited both of you to be collaborators on this repo, so can easier manage what's needed, though for this particular issue, I think it's only a database values update in the Heroku env vars. Also opened #5 which updates all the dependencies to a more up-to-date version, so the server should be more solid, but so far only tested it locally. |
|
@imrehg Thanks. I'll modify the database env vars on Heroku once I know more. @jcvangent here are the DB details:
If the server's gone: no problem, I'll have it point to my servers. It would be great if we could recover the data though. |
|
@stevenbeeckman how is it going, made any progress on this or any help that can be given? |
|
@imrehg apparently the DB has been lost. Mike’s looking if he has any
back-ups. I should make a new database on my own server and configure the
Heroku env var’s appropriately.
Thus I think this issue may be closed.
Op wo 2 dec. 2020 om 15:43 schreef Gergely Imreh <notifications@github.com>
… @stevenbeeckman <https://github.com/stevenbeeckman> how is it going, made
any progress on this or any help that can be given?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADBQAAQP6VG5WKKF6LZPT3SSZHBPANCNFSM4T6OQXPQ>
.
|
After upgrading Heroku to the heroku-20 stack the app was redeployed and it turns out the DB is no longer available.
The text was updated successfully, but these errors were encountered: