Quick Links

Re: BUG #4771: Postgres wont start

From:	Christine Penner <christinep(at)telus(dot)net>
To:	pgsql-bugs(at)postgresql(dot)org
Subject:	Re: BUG #4771: Postgres wont start
Date:	2009-04-24 15:08:08
Message-ID:	19740414223344.ADBA38313C0AE851@priv-edtnaa06.telusplanet.net
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-bugs

<html>
<body>
When I looked at the Windows Event Log I found this: 
%t FATAL:  bogus data in lock file
"postmaster.pid": "" 
So what do I do now? I have already re installed and that didn't
help. 
Christine 
At 02:45 AM 4/23/2009, you wrote: 
<blockquote type=cite class=cite cite="">Christine, 
when PostgreSQL does not start on Windows, the first place to look for
errors is the Microsoft Windows EventLog. That is the standard place to
report errors. 
You can dig there via Control Panel; exact click path depending on your
Windows Version (XP / Vista / W2003 / W2008 / W7); or start a commandline
and type eventvwr (works on all) 
There you go to the errors of "Application"; and track down the
information of the PostgreSQL service. 
In my experience (~ 200 different Windows Computers in ~15 Administrative
Environments)  the most common errors are: 
- "something" is taking away the
"run-as-service"-privilege of the postgres-Windows-User. Likely
culprits for "something" are GroupPolicies within
ActiveDirectory. To be more challenging, it does not happen immediately,
but after x days of normal working 
- "something" is taking away access rights to the PostgreSQL
Data Directory / the PostgreSQL Configuration files 
- Switching distributions between versions (from pginstaller to one click
installer or vice versa) 
- Difference within PostgreSQL packagings ("pg_debugger" was
default acitvated in 8.3.0-8.3.4; and is no more default activated by
default in 8.3.7; a line with "preload pg_debugger " in
postgresql.conf may lead to non starting PostgreSQL service) 
- Some (anti)viral products block the access off ports; or files, or
starting of processes by Postgresql. 
Most of these errors are best detected by checking the error log. (just
with AntiVir Products you're in the wild, most of the time. Check their
logfiles!) 
Harald 
 
 
 
On Thu, Apr 23, 2009 at 5:08 AM, Christine Penner
<<a href="mailto:christinep(at)telus(dot)net">christinep(at)telus(dot)net</a>>
wrote:
<dl>
<dd>I get no error. The only way I know its not connected is by trying to
log in to pgAdmin. It tells me the server doesn't listen. Then I told it
to start. Last time that worked. Now it won't start at all but it never
gives any error.

<dd>When I tried to open it with pg_ctl it tells me can not open PID file
(Postmaster.pid). Permission denied. That's odd because I am an
administrative user on Vista and it was working at one point.

<dd>Should Postgres not be in the Program Files directory for Vista?
<dd>In any case how to I fix it. I want to at least get the data out so I
can re load it. I have a backup but its not as recent as I would
like.

<dd>Christine

<dd>At 10:46 PM 4/21/2009, you wrote:

<dl>
<dd>-----BEGIN PGP SIGNED MESSAGE-----
<dd>Hash: SHA1

<dd>Christine Penner wrote:
<dd>> The following bug has been logged online:
<dd>>
<dd>> Bug reference:      4771
<dd>> Logged by:         
Christine Penner
<dd>> Email address:     
<a href="mailto:christinep(at)telus(dot)net">christinep(at)telus(dot)net</a>
<dd>> PostgreSQL version: 8.3.7
<dd>> Operating system:   Vista
<dd>> Description:        Postgres
wont start
<dd>> Details:
<dd>>
<dd>> I have had Postgres running and working on the computer for
about a month. A
<dd>> week ago I started and realized that the Postgres service was
not started. I
<dd>> started it and it worked fine. Today I started up and again
Postgres has not
<dd>> started. I have tried again and again to start it but it won't
start. I have
<dd>> restarted my computer 3 times, shut down programs running that
may interfere
<dd>> but still nothing.
<dd>>
<dd>> I can't find a log file that will give me more info on why it
won't start.
<dd>>

<dd>what is the Error you are getting ?

<dd>go to bin folder of postgres and try to start using pg_ctl

<dd>like :- pg_ctl -D  c:/postgres/8.3/...path upto data
folder  START

<dd>
                                            
--
<dd>
                                      
regards,tushar
<dd>
                                      
<a href="http://webeatoracle.com">http://webeatoracle.com</a>
<dd>-----BEGIN PGP SIGNATURE-----
<dd>Version: GnuPG v1.2.2 (GNU/Linux)

<dd>iD8DBQFJ7q9LfQNodY2PIRoRArjqAKCIfLk/392qYIn+cQY7iy23IPXNxQCgtetG
<dd>8Q7KHYTH/gcd3+WSQnCd/Zw=
<dd>=7r7H
<dd>-----END PGP SIGNATURE-----

<dd>__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4029 (20090422) __________

<dd>The message was checked by ESET NOD32 Antivirus.

</dl>
<dd>--
<dd>Sent via pgsql-bugs mailing list
(<a href="mailto:pgsql-bugs(at)postgresql(dot)org">pgsql-bugs(at)postgresql(dot)org</a>
)
<dd>To make changes to your subscription:
<dd><a href="http://www.postgresql.org/mailpref/pgsql-bugs">
http://www.postgresql.org/mailpref/pgsql-bugs</a> 
</dl> 
 
-- 
GHUM Harald Massa 
persuadere et programmare 
Harald Armin Massa 
Spielberger Straße 49 
70435 Stuttgart 
0173/9409607 
no fx, no carrier pigeon 
- 
LASIK good, steroids bad?</blockquote></body>
</html>

Attachment	Content-Type	Size
unknown_filename	text/html	6.1 KB

Browse pgsql-bugs by date

	From	Date	Subject
Next Message	Ted Holzman	2009-04-24 16:07:26	BUG #4780: Aggregate functions are unaware of LIMIT clauses in SELECTs
Previous Message	Thomas S. Chin	2009-04-24 14:34:58	Re: BUG #4779: LIMIT/OFFSET behavior change (possibly related to Top-n)