PG 8.4 won't start on Windows Server 2008 64-bit
I installed PostgreSQL 8.4 using the one-click installer. However, the
postgres-8.4 windows service will not start. I have checked the Windows
Event Log but there are no entries except one saying that the service
start timed out. I checked the pg_log directory and all that is logged is
2010-08-03 10:42:26 EDT DEBUG: 00000: logger shutting down
2010-08-03 10:42:26 EDT LOCATION: SysLoggerMain,
.\src\backend\postmaster\syslogger.c:446
2010-08-03 10:42:26 EDT DEBUG: 00000: shmem_exit(0): 0 callbacks to make
2010-08-03 10:42:26 EDT LOCATION: shmem_exit,
.\src\backend\storage\ipc\ipc.c:211
2010-08-03 10:42:26 EDT DEBUG: 00000: proc_exit(0): 0 callbacks to make
2010-08-03 10:42:26 EDT LOCATION: proc_exit_prepare,
.\src\backend\storage\ipc\ipc.c:183
2010-08-03 10:42:26 EDT DEBUG: 00000: exit(0)
2010-08-03 10:42:26 EDT LOCATION: proc_exit,
.\src\backend\storage\ipc\ipc.c:135
Any ideas how to get this to work?
Thanks in advance, David
--
David R Robison
Open Roads Consulting, Inc.
103 Watson Road, Chesapeake, VA 23320
phone: (757) 546-3401
e-mail: drrobison@openroadsconsulting.com
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com
book: http://www.xulonpress.com/bookstore/bookdetail.php?PB_ISBN=9781597816526
I ran postgres manually and got some additional information. The full
log is
2010-08-03 15:34:01 GMT DEBUG: 00000: postgres: PostmasterMain: initial
environ dump:
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:736
2010-08-03 15:34:01 GMT DEBUG: 00000:
-----------------------------------------
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:738
2010-08-03 15:34:01 GMT DEBUG: 00000: ALLUSERSPROFILE=C:\ProgramData
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
APPDATA=C:\Users\postgres\AppData\Roaming
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: CLIENTNAME=ORC-LPT-053
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: CommonProgramFiles=c:\Program
Files (x86)\Common Files
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
CommonProgramFiles(x86)=c:\Program Files (x86)\Common Files
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: CommonProgramW6432=c:\Program
Files\Common Files
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: COMPUTERNAME=TRAVELTIMEDEV
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
ComSpec=C:\Windows\system32\cmd.exe
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: FP_NO_HOST_CHECK=NO
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: HOMEDRIVE=C:
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: HOMEPATH=\Users\postgres
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
LOCALAPPDATA=C:\Users\postgres\AppData\Local
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LOGONSERVER=\\TRAVELTIMEDEV
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: OS=Windows_NT
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_ARCHITECTURE=x86
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_ARCHITEW6432=AMD64
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_IDENTIFIER=Intel64
Family 6 Model 26 Stepping 5, GenuineIntel
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_LEVEL=6
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_REVISION=1a05
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: ProgramData=C:\ProgramData
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: ProgramFiles=c:\Program Files
(x86)
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: ProgramFiles(x86)=c:\Program
Files (x86)
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: ProgramW6432=c:\Program Files
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROMPT=$P$G
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PUBLIC=C:\Users\Public
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: SESSIONNAME=RDP-Tcp#0
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: SystemDrive=C:
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: SystemRoot=C:\Windows
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
TEMP=C:\Users\postgres\AppData\Local\Temp\2
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
TMP=C:\Users\postgres\AppData\Local\Temp\2
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: USERDOMAIN=TRAVELTIMEDEV
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: USERNAME=postgres
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: USERPROFILE=C:\Users\postgres
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: windir=C:\Windows
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
PGLOCALEDIR=C:/PostgreSQL/8.4/share/locale
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
PGSYSCONFDIR=C:/PostgreSQL/8.4/etc
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_COLLATE=English_United
States.1252
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_CTYPE=English_United
States.1252
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_MONETARY=C
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_NUMERIC=C
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_TIME=C
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_MESSAGES=C
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
-----------------------------------------
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
2010-08-03 11:34:02 EDT DEBUG: 00000: shmem_exit(0): 0 callbacks to make
2010-08-03 11:34:02 EDT LOCATION: shmem_exit,
.\src\backend\storage\ipc\ipc.c:211
2010-08-03 11:34:02 EDT DEBUG: 00000: proc_exit(0): 0 callbacks to make
2010-08-03 11:34:02 EDT LOCATION: proc_exit_prepare,
.\src\backend\storage\ipc\ipc.c:183
2010-08-03 11:34:02 EDT DEBUG: 00000: exit(0)
2010-08-03 11:34:02 EDT LOCATION: proc_exit,
.\src\backend\storage\ipc\ipc.c:135
Hope this helps.
David
On 8/3/2010 11:05 AM, David R Robison wrote:
I installed PostgreSQL 8.4 using the one-click installer. However,
the postgres-8.4 windows service will not start. I have checked the
Windows Event Log but there are no entries except one saying that the
service start timed out. I checked the pg_log directory and all that
is logged is2010-08-03 10:42:26 EDT DEBUG: 00000: logger shutting down
2010-08-03 10:42:26 EDT LOCATION: SysLoggerMain,
.\src\backend\postmaster\syslogger.c:446
2010-08-03 10:42:26 EDT DEBUG: 00000: shmem_exit(0): 0 callbacks to make
2010-08-03 10:42:26 EDT LOCATION: shmem_exit,
.\src\backend\storage\ipc\ipc.c:211
2010-08-03 10:42:26 EDT DEBUG: 00000: proc_exit(0): 0 callbacks to make
2010-08-03 10:42:26 EDT LOCATION: proc_exit_prepare,
.\src\backend\storage\ipc\ipc.c:183
2010-08-03 10:42:26 EDT DEBUG: 00000: exit(0)
2010-08-03 10:42:26 EDT LOCATION: proc_exit,
.\src\backend\storage\ipc\ipc.c:135Any ideas how to get this to work?
Thanks in advance, David
--
David R Robison
Open Roads Consulting, Inc.
103 Watson Road, Chesapeake, VA 23320
phone: (757) 546-3401
e-mail: drrobison@openroadsconsulting.com
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.
I uninstalled 8.4 and installed 8.3 with the same results. Any
thoughts? David
On 8/3/2010 11:37 AM, David R Robison wrote:
I ran postgres manually and got some additional information. The full
log is2010-08-03 15:34:01 GMT DEBUG: 00000: postgres: PostmasterMain:
initial environ dump:
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:736
2010-08-03 15:34:01 GMT DEBUG: 00000:
-----------------------------------------
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:738
2010-08-03 15:34:01 GMT DEBUG: 00000: ALLUSERSPROFILE=C:\ProgramData
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
APPDATA=C:\Users\postgres\AppData\Roaming
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: CLIENTNAME=ORC-LPT-053
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
CommonProgramFiles=c:\Program Files (x86)\Common Files
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
CommonProgramFiles(x86)=c:\Program Files (x86)\Common Files
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
CommonProgramW6432=c:\Program Files\Common Files
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: COMPUTERNAME=TRAVELTIMEDEV
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
ComSpec=C:\Windows\system32\cmd.exe
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: FP_NO_HOST_CHECK=NO
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: HOMEDRIVE=C:
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: HOMEPATH=\Users\postgres
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
LOCALAPPDATA=C:\Users\postgres\AppData\Local
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LOGONSERVER=\\TRAVELTIMEDEV
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: OS=Windows_NT
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_ARCHITECTURE=x86
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_ARCHITEW6432=AMD64
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 26 Stepping 5, GenuineIntel
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_LEVEL=6
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROCESSOR_REVISION=1a05
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: ProgramData=C:\ProgramData
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: ProgramFiles=c:\Program
Files (x86)
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
ProgramFiles(x86)=c:\Program Files (x86)
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: ProgramW6432=c:\Program Files
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PROMPT=$P$G
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: PUBLIC=C:\Users\Public
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: SESSIONNAME=RDP-Tcp#0
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: SystemDrive=C:
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: SystemRoot=C:\Windows
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
TEMP=C:\Users\postgres\AppData\Local\Temp\2
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
TMP=C:\Users\postgres\AppData\Local\Temp\2
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: USERDOMAIN=TRAVELTIMEDEV
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: USERNAME=postgres
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: USERPROFILE=C:\Users\postgres
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: windir=C:\Windows
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
PGLOCALEDIR=C:/PostgreSQL/8.4/share/locale
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
PGSYSCONFDIR=C:/PostgreSQL/8.4/etc
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_COLLATE=English_United
States.1252
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_CTYPE=English_United
States.1252
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_MONETARY=C
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_NUMERIC=C
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_TIME=C
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000: LC_MESSAGES=C
2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
.\src\backend\postmaster\postmaster.c:741
2010-08-03 15:34:01 GMT DEBUG: 00000:
-----------------------------------------
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
2010-08-03 11:34:02 EDT DEBUG: 00000: shmem_exit(0): 0 callbacks to make
2010-08-03 11:34:02 EDT LOCATION: shmem_exit,
.\src\backend\storage\ipc\ipc.c:211
2010-08-03 11:34:02 EDT DEBUG: 00000: proc_exit(0): 0 callbacks to make
2010-08-03 11:34:02 EDT LOCATION: proc_exit_prepare,
.\src\backend\storage\ipc\ipc.c:183
2010-08-03 11:34:02 EDT DEBUG: 00000: exit(0)
2010-08-03 11:34:02 EDT LOCATION: proc_exit,
.\src\backend\storage\ipc\ipc.c:135Hope this helps.
DavidOn 8/3/2010 11:05 AM, David R Robison wrote:
I installed PostgreSQL 8.4 using the one-click installer. However,
the postgres-8.4 windows service will not start. I have checked the
Windows Event Log but there are no entries except one saying that the
service start timed out. I checked the pg_log directory and all that
is logged is2010-08-03 10:42:26 EDT DEBUG: 00000: logger shutting down
2010-08-03 10:42:26 EDT LOCATION: SysLoggerMain,
.\src\backend\postmaster\syslogger.c:446
2010-08-03 10:42:26 EDT DEBUG: 00000: shmem_exit(0): 0 callbacks to
make
2010-08-03 10:42:26 EDT LOCATION: shmem_exit,
.\src\backend\storage\ipc\ipc.c:211
2010-08-03 10:42:26 EDT DEBUG: 00000: proc_exit(0): 0 callbacks to make
2010-08-03 10:42:26 EDT LOCATION: proc_exit_prepare,
.\src\backend\storage\ipc\ipc.c:183
2010-08-03 10:42:26 EDT DEBUG: 00000: exit(0)
2010-08-03 10:42:26 EDT LOCATION: proc_exit,
.\src\backend\storage\ipc\ipc.c:135Any ideas how to get this to work?
Thanks in advance, David
--
David R Robison
Open Roads Consulting, Inc.
103 Watson Road, Chesapeake, VA 23320
phone: (757) 546-3401
e-mail: drrobison@openroadsconsulting.com
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.
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.
What's your log level set to in postgresql.conf ? If "log_min_messages"
isn't set to "debug5", set it to debug5 and try again.
log_min_messages = debug5
It'd also be helpful to set log_line_prefix:
log_line_prefix = '%t %p '
... then try to start the service again.
If you're game, you can potentially run PostgreSQL from Visual Studio
after configuring your symbol path and installing the source code, so
you can set breakpoints and step through startup. This will help you
isolate where things go wrong, but will require some knowledge of C
programming to be practical given the difficulty of doing any kind of
remote support. If you're interested in giving this a try, see:
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
... which covers setup of the symbol path and Visual Studio. I haven't
written anything for debugging PostgreSQL startup problems there, but it
should be pretty simple to get Visual Studio to fire up a postgresql
backend in single-user mode:
http://www.postgresql.org/docs/current/static/app-postgres.html
postgres.exe --single -D "\path\to\data\dir" ...other args...
... though on Windows the need to run postgres.exe as the "postgres"
user will complicate things. I'm not too sure if Visual Studio will
debug a process invoked via runas.exe. I don't have a Windows machine
with Visual Studio to hand so I can't test this right now, but you might
want to have a play and see if you have any luck.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
Craig Ringer <craig@postnewspapers.com.au> 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.
regards, tom lane
On 04/08/10 13:22, Tom Lane wrote:
Craig Ringer <craig@postnewspapers.com.au> 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:446This 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.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
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@postnewspapers.com.au> 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:446This 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@openroadsconsulting.com
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.