Andreas Tille wrote:
Package: pgadmin3
Version: 1.4.1-1
Severity: normal
Hi,
Hi Andreas!
I tried to follow some adwises written for pgAdmin3 running on a Win machine
as user postgres. This has some drawbacks because user postgres under Debian
has no writable home directory. I switched to postgres using
su -c "su -s /bin/sh postgres"
At first I had to do
psql template1 -c "ALTER ROLE WITH ENCRYPTED PASSWORD 'password' ;"
to enable user postgres logging into a server using pgAdmin3. It is
boring in general that pgAdmin3 does not seem to support ident authentication.
At least I had not found out how to log into localhost as a user with
no password which is the default in Debian. (Should I report this as a
separate bug?)
So, since version 1.4.0 it's now possible to use the local unix socket
to connect to the database, you just need to enter the path to the
PostgreSQL socket instead of an IP adress. Under Debian, just enter
/var/run/postgresql in the adress field of pgAdmin III connection window.
Then I tried to Edit pg_hba.conf (regarding to the advise mentioned above)
and tried to load the file. This crashed pgAdmin3 and on the console
I've got the following output:
(pgadmin3:18905): libgnomevfs-WARNING **: Unable to create ~/.gnome2 directory:
Permission denied
(pgadmin3:18905): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table
!= NULL' failed
(pgadmin3:18905): libgnomevfs-WARNING **: Internal error: the configuration
system was not initialized. Did you call _gnome_vfs_configuration_init?
(pgadmin3:18905): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table
!= NULL' failed
(pgadmin3:18905): libgnomevfs-WARNING **: Internal error: the configuration
system was not initialized. Did you call _gnome_vfs_configuration_init?
** (pgadmin3:18905): CRITICAL **: ORBit_POA_new_from: assertion `parent !=
CORBA_OBJECT_NIL' failed
** (pgadmin3:18905): CRITICAL **: ORBit_ObjectAdaptor_set_thread_hintv:
assertion `adaptor != NULL' failed
(pgadmin3:18905): Bonobo-WARNING **: Could not create/get poa
'BonoboPOAHintPerObject'
libgnomevfs-ERROR **: Can't allocate gnome-vfs client POA
aborting...
This sounds reasonable because user postgres is not able to write into its $HOME
directory by default. I did not wanted to change this and tried to trick
pgAdmin3
by just setting
HOME=/tmp pgadmin3
Unfortunately even this did not really help. I don't now really whether
pgAdmin3
is intended to be run as user postgres, but this is nearly the only chance to
edit pg_hba.conf (if you do not want to do it as root).
I must check this on a Debian/sid environment, I only have sarge here. I
managed to get the pg_hba.conf and rest of the files edited in pgadmin3
by launching pgadmin3 in sudo:
sudo -H -u postgres pgadmin3
Can you confirm you are able to connect to a local database as explained
previously until I come back to you after some tests under sid.
Regards,
Raphaël
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
