`upgrade` doesn't create user. _Internal project (id=1) does not exist_ about self-hosted

[mattrobenolt]

Sounds like you're running out of memory.

[thinhnd580]

I delete and clone agian this repo, did what readme said and good to go

[mario-devops]

the same problem with you, the pgsql has nothings

[mario-devops]

postgres-# \l
List of databases
Name | Owner | Encoding | Collate | Ctype | Access privileges
-----------+----------+----------+------------+------------+-----------------------
postgres | postgres | UTF8 | en_US.utf8 | en_US.utf8 |
template0 | postgres | UTF8 | en_US.utf8 | en_US.utf8 | =c/postgres +
| | | | | postgres=CTc/postgres
template1 | postgres | UTF8 | en_US.utf8 | en_US.utf8 | =c/postgres +
| | | | | postgres=CTc/postgres
(3 rows)

[exp0nge]

+1

edit: @jean @mario-devops Are you sure the initial call to upgrade worked? Or does the initial call not even migrate at all?

[KillerCodeMonkey]

same issue. it happens on my EC2 instance. if i run the upgrade command it gets stuck by migration 298 and i am not even able to connect to my instance in another shell Oo.

after a while i can reconnect to my instance and run the migration command again. After that this error occurs.

[exp0nge]

For sure he is. I think if you squash the migrations or like generate initial ones it should be fine.

[KillerCodeMonkey]

@mattrobenolt bääääm instant reply :D

sure i only tried it with micro teer.
will check with a larger type

[mattrobenolt]

Would love to do that some day, but that's nontrivial. :)

[KillerCodeMonkey]

works with small instance type 👍

[falstack]

same issue.

[dmugtasimov]

How much memory is required (just) to run migrations?

[exp0nge]

The micro instance on AWS is definately not enough. I have tried it with medium.

…

On Wed, Jun 20, 2018, 3:44 PM Dmitry Mugtasimov ***@***.***> wrote: How much memory is required (just) to run migrations? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#49 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALM_rexe2ORW19ySJYk6b-F6zOCEYjHeks5t-qYZgaJpZM4Oipvt> .

[revolunet]

try to delete the docker volume and restart migrations with docker-compose run --rm web upgrade

[lilywang711]

same issue.

[solars]

same problem...

[image72]

maybe resolve that.

Install-Sentry-services
docker-compose run --rm web shell

from sentry.models import Project
from sentry.receivers.core import create_default_projects
create_default_projects([Project])

// getsentry/sentry#9270 (comment)
docker exec -it onpremise_postgres_1 bash
psql -h 127.0.0.1 -d postgres -U postgres

create or replace function sentry_increment_project_counter( project bigint, delta int) returns int as $$ declare new_val int; begin loop update sentry_projectcounter set value = value + delta where project_id = project returning value into new_val; if found then return new_val; end if; begin insert into sentry_projectcounter(project_id, value) values (project, delta) returning value into new_val; return new_val; exception when unique_violation then end; end loop; end $$ language plpgsql;

[BYK]

Closing as this seems to be related to memory constraints and this is now documented in the README.