Thread: FW: Latest cygwin always crashing with Postgres
Attached. -----Original Message----- From: pgsql-cygwin-owner@postgresql.org [mailto:pgsql-cygwin-owner@postgresql.org]On Behalf Of Jason Tishler Sent: Saturday, February 08, 2003 7:49 PM To: Seth Rubin Cc: pgsql-cygwin@postgresql.org Subject: Re: [CYGWIN] Latest cygwin always crashing with Postgres Seth, Thanks for posting! On Sat, Feb 08, 2003 at 11:16:36AM -0500, Seth Rubin wrote: > Installed the cygwin1.dll from Feb 7. Still having same problem. Please post postgres.exe.stackdump. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
Attachment
Seth, On Sat, Feb 08, 2003 at 11:10:02PM -0500, Seth Rubin wrote: > Attached. Well, it is crashing (for you) in postgres.exe and not cygwin1.dll. I will try with 1.3.19-1 and 1.3.20-1 and report back tomorrow. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Seth, On Sun, Feb 09, 2003 at 08:10:27PM -0500, Jason Tishler wrote: > On Sat, Feb 08, 2003 at 11:10:02PM -0500, Seth Rubin wrote: > > Attached. > > Well, it is crashing (for you) in postgres.exe and not cygwin1.dll. > I will try with 1.3.19-1 and 1.3.20-1 and report back tomorrow. I found some unexpected time tonight. Sorry, but I cannot reproduce your problem on Windows 2000. Under Cygwin 1.3.19-1 and 1.3.20-1, PostgreSQL 7.3.1-1 successfully ran the entire regression test (i.e., make installcheck) without any stackdumps. My WAG is something specific to your setup (e.g., XP, Cygwin configuration, etc.) is tickling a bug. On Fri, Feb 07, 2003 at 07:14:52PM -0500, Seth Rubin wrote: > I'm even open to trying to debug it, if you can give me some idea how > to do that in the winxp world. Well, debugging under Cygwin (on any Windows OS) is pretty much the same as anywhere else the GNU tools run. If you want to roll up your sleeves and debug, then: 1. download the PostgreSQL 7.3.1-1 source from any Cygwin mirror 2. configure --enable-debug --enable-multibyte --prefix=/usr --sysconfdir=/etc 3. make 4. cp postgresql-7.3.1-1/src/backend/postgres.exe /usr/bin 5. gdb -nw postmaster 6. run -D /usr/share/postgresql/data (in gdb) 7. psql template1 (in another window) 8. investigate SEGV (in gdb) Good Luck, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
On step 6, something unusual happened. Instead of postmaster starting, I
got:
Starting program: /usr/bin/postmaster -D pgdata
LOG: database system was shut down at 2003-02-09 23:17:47 EST
LOG: checkpoint record is at 0/83B1E8
LOG: redo record is at 0/83B1E8; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 480; next oid: 16976
LOG: database system is ready
FATAL: Database "Owner" does not exist in the system catalog.
LOG: shutting down
LOG: database system is shut down
Here's the text from my initdb previously:
-----------------------------------------------
$ initdb pgdata
The files belonging to this database system will be owned by user "Owner".
This user must also own the server process.
The database cluster will be initialized with locale C.
creating directory pgdata... ok
creating directory pgdata/base... ok
creating directory pgdata/global... ok
creating directory pgdata/pg_xlog... ok
creating directory pgdata/pg_clog... ok
creating template1 database in pgdata/base/1... ok
creating configuration files... 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
vacuuming database template1... ok
copying template1 to template0... ok
Success. You can now start the database server using:
/usr/bin/postmaster -D pgdata
or
/usr/bin/pg_ctl -D pgdata -l logfile start
-----------------------------------------------
Could all this be somehow related to XP account/computer naming? E.g. in
the bash shell, my username is coming out as "Owner@Thought1" Maybe
something internally is reading that @ and getting all fouled up.
Thanks for all your help so far.
-- Seth
-----Original Message-----
From: Jason Tishler [mailto:jason@tishler.net]
Sent: Sunday, February 09, 2003 9:34 PM
To: Seth Rubin
Cc: Pgsql-Cygwin
Subject: Re: FW: [CYGWIN] Latest cygwin always crashing with Postgres
Seth,
On Sun, Feb 09, 2003 at 08:10:27PM -0500, Jason Tishler wrote:
> On Sat, Feb 08, 2003 at 11:10:02PM -0500, Seth Rubin wrote:
> > Attached.
>
> Well, it is crashing (for you) in postgres.exe and not cygwin1.dll.
> I will try with 1.3.19-1 and 1.3.20-1 and report back tomorrow.
I found some unexpected time tonight. Sorry, but I cannot reproduce
your problem on Windows 2000. Under Cygwin 1.3.19-1 and 1.3.20-1,
PostgreSQL 7.3.1-1 successfully ran the entire regression test (i.e.,
make installcheck) without any stackdumps.
My WAG is something specific to your setup (e.g., XP, Cygwin
configuration, etc.) is tickling a bug.
On Fri, Feb 07, 2003 at 07:14:52PM -0500, Seth Rubin wrote:
> I'm even open to trying to debug it, if you can give me some idea how
> to do that in the winxp world.
Well, debugging under Cygwin (on any Windows OS) is pretty much the same
as anywhere else the GNU tools run. If you want to roll up your sleeves
and debug, then:
1. download the PostgreSQL 7.3.1-1 source from any Cygwin mirror
2.
configure --enable-debug --enable-multibyte --prefix=/usr --sysconfdir=/etc
3. make
4. cp postgresql-7.3.1-1/src/backend/postgres.exe /usr/bin
5. gdb -nw postmaster
6. run -D /usr/share/postgresql/data (in gdb)
7. psql template1 (in another window)
8. investigate SEGV (in gdb)
Good Luck,
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Seth,
On Sun, Feb 09, 2003 at 11:47:28PM -0500, Seth Rubin wrote:
> On step 6, something unusual happened. Instead of postmaster
> starting, I got:
>
> Starting program: /usr/bin/postmaster -D pgdata
> LOG: database system was shut down at 2003-02-09 23:17:47 EST
> LOG: checkpoint record is at 0/83B1E8
> LOG: redo record is at 0/83B1E8; undo record is at 0/0; shutdown TRUE
> LOG: next transaction id: 480; next oid: 16976
> LOG: database system is ready
> FATAL: Database "Owner" does not exist in the system catalog.
^^^^^
Does the above occur when invoked from the command line?
Does your /etc/passwd have an entry for "Owner"? If so, then please
post it. If not, then try the following:
$ mkpasswd -l -u Owner >>/etc/passwd
Note:
1. If Owner is a domain account, then use mkpasswd -d
2. If Owner corresponds to a Windows user with a different name, then
use the Windows user name instead above.
> Could all this be somehow related to XP account/computer naming?
Maybe. Note that I do *not* have access to XP so I cannot debug this
myself.
> in the bash shell, my username is coming out as "Owner@Thought1"
> Maybe something internally is reading that @ and getting all fouled
> up.
The default bash prompt is user@machine. If "Thought1" is your machine
name, then the above is OK.
> Thanks for all your help so far.
No problem. Sorry, for the slow response time, but weekends are tough
for me to get near my computer. :,(
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6