-
Notifications
You must be signed in to change notification settings - Fork 119
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
There is 1 other session using the database error #69
Comments
I'm getting this too. It appears the issue is caused by an update to SQLAlchemy. You can work around this by running: |
Hmm, I still get this error even after installing the versions of SQLAlchemy @kaedroho suggests. |
Thanks for reporting the issue. I quickly reinstalled stellar on my Mac but failed to reproduce this issue. The error message says that there is some other session going on that database. The other session can come from stellar itself(=same process), or from some other process(=stuck? stellar background process). Can you try to check if there was some sql process going before running the stellar command? So run Can you also just paste |
I have the same problem . here is the log
|
@jalada Sorry, I posted the wrong version. I've updated my original comment. SQLAlchemy 1.2.6 and above have this issue. It can be worked around for now by downgrading to 1.2.5 ( |
yes ,pip install SQLAlchemy==1.2.5 SQLAlchemy-Utils==0.33.1 works! , @kaedroho thanks |
I'm also getting this issue, but @kaedroho's fix worked! |
Snap, thanks @kaedroho! |
I tried to install the mentioned version of SQLAlchemy but I can't still reproduce the issue for some reason.
|
Well I can reproduce it very vividly:
|
The difference may be the Postgresql version. I had SQLAlchemy1.2.9 and SQLAlchemy-Utils 0.33.3 and they worked without issue using Postgresql 9.6. After I upgraded to Postgresql 10.5 I got the same "source database "template1" is being accessed by other users" error as above. (via Homebrew on macOS 10.13.6 using Stellar 0.4.5) After finding this issue I tested do downgraded to SQLAlchemy 1.2.5 and SQLAlchemy-Utils 0.33.1 as suggested and I got a working stellar again. |
Also happens to me with stellar 0.4.5/Python 3.6.7/Ubuntu 18.04/pip 18.1/PostgreSQL 10.6 |
Same here.... stellar 0.4.5/Python 3.6.7/pip3 9.0.1/psql 10.8 |
This is workaround for me: where $USER is your DB user name stellar is working with (needs corresponding privileges obviously) |
@nick4u, thank you, that seems to be the most correct solution. |
The stellar package was not used, and the latest available release is from 2018, and has known issues, including, but not limited to: - github.com/fastmonkeys/stellar/issues/69 - stackoverflow.com/questions/62688256/
The stellar package was not used, and the latest available release is from 2018, and has known issues, including, but not limited to: - github.com/fastmonkeys/stellar/issues/69 - stackoverflow.com/questions/62688256/
I'm getting this error when trying to snapshot a postgres database
The source database is not being used when doing the backup.
I'm running Mac OS 10.13.4, probably with the default python version (2.7.14)
The text was updated successfully, but these errors were encountered: