Psycopg2.operationalerror Error No Such Database
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow psycopg2.connect example the company Business Learn more about hiring developers or posting ads with us Stack
Psycopg2.connect Port
Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of operationalerror: could not connect to server: no such file or directory odoo 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Can't connect the postgreSQL with psycopg2 up vote 20 down vote favorite 5 It's the first time that
Psycopg2 Operationalerror Could Not Connect To Server
I can't find the answer about some tech problems Here's my problems: >> conn=psycopg2.connect(database="mydb", user="postgres", password="123",port=5432) Traceback (most recent call last): File "
LDAP (2) linux (16) misctools (3) network (4) noplone (3) open source (11) parallelization (1) photography (7) plone (16) puppet (1) python (3)
Psycopg2 Connect Without Password
review (7) soap (2) soaring (3) software (37) software engineering (1) squeezebox
Psycopg2.operationalerror Could Not Connect To Server Connection Refused
(3) sugarcrm (3) syncmaster_204b (3) testing (2) travel (2) turbostation (3) usability (1) version_control (1) wordpress (2) world psycopg2 connection string wide web (4) zookeeper (1) Archive 2015 2013 2011 2010 2009 2008 2007 2006 PostgreSQL/Python/psycopg2: Confusing error, port setting required for socket connections Published: 2010-02-06 13:43 UTC. Tags: django python http://stackoverflow.com/questions/5500332/cant-connect-the-postgresql-with-psycopg2 When trying to get my local development copy of this website running after upgrading my Ubuntu, I got the following confusing error message from the psycopg2 python module: psycopg2.OperationalError: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? My django settings file was correct: DATABASE_ENGINE = 'postgresql_psycopg2' http://efod.se/blog/archive/2010/02/06/pscopg2-operationalerror # 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'. DATABASE_NAME = 'dbname' # Or path to database file if using sqlite3. DATABASE_USER = 'dbuser' # Not used with sqlite3. DATABASE_PASSWORD = 'dbpassword' # Not used with sqlite3. DATABASE_HOST = '' # Set to empty string for localhost. Not used with sqlite3. DATABASE_PORT = '' # Set to empty string for default. Not used with sqlite3. Confusing, since my Postgres server was running and I could connect using psql: psql -U dbuser -W dbname This turned out to be one of these problems when Google is of no help - others had the same problem, but I could only find posts where people asked the question, no posts where the actual solution was found. The cause of the problem was that my PostgreSQL installation was configured to listen on port 5433 instead of the default 5432, and as seen in the error message, the port number is part of the path to the unix socket. The different port was probably setup when I upgraded my Ubuntu, since that installed PostgreSQL 8.4 without completely
a GitHub account Sign in Create a gist now Instantly https://gist.github.com/4365146 share code, notes, and snippets. Star 0 Fork 0 natea/psycopg2.OperationalError Created Dec 23, 2012 Embed What would you like to do? Embed Embed this gist in your website. Embed Share Copy sharable URL for this gist. Share Clone via HTTPS Clone with Git or could not checkout with SVN using the repository's web address. HTTPS Learn more about clone URLs Download ZIP Code Revisions 1 psycopg2.OperationalError: could not connect to server: No such file or directory Raw psycopg2.OperationalError $ dotcloud deploy --application mediathread9 latest ==> Submitting a deployment request for revision could not connect latest of application mediathread9 ==> Deployment of revision rsync-1356287081260 scheduled for mediathread9 - 2012-12-23 (mediathread9 deployment, deploy_id=efb24b35-55be-4933-89f6-eb0af54516a9) 12:30:44: --> Deployment scheduled for application (mediathread9) at revision rsync-1356287081260 12:31:15: [www.0] Running postinstall script... 12:31:17: [www.0] + python createdb.py 12:31:18: [www.0] create_dbs start 12:31:18: [www.0] create_dbs: let's go. 12:31:18: [www.0] create_dbs: got settings. 12:31:18: [www.0] creating database mediathread9 on mediathread9-natea.azva.dotcloud.net 12:31:18: [www.0] database "mediathread9" already exists 12:31:18: [www.0] 12:31:18: [www.0] moving right along... 12:31:18: [www.0] + mkdir -p /home/dotcloud/data/media /home/dotcloud/volatile/static 12:31:18: [www.0] + python mediathread/manage.py syncdb --noinput 12:31:19: [www.0] Syncing... 12:31:19: [www.0] Traceback (most recent call last): 12:31:19: [www.0] File "mediathread/manage.py", line 14, in