Обсуждение: BUG #6522: PostgreSQL does not start
The following bug has been logged on the website: Bug reference: 6522 Logged by: Tatiana=20 Email address: tatypr18@gmail.com PostgreSQL version: 8.3.0 Operating system: Windows Server 2008 R2 Standard Description:=20=20=20=20=20=20=20=20 Hello: My postgresql does not start and giving me this error: Could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host =E2=80=9C127.0.0.1=E2=80=9D and accepting TCP/IP con= nections on port 5432? I made =E2=80=8B=E2=80=8Bseveral attempts to restart the service: One, My postgresql.conf file have '*' to listen on all available IP addresses.=20 Two, I delete the file postmaster.pid and did not work. Three, I change the way to start the service in services to a Local Systems and not work. Four, the firewall in not activated.=20 Please any suggestions on how I can solve this problem. Tatiana=20
<tatypr18@gmail.com> wrote: =20 > My postgresql does not start and giving me this error: >=20 > Could not connect to server: Connection refused (0x0000274D/10061) > Is the server running on host *127.0.0.1* and accepting TCP/IP > connections on port 5432? =20 That message looks like it is coming from some client software on an attempt to connect to a PostgreSQL server; not from the server itself. =20 > I delete the file postmaster.pid and did not work. =20 Are you quite sure the PostgreSQL service was not running? (How did you check?) The pid file should be deleted automatically when the service is stopped. Deleting it while the service is running can cause problems if you later try to start the service. =20 > I change the way to start the service in services to a Local > Systems and not work. =20 I can't do much with information that vague. =20 > Please any suggestions on how I can solve this problem. =20 You need to provide a clearer description of what your problem is before anyone can make useful suggestions. =20 http://wiki.postgresql.org/wiki/Guide_to_reporting_problems =20 So far all we know from your description is that a client wasn't able to connect to the service, and you subsequently did some things which could break the service. =20 -Kevin
[Please keep the list copied. Also, please quote selected portions of a post to which you are replying, and put your reply below, like you see here.] Tatiana Ortiz <tatypr18@gmail.com> wrote: =20 > I have the program PostgreSQL with PostGIS extension. =20 Obtained from where? Installed how? =20 > In postgre I have a database installed. =20 So you were able to connect to PostgreSQL to create the database?=20 What has changed since then? =20 > Could not connect to server: Connection refused (0x0000274D/10061) =20 "Connection refused" generally means that the attempt establish the TCP connection found the specified host, but the port on which you're trying to connect is not available to be opened. That usually means the service which offers that port is not running, or that a firewall is blocking access. =20 > Is the server running on host *127.0.0.1* and accepting TCP/IP > connections on port 5432? > > If you encounter this message, please check if the server you`re > trying to contact is actually running PostgreSQL on the given > port. =20 What did you do to check this? =20 > Test if you have network connectivity from your client to the > server host using ping or equivalent tools. =20 Do you get a response when you ping 127.0.0.1? =20 > Is your network / VPN/SSH tunnel / firewall configured > correctly? =20 What did you do to check that? =20 > If you double-checked your configuration but still get this error > message, it`s still unlikely that you encounter a fatal PostgreSQL > misbehavior. You probably have some low level network connectivity > problems (e.g. firewall configuration). Please check this > thoroughly before reporting a bug to the PostgreSQL community. =20 What did you do to check this? =20 > Doing a search online to solve the problem and be able to use my > database, I made the different processes to explain in the > previous email to make the database ENABLE. =20 Your previous email mentioned deleting the postmaster.pid file. Do you have any more detail on what you did? =20 > If you know of something I could do to gain access to the database > let me know. =20 Start Task Manager and look in the Processes tab. Are there any postgres process active? From a command line, run: =20 netstat -p TCP -a and see if anything is listening on port 5432. =20=20 -Kevin
[Please keep the list copied. I won't respond to any more emails directly to me without a copy to the list.] =20 Tatiana Ortiz <tatypr18@gmail.com> wrote: > Kevin Grittner <Kevin.Grittner@wicourts.gov wrote: =20 >>> Test if you have network connectivity from your client to the >>> server host using ping or equivalent tools. >>=20 >> Do you get a response when you ping 127.0.0.1? >=20 > I have not tried that. =20 Well, nobody here can, so how will we know if that is working? =20 >>> Is your network / VPN/SSH tunnel / firewall configured >>> correctly? >>=20 >> What did you do to check that? >=20 > It*s configured correctly; I have verified it in the control > panel. =20 What, exactly, did you verify was true about the configuration? =20 >>> If you double-checked your configuration but still get this >>> error message, it`s still unlikely that you encounter a fatal >>> PostgreSQL misbehavior. You probably have some low level network >>> connectivity problems (e.g. firewall configuration). Please >>> check this thoroughly before reporting a bug to the PostgreSQL >>> community. >>=20 >> What did you do to check this? >=20 > The Firewall configuration is correct. =20 Something isn't. If you have a firewall running, I sure wouldn't rule it out without pretty good evidence pointing to something else. Do you have an anti-virus product installed? (Note, I didn't ask whether it was enabled -- even when supposedly disabled, many AV products can cause problems like this.) =20 >> Your previous email mentioned deleting the postmaster.pid file.=20 >> Do you have any more detail on what you did? >=20 > When I deleted the postmaster.pid, and then went to the Services > to give a restart to the Postgre service, the file reappeared. =20 That's an interesting data point, although not enough to pin it down without other facts not in evidence. =20 >>> If you know of something I could do to gain access to the >>> database let me know. >>=20 >> Start Task Manager and look in the Processes tab. Are there any >> Postgres processes active? >=20 > [suggestion apparently ignored] =20 If you won't provide information, nobody can help you. =20 >> From a command line, run: >>=20 >> netstat -p TCP -a >>=20 >> and see if anything is listening on port 5432. >=20 > I tried this, and it gave me this result: >=20 > [image: nothing listening on port 5432] =20 So, either the PostgreSQL service isn't running, or it is not offering IP services on the default port. =20 Is anything appearing in any of the Windows event logs around the time you attempt to start the service? Can you find a PostgreSQL log file anywhere? Without knowing what installer was used, it would be hard to suggest where to look, but sometimes the log files are in a subdirectory named pg_log, and sometimes there is a file named "logfile" in the PostgreSQL data directory. =20 Assistance on this list is provided by volunteers. If you don't care enough about what you've got wrong in your environment to perform the requested diagnostic steps, those contributing their time are likely to lose interest and stop responding. I have 200 databases running just fine on 100 servers scattered across the state. What are you doing that isn't working? It's not my responsibility to sort that out, but I'm willing to help if you're willing to take responsibility for your end. =20 -Kevin
According to what I can see from this defect that it is not confirmed whether the Postgre server is started or not properly. You can try on confirming about the following 2 points: 1. How many postgres processes you are able to see in your task manager. This can give hint whether appropriate postgres services are started 2. try to start the postgres from command promt with command Postgres.exe -D <your data directory path> Please tell what it prints on command promt. -----Original Message----- From: pgsql-bugs-owner@postgresql.org [mailto:pgsql-bugs-owner@postgresql.org] On Behalf Of Kevin Grittner Sent: Monday, April 02, 2012 11:43 PM To: Tatiana Ortiz Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #6522: PostgreSQL does not start [Please keep the list copied. I won't respond to any more emails directly to me without a copy to the list.] Tatiana Ortiz <tatypr18@gmail.com> wrote: > Kevin Grittner <Kevin.Grittner@wicourts.gov wrote: >>> Test if you have network connectivity from your client to the >>> server host using ping or equivalent tools. >> >> Do you get a response when you ping 127.0.0.1? > > I have not tried that. Well, nobody here can, so how will we know if that is working? >>> Is your network / VPN/SSH tunnel / firewall configured >>> correctly? >> >> What did you do to check that? > > It*s configured correctly; I have verified it in the control > panel. What, exactly, did you verify was true about the configuration? >>> If you double-checked your configuration but still get this >>> error message, it`s still unlikely that you encounter a fatal >>> PostgreSQL misbehavior. You probably have some low level network >>> connectivity problems (e.g. firewall configuration). Please >>> check this thoroughly before reporting a bug to the PostgreSQL >>> community. >> >> What did you do to check this? > > The Firewall configuration is correct. Something isn't. If you have a firewall running, I sure wouldn't rule it out without pretty good evidence pointing to something else. Do you have an anti-virus product installed? (Note, I didn't ask whether it was enabled -- even when supposedly disabled, many AV products can cause problems like this.) >> Your previous email mentioned deleting the postmaster.pid file. >> Do you have any more detail on what you did? > > When I deleted the postmaster.pid, and then went to the Services > to give a restart to the Postgre service, the file reappeared. That's an interesting data point, although not enough to pin it down without other facts not in evidence. >>> If you know of something I could do to gain access to the >>> database let me know. >> >> Start Task Manager and look in the Processes tab. Are there any >> Postgres processes active? > > [suggestion apparently ignored] If you won't provide information, nobody can help you. >> From a command line, run: >> >> netstat -p TCP -a >> >> and see if anything is listening on port 5432. > > I tried this, and it gave me this result: > > [image: nothing listening on port 5432] So, either the PostgreSQL service isn't running, or it is not offering IP services on the default port. Is anything appearing in any of the Windows event logs around the time you attempt to start the service? Can you find a PostgreSQL log file anywhere? Without knowing what installer was used, it would be hard to suggest where to look, but sometimes the log files are in a subdirectory named pg_log, and sometimes there is a file named "logfile" in the PostgreSQL data directory. Assistance on this list is provided by volunteers. If you don't care enough about what you've got wrong in your environment to perform the requested diagnostic steps, those contributing their time are likely to lose interest and stop responding. I have 200 databases running just fine on 100 servers scattered across the state. What are you doing that isn't working? It's not my responsibility to sort that out, but I'm willing to help if you're willing to take responsibility for your end. -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs