Is the server running locally and acceptingĬonnections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?īut Postgres is still clearly running: $ ps aux | grep postgres Psql: could not connect to server: No such file or directory I am unable to connect (but was able to before pre-Mountain Lion): $ psql -U rails -d myapp_development I'm not a DBA, but hoping someone can tell me how to troubleshoot this. ![]() It was installed originally via Homebrew. I'm not an expert with databases or Linux, so any help why this might happen and how I can figure out what exactly is happening is highly appreciated, thank you.Recently updated my machine from Mac OS X Lion (10.7.4) to Mountain Lion (10.8) and I think it borked my PostgreSQL installation. ![]() What is so confusing about this is that it worked perfectly fine just a yesterday, and I have not changed anything. I can't seem to find any errors in the logs for the regular SELECT queries from my Python scripts, so I don't know why the connection is closed for this all the time. 11:25:18.891 CEST HINT: In a moment you should be able to reconnect to the database and repeat your command. 11:25:18.891 CEST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 11:25:18.891 CEST WARNING: terminating connection because of crash of another server process 11:25:18.891 CEST LOG: terminating any other active server processes 11:25:18.891 CEST DETAIL: Failed process was running: SELECT * FROM transactionoutputs WHERE fileheader '' I got this message a lot during the night where I was not doing anything with it either.įor the actual error regarding the query from pgAdmin, this is what I get: 11:25:18.891 CEST LOG: server process (PID 20569) was terminated by signal 11: Segmentation fault It is showing this message for the default postgres database and not my own, but it still confuses me why this happens as I'm using the default postgres user for both databases. I am certain that I am using the correct password, as it does work 50% of the time of the queries. 19:43:26.959 CEST DETAIL: Password does not match for user "postgres".Ĭonnection matched pg_hba.conf line 102: "host all all all md5" The last few days, it constantly gave me the following message: 19:43:26.959 CEST FATAL: password authentication failed for user "postgres" The logs are not making much sense to me, but there are several things wrong. I did try to restart the service to no avail. What is weird is that the database has been running for over a month without any issues, and this only started today. I couldn't find any other examples where this happens in pgAdmin, but there is surely something wrong. This query specifically worked fine a few days ago. However, when I try to run the following query in pgAdmin, I get the message Connection to the server has been lost. Interestingly, the same queries (which are simple "SELECT * FROM table" statements) run perfectly fine in pgAdmin. This probably means the server terminated abnormally Server closed the connection unexpectedly I am using SQLAlchemy and it is giving me the following error: : terminating connection due to administrator command In about 50% of the cases, my Python script will fail to return any data because the DB server closed the connection. ![]() Since today, I am suddenly getting errors when querying data from a Python script running on the same machine, and in some edge cases also in pgAdmin 4. I have a PostgreSQL 10.12 server running on an Ubuntu 18.04 Server.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |