Thread: Re: Newbie: problem Connecting to Server
I am having this exact same problem. Any help would be greatly appreciated. Thank you. "Ferindo Middleton Jr" <ferindo.middleton@verizon.net> wrote in message news:pan.2003.03.31.01.23.34.434512@verizon.net... > I'm running Redhat Linux 8. I have registration to the Redhat Network so > I'm probably running the latest version of postgre sql available. I also > have Redhat Databse v2.1 installed, but whenever I try to start a session, > I get the following error message: > > psql: could not connect to server: No such file or directory > Is the server running locally and accepting > connections on Unix domain socket "/tmp/.s.PGSQL.5432"? > > Please help me configure my system so that I can connect and begin to use > postgresql.
Frustrated Beginner wrote: > I am having this exact same problem. Any help would be greatly appreciated. > Thank you. > > > > "Ferindo Middleton Jr" <ferindo.middleton@verizon.net> wrote in message > news:pan.2003.03.31.01.23.34.434512@verizon.net... > >>I'm running Redhat Linux 8. I have registration to the Redhat Network so >>I'm probably running the latest version of postgre sql available. I also >>have Redhat Databse v2.1 installed, but whenever I try to start a session, >>I get the following error message: >> >>psql: could not connect to server: No such file or directory >> Is the server running locally and accepting >> connections on Unix domain socket "/tmp/.s.PGSQL.5432"? >> >>Please help me configure my system so that I can connect and begin to use >>postgresql. you guys first have to create a POSTGRESQL USER, under which the server will run... in other words: the server (postmaster) must be running, which it is not, apparently. /tmp/.s.PGSQL.5432 is a unix socket, to which the client connects. the postgresql-server creates that socket itself. since you guys are running redhat, you should be able to set the scripts to started at boot time in different runlevels (runlevel editor) and select postgresql to be started... as root as a matter of course. if none of that works, then try the following as root: first uninstall the postgresql, download the kernelheaders to your current kernel, download the current postgresql-sources (7.3.2), compile that, and install (make install - as root) follow these directions (all as root): - create the user "postgres" belonging to group "daemon" - mkdir /usr/local/pgsql/logs - mkdir /usr/local/pgsql/data - chmod 700 /usr/local/pgsql/data - echo "/usr/local/pgsql/lib" >> /etc/ld.so.conf - ldconfig - chown -R postgres:daemon /usr/local/pgsql - su postgres -c '/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data' - su postgres -c '/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >> /usr/local/pgsql/logs/server.log 2>&1' & (all in one line) and you're done, you may now create a new and fresh database, just like this: - su postgres -c '/usr/local/pgsql/bin/createdb <databasename>' notice that "su postgres .." command... it is because postmaster (the server binary) likes to be started as a user and not as root, since that would be a dangerous act. all programs can be exploited and evil, evil badboys could gain root privileges and destroy the whole world... postgresql simply won't start as root - security issues. ANYONE: please correct me, if I'm wrong!!!!! it is important, so I or them won't mess up their systems.. cheers, alex
So others might learn from this. The following solution was offered and helped considerably in my case: With an RPM install of PostgreSQL (which RedHat Database is), please consult README.rpm-dist (find it with 'rpm -ql postgresql |grep rpm'). The short of it: The RPM install scripts handle the user creation. All one must do is (as root): '/sbin/service postgresql start' to get an initdb done and postmaster started. Then edit /var/lib/pgsql/data/pg_hba.conf to allow access to the client IP address, and edit postgresql.conf (in the same directory) for tcpip_socket to be true (if you are doing TCP/IP connections, that is). To get postgresql started automatically at boot, do (assuming you want postgresql to run in runlevels 3, 4, and 5): '/sbin/chkconfig --level 345 postgresql on' List the currently valid runlevels with '/sbin/chkconfig --list postgresql' If it complains about postgresql not be a known service, execute '/sbin/chkconfig --add postgresql' -- if that doesn't work, check to see if the postgresql-server RPM is installed ('rpm -qa|grep postgresql'). -No Longer Frustrated "Frustrated Beginner" <nowweare@access4cheap.com> wrote in message news:3e8b9c82_1@newsfeed... > I am having this exact same problem. Any help would be greatly appreciated. > Thank you. > > > > "Ferindo Middleton Jr" <ferindo.middleton@verizon.net> wrote in message > news:pan.2003.03.31.01.23.34.434512@verizon.net... > > I'm running Redhat Linux 8. I have registration to the Redhat Network so > > I'm probably running the latest version of postgre sql available. I also > > have Redhat Databse v2.1 installed, but whenever I try to start a session, > > I get the following error message: > > > > psql: could not connect to server: No such file or directory > > Is the server running locally and accepting > > connections on Unix domain socket "/tmp/.s.PGSQL.5432"? > > > > Please help me configure my system so that I can connect and begin to use > > postgresql. > >