Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 866529F9EED for ; Thu, 16 Nov 2006 13:41:01 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 89395-08-2 for ; Thu, 16 Nov 2006 13:40:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from web62414.mail.re1.yahoo.com (web62414.mail.re1.yahoo.com [69.147.75.91]) by postgresql.org (Postfix) with SMTP id 6FA8B9F9DAD for ; Thu, 16 Nov 2006 13:40:52 -0400 (AST) Received: (qmail 93092 invoked by uid 60001); 16 Nov 2006 17:40:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=CbxU97K0Es8S2Ps88nS8mxtAidrd01v8c7dJpBH94sBHvCHu09Q+YIjcxqr+KdPXOTdQaT8tk9ykS9UxbjE/3ExQTRoQtWhsHNxm+ZAENEFMTtI3/8hm9dGeZWG9Yt/+l/1M0jXN627r3KpDhTcObDu3vpV2Z8Xn91hK3/glXAY= ; Message-ID: <20061116174050.93090.qmail@web62414.mail.re1.yahoo.com> Received: from [71.230.250.141] by web62414.mail.re1.yahoo.com via HTTP; Thu, 16 Nov 2006 09:40:49 PST Date: Thu, 16 Nov 2006 09:40:49 -0800 (PST) From: Will Cameron Subject: Re: all postgres users do "not exist" To: pgsql-admin@postgresql.org In-Reply-To: <12936.1163658755@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-2042861896-1163698849=:93072" Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.131 tagged_above=0 required=5 tests=BAYES_00, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, HTML_30_40, HTML_MESSAGE X-Spam-Level: * X-Archive-Number: 200611/163 X-Sequence-Number: 23690 --0-2042861896-1163698849=:93072 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, I'm not sure what exactly you mean by "starting a standalone postgres session and using it to recreate your SQL users". Do you mean running initdb on a new data directory and then trying to create new users? I'm fairly certain we already tried that. Since we cannot log into the postgres user at all we can't run createuser. We can start and stop the database but cannot log in with any users. We ran the script in this fashion: psql -f etc/database_schema_12-13.sql [DSpace database name] -h localhost The script just contains sql commands to create tables and sequences within the database specified. Again, I don't know much about the template1 database but we did not touch it (that we know of) if it does contain user accounts. I'm thinking perhaps since the local data directory actually just points to another one which has the real data that psql might have been confused. /usr/local/pgsql/data lrwxrwxrwx 1 root other 22 Apr 18 2006 data -> /home/local/pgsql/data /home/local/pgsql/data drwx------ 10 postgres staff 512 Nov 15 14:10 data Thanks, Will Tom Lane wrote: Will Cameron writes: > We are using (PostgreSQL) 8.0.1 for Solaris. Apparently our > postgres users were wiped out somehow, for I cannot even log in as > superuser "postgres". Our pg_hba.conf settings are as loose as possible > ("trust"). This problem started mid session after we ran a .sql script > to upgrade a DSpace digital library database within the postgres system. Better take a closer look at what that script did. Meanwhile, you can probably get out of this by starting a standalone postgres session and using it to recreate your SQL users. regards, tom lane --------------------------------- Sponsored Link Mortgage rates as low as 4.625% - $150,000 loan for $579 a month. Intro-*Terms --0-2042861896-1163698849=:93072 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit     Hello,
    
             I'm not sure what exactly you mean by "starting a standalone
postgres session and using it to recreate your SQL users".  Do you mean running initdb on a new data directory and then trying to create new users?  I'm fairly certain we already tried that.  Since we cannot log into the postgres user at all we can't run createuser.  We can start and stop the database but cannot log in with any users.  We ran the script in this fashion:

psql -f etc/database_schema_12-13.sql [DSpace database name] -h localhost

      The script just contains sql commands to create tables and sequences within the database specified.  Again, I don't know much about the template1 database but we did not touch it (that we know of) if it does contain user accounts.  I'm thinking perhaps since the local data directory actually just points to another one which has the real data that psql might have been confused.

/usr/local/pgsql/data

lrwxrwxrwx   1 root     other         22 Apr 18  2006 data -> /home/local/pgsql/data


/home/local/pgsql/data
drwx------  10 postgres staff        512 Nov 15 14:10 data

Thanks,
Will







Tom Lane <tgl@sss.pgh.pa.us> wrote:
Will Cameron writes:
> We are using (PostgreSQL) 8.0.1 for Solaris. Apparently our
> postgres users were wiped out somehow, for I cannot even log in as
> superuser "postgres". Our pg_hba.conf settings are as loose as possible
> ("trust"). This problem started mid session after we ran a .sql script
> to upgrade a DSpace digital library database within the postgres system.

Better take a closer look at what that script did.

Meanwhile, you can probably get out of this by starting a standalone
postgres session and using it to recreate your SQL users.

regards, tom lane


Sponsored Link

Mortgage rates as low as 4.625% - $150,000 loan for $579 a month. Intro-*Terms --0-2042861896-1163698849=:93072--