Unknown Type 'ame' [urgent]

Started by Mike Rogersabout 25 years ago7 messagesgeneral
Jump to latest
#1Mike Rogers
temp6453@hotmail.com

I was having problems with AME in 7.0.3 running initdb so I figured I would
try to install 7.1beta3 and see if it is fixed. I get the following error:
"ERROR: Error: unknown type 'ame'." still with this version. Clearly
something is wrong. Does anyone have any ideas?

--
Mike

[postgres pgsql]$ /usr/pgsql/bin/initdb -D /usr/pgsql/data
This database system will be initialized with username "postgres".
This user will own all the data files and must also own the server process.

Fixing permissions on existing directory /usr/pgsql/data
Creating directory /usr/pgsql/data/base
Creating directory /usr/pgsql/data/global
Creating directory /usr/pgsql/data/pg_xlog
Creating template1 database in /usr/pgsql/data/base/1
DEBUG: starting up
DEBUG: database system was shut down at 2001-01-16 13:06:34
DEBUG: CheckPoint record at (0, 8)
DEBUG: Redo record at (0, 8); Undo record at (0, 8); Shutdown TRUE
DEBUG: NextTransactionId: 514; NextOid: 16384
DEBUG: database system is in production state
ERROR: Error: unknown type 'ame'.

Creating global relations in /usr/pgsql/data/global
DEBUG: starting up
DEBUG: database system was interrupted at 2001-01-16 13:06:34
DEBUG: CheckPoint record at (0, 8)
DEBUG: Redo record at (0, 8); Undo record at (0, 8); Shutdown TRUE
DEBUG: NextTransactionId: 514; NextOid: 16384
DEBUG: database system was not properly shut down; automatic recovery in
progress...
FATAL 2: cannot open pg_log: No such file or directory

initdb failed.
Removing temp file /tmp/initdb.29632.

---
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

#2Fred Yankowski
fred@ontosys.com
In reply to: Mike Rogers (#1)
Re: Unknown Type 'ame' [urgent]

That message could be generated by bootstrap.c. It looks like that
would happen if the bootstrap scanner/parser thought it saw a clause
like "something = ame" in some config file, which looks awfully close
to the "something = name" clause that appears many times in the
*.bki.source files. Perhaps something is wrong with the flex
scanner-generator on your system?

On Tue, Jan 16, 2001 at 06:10:00PM +0000, Mike Miller wrote:

I was having problems with AME in 7.0.3 running initdb so I figured I would
try to install 7.1beta3 and see if it is fixed. I get the following error:
"ERROR: Error: unknown type 'ame'." still with this version. Clearly
something is wrong. Does anyone have any ideas?

--
Fred Yankowski fred@OntoSys.com tel: +1.630.879.1312
Principal Consultant www.OntoSys.com fax: +1.630.879.1370
OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA

#3Fred Yankowski
fred@ontosys.com
In reply to: Fred Yankowski (#2)
Re: Unknown Type 'ame' [urgent]

I see that the genbki.sh file in backend/catalog has some sed strings
like these:

-e "s/[ ]NameData/\ name/g" \
-e "s/^NameData/\name/g" \

Those look bogus to me. I wonder if that '\n' becomes newline for
some versions of shell and/or sed?

--
Fred Yankowski fred@OntoSys.com tel: +1.630.879.1312
Principal Consultant www.OntoSys.com fax: +1.630.879.1370
OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA

#4Bruce Momjian
bruce@momjian.us
In reply to: Fred Yankowski (#3)
Re: Re: Unknown Type 'ame' [urgent]

I see that the genbki.sh file in backend/catalog has some sed strings
like these:

-e "s/[ ]NameData/\ name/g" \
-e "s/^NameData/\name/g" \

Those look bogus to me. I wonder if that '\n' becomes newline for
some versions of shell and/or sed?

What is that \n doing in there? It is certainly wrong. I am just
wondering what is should be.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
#5Bruce Momjian
bruce@momjian.us
In reply to: Fred Yankowski (#3)
Re: Re: Unknown Type 'ame' [urgent]

I see that the genbki.sh file in backend/catalog has some sed strings
like these:

-e "s/[ ]NameData/\ name/g" \
-e "s/^NameData/\name/g" \

Those look bogus to me. I wonder if that '\n' becomes newline for
some versions of shell and/or sed?

I have just removed the backslash to it is now:

-e "s/^NameData/name/g" \

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
#6Tom Lane
tgl@sss.pgh.pa.us
In reply to: Bruce Momjian (#4)
Re: Re: Unknown Type 'ame' [urgent]

Bruce Momjian <pgman@candle.pha.pa.us> writes:

-e "s/[ ]NameData/\ name/g" \
-e "s/^NameData/\name/g" \

What is that \n doing in there? It is certainly wrong. I am just
wondering what is should be.

It's been like that since 1996, according to the CVS logs. I'm
surprised we have not had more reports of trouble --- either the shell
or sed might be deciding to translate that \n to a newline, although
evidently the consensus behavior is not to.

I zapped the gratuitous backslashes before the spaces, too, just
for luck.

regards, tom lane

#7Bruce Momjian
bruce@momjian.us
In reply to: Tom Lane (#6)
Re: Re: Unknown Type 'ame' [urgent]

Bruce Momjian <pgman@candle.pha.pa.us> writes:

-e "s/[ ]NameData/\ name/g" \
-e "s/^NameData/\name/g" \

What is that \n doing in there? It is certainly wrong. I am just
wondering what is should be.

It's been like that since 1996, according to the CVS logs. I'm
surprised we have not had more reports of trouble --- either the shell
or sed might be deciding to translate that \n to a newline, although
evidently the consensus behavior is not to.

It is truly amazing that is worked since 1996 that way.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026