psql -U gary -d archivedb gives:
FATAL: Peer authentication failed for user "gary"
which probably means that psql can't find the database either.
My process table ( ps -xaf) shows:
642 ? S 0:07 /usr/lib/postgresql/9.6/bin/postgres -D /var/lib/postgresql/9.6/main -c config_file=/etc/postgresql/9.6/main/postgresql.conf
754 ? Ss 0:00 \_ postgres: 9.6/main: checkpointer process
755 ? Ss 0:04 \_ postgres: 9.6/main: writer process
756 ? Ss 0:04 \_ postgres: 9.6/main: wal writer process
757 ? Ss 0:04 \_ postgres: 9.6/main: autovacuum launcher process
758 ? Ss 0:05 \_ postgres: 9.6/main: stats collector process
643 ? S 0:12 /usr/lib/postgresql/9.5/bin/postgres -D /var/lib/postgresql/9.5/main -c config_file=/etc/postgresql/9.5/main/postgresql.conf
768 ? Ss 0:00 \_ postgres: checkpointer process
772 ? Ss 0:11 \_ postgres: stats collector process
6501 ? Ss 0:00 \_ postgres: postgres postgres [local] idle
So the database seems to be running. No sure why there are two versions running but may be due to Debian using the older version of something. Is this a path problem?
Does this help
Gary R.
On 10/22/2016 01:13 PM, Vijay Khemlani wrote:
Can you connect to the database via command line?
psql -U gary -d archivedb
On Sat, Oct 22, 2016 at 3:48 PM, Jamie Lawrence <jalawrence@gmail.com> wrote:
> On Oct 22, 2016, at 11:35 AM, Gary Roach <gary719_list1@verizon.net> wrote:
> When I try to migrate, I get the following error:
>
>> psycopg2.OperationalError: FATAL: database "archivedb" does not exist
> What's happening here?
Are you certain the 'archivedb' database actually exists?
If it does, is in in an accessible schema?
If it is, is it in the cluster you're connecting to in Django?
-j
No comments:
Post a Comment