Hi, When running most recent upgrade (something 6 to 7), rake db:migrate failed because of a supposed duplicate username. As I’m not really comfortable with the Linux commandline, I then tried to enter the rails console in order to fix this but the console won’t load because it couldn’t connect to …

@pfaffman fixed it. I recommend this guy :slight_smile:

[afbeelding] Judith: Can anyone advise how to restore the server? @pfaffman specializes in this kind of support, perhaps contact him. [afbeelding] Judith: rake db:migrate failed because of a supposed duplicate username. Do you have the exact failure? you may need a bit of scrolling, b…

There was a bug somewhere along the way that allowed usernames with different capitalization. And then it got fixed so that it doesn’t. You might be able to crank up the old container and fix it with the ux. But if you haven’t done a command line upgrade for a while, then there’s also a database u…

This is the output from the web interface: *** Please be patient, next steps might take a while *** ******************************************************** Cycling Unicorn, to free up memory Restarting unicorn pid: 46 Waiting for Unicorn to reload. Waiting for Unicorn to reload.. Waiting for Unico…

I have seen this error before, it happens when there is an internal corruption in the users table. Somehow you have a duplicate “user” record in the table, it snuck in during an earlier version or during an upgrade or during a rude shutdown. I still do not know exactly why it happens, but I have se…

Thank you for your quick replies! How do I boot a data container? I tried ./launcher start app and then rails c, but Rails won’t start because the database is not running. I tried /etc/init.d/postgresql restart but got the error you see in the initial post, something about the Postgresql version bei…

Look in the sample dir for an example data container You just need to point it at the right location, then you should be able to enter the container and run psql Yeah you are already upgraded to 13

Help! Upgrade leidde tot een complete mislukking

Ondersteuning Installatie

Judith (Judith Meyer) 9 maart 2021 om 19:39 8

@pfaffman fixed it. I recommend this guy

Upgrade Issues: Failed Upgrade due to Duplicate Key, Failed Snapshot Restore

Topic		Antwoorden	Weergaven
Migration from discourse v2.8.13 (on Ubuntu 20.04.6 LTS) to latest Self-hosting	3	769	15 augustus 2023
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2055	15 februari 2021
Update failed for some reason? Self-hosting	1	698	30 maart 2022
Error upgrading from 3.0.1 to 3.1.0 Self-hosting	14	785	28 maart 2023
Problem after Discourse update Self-hosting	17	1841	8 maart 2021

Help! Upgrade leidde tot een complete mislukking

Gerelateerde topics