Re: [cobalt-users] RaQ4 - cobalt-psql Database setup & Interaction with system ?

[Joerg Mertin <mertinj@xxxxxxx>]

Hi Duncan,

This is the best support I ever Had. Thx a lot. If Ever you pass by
Switzerland, let me know. I ow you a beer ;)

I have however another Question. Using psql, I'm not able to log in as
used admin or postgres (Users automatically added by the scripts).

However, looking the pg_shadow Entry, postgres does not have a passwdord
set, but admin does.

cobalt=# select * from pg_shadow;
 usename  | usesysid | usecreatedb | usetrace | usesuper | usecatupd |      passwd      | valuntil 
----------+----------+-------------+----------+----------+-----------+------------------+----------
 postgres |       26 | t           | t        | t        | t         |                  | 
 admin    |       27 | f           | f        | f        | f         | 12345bacdedf | 
(2 rows)

PS: I falsified the password here ;)

Does the Password generated fo admin is a special one just for testing
the availability of the postgres-sql server ?

Also, in not beeing able to create new databases cobalt seems to have
tried to protect itself. But it didn't work right (I managed to get
postgres-user access on it by fiddling around with pg_hba.conf).

Am I right in the assumption that the password in the pg_shadow has
nothing to do with the System password and used solely for swatch ? and
that an admin User is not able to connect the Database ?

Thx for any update :)

Regards

	Joerg

[...]

On Tue, Oct 31, 2000 at 10:13:13AM -0700, Duncan Laurie wrote: 
> Before resetting the database you can check a few places and make sure the
> setup is sane.  First, look in the postgresql "host access control file" 
> located at /var/lib/pgsql/data/pg_hba.conf.  At a minimum it should contain
> an uncommented line that says "local cobalt crypt".  This allows local
> programs to connect to the postgresql backend via a unix local domain socket
> in /tmp/.s.PGSQL.5432, the next step is to make sure this file exists and
> is owned by the "postgres" user.
> 
> If the above checks don't turn up anything unusual, then try resetting the
> database.  On a RaQ4 this is fairly simple:  (this will NOT work on a RaQ3)
> 
> stop the running postgresql daemon:
> 	/etc/rc.d/init.d/postgresql stop
> 
> move the existing data directory out of the way:
> 	mv /var/lib/pgsql/data /var/lib/pgsql/data.save
> 
> restart the postgresql daemon:
> 	/etc/rc.d/init.d/postgresql start
> 
> You should see some output indicating that the database system is being
> initialized, etc..  Once this completes, hopefully without any errors,
> it will automatically add the necessary cobalt database and tables from
> the /etc/cobalt/postgres.db file.  The next step is to reconstruct the
> tables from your system configuration by running:
> 	/usr/local/sbin/meta-verify -f
> 
> Which should also display some encouraging output about repairing invalid
> virtual sites and users, and hopefully marking each one "saved".  That
> should be all you need to do, but you can test to see if swatch is happier
> by running:
> 	/usr/local/sbin/swatch -d
> 
> and looking for any warnings or errors.  It will attempt to connect to
> the database first thing and will not continue if it does not succeed.
> If all is well with swatch and the Admin GUI then go ahead and delete the
> saved data directory in /var/lib/pgsql.
> 
> good luck,
> -duncan
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users

-- 
----------------------------------------------------------------------
Joerg Mertin                    PSINet Europe
Managed Service Group Manager   Rue Fritz-Courvoisier 103
Phone: +41-32-967 52 00	        2300 La Chaux-de-Fonds
E-mail: mertinj@xxxxxxx	        Switzerland
     *** Support Pages => http://support.europe.psinet.com ***