Does "Could not execv" mean that I do not have rights to execute this script?
This seems to say that Other users, like postgres, should be able to execute it. I'm confused, here.biko:/usr/bin# ls -al | grep psql lrwxrwxrwx 1 root root 10 Oct 10 16:24 psql -> pg_wrapper biko:/usr/bin#
-- Hugh
I did this tonight
dpkg --purge postgresql
apt-get install postgresql
and am now still getting the following:
biko:/usr/bin# psql -U postgres No database specified biko:/usr/bin# psql -U postgres template1 Could not execv /usr/lib/postgresql/bin/psql biko:/usr/bin# psql -U postgres template0 Could not execv /usr/lib/postgresql/bin/psql biko:/usr/bin# psql -U postgres ggp_test Could not execv /usr/lib/postgresql/bin/psql biko:/usr/bin#
My pg_hba.conf temporarily reads:
(Eventually, before I take this live, I'll figure out the crypt part).local all trust host all 127.0.0.1 255.255.255.255 trust host template1 192.168.2.21 255.255.255.0 trust host all 0.0.0.0 0.0.0.0 reject
The postgresql installation is at 192.168.10. I'm working from a shell at 192.168.2.21. But I also tried running this from the application server at 2.10 as well and got the same errors.
And now pgAdmin II is giving me a connection error:
An error has occured in pgAdmin II:frmConnect.cmdConnect_Click Number -2147467259 Description: Could not connect to the server; Could not connect to remote socket.
/etc/postgresql/postgresql.conf includes a line reading:
which I assume means that I _should_ be able to make a TCP connection across the network. Although I cannot seem to do so.tcpip_socket = 1
Working in Debian 3.0 Woody, with postgreSQL 7.2. Still looking for clues, in fact I seem to be looking for more clues now than I was yesterday.
-- Hugh
At 05:20 PM 11/19/02 +0000, you wrote:
Did you install your package using apt-get ?
All the instalations that I do are using those tools from debian. You have to see all the packages that you have instaled in your computer like:
dpkg -l | grep postgresql
ii postgresql 7.2.1-2 Object-relational SQL database, descended fr
ii postgresql-cli 7.2.1-2 Front-end programs for PostgreSQL
ii postgresql-con 7.2.1-2 Additional facilities for PostgreSQL
Then you do: dpkg --purge postgresql. You can now run the first command to see if something is still installed. If some are instaled, the you remove it using again dpkg --purge.
Luis Sousa
Hugh Esco wrote:
I have reinstalled before. I wonder though, how I ensure that I have cleanly un-installed it first, so that I leave no residue from the previously botched installation around to mess things up the next time.
-- Hugh Esco
At 09:03 AM 11/19/02 +0000, Luis Sousa wrote:
Tom Lane wrote:
Start over: delete your PG installation and reinstall the Debian
package. It seems very clear that you've got an incomplete package.
regards, tom lane
I agree with Tom Lane. Probably is the best thing to do. When you install all it over, in theory, all the problems will solve by them selfs.
Luis Sousa
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
