-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
Bug: Prisma Plugin Did Not Start in time #582
Comments
I was able to get it working using the trunk tag but still an issue with the latest one |
I just set up ZipLine hours ago. Everything worked just fine when I tested the docker-compose setup on my desktop. When I tried to do the same thing on the NAS, I got this very same error. I dropped everything in the database and re-started the compose project. I had to do it two more times, but at the 4th attempt, everything was working once again. I have no idea how this is possible, but hey, as long as it works... (It has to be some sort of concurrency execution thing during the DB migration. No other explanation of the ad-hoc error IMO) |
Having the same problem |
Yeah I was doing it on my Synology nas using portainer and this was the error I was getting. Trunk version worked though so I just stuck with that. |
tried trunk version too, still wont work same error as described above. |
@roafhtun as I said, I had to clean up Postgres, then Ohh, and when you clean postgres make sure you delete everything, not just the tables. |
I also encountered this problem on Synology's nas. I can run it locally without problems. However, no matter how many times I reset and delete postgres and restart the project on Synology, it seems to be unable to work properly. I also tried the trunk version, but it didn't work either. But the good news is that I found a way to solve the problem stably. volumes:
- ./pg_data:/var/lib/postgresql/data After the local docker successfully runs and the configuration is complete, replacing the local pg_data folder with the pg_data folder on Synology will make it work. |
What happened?
Fresh clone with docker and I get these logs
Version
latest (ghcr.io/diced/zipline or ghcr.io/diced/zipline:latest)
What browser(s) are you seeing the problem on?
No response
Zipline Logs
Browser Logs
Additional Info
I found this link around the error issue.. Not sure if it helps: fastify/fastify-cli#422
The text was updated successfully, but these errors were encountered: