Thread: FW: FW: Latest cygwin always crashing with Postgres

When I run from gdb, FATAL error occurs when "run", when I run from command
line, the same error occurs, but not until I access with psql or other...

This entry in /etc/passwd file was already there:

Owner:unused_by_nt/2000/xp:1003:513:U-YOUR-W92P4BHLZG\Owner,S-1-5-21-6707922
05-1163395192-3403473811-1003:/home/Owner:/bin/bash

-- Seth
-----Original Message-----
From: pgsql-cygwin-owner@postgresql.org
[mailto:pgsql-cygwin-owner@postgresql.org]On Behalf Of Jason Tishler
Sent: Monday, February 10, 2003 8:52 AM
To: Seth Rubin
Cc: Pgsql-Cygwin
Subject: Re: FW: [CYGWIN] Latest cygwin always crashing with Postgres


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

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Seth,

On Mon, Feb 10, 2003 at 10:03:03AM -0500, Seth Rubin wrote:
> When I run from gdb, FATAL error occurs when "run", when I run from
> command line, the same error occurs, but not until I access with psql
> or other...

Hmm...

Also, where did the SEGVs go?

> This entry in /etc/passwd file was already there:
>
> Owner:unused_by_nt/2000/xp:1003:513:U-YOUR-W92P4BHLZG\Owner,S-1-5-21-6707922
                                        ^^^^^^^^^^^^^^^
                                        ***************

> 05-1163395192-3403473811-1003:/home/Owner:/bin/bash

Looks OK, except that I expected to see "Thought1" above.

I'm sorry, but I think that you are having a problem due to XP Home or
some other misconfiguration.  You will have to debug further yourself.

I would start in src/backend/utils/init/postinit.c:

    /*
     * Find oid and path of the database we're about to open. Since
     * we're not yet up and running we have to use the hackish
     * GetRawDatabaseInfo.
     */
**> GetRawDatabaseInfo(dbname, &MyDatabaseId, datpath);

    if (!OidIsValid(MyDatabaseId))
        elog(FATAL,
             "Database \"%s\" does not exist in the system catalog.",
             dbname);

and figure out why GetRawDatabaseInfo() fails and/or returns a bogus
MyDatabaseId value.

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