To confirm, I'm not getting the
"This
application has requested the Runtime to terminate it in an unusual way"
error even when I run postgres manually (not as a service). We are
running as a VMWare VM with Server 2008 Enterprise Edition. I am going
to try a fresh VM with 2008 Standard version. Maybe something is broken
in my previous OS setup. Will let you know what I find.
David
On 8/4/2010 1:33 AM, Craig Ringer wrote:
On 04/08/10 13:22, Tom Lane wrote:
Craig Ringer<craig@xxxxxxxxxxxxxxxxxxxxx> writes:
On 03/08/10 23:37, David R Robison wrote:
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:743
2010-08-03 15:34:01 GMT DEBUG: 00000: TZ "US/Eastern" matches Windows
timezone "Eastern Daylight Time"
2010-08-03 15:34:01 GMT LOCATION: identify_system_timezone,
.\src\timezone\pgtz.c:1088
2010-08-03 11:34:01 EDT DEBUG: 00000: invoking
IpcMemoryCreate(size=37044224)
2010-08-03 11:34:01 EDT LOCATION: CreateSharedMemoryAndSemaphores,
.\src\backend\storage\ipc\ipci.c:130
2010-08-03 11:34:01 EDT DEBUG: 00000: max_safe_fds = 987, usable_fds =
1000, already_open = 3
2010-08-03 11:34:01 EDT LOCATION: set_max_safe_fds,
.\src\backend\storage\file\fd.c:479
2010-08-03 11:34:02 EDT DEBUG: 00000: logger shutting down
2010-08-03 11:34:02 EDT LOCATION: SysLoggerMain,
.\src\backend\postmaster\syslogger.c:446
This is pretty odd. It seems to init shared memory OK, set up the fd
limits, then exit.
Actually, the logger is launched after those two steps, so the fact that
we see anything at all from the logger is interesting. What it looks
like to me is that the postmaster crashed at some point after launching
syslogger. There is (not supposed to be) any exit path that wouldn't
have logged a complaint message, ergo it was a crash not intentional
exit. But just where it crashed is hard to tell from this.
On Windows, there should've been an error from the runtime, like "This
application has requested the Runtime to terminate it in an unusual way" ...
I'm uncertain if such an error would get logged to the postgresql logs
if the *postmaster* crashes, though. I've seen such crashes reported in
Pg logs before, but they may have been from crashing backends rather
than the postmaster its self.
One would expect to see something in the pg logs or the service manager
/ event log history though...
If the postmaster is crashing in startup, a different approach will be
required to debug it. This article may be helpful in explaining how to
set things up if the OP wants to try their hand at hooking up a debugger.
http://www.debuginfo.com/articles/debugstartup.html
The discussion of using Visual Studio's JIT debugger probably won't help
though, as Visual Studio Express (the free version) doesn't, AFAIK,
include the JIT debugger. You'd have to use windbg from Debugging Tools
for Windows (ugh). And anyway, the postgres account isn't privelged
enough to launch the JIT debugger.
--
David R Robison
Open Roads Consulting, Inc.
103 Watson Road, Chesapeake, VA 23320
phone: (757) 546-3401
e-mail: drrobison@xxxxxxxxxxxxxxxxxxxxxxx
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com
book: http://www.xulonpress.com/bookstore/bookdetail.php?PB_ISBN=9781597816526
This e-mail communication (including any attachments) may contain confidential and/or privileged material intended solely for the individual or entity to which it is addressed. If you are not the intended recipient, you should immediately stop reading this message and delete it from all computers that it resides on. Any unauthorized reading, distribution, copying or other use of this communication (or its attachments) is strictly prohibited. If you have received this communication in error, please notify us immediately.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
