Postgresql socket error on OSX 10.7.3 when running Django's syncdb

E

7

14

Since upgrading OSX to version 10.7.3, when I attempt to run a Django "syncdb" command, I receive the following psycopg2 error from Postgresql 8.4.2:

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/pgsql_socket/.s.PGSQL.5432"?

I'm able to open psql without incident, but when I attempt to run "pg_ctl status", I receive this error as well:

pg_ctl: could not open PID file "/Library/PostgreSQL/8.4/data/postmaster.pid": Permission denied

Is there a correlation?

Erotica answered 3/2, 2012 at 18:48 Comment(3)

pg_ctl is a seperate issue, it must be run as the postgres user otherwise it can't access the pid file. When you run psql do you specify a host or ip with -h? – Listerism 4/2, 2012 at 7:20

No, I do not specify a host. Prior to 10.7.3, I never had to. – Erotica 5/2, 2012 at 0:44

I've noticed that adding "-h localhost" to my "psql -U postgres mydatabase" commands fixes the problem. Any thoughts on that front? – Erotica 7/2, 2012 at 22:46

H

33

I had the same problem too: updated osx to 10.7.3 and after I restarted the postgres server I got the same issue when I tried to run $ ./manage.py dbshell that goes through psycopg2, but didn't have problem connecting to postgres using psql.

To me the problem appears to be related just to "connections on Unix domain socket", because psycopg2 uses the newly 10.7.3 osx updated postgres library.

I tried to reinstall psycopg2, but nothing was changed.

So, I changed the HOST value on the databases section of my django settings.py, and instead of having an empty string I put 'localhost'.

and it works perfectly!

Heaviness answered 7/2, 2012 at 21:20 Comment(8)

I changed the "DATABASE_HOST" value, but the problem persists. – Erotica 7/2, 2012 at 21:59

Do you have in your postgresql.conf this variable setted as: listen_addresses = 'localhost' or listen_addresses = '*' otherwise postgres doesn't allow you to connect via 'network' And of course you have to check if everything's correct in pg_hba.conf too – Heaviness 9/2, 2012 at 15:58

I just made the suggested change, restarted Postgresql, and the problem persists. – Erotica 10/2, 2012 at 16:41

This worked for me after upgrading from 10.6 to 10.8 with no restart of Postgres. – Unfeeling 26/7, 2012 at 18:25

Very nice. I had the same issue. Changed the HOST string to localhost and boom! Worked like a charm. That was frustrating. Thanks for the tip! – Tb 16/3, 2013 at 5:16

adding localhost fixed it for me in 10.8 – Grievous 19/6, 2013 at 11:51

adding localhost fixed it for me in 10.8 as well, awesome dude – Fester 10/7, 2013 at 13:34

Thank you! I don't think there is ANY way I would've found a fix to this on my own. – Cropland 24/9, 2013 at 22:24

L

8

Eelke 's problem was the same as mine. The quickest fix for this would be to add

export PGHOST=/tmp

an environment variable in your .bashrc/.zshrc/etc file (depending on which you use).

The best fix would be to set the specific path in your apps config file.

Lykins answered 16/2, 2012 at 22:4 Comment(2)

i think this works because it changes which psql you use from the problematic apple one, to the one you get when you install postgres maybe? – Saturate 21/7, 2012 at 17:19

Not a bash wizard myself, but it might have to read export PGHOST="/tmp" – Forkey 30/9, 2014 at 17:58

L

4

Did a bit of testing on my Mac and I noticed that there are two versions on my system for several commands. One version is in /usr/bin the other is in /Library/PostgreSQL/9.0/bin. The version in /usr/bin is expecting /var/pgsql_socket/.s.PGSQL.5432, the right version for my install expects /tmp/.s.PGSQL.5432

The version in /usr/bin is 9.0.5 and it has been installed by Apple.

Unfortunatly I do not know much about django, but my bet is it is either calling a command in the wrong path or it is loading a library from the wrong location.

Listerism answered 5/2, 2012 at 8:29 Comment(0)

S

2

You can fix the problem by creating a symlink:

 ln -s /tmp/.s.PGSQL.5432 /var/pgsql_socket/

Spirit answered 27/2, 2012 at 16:8 Comment(0)

B

2

This did the trick for me in the end...

Change the HOST value in the database dictionary in settings.py to this:

'HOST': '/tmp',

Source: http://jeffammons.net/2011/09/fixing-postgres-on-mac-10-7-tiger-for-django

Bartz answered 4/4, 2012 at 23:36 Comment(0)

N

1

Reinstalling psycopg2 worked for me

Nikolenikoletta answered 23/10, 2012 at 4:6 Comment(1)

This is most likely incidental, not solving the problem generally. – Forkey 30/9, 2014 at 18:58

E

0

I ran into the same issue just after upgrading to OSX 10.7.3; reinstalling PostgreSQL solved the problem and did not delete my existing data.

Eliseo answered 7/2, 2012 at 9:35 Comment(0)

Recommended topics

Hot tags