Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Persistence of Errors After Upgrading to Penpot 2.0.1 #4550

Open
kaicox opened this issue May 6, 2024 · 1 comment
Open

Issue with Persistence of Errors After Upgrading to Penpot 2.0.1 #4550

kaicox opened this issue May 6, 2024 · 1 comment
Assignees
Labels
bug self-hosted The issue is happening on a self-hosted instance

Comments

@kaicox
Copy link

kaicox commented May 6, 2024

Hello Team,

I recently upgraded Penpot from version 1.19.3 to 2.0.1 but continue to face the same issue. After deleting v2-migrated from server_prop and attempting to restart the containers, the issue persists. Observing the backend logs post-restart, I noticed the following entries:

[2024-05-06 08:03:26.043] I app.migrations.v2 - hint="v2 migration started"
[2024-05-06 08:03:26.088] I app.migrations.v2 - hint="v2 migration finished", files=nil, teams=nil, errors=nil, elapsed="0.083884949s"

Despite these indications of a successful migration, I am unable to open my project. The project does not load at all, as illustrated in the screenshot linked below:
image
Here is the Docker Compose configuration I am using:

version: "3.8"

networks:
  penpot:

volumes:
  penpot_postgres_data2:
  penpot_assets_data2:

services:
  penpot-frontend:
    image: "penpotapp/frontend:2.0.1"
    ports:
      - 80:80

    volumes:
      - ./penpot_assets_data2:/opt/data

    env_file:
      - config.env

    depends_on:
      - penpot-backend
      - penpot-exporter

    networks:
      - penpot

  penpot-backend:
    image: "penpotapp/backend:2.0.1"
    volumes:
      - ./penpot_assets_data2:/opt/data

    depends_on:
      - penpot-postgres
      - penpot-redis

    env_file:
      - config.env

    networks:
      - penpot

  penpot-exporter:
    image: "penpotapp/exporter:2.0.1"
    env_file:
      - config.env
    environment:
      # Don't touch it; this uses internal docker network to
      # communicate with the frontend.
      - PENPOT_PUBLIC_URI=http://penpot-frontend
    networks:
      - penpot

  penpot-postgres:
    image: "postgres:15"
    restart: always
    stop_signal: SIGINT
    ports:
      - 5432:5432
    environment:
      - POSTGRES_INITDB_ARGS=--data-checksums
      - POSTGRES_DB=penpot
      - POSTGRES_USER=penpot
      - POSTGRES_PASSWORD=penpot

    volumes:
      - ./penpot_postgres_data2:/var/lib/postgresql/data

    networks:
      - penpot

  penpot-redis:
    image: "redis:7"
    restart: always
    networks:
      - penpot
  penpot-mailcatch:
    image: sj26/mailcatcher:latest
    restart: always
    expose:
      - '1025'
    ports:
      - "1080:1080"
    networks:
      - penpot
@madalenapmelo-kp madalenapmelo-kp added bug self-hosted The issue is happening on a self-hosted instance labels May 6, 2024
@niwinz
Copy link
Contributor

niwinz commented May 23, 2024

Hello,

It is not clear to me what the problem is here, in the screenshot I see that nothing has been migrated, that is, 0 migrated files. I also don't see any persistence problem that you mention in the title.

My recommendation is that you try to approach topic by topic, try creating an instance from 0, with new volumes and see what problems you have.

@niwinz niwinz self-assigned this May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug self-hosted The issue is happening on a self-hosted instance
Projects
None yet
Development

No branches or pull requests

3 participants