-
Notifications
You must be signed in to change notification settings - Fork 360
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
Update setup.sh to create DB user with a password #113
Comments
I am having what sounds like a similar issue - The above exception was the direct cause of the following exception: Traceback (most recent call last): You may be able to resolve this warning by setting The above exception was the direct cause of the following exception: ╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮ |
For me the issue was postgres was already running. I closed it, reran setup.sh and it worked fine |
@ryanholtschneider2 that's interesting -- we have a check to see if postgres is already running before running commands. A few questions:
|
Native instance.
When I ran pg_ready it said something to the effect of the pg was running
…On Fri, Mar 22, 2024 at 12:03 AM Suchintan ***@***.***> wrote:
@ryanholtschneider2 <https://github.com/ryanholtschneider2> that's
interesting -- we have a check to see if postgres is already running before
running commands.
https://github.com/Skyvern-AI/skyvern/blob/main/setup.sh#L179
A few questions:
1. Did you have it running in Docker? Or as a native instance?
2. What do you get as output on the pg_ready command?
—
Reply to this email directly, view it on GitHub
<#113 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BCBQYUL7KLEGHD3ROBKN6K3YZOUQ7AVCNFSM6AAAAABE6O5THOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJUGMYTIMJYGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Another similar issue recently shared in our Discord: https://discord.com/channels/1212486326352617534/1214296823066534021/1220547538294411365 I'm going to try and spend some time fixing this over the weekend, it's safe to say that it's a common issue now. |
Yeah this issue happens if you already have postgres running ( I had it running in docker with port mapping), stopped my local instance and reran the setup and it worked fine. |
Any movement / work-arounds on this one? |
This issue is stale because it has been open for 30 days with no activity. |
I saw a couple of cases on Discord where re-creating the postgresql user with a password solved some issues.
References:
The text was updated successfully, but these errors were encountered: