This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Postgres not working anymore


Igor Pechtchanski wrote:
On Wed, 13 Jul 2005, Jon A. Lambert wrote:

I dunno. I still cannot execute initdb script with latest coreutils.
Or is this some sort of bash/ash problem?
[snip]
/usr/bin/initdb: line 564: 484 Bad system call "$PGPATH"/postgres -boot -x0 $TEST_OPT template1 </dev/null
>/dev/null 2>&1
                                  ^^^^^^^^^^^^^^^
cygserver is either not running or not accessible.  See
/usr/share/doc/Cygwin/cygserver.README

Yes I had failed to export CYGWIN=server variable


Still I am having problems.

I installed as a service with -e "CYGWIN=server" and was getting signal 11 raised upon starting it.

So I decided to start it locally. I deleted the tempfiles it creates and recreated the database:

jlambert@agamemnon /var/postgresql
$ initdb -D /var/postgresql/data
The files belonging to this database system will be owned by user "jlambert".
This user must also own the server process.


The database cluster will be initialized with locale C.

creating directory /var/postgresql/data... ok
creating directory /var/postgresql/data/base... ok
creating directory /var/postgresql/data/global... ok
creating directory /var/postgresql/data/pg_xlog... ok
creating directory /var/postgresql/data/pg_clog... ok
selecting default max_connections... 40
selecting default shared_buffers... 1000
creating configuration files... ok
creating template1 database in /var/postgresql/data/base/1... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ok
setting privileges on built-in objects... ok
creating information schema... ok
vacuuming database template1... ok
copying template1 to template0... ok

Success. You can now start the database server using:

   /usr/bin/postmaster -D /var/postgresql/data
or
   /usr/bin/pg_ctl -D /var/postgresql/data -l logfile start


So far so good...


jlambert@agamemnon /var/postgresql
$ env | grep CYGWIN
CYGWIN=server

Environment set correctly. I also exported it to make sure..


jlambert@agamemnon /var/postgresql $ /usr/bin/postmaster -D /var/postgresql/data Segmentation fault (core dumped)

Ouch.


jlambert@agamemnon /var/postgresql
$ cat postgres.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=610028AA
eax=00000000 ebx=61258EF8 ecx=0000002A edx=000001A8 esi=000001A8 edi=61259000
ebp=0022E948 esp=0022E910 program=C:\cygwin\bin\postgres.exe, pid 360, thread ma
in
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
0022E948 610028AA (00000000, 61258CF8, 0022E978, 6101F5E8)
0022E978 6101171C (61156498, 61258CF8, 0022E9C8, 61010F4E)
0022E9A8 61011CED (61154A78, 61156458, 611D8238, 61154A78)
0022E9E8 61011E38 (61154A78, 00000000, 000007B7, 00002000)
0022EA28 6108E3FD (00000000, 00002000, 0022EA68, 1001678C)
0022EA58 610844FF (0022EA78, 0022EA7C, 0022EA88, 0053F2C3)
0022EA88 0055945A (00001538, 00000000, 00001538, 10016660)
0022EEE8 0053D258 (00000003, 10010208, 0022EF18, 61087959)
0022EF18 00506FFD (00000003, 611576A0, 10010090, 7C919AF0)
0022EFD8 61004DD2 (0022EFF0, 00000000, 00000000, 00000000)
0022FF88 6100594F (00000000, 00000000, 00000000, 00000000)
End of stack trace


Nasty.
BTW I have done a clean reinstall of Postgres as well.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]