an error occurred unable to update nested relation. [object object]/Ghost Server Error

Hi Guys

I think I’m in the right place - It’s been going really smoothly, then from nowhere - an error occurred unable to update nested relation. [object object]

• when trying to edit a page then a ‘Ghost Server Error’ -
  Ghost server error: insert into settings (created_at, created_by, id, key, type, updated_at, updated_by, value`) values (‘2020-09-28 21:45:44’, 1, ‘5f725988e7188c001e25ad0e’, ‘active_apps’, ‘app’, ‘2020-09-28 21:45:44’, 1, ‘[]’) - ER_TABLEACCESS_DENIED_ERROR: INSERT command denied to user ‘f5gan8ytezqkq9go’@‘3.248.219.90’ for table ‘settings’ Error: ER_TABLEACCESS_DENIED_ERROR: INSERT command denied to user ‘f5gan8ytezqkq9go’@‘3.248.219.90’ for table ‘settings’
• when trying to upgrade - which is what was the most common advice for this error - which I retrieved from the heroku logs which finished with the standard -

2020-09-28T21:45:52.322147+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-09-28T21:45:52.322520+00:00 app[web.1]: npm ERR! errno 1
2020-09-28T21:45:52.325100+00:00 app[web.1]: npm ERR! ghost-on-heroku@1.25.5 start: `node server.js`
2020-09-28T21:45:52.325206+00:00 app[web.1]: npm ERR! Exit status 1
2020-09-28T21:45:52.325353+00:00 app[web.1]: npm ERR!
2020-09-28T21:45:52.325440+00:00 app[web.1]: npm ERR! Failed at the ghost-on-heroku@1.25.5 start script.
2020-09-28T21:45:52.325548+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-09-28T21:45:52.332858+00:00 app[web.1]: 
2020-09-28T21:45:52.333066+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-09-28T21:45:52.333214+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2020-09-28T21_45_52_326Z-debug.log
2020-09-28T21:45:52.378534+00:00 heroku[web.1]: Process exited with status 1
2020-09-28T21:45:52.404244+00:00 heroku[web.1]: State changed from starting to crashed
`

Error message, there's around 3 weeks of solid data entry in there and no backups can be imported back into Ghost which is, just great :( and this is linked up to a Gatsby front-end

Any help would be most appreciated, Google wasn't particularly helpful when searching out the error messages - as stated, most common advice was to upgrade, which led to the server error.

If I should be posting any other logs, just let me know and I'd be happy to oblige.

Cheers

Terry

[eltel]

Yes, of course - sorry - it’s been a while since I’ve been on here and I forgot to check the previews - I’ve been running around in panic all afternoon - I’ll resolve that now.

Thanks again!

[paulmelnikow]

Glad you solved it.

Most of what you’ve posted here is nearly unreadable due to formatting. For the benefit of other people who might see this, you could try to fix that. You can probably wrap the logs in triple backticks. Also formatting your message properly is a nice thing to do in the future when you’re asking for help 😄

for future reference, I’d really like to know - could the DB actually be corrupted by deleting a page that’s being linked to? It’s the only thing that’s happened that I’m aware of.

I imagine the Ghost forum might be a better place to get an answer to that.