Re: error while starting database - Mailing list pgsql-bugs
From | Douglas Toltzman |
---|---|
Subject | Re: error while starting database |
Date | |
Msg-id | B6FF72E5-3A0E-494B-9773-5924EA5E5C3A@oakstreetsoftware.com Whole thread Raw |
In response to | Fwd: error while starting database ("Nitin Saxena" <nitinmca05@gmail.com>) |
Responses |
Re: error while starting database
|
List | pgsql-bugs |
Since you do not have a /tmp folder in your filesystem, it may be that the server cannot create the socket file and so it will not start. You cannot telnet to port 5432, because no service is listening on that port. The PostgreSQL server is not started. I'm sorry I didn't answer you last night. It was 02:00 in the morning when I got home and sent you the previous message, I went straight to bed after checking my mail. In any case, the server specifically calls out an error creating "/tmp/.s.PGSQL.5432". I would start by creating a world-writable /tmp folder. If that allows you to start the service, then you can do a backup with pg_dumpall. On Aug 18, 2007, at 12:20 AM, Nitin Saxena wrote: > Hi, > > When i m using > ps -ax |grep postgres > > [root@imap /root]# ps -ax |grep postgres > 994 tty1 S 0:00 su - postgres > > when i am using > > netstat -a , it gives > > Active Internet connections (servers and established) > Proto Recv-Q Send-Q Local Address Foreign Address > State > tcp 0 0 *:32768 *:* > LISTEN > tcp 0 0 *:shell *:* > LISTEN > tcp 0 0 *:time *:* > LISTEN > tcp 0 0 *:8007 *:* > LISTEN > tcp 0 0 *:netbios-ssn *:* > LISTEN > tcp 0 0 *:pop3 *:* > LISTEN > tcp 0 0 *:imap *:* > LISTEN > tcp 0 0 *:finger *:* > LISTEN > tcp 0 0 *:sunrpc *:* > LISTEN > tcp 0 0 *:http *:* > LISTEN > tcp 0 0 *:ftp *:* > LISTEN > tcp 0 0 *:ssh *:* > LISTEN > tcp 0 0 *:telnet *:* > LISTEN > tcp 0 0 *:smtp *:* > LISTEN > tcp 0 0 10.2.0.48:http 192.168.255.10:35046 > TIME_WAIT > tcp 0 138 10.2.0.48:telnet 10.1.65.25:4468 > ESTABLISHED > udp 0 0 *:32768 *:* > udp 0 0 10.2.0.48:netbios-ns *:* > udp 0 0 *:netbios-ns *:* > udp 0 0 10.2.0.48:netbios-dgm *:* > udp 0 0 *:netbios-dgm *:* > udp 0 0 *:680 *:* > udp 0 0 *:tftp *:* > udp 0 0 *:sunrpc *:* > Active UNIX domain sockets (servers and established) > Proto RefCnt Flags Type State I-Node Path > unix 2 [ ACC ] STREAM LISTENING 1405 /dev/gpmctl > unix 10 [ ] DGRAM 776 /dev/log > unix 2 [ ] DGRAM 9828 > unix 2 [ ] DGRAM 1556 > unix 2 [ ] DGRAM 1417 > unix 2 [ ] DGRAM 1386 > unix 2 [ ] DGRAM 1032 > unix 2 [ ] DGRAM 973 > unix 2 [ ] DGRAM 821 > unix 2 [ ] DGRAM 785 > unix 2 [ ] STREAM CONNECTED 525 > > Please help as it is urgent. > > Regards: > > Nitin Saxena > 91-9899995709 > > ---------- Forwarded message ---------- > From: Nitin Saxena <nitinmca05@gmail.com> > Date: Aug 18, 2007 8:42 AM > Subject: Re: [BUGS] error while starting database > To: Douglas Toltzman <doug@oakstreetsoftware.com>, pgsql- > bugs@postgresql.org > > Hi > > All the command such as gives following output; > > 1: :ls -a/tmp: No such file or directory > > 2 : "rm -f/tmp/.s.PGSQL.5432" > bash: rm -f/tmp/.s.PGSQL.5432: No such file or directory > > 3:"ps -ax|grep postgres" > bash: ps -ax|grep postgres: command not found > > > Does PID in postmaster.pid file is automatically created when we > start the database. > > When i am giving command pg_ctl status at root, It is giving error > message as > > pg_ctl: No database directory or environment variable $PGDATA is > specified > > > and > > When i am giving command pg_ctl status at bash it is giving > postmaster is running > > [root@imap /root]# su - postgres > bash-2.04$ pg_ctl status > pg_ctl: postmaster is running (pid: 776) > options are: > /usr/bin/postmaster > -p 5432 > -D /var/lib/pgsql/data > -B 64 > -b /usr/bin/postgres > -i > -N 32 > > When i am giving command at root directory: > > [root@imap /root]# pg_ctl stop > pg_ctl: No database directory or environment variable $PGDATA is > specified > > [root@imap /root]# su - postgres > bash-2.04$ pg_ctl stop > /usr/bin/pg_ctl: kill: (776) - No such pid > postmaster successfully shut down. > > when i am giving command > bash-2.04$ pg_ctl start > pg_ctl: It seems another postmaster is running. Try to start > postmaster anyway. > FATAL: StreamServerPort: bind() failed: No such file or directory > Is another postmaster already running on that port? > If not, remove socket node (/tmp/.s.PGSQL.5432) and retry. > pg_ctl: Cannot start postmaster. Is another postmaster is running? > bash-2.04$ /usr/bin/postmaster: cannot create UNIX stream port > > > when i am giving pg_ctl restart > > bash-2.04$ pg_ctl restart > /usr/bin/pg_ctl: kill: (776) - No such pid > Waiting for postmaster shutting > down...............................................................pg_ > ctl: postmaster does not shut down > > Please tell how to start services in postgres > > when i m giving command > > [root@imap /root]# service postgresql restart > Stopping postgresql service: [FAILED] > Checking postgresql installation: [ OK ] > Starting postgresql service: [FAILED] > > > Please help ASAP, as i have to up the application as soon as possible > > > Thanks & Regards: > > Nitin Saxena > > > > > On 8/17/07, Douglas Toltzman <doug@oakstreetsoftware.com > wrote: > PostgreSQL version 7.0 is really, really out of date, but as far as > I know, it should still work. > > I generally use "ps -ax | grep postges" to see if there is a > postgres process running. Also, I use "netstat -a" to see open > sockets and listening servers. > > Have you removed the socket file in /tmp and tried to start the > server? You may also want to check the server log to see if there > is any indication of why it crashed. Once you clean up the residue > from the server that abended, you'll be able to start it again, > unless there are serious problems with the database. I've only > seen one case where I couldn't get the server restarted, though, > and that was after a hard drive failure caused corruption in > several files. Even then, I was able to recover everything. > > BTW: the socket file ("/tmp/.s.PGSQL.5432") will be a hidden file. > You'll need to "ls -a /tmp" to see it. You can just "rm -f / > tmp/.s.PGSQL.5432" as root and that should clean it up for you. > > p.s. This is not a bug, and even if it was, I'm sure version 7.0 is > no longer supported. You may want to use a different list if you > require additional assistance. > > On Aug 17, 2007, at 10:31 AM, Nitin Saxena wrote: > >> >> >> I am using postgres 7.0 on linux platform. >> My java application was running fine ,but i got this message >> >> Connection refused. Check that the hostname and port is correct, >> and that the postmaster is r >> unning with the -i flag, which enables TCP/IP networking. >> at org.postgresql.Connection.openConnection(Connection.java:123) >> at org.postgresql.Driver.connect(Driver.java:116) >> at java.sql.DriverManager.getConnection(DriverManager.java:517) >> at java.sql.DriverManager.getConnection (DriverManager.java:177) >> at SendGrpSmpp.readSMPPtable(SendGrpSmpp.java:219) >> at SendGrpSmpp.run(SendGrpSmpp.java:96) >> >> >> When i am connecting as su via su - postgres >> at bash: when i give psql Database Name >> >> It is giving error: >> >> psql: connectDBStart() -- connect() failed: No such file or directory >> Is the postmaster running at 'localhost' >> and accepting connections on Unix socket '5432'? >> >> when i am using pg_ctl status command: >> >> it gives output: pg_ctl: postmaster is running (pid: 776) >> options are: >> /usr/bin/postmaster >> -p 5432 >> -D /var/lib/pgsql/data >> -B 64 >> -b /usr/bin/postgres >> -i >> -N 32 >> >> >> when i am using pg_ctl stop it gives >> >> /usr/bin/pg_ctl: kill: (776) - No such pid >> postmaster successfully shut down. >> >> >> when i am using pg_ctl restart it gives >> >> >> bash-2.04$ pg_ctl restart >> /usr/bin/pg_ctl: kill: (776) - No such pid >> Waiting for postmaster shutting >> down...............................................................pg >> _ctl: postmaster does not shut down >> >> >> when i am giving pg_ctl start: >> >> pg_ctl: It seems another postmaster is running. Try to start >> postmaster anyway. >> FATAL: StreamServerPort: bind() failed: No such file or directory >> Is another postmaster already running on that port? >> If not, remove socket node (/tmp/.s.PGSQL.5432) and retry. >> pg_ctl: Cannot start postmaster. Is another postmaster is running? >> bash-2.04$ /usr/bin/postmaster: cannot create UNIX stream port. >> >> >> Expecting your kind help on urgent. >> >> >> Regards-- >> NItin Saxena > > Douglas Toltzman > doug@oakstreetsoftware.com > (910) 526-5938 > > > > > > > -- > NItin Saxena > > -- > NItin Saxena Douglas Toltzman doug@oakstreetsoftware.com (910) 526-5938
pgsql-bugs by date: