phppgadmin-users — General phpPgAdmin topics for all user

RE: [ppa-users] step-by-step detailed and comprehensive quickstart?

[<kke...@ne...>]

Hello,

About a year back I wrote a step by step method of getting PostgreSQL running on Redhat 7.0.  
You can read it at http://www.phpbuilder.com/columns/kevin20010314.php3

I don't know how much different Debian is and I know there has been some changes in the files for configuration.  If you have any questions I will try to help.

Kevin
Sebastien Blondeel <blo...@cl...> wrote:

>Hello guys,
>
>Sometimes I feel like I am being thick. Like today. But eventually I
>think I can pretty well blame this on lack of good documentation in
>both phppgadmin and PostgreSQL (if not, give me the meta-information on
>where to find the information I need). Mailing-lists and annotations on
>the official PostgreSQL documentation confirmed me I was not the only
>one to feel like this.
>
>Situation: I am on a GNU/Linux box, running Debian, with no much
>experience of SQL, PostgreSQL, phppgadmin. I would like to play with
>phppgadmin locally. So simple a wish I thought it would take a few
>minutes.  Nope. Even though "apt-get install phppgadmin" worked, no
>post-configuration script asked me anything.
>
>I can either become crazy on this and spend hours not going anywhere, or
>have someone experimented spend 5 minutes on this with me. I did my
>homework, and really tried to read the docs. I can volunteer the writing
>of the step-by-step guide that will be the outcome of this. At every
>step I am planning to collect possible error messages and give the
>fixes.
>
>Local setup:
>postgres is the PostgreSQL super-user
>
>Example wish:
>starting from scratch, what commands should I run as whom to get to the
>following result: access to phppgadmin through
>http://localhost/phppgadmin/, with or without password (preferably
>without), through Mozilla or w3m, with the following values:
>
>. PostgreSQL user: Unix user, say "blah"
>. PostgreSQL password (if applicable): say "bloh"
>. PostgreSQL database: say "blih"
>
>Can somebody please tell me step by step what exact lines to add in what
>exact places, and what exact commands to type under what exact userids.
>
>At each step I would feel better if I were given other commands or
>diagnosis to, now or later on:
>. check the step I just did went fine
>. undo that step
>
>I could find until now that running "createuser" as userid postgres
>helped a little (command-line postgresql reacted a little better), but
>no matter what I wrote in /etc/phppgadmin/config.inc.php, no matter what
>I typed in the HTML form that came up at the
>http://localhost/phppgadmin/ URL, with or without password, I got
>nowhere (no password stays there; a password gives the same HTML form
>with an error message, and if I fiddle a little with
>/etc/phppgadmin/config.inc.php I got a HTML page with a SQL connect
>error message in red and a javascript.history("back") link at the bottom
>of the page:
>
>-=-=-=
>Error - /usr/share/phppgadmin/lib.inc.php -- Line: 265
>
>PostgreSQL said:
>Your query:
>Unable to connect with settings: host='localhost' port='5432' dbname='blih' user='blah' password='bloh'
>Back
>-=-=-=
>
>Can somebody with a better knowledge than me sit at a clean computer and
>take note one after the other of the things he does to get there (things
>that will be obvious to him?). I don't want to read things like "It's up
>to you to look up the appropiate part in the PostgresSQL manual." I want
>to be told the 2 or 3 relevant commands now in order to play a little; I
>will look up this manual later.
>
>Regards,
>
>PS: did I fail to find the phppgadmin equivalent for
>http://phpmyadmin.sourceforge.net/phpMyAdmin/index.php3
>or does it not exist?
>
>I sometimes am reluctant to make my projects newcomers-friendly and
>documented, but this is needed if one wishes to see his job used and
>useful. I therefore hope you will hear my desperate call :)
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>phpPgAdmin-users mailing list
>php...@li...
>https://lists.sourceforge.net/lists/listinfo/phppgadmin-users
>


__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

[ppa-users] step-by-step detailed and comprehensive quickstart?

[Sebastien B. <blo...@cl...>]

Hello guys,

Sometimes I feel like I am being thick. Like today. But eventually I
think I can pretty well blame this on lack of good documentation in
both phppgadmin and PostgreSQL (if not, give me the meta-information on
where to find the information I need). Mailing-lists and annotations on
the official PostgreSQL documentation confirmed me I was not the only
one to feel like this.

Situation: I am on a GNU/Linux box, running Debian, with no much
experience of SQL, PostgreSQL, phppgadmin. I would like to play with
phppgadmin locally. So simple a wish I thought it would take a few
minutes.  Nope. Even though "apt-get install phppgadmin" worked, no
post-configuration script asked me anything.

I can either become crazy on this and spend hours not going anywhere, or
have someone experimented spend 5 minutes on this with me. I did my
homework, and really tried to read the docs. I can volunteer the writing
of the step-by-step guide that will be the outcome of this. At every
step I am planning to collect possible error messages and give the
fixes.

Local setup:
postgres is the PostgreSQL super-user

Example wish:
starting from scratch, what commands should I run as whom to get to the
following result: access to phppgadmin through
http://localhost/phppgadmin/, with or without password (preferably
without), through Mozilla or w3m, with the following values:

. PostgreSQL user: Unix user, say "blah"
. PostgreSQL password (if applicable): say "bloh"
. PostgreSQL database: say "blih"

Can somebody please tell me step by step what exact lines to add in what
exact places, and what exact commands to type under what exact userids.

At each step I would feel better if I were given other commands or
diagnosis to, now or later on:
. check the step I just did went fine
. undo that step

I could find until now that running "createuser" as userid postgres
helped a little (command-line postgresql reacted a little better), but
no matter what I wrote in /etc/phppgadmin/config.inc.php, no matter what
I typed in the HTML form that came up at the
http://localhost/phppgadmin/ URL, with or without password, I got
nowhere (no password stays there; a password gives the same HTML form
with an error message, and if I fiddle a little with
/etc/phppgadmin/config.inc.php I got a HTML page with a SQL connect
error message in red and a javascript.history("back") link at the bottom
of the page:

-=-=-=
Error - /usr/share/phppgadmin/lib.inc.php -- Line: 265

PostgreSQL said:
Your query:
Unable to connect with settings: host='localhost' port='5432' dbname='blih' user='blah' password='bloh'
Back
-=-=-=

Can somebody with a better knowledge than me sit at a clean computer and
take note one after the other of the things he does to get there (things
that will be obvious to him?). I don't want to read things like "It's up
to you to look up the appropiate part in the PostgresSQL manual." I want
to be told the 2 or 3 relevant commands now in order to play a little; I
will look up this manual later.

Regards,

PS: did I fail to find the phppgadmin equivalent for
http://phpmyadmin.sourceforge.net/phpMyAdmin/index.php3
or does it not exist?

I sometimes am reluctant to make my projects newcomers-friendly and
documented, but this is needed if one wishes to see his job used and
useful. I therefore hope you will hear my desperate call :)

[ppa-users] Solution to the Login Problems

[Plix D. <pl...@pl...>]

    Clear your cookies.  It appears as if phpPgAdmin will install =
multiple instances of the PHP_PGADMIN_USER cookie as the result of a bug =
either in PHP or in IE.  Either way, the initial login screen =
authentication will work (since it checks $set_user) but you will then =
end up on the frame page with two more login forms.  If you look at the =
error pgsql raises in the log file you'll see "FATAL: failed to =
authenticate user '<other value for PHP_PGADMIN_USER>'".  While I was =
unable to determine a way to remove that second cookie with PHP (logging =
out again with phpPgAdmin [setcookie();] certainly doesn't work), it is =
possible using IE's "Clear Cookies" option.

    Note that this is only a possible solution to the problem where =
logging in from the console would work and phpPgAdmin wouldn't.

.plix

[ppa-users] RE: [PHP] Release: phpPgAdmin 2.4.2

[Dan W. <kil...@us...>]

Yes,  If you read the requirements for phpPgAdmin, you will find that we no 
longer support versions of Postgres older the 7.  Earlier versions of 
phpPgAdmin however did a better job of supporting 6.5.x.  You can stick with 
those, but it has become to difficult to have certain features and maintain 
support for pre-7.0 pgsql.

-Dan

Quoting philip johnson <phi...@at...>:

> seems that there a little problems with postgresql 6.5.3 version
> 
> Warning: pg_exec() query failed: ERROR: parser: parse error at or near " "
> in /opt/apache_web/phppgadmin-2.4.2/all_db.php on line 37
> Error - /opt/apache_web/phppgadmin-2.4.2/all_db.php -- Line: 37
> PostgreSQL said: ERROR: parser: parse error at or near " "
> Your query:
> 
> SELECT datname, usename AS owner, pg_encoding_to_char(encoding) AS enc
> FROM pg_database d, pg_user u
> WHERE d.datdba = u.usesysid AND datname NOT LIKE 'template_'
> UNION
> SELECT datname, NULL AS owner, 'unknown' AS enc
> FROM pg_database
> WHERE datdba NOT IN (SELECT usesysid FROM pg_user) AND datname NOT LIKE
> 'template_'
> 
> 
> -----Message d'origine-----
> De : pgs...@po...
> [mailto:pgs...@po...]De la part de Dan Wilson
> Envoyé : lundi 8 juillet 2002 20:17
> À : php...@li...
> Cc : pgs...@po...; php...@li...;
> pgs...@po...
> Objet : [PHP] Release: phpPgAdmin 2.4.2
> 
> 
> http://sourceforge.net/projects/phppgadmin/
> 
> The phpPgAdmin team is pleased to announce the most recent maintenance
> release -- 2.4.2.
> 
> Release 2.4.2 now includes the ability to run phpPgAdmin in an environment
> with PHP's register_globals setting turned off, the default for PHP 4.2x.
> 
> Also included is several fixes and updates for PostgreSQL 7.2, including new
> ACL (privileges) values.  Another enhancement makes it possible to have
> edit/delete buttons after a manually entered query.
> 
> Click the following to view the full list of changes:
> http://sourceforge.net/project/shownotes.php?release_id=98604
> 
> Download phpPgAdmin 2.4.2 through the following link:
> http://sourceforge.net/project/showfiles.php?group_id=37132
> 
> Note: We did not receive much feedback from our beta (release for a month),
> so
> that means we are incredibly good coders, or not many users decided to help
> us
> out with this beta.... of course we all know it's the latter option, so
> please
> submit any bug reports or enhancement requests through the SourceForge
> tracker.
> 
> As always, thanks to SourceForge for hosting!
> 
> -Dan
> phpPgAdmin Development Lead
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org

[ppa-users] RE: [PHP] Release: phpPgAdmin 2.4.2

[philip j. <phi...@at...>]

seems that there a little problems with postgresql 6.5.3 version

Warning: pg_exec() query failed: ERROR: parser: parse error at or near " =
"
in /opt/apache_web/phppgadmin-2.4.2/all_db.php on line 37
Error - /opt/apache_web/phppgadmin-2.4.2/all_db.php -- Line: 37
PostgreSQL said: ERROR: parser: parse error at or near " "
Your query:

SELECT datname, usename AS owner, pg_encoding_to_char(encoding) AS enc
FROM pg_database d, pg_user u
WHERE d.datdba =3D u.usesysid AND datname NOT LIKE 'template_'
UNION
SELECT datname, NULL AS owner, 'unknown' AS enc
FROM pg_database
WHERE datdba NOT IN (SELECT usesysid FROM pg_user) AND datname NOT LIKE
'template_'


-----Message d'origine-----
De : pgs...@po...
[mailto:pgs...@po...]De la part de Dan Wilson
Envoy=E9 : lundi 8 juillet 2002 20:17
=C0 : php...@li...
Cc : pgs...@po...; php...@li...;
pgs...@po...
Objet : [PHP] Release: phpPgAdmin 2.4.2


http://sourceforge.net/projects/phppgadmin/

The phpPgAdmin team is pleased to announce the most recent maintenance
release -- 2.4.2.

Release 2.4.2 now includes the ability to run phpPgAdmin in an environmen=
t
with PHP's register_globals setting turned off, the default for PHP 4.2x.

Also included is several fixes and updates for PostgreSQL 7.2, including =
new
ACL (privileges) values.  Another enhancement makes it possible to have
edit/delete buttons after a manually entered query.

Click the following to view the full list of changes:
http://sourceforge.net/project/shownotes.php?release_id=3D98604

Download phpPgAdmin 2.4.2 through the following link:
http://sourceforge.net/project/showfiles.php?group_id=3D37132

Note: We did not receive much feedback from our beta (release for a month=
),
so
that means we are incredibly good coders, or not many users decided to he=
lp
us
out with this beta.... of course we all know it's the latter option, so
please
submit any bug reports or enhancement requests through the SourceForge
tracker.

As always, thanks to SourceForge for hosting!

-Dan
phpPgAdmin Development Lead



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

http://archives.postgresql.org

[ppa-users] Release: phpPgAdmin 2.4.2

[Dan W. <kil...@us...>]

http://sourceforge.net/projects/phppgadmin/

The phpPgAdmin team is pleased to announce the most recent maintenance 
release -- 2.4.2.

Release 2.4.2 now includes the ability to run phpPgAdmin in an environment 
with PHP's register_globals setting turned off, the default for PHP 4.2x. 

Also included is several fixes and updates for PostgreSQL 7.2, including new 
ACL (privileges) values.  Another enhancement makes it possible to have 
edit/delete buttons after a manually entered query.

Click the following to view the full list of changes: 
http://sourceforge.net/project/shownotes.php?release_id=98604

Download phpPgAdmin 2.4.2 through the following link: 
http://sourceforge.net/project/showfiles.php?group_id=37132

Note: We did not receive much feedback from our beta (release for a month), so 
that means we are incredibly good coders, or not many users decided to help us 
out with this beta.... of course we all know it's the latter option, so please 
submit any bug reports or enhancement requests through the SourceForge tracker.

As always, thanks to SourceForge for hosting!

-Dan
phpPgAdmin Development Lead

[ppa-users] Re: [GENERAL] login issue..

[Robert T. <rt...@we...>]

Well, we have seen this problem in the past with folks who have cookies
turned off in there browser, so there definitely could be some kind of
cookie issue going on with apache2. Unfortunately I haven't played with
apache2 nearly enough to be of help on that side of it. perhaps someone
else on the list can help out?

Robert Treat
xz...@us...
phpPgAdmin development team

On Tue, 2002-06-25 at 13:41, Chris Bowlby wrote:
> On 25 Jun 2002, Robert Treat wrote:
> 
> Hi Robert,
> 
>  Just tried 2.4.2-beta and still get the same results....:(... I am able
> to log in but I still only get two frames that contain login screens
> again. are there issues with Apache 2? I know there are issues with PHP
> 4.2.x and storing multiple cookie's....
> 
> 
> > Assuming you are running a newer version of php, there is a new beta
> > (2.4.2-beta) available of phpPgAdmin which is supposed to address the
> > issue your talking about. You can get it at
> > http://sourceforge.net/project/shownotes.php?release_id=93000
> >
> > Robert Treat
> > xz...@us...
> > phpPgAdmin Development Team
> >
> > On Mon, 2002-06-24 at 12:21, Chris Bowlby wrote:
> > > On 24 Jun 2002, Robert Treat wrote:
> > >
> > > Hi Robert,
> > >
> > <snip>
> > > >
> > > > On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote:
> > > > > On 20 Jun 2002, Robert Treat wrote:
> > > > >
> > > > > Hi Robert,
> > > > >
> > > > >  Ok, that worked for getting me into it. However phppgadmin is now
> > > > > giving me two login screens after I manage to log in, as it it's not
> > > > > seeing the connection... the frame's are loaded, but it does not give me
> > > > > the familiar listing of databases's in the left frame and links on the
> > > > > right... only two login screens... anyone run into this as well?
> > > > >
> > > > >
> > > > > > On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> > > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > >  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> > > > > > > attempting to configure pgadmin to allow a "user" to see all their
> > > > > > > databases, however we use a password configuration scheme.
> > > > > > >
> > > > > > >  the pg_hba.conf file looks like:
> > > > > > >
> > > > > > >  host testme_database 192.168.1.2 255.255.255.255 password password_file
> > > > > > >
> > > > > > >  However, the test account that I have specified in the password file is
> > > > > > > not "acknowledged" by postgreSQL unless I also have the user as being
> > > > > > > create in the system tables.
> > > > > >
> > > > > > AFAIK this is by design in postgreSQL; you are not a valid user unless
> > > > > > you have an entry in pg_shadow.
> > > > > >
> > > > > > > I am cross posting this one to both lists
> > > > > > > because I know part of the problem is "pgsql" related and the other half
> > > > > > > (getting to it) is phppgadmin related (I think)..
> > > > > > >
> > > > > > >  The other problem is, that when I can access the database from the
> > > > > > > console, I can not access it via the phppgadmin interface unless I put the
> > > > > > > username and password in the config file, regardless of if I'm using
> > > > > > > adv_auth or not...
> > > > > > >
> > > > > > >  anyone run into something similar and figure out a solution for it?
> > > > > > >
> > > > > >
> > > > > > I just set this up on one of our servers and it worked so it is doable.
> > > > > > 9 times out of 10 this is an issue of tcp sockets vs. unix sockets. Your
> > > > > > config.inc should probably look like:
> > > > > >
> > <snip>
> > > > > >
> > > > > >
> > > > > > also try looking in your postgres logs, you should be generating "FATAL"
> > > > > > errors every time login fails, they should give you better insight as to
> > > > > > where things are going wrong.
> > > > > >
> > > > > > Robert Treat
> > > > > > xz...@us...
> > > > > > member phpPgAdmin development team
> > > > > >
> > > >
> > >
> > >  Chris Bowlby,
> > >  -----------------------------------------------------
> > >  Manager of Information and Technology.
> > >  exc...@hu...
> > >  www.hub.org
> > >  1-902-542-3657
> > >  -----------------------------------------------------
> >
> >
> >
> 
>  Chris Bowlby,
>  -----------------------------------------------------
>  Manager of Information and Technology.
>  exc...@hu...
>  www.hub.org
>  1-902-542-3657
>  -----------------------------------------------------

[ppa-users] Re: [GENERAL] login issue..

[Chris B. <exc...@hu...>]

On 25 Jun 2002, Robert Treat wrote:

Hi Robert,

 Just tried 2.4.2-beta and still get the same results....:(... I am able
to log in but I still only get two frames that contain login screens
again. are there issues with Apache 2? I know there are issues with PHP
4.2.x and storing multiple cookie's....


> Assuming you are running a newer version of php, there is a new beta
> (2.4.2-beta) available of phpPgAdmin which is supposed to address the
> issue your talking about. You can get it at
> http://sourceforge.net/project/shownotes.php?release_id=93000
>
> Robert Treat
> xz...@us...
> phpPgAdmin Development Team
>
> On Mon, 2002-06-24 at 12:21, Chris Bowlby wrote:
> > On 24 Jun 2002, Robert Treat wrote:
> >
> > Hi Robert,
> >
> <snip>
> > >
> > > On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote:
> > > > On 20 Jun 2002, Robert Treat wrote:
> > > >
> > > > Hi Robert,
> > > >
> > > >  Ok, that worked for getting me into it. However phppgadmin is now
> > > > giving me two login screens after I manage to log in, as it it's not
> > > > seeing the connection... the frame's are loaded, but it does not give me
> > > > the familiar listing of databases's in the left frame and links on the
> > > > right... only two login screens... anyone run into this as well?
> > > >
> > > >
> > > > > On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> > > > > >
> > > > > > Hi All,
> > > > > >
> > > > > >  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> > > > > > attempting to configure pgadmin to allow a "user" to see all their
> > > > > > databases, however we use a password configuration scheme.
> > > > > >
> > > > > >  the pg_hba.conf file looks like:
> > > > > >
> > > > > >  host testme_database 192.168.1.2 255.255.255.255 password password_file
> > > > > >
> > > > > >  However, the test account that I have specified in the password file is
> > > > > > not "acknowledged" by postgreSQL unless I also have the user as being
> > > > > > create in the system tables.
> > > > >
> > > > > AFAIK this is by design in postgreSQL; you are not a valid user unless
> > > > > you have an entry in pg_shadow.
> > > > >
> > > > > > I am cross posting this one to both lists
> > > > > > because I know part of the problem is "pgsql" related and the other half
> > > > > > (getting to it) is phppgadmin related (I think)..
> > > > > >
> > > > > >  The other problem is, that when I can access the database from the
> > > > > > console, I can not access it via the phppgadmin interface unless I put the
> > > > > > username and password in the config file, regardless of if I'm using
> > > > > > adv_auth or not...
> > > > > >
> > > > > >  anyone run into something similar and figure out a solution for it?
> > > > > >
> > > > >
> > > > > I just set this up on one of our servers and it worked so it is doable.
> > > > > 9 times out of 10 this is an issue of tcp sockets vs. unix sockets. Your
> > > > > config.inc should probably look like:
> > > > >
> <snip>
> > > > >
> > > > >
> > > > > also try looking in your postgres logs, you should be generating "FATAL"
> > > > > errors every time login fails, they should give you better insight as to
> > > > > where things are going wrong.
> > > > >
> > > > > Robert Treat
> > > > > xz...@us...
> > > > > member phpPgAdmin development team
> > > > >
> > >
> >
> >  Chris Bowlby,
> >  -----------------------------------------------------
> >  Manager of Information and Technology.
> >  exc...@hu...
> >  www.hub.org
> >  1-902-542-3657
> >  -----------------------------------------------------
>
>
>

 Chris Bowlby,
 -----------------------------------------------------
 Manager of Information and Technology.
 exc...@hu...
 www.hub.org
 1-902-542-3657
 -----------------------------------------------------

[ppa-users] Re: [GENERAL] login issue..

[Robert T. <rt...@we...>]

Assuming you are running a newer version of php, there is a new beta
(2.4.2-beta) available of phpPgAdmin which is supposed to address the
issue your talking about. You can get it at
http://sourceforge.net/project/shownotes.php?release_id=93000

Robert Treat
xz...@us...
phpPgAdmin Development Team

On Mon, 2002-06-24 at 12:21, Chris Bowlby wrote:
> On 24 Jun 2002, Robert Treat wrote:
> 
> Hi Robert,
> 
<snip>
> >
> > On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote:
> > > On 20 Jun 2002, Robert Treat wrote:
> > >
> > > Hi Robert,
> > >
> > >  Ok, that worked for getting me into it. However phppgadmin is now
> > > giving me two login screens after I manage to log in, as it it's not
> > > seeing the connection... the frame's are loaded, but it does not give me
> > > the familiar listing of databases's in the left frame and links on the
> > > right... only two login screens... anyone run into this as well?
> > >
> > >
> > > > On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > >  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> > > > > attempting to configure pgadmin to allow a "user" to see all their
> > > > > databases, however we use a password configuration scheme.
> > > > >
> > > > >  the pg_hba.conf file looks like:
> > > > >
> > > > >  host testme_database 192.168.1.2 255.255.255.255 password password_file
> > > > >
> > > > >  However, the test account that I have specified in the password file is
> > > > > not "acknowledged" by postgreSQL unless I also have the user as being
> > > > > create in the system tables.
> > > >
> > > > AFAIK this is by design in postgreSQL; you are not a valid user unless
> > > > you have an entry in pg_shadow.
> > > >
> > > > > I am cross posting this one to both lists
> > > > > because I know part of the problem is "pgsql" related and the other half
> > > > > (getting to it) is phppgadmin related (I think)..
> > > > >
> > > > >  The other problem is, that when I can access the database from the
> > > > > console, I can not access it via the phppgadmin interface unless I put the
> > > > > username and password in the config file, regardless of if I'm using
> > > > > adv_auth or not...
> > > > >
> > > > >  anyone run into something similar and figure out a solution for it?
> > > > >
> > > >
> > > > I just set this up on one of our servers and it worked so it is doable.
> > > > 9 times out of 10 this is an issue of tcp sockets vs. unix sockets. Your
> > > > config.inc should probably look like:
> > > >
<snip>
> > > >
> > > >
> > > > also try looking in your postgres logs, you should be generating "FATAL"
> > > > errors every time login fails, they should give you better insight as to
> > > > where things are going wrong.
> > > >
> > > > Robert Treat
> > > > xz...@us...
> > > > member phpPgAdmin development team
> > > >
> >
> 
>  Chris Bowlby,
>  -----------------------------------------------------
>  Manager of Information and Technology.
>  exc...@hu...
>  www.hub.org
>  1-902-542-3657
>  -----------------------------------------------------

Re: [ppa-users] Re: [GENERAL] login issue..

[Chris B. <exc...@hu...>]

On Mon, 24 Jun 2002, Dan Wilson wrote:

Hi Dan,

 Hmmm yes, I've checked to make sure, I am heavily using other sites that
use cookies/javascript on a continuous basis that I designed and am having
no issues with...

> The other possibility here is that you are not accepting cookies...  have you
> verified that you are?
>
> -Dan
>
> Quoting Chris Bowlby <exc...@hu...>:
>
> > On 24 Jun 2002, Robert Treat wrote:
> >
> > Hi Robert,
> >
> >  Just did a quick check to make sure the register globals is enabled, and
> > she is...
> >
> > > Hey Chris,
> > >
> > > I left early friday and missed this one but I was just wondering if you
> > > got this resolved. The problem your describing sounds like register
> > > globals issue, where register globals needs to be turned on. Usually
> > > this problem crops up in newer version of PHP, I think the 4.2 release
> > > and maybe some of the later 4.1 series as well. HTH
> > >
> > > Robert
> > >
> > > On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote:
> > > > On 20 Jun 2002, Robert Treat wrote:
> > > >
> > > > Hi Robert,
> > > >
> > > >  Ok, that worked for getting me into it. However phppgadmin is now
> > > > giving me two login screens after I manage to log in, as it it's not
> > > > seeing the connection... the frame's are loaded, but it does not give me
> > > > the familiar listing of databases's in the left frame and links on the
> > > > right... only two login screens... anyone run into this as well?
> > > >
> > > >
> > > >
> > > > > On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> > > > > >
> > > > > > Hi All,
> > > > > >
> > > > > >  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> > > > > > attempting to configure pgadmin to allow a "user" to see all their
> > > > > > databases, however we use a password configuration scheme.
> > > > > >
> > > > > >  the pg_hba.conf file looks like:
> > > > > >
> > > > > >  host testme_database 192.168.1.2 255.255.255.255 password
> > password_file
> > > > > >
> > > > > >  However, the test account that I have specified in the password file
> > is
> > > > > > not "acknowledged" by postgreSQL unless I also have the user as
> > being
> > > > > > create in the system tables.
> > > > >
> > > > > AFAIK this is by design in postgreSQL; you are not a valid user unless
> > > > > you have an entry in pg_shadow.
> > > > >
> > > > > > I am cross posting this one to both lists
> > > > > > because I know part of the problem is "pgsql" related and the other
> > half
> > > > > > (getting to it) is phppgadmin related (I think)..
> > > > > >
> > > > > >  The other problem is, that when I can access the database from the
> > > > > > console, I can not access it via the phppgadmin interface unless I
> > put the
> > > > > > username and password in the config file, regardless of if I'm using
> > > > > > adv_auth or not...
> > > > > >
> > > > > >  anyone run into something similar and figure out a solution for it?
> > > > > >
> > > > >
> > > > > I just set this up on one of our servers and it worked so it is
> > doable.
> > > > > 9 times out of 10 this is an issue of tcp sockets vs. unix sockets.
> > Your
> > > > > config.inc should probably look like:
> > > > >
> > > > > $cfgServers[2]['local']         = false;
> > > > > $cfgServers[2]['host']          = '192.168.0.xxx'; // IP of DB server
> > > > > $cfgServers[2]['port']          = '5432';
> > > > > $cfgServers[2]['adv_auth']      = true;
> > > > >
> > > > > $cfgServers[2]['user']          = '';   // if you are not using
> > > > > $cfgServers[2]['password']      = '';   // if you are not using
> > adv_auth
> > > > > $cfgServers[2]['only_db']       = '';   // if set to a db-name, only
> > > > >
> > > > >
> > > > > also try looking in your postgres logs, you should be generating
> > "FATAL"
> > > > > errors every time login fails, they should give you better insight as
> > to
> > > > > where things are going wrong.
> > > > >
> > > > > Robert Treat
> > > > > xz...@us...
> > > > > member phpPgAdmin development team
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >  Chris Bowlby,
> > > >  -----------------------------------------------------
> > > >  Manager of Information and Technology.
> > > >  exc...@hu...
> > > >  www.hub.org
> > > >  1-902-542-3657
> > > >  -----------------------------------------------------
> > >
> > >
> > >
> >
> >  Chris Bowlby,
> >  -----------------------------------------------------
> >  Manager of Information and Technology.
> >  exc...@hu...
> >  www.hub.org
> >  1-902-542-3657
> >  -----------------------------------------------------
> >
> >
> >
> > -------------------------------------------------------
> > Sponsored by:
> > ThinkGeek at http://www.ThinkGeek.com/
> > _______________________________________________
> > phpPgAdmin-users mailing list
> > php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phppgadmin-users
>
>
>
>
>
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> phpPgAdmin-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phppgadmin-users
>

 Chris Bowlby,
 -----------------------------------------------------
 Manager of Information and Technology.
 exc...@hu...
 www.hub.org
 1-902-542-3657
 -----------------------------------------------------

Re: [ppa-users] Re: [GENERAL] login issue..

[Dan W. <kil...@us...>]

The other possibility here is that you are not accepting cookies...  have you 
verified that you are?

-Dan

Quoting Chris Bowlby <exc...@hu...>:

> On 24 Jun 2002, Robert Treat wrote:
> 
> Hi Robert,
> 
>  Just did a quick check to make sure the register globals is enabled, and
> she is...
> 
> > Hey Chris,
> >
> > I left early friday and missed this one but I was just wondering if you
> > got this resolved. The problem your describing sounds like register
> > globals issue, where register globals needs to be turned on. Usually
> > this problem crops up in newer version of PHP, I think the 4.2 release
> > and maybe some of the later 4.1 series as well. HTH
> >
> > Robert
> >
> > On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote:
> > > On 20 Jun 2002, Robert Treat wrote:
> > >
> > > Hi Robert,
> > >
> > >  Ok, that worked for getting me into it. However phppgadmin is now
> > > giving me two login screens after I manage to log in, as it it's not
> > > seeing the connection... the frame's are loaded, but it does not give me
> > > the familiar listing of databases's in the left frame and links on the
> > > right... only two login screens... anyone run into this as well?
> > >
> > >
> > >
> > > > On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > >  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> > > > > attempting to configure pgadmin to allow a "user" to see all their
> > > > > databases, however we use a password configuration scheme.
> > > > >
> > > > >  the pg_hba.conf file looks like:
> > > > >
> > > > >  host testme_database 192.168.1.2 255.255.255.255 password
> password_file
> > > > >
> > > > >  However, the test account that I have specified in the password file
> is
> > > > > not "acknowledged" by postgreSQL unless I also have the user as
> being
> > > > > create in the system tables.
> > > >
> > > > AFAIK this is by design in postgreSQL; you are not a valid user unless
> > > > you have an entry in pg_shadow.
> > > >
> > > > > I am cross posting this one to both lists
> > > > > because I know part of the problem is "pgsql" related and the other
> half
> > > > > (getting to it) is phppgadmin related (I think)..
> > > > >
> > > > >  The other problem is, that when I can access the database from the
> > > > > console, I can not access it via the phppgadmin interface unless I
> put the
> > > > > username and password in the config file, regardless of if I'm using
> > > > > adv_auth or not...
> > > > >
> > > > >  anyone run into something similar and figure out a solution for it?
> > > > >
> > > >
> > > > I just set this up on one of our servers and it worked so it is
> doable.
> > > > 9 times out of 10 this is an issue of tcp sockets vs. unix sockets.
> Your
> > > > config.inc should probably look like:
> > > >
> > > > $cfgServers[2]['local']         = false;
> > > > $cfgServers[2]['host']          = '192.168.0.xxx'; // IP of DB server
> > > > $cfgServers[2]['port']          = '5432';
> > > > $cfgServers[2]['adv_auth']      = true;
> > > >
> > > > $cfgServers[2]['user']          = '';   // if you are not using
> > > > $cfgServers[2]['password']      = '';   // if you are not using
> adv_auth
> > > > $cfgServers[2]['only_db']       = '';   // if set to a db-name, only
> > > >
> > > >
> > > > also try looking in your postgres logs, you should be generating
> "FATAL"
> > > > errors every time login fails, they should give you better insight as
> to
> > > > where things are going wrong.
> > > >
> > > > Robert Treat
> > > > xz...@us...
> > > > member phpPgAdmin development team
> > > >
> > > >
> > > >
> > > >
> > >
> > >  Chris Bowlby,
> > >  -----------------------------------------------------
> > >  Manager of Information and Technology.
> > >  exc...@hu...
> > >  www.hub.org
> > >  1-902-542-3657
> > >  -----------------------------------------------------
> >
> >
> >
> 
>  Chris Bowlby,
>  -----------------------------------------------------
>  Manager of Information and Technology.
>  exc...@hu...
>  www.hub.org
>  1-902-542-3657
>  -----------------------------------------------------
> 
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> phpPgAdmin-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phppgadmin-users

[ppa-users] Re: [GENERAL] login issue..

[Chris B. <exc...@hu...>]

On 24 Jun 2002, Robert Treat wrote:

Hi Robert,

 Just did a quick check to make sure the register globals is enabled, and
she is...

> Hey Chris,
>
> I left early friday and missed this one but I was just wondering if you
> got this resolved. The problem your describing sounds like register
> globals issue, where register globals needs to be turned on. Usually
> this problem crops up in newer version of PHP, I think the 4.2 release
> and maybe some of the later 4.1 series as well. HTH
>
> Robert
>
> On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote:
> > On 20 Jun 2002, Robert Treat wrote:
> >
> > Hi Robert,
> >
> >  Ok, that worked for getting me into it. However phppgadmin is now
> > giving me two login screens after I manage to log in, as it it's not
> > seeing the connection... the frame's are loaded, but it does not give me
> > the familiar listing of databases's in the left frame and links on the
> > right... only two login screens... anyone run into this as well?
> >
> >
> >
> > > On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> > > >
> > > > Hi All,
> > > >
> > > >  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> > > > attempting to configure pgadmin to allow a "user" to see all their
> > > > databases, however we use a password configuration scheme.
> > > >
> > > >  the pg_hba.conf file looks like:
> > > >
> > > >  host testme_database 192.168.1.2 255.255.255.255 password password_file
> > > >
> > > >  However, the test account that I have specified in the password file is
> > > > not "acknowledged" by postgreSQL unless I also have the user as being
> > > > create in the system tables.
> > >
> > > AFAIK this is by design in postgreSQL; you are not a valid user unless
> > > you have an entry in pg_shadow.
> > >
> > > > I am cross posting this one to both lists
> > > > because I know part of the problem is "pgsql" related and the other half
> > > > (getting to it) is phppgadmin related (I think)..
> > > >
> > > >  The other problem is, that when I can access the database from the
> > > > console, I can not access it via the phppgadmin interface unless I put the
> > > > username and password in the config file, regardless of if I'm using
> > > > adv_auth or not...
> > > >
> > > >  anyone run into something similar and figure out a solution for it?
> > > >
> > >
> > > I just set this up on one of our servers and it worked so it is doable.
> > > 9 times out of 10 this is an issue of tcp sockets vs. unix sockets. Your
> > > config.inc should probably look like:
> > >
> > > $cfgServers[2]['local']         = false;
> > > $cfgServers[2]['host']          = '192.168.0.xxx'; // IP of DB server
> > > $cfgServers[2]['port']          = '5432';
> > > $cfgServers[2]['adv_auth']      = true;
> > >
> > > $cfgServers[2]['user']          = '';   // if you are not using
> > > $cfgServers[2]['password']      = '';   // if you are not using adv_auth
> > > $cfgServers[2]['only_db']       = '';   // if set to a db-name, only
> > >
> > >
> > > also try looking in your postgres logs, you should be generating "FATAL"
> > > errors every time login fails, they should give you better insight as to
> > > where things are going wrong.
> > >
> > > Robert Treat
> > > xz...@us...
> > > member phpPgAdmin development team
> > >
> > >
> > >
> > >
> >
> >  Chris Bowlby,
> >  -----------------------------------------------------
> >  Manager of Information and Technology.
> >  exc...@hu...
> >  www.hub.org
> >  1-902-542-3657
> >  -----------------------------------------------------
>
>
>

 Chris Bowlby,
 -----------------------------------------------------
 Manager of Information and Technology.
 exc...@hu...
 www.hub.org
 1-902-542-3657
 -----------------------------------------------------

RE: [ppa-users] Failed opening '' for inclusion

[Paul O. <pa...@th...>]

I have just downloaded and installed 2.4.2-beta and the problem seems to be sorted.

Thanks very much for your prompt and effective response Dan.

Paul


-----Original Message-----
From:	Dan Wilson [SMTP:kil...@us...]
Sent:	Sunday, June 23, 2002 3:43 PM
To:	php...@li...
Subject:	Re: [ppa-users] Failed opening '' for inclusion

Have you tried upgrading to the latest beta [2.4.2-beta]?  I believe this is 
an issue with register_globals set to off.  It is not seeing the variable 
which tells it which file to include.  The 2.4.2 will correct that issue.

http://sourceforge.net/project/showfiles.php?group_id=37132

-Dan


Quoting Paul Older <pa...@th...>:

> I appreciate that the following problem is probably going to be due to a 
> faulty configuration somewhere rather than an issue with phpPgAdmin itself 
> but I'd be really grateful if someone could give me some pointers...
> 
> 
> 
> --- Environment ---
> 
> 	RedHat Linux 7.2
> 	php 4.2.0
> 	phpPgAdmin 2.4-1
> 	apache 1.3.24
> 	
> 
> 
> --- What Works ---
> 
> When I browse   /index.php   the left hand nav correctly lists the 
> databases I have running.
> 
> One of these databases is called "paulo".
> 
> If I then browse   /db_details.php?server=1&db=paulo  the right hand side 
> of phpPgAdmin correctly displays the tables in database paulo and also the 
> number of records in each table.
> 
> 
> 
> --- What Doesn't Work ---
> 
> However if I try and use any of the functionality of phpPgAdmin I get 
> various error messages.
> 
> For example I if click on browse I get:
> 
> Warning: Failed opening '' for inclusion 
> (include_path='.:/usr/local/lib/php') in /apps/sites/phpPgAdmin/sql.php on 
> line 130
> 
> I notice someone posted a similar (but slightly different) error as a bug 
> at http://gborg.postgresql.org/project/phppgadmin/bugs/bugupdate.php?322
> 
> The solution to the error given was to update one's include path to include 
> at least the current directory. It is clear in this case that my 
> include_path *does* include the current directory so it must be something 
> else.
> 
> 
> 
> Anyone got any ideas?
> 
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> phpPgAdmin-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phppgadmin-users





-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
phpPgAdmin-users mailing list
php...@li...
https://lists.sourceforge.net/lists/listinfo/phppgadmin-users

Re: [ppa-users] Failed opening '' for inclusion

[Dan W. <kil...@us...>]

Have you tried upgrading to the latest beta [2.4.2-beta]?  I believe this is 
an issue with register_globals set to off.  It is not seeing the variable 
which tells it which file to include.  The 2.4.2 will correct that issue.

http://sourceforge.net/project/showfiles.php?group_id=37132

-Dan


Quoting Paul Older <pa...@th...>:

> I appreciate that the following problem is probably going to be due to a 
> faulty configuration somewhere rather than an issue with phpPgAdmin itself 
> but I'd be really grateful if someone could give me some pointers...
> 
> 
> 
> --- Environment ---
> 
> 	RedHat Linux 7.2
> 	php 4.2.0
> 	phpPgAdmin 2.4-1
> 	apache 1.3.24
> 	
> 
> 
> --- What Works ---
> 
> When I browse   /index.php   the left hand nav correctly lists the 
> databases I have running.
> 
> One of these databases is called "paulo".
> 
> If I then browse   /db_details.php?server=1&db=paulo  the right hand side 
> of phpPgAdmin correctly displays the tables in database paulo and also the 
> number of records in each table.
> 
> 
> 
> --- What Doesn't Work ---
> 
> However if I try and use any of the functionality of phpPgAdmin I get 
> various error messages.
> 
> For example I if click on browse I get:
> 
> Warning: Failed opening '' for inclusion 
> (include_path='.:/usr/local/lib/php') in /apps/sites/phpPgAdmin/sql.php on 
> line 130
> 
> I notice someone posted a similar (but slightly different) error as a bug 
> at http://gborg.postgresql.org/project/phppgadmin/bugs/bugupdate.php?322
> 
> The solution to the error given was to update one's include path to include 
> at least the current directory. It is clear in this case that my 
> include_path *does* include the current directory so it must be something 
> else.
> 
> 
> 
> Anyone got any ideas?
> 
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> phpPgAdmin-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phppgadmin-users

[ppa-users] Failed opening '' for inclusion

[Paul O. <pa...@th...>]

I appreciate that the following problem is probably going to be due to a 
faulty configuration somewhere rather than an issue with phpPgAdmin itself 
but I'd be really grateful if someone could give me some pointers...



--- Environment ---

	RedHat Linux 7.2
	php 4.2.0
	phpPgAdmin 2.4-1
	apache 1.3.24
	


--- What Works ---

When I browse   /index.php   the left hand nav correctly lists the 
databases I have running.

One of these databases is called "paulo".

If I then browse   /db_details.php?server=1&db=paulo  the right hand side 
of phpPgAdmin correctly displays the tables in database paulo and also the 
number of records in each table.



--- What Doesn't Work ---

However if I try and use any of the functionality of phpPgAdmin I get 
various error messages.

For example I if click on browse I get:

Warning: Failed opening '' for inclusion 
(include_path='.:/usr/local/lib/php') in /apps/sites/phpPgAdmin/sql.php on 
line 130

I notice someone posted a similar (but slightly different) error as a bug 
at http://gborg.postgresql.org/project/phppgadmin/bugs/bugupdate.php?322

The solution to the error given was to update one's include path to include 
at least the current directory. It is clear in this case that my 
include_path *does* include the current directory so it must be something 
else.



Anyone got any ideas?

Re: [ppa-users] Re: [GENERAL] login issue..

[Dan W. <kil...@us...>]

Chris,

I'm guessing that you have register_globals off (which is default with a new 
PHP install after 4.1) and you are running phpPgAdmin 2.4.1 or earlier...

If you upgrade to phpPgAdmin 2.4.2-beta, it should correct this problem.  It 
just allows it to work with register_globals off.

-Dan

Quoting Chris Bowlby <exc...@hu...>:

> On 20 Jun 2002, Robert Treat wrote:
> 
> Hi Robert,
> 
>  Ok, that worked for getting me into it. However phppgadmin is now
> giving me two login screens after I manage to log in, as it it's not
> seeing the connection... the frame's are loaded, but it does not give me
> the familiar listing of databases's in the left frame and links on the
> right... only two login screens... anyone run into this as well?
> 
> 
> 
> > On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> > >
> > > Hi All,
> > >
> > >  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> > > attempting to configure pgadmin to allow a "user" to see all their
> > > databases, however we use a password configuration scheme.
> > >
> > >  the pg_hba.conf file looks like:
> > >
> > >  host testme_database 192.168.1.2 255.255.255.255 password password_file
> > >
> > >  However, the test account that I have specified in the password file is
> > > not "acknowledged" by postgreSQL unless I also have the user as being
> > > create in the system tables.
> >
> > AFAIK this is by design in postgreSQL; you are not a valid user unless
> > you have an entry in pg_shadow.
> >
> > > I am cross posting this one to both lists
> > > because I know part of the problem is "pgsql" related and the other half
> > > (getting to it) is phppgadmin related (I think)..
> > >
> > >  The other problem is, that when I can access the database from the
> > > console, I can not access it via the phppgadmin interface unless I put
> the
> > > username and password in the config file, regardless of if I'm using
> > > adv_auth or not...
> > >
> > >  anyone run into something similar and figure out a solution for it?
> > >
> >
> > I just set this up on one of our servers and it worked so it is doable.
> > 9 times out of 10 this is an issue of tcp sockets vs. unix sockets. Your
> > config.inc should probably look like:
> >
> > $cfgServers[2]['local']         = false;
> > $cfgServers[2]['host']          = '192.168.0.xxx'; // IP of DB server
> > $cfgServers[2]['port']          = '5432';
> > $cfgServers[2]['adv_auth']      = true;
> >
> > $cfgServers[2]['user']          = '';   // if you are not using
> > $cfgServers[2]['password']      = '';   // if you are not using adv_auth
> > $cfgServers[2]['only_db']       = '';   // if set to a db-name, only
> >
> >
> > also try looking in your postgres logs, you should be generating "FATAL"
> > errors every time login fails, they should give you better insight as to
> > where things are going wrong.
> >
> > Robert Treat
> > xz...@us...
> > member phpPgAdmin development team
> >
> >
> >
> >
> 
>  Chris Bowlby,
>  -----------------------------------------------------
>  Manager of Information and Technology.
>  exc...@hu...
>  www.hub.org
>  1-902-542-3657
>  -----------------------------------------------------
> 
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> phpPgAdmin-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phppgadmin-users

[ppa-users] Re: [GENERAL] login issue..

[Chris B. <exc...@hu...>]

On 20 Jun 2002, Robert Treat wrote:

Hi Robert,

 Ok, that worked for getting me into it. However phppgadmin is now
giving me two login screens after I manage to log in, as it it's not
seeing the connection... the frame's are loaded, but it does not give me
the familiar listing of databases's in the left frame and links on the
right... only two login screens... anyone run into this as well?



> On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> >
> > Hi All,
> >
> >  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> > attempting to configure pgadmin to allow a "user" to see all their
> > databases, however we use a password configuration scheme.
> >
> >  the pg_hba.conf file looks like:
> >
> >  host testme_database 192.168.1.2 255.255.255.255 password password_file
> >
> >  However, the test account that I have specified in the password file is
> > not "acknowledged" by postgreSQL unless I also have the user as being
> > create in the system tables.
>
> AFAIK this is by design in postgreSQL; you are not a valid user unless
> you have an entry in pg_shadow.
>
> > I am cross posting this one to both lists
> > because I know part of the problem is "pgsql" related and the other half
> > (getting to it) is phppgadmin related (I think)..
> >
> >  The other problem is, that when I can access the database from the
> > console, I can not access it via the phppgadmin interface unless I put the
> > username and password in the config file, regardless of if I'm using
> > adv_auth or not...
> >
> >  anyone run into something similar and figure out a solution for it?
> >
>
> I just set this up on one of our servers and it worked so it is doable.
> 9 times out of 10 this is an issue of tcp sockets vs. unix sockets. Your
> config.inc should probably look like:
>
> $cfgServers[2]['local']         = false;
> $cfgServers[2]['host']          = '192.168.0.xxx'; // IP of DB server
> $cfgServers[2]['port']          = '5432';
> $cfgServers[2]['adv_auth']      = true;
>
> $cfgServers[2]['user']          = '';   // if you are not using
> $cfgServers[2]['password']      = '';   // if you are not using adv_auth
> $cfgServers[2]['only_db']       = '';   // if set to a db-name, only
>
>
> also try looking in your postgres logs, you should be generating "FATAL"
> errors every time login fails, they should give you better insight as to
> where things are going wrong.
>
> Robert Treat
> xz...@us...
> member phpPgAdmin development team
>
>
>
>

 Chris Bowlby,
 -----------------------------------------------------
 Manager of Information and Technology.
 exc...@hu...
 www.hub.org
 1-902-542-3657
 -----------------------------------------------------

[ppa-users] Re: [GENERAL] login issue..

[Robert T. <rt...@we...>]

On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
> 
> Hi All,
> 
>  Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> attempting to configure pgadmin to allow a "user" to see all their
> databases, however we use a password configuration scheme.
> 
>  the pg_hba.conf file looks like:
> 
>  host testme_database 192.168.1.2 255.255.255.255 password password_file
> 
>  However, the test account that I have specified in the password file is
> not "acknowledged" by postgreSQL unless I also have the user as being
> create in the system tables.

AFAIK this is by design in postgreSQL; you are not a valid user unless
you have an entry in pg_shadow.

> I am cross posting this one to both lists
> because I know part of the problem is "pgsql" related and the other half
> (getting to it) is phppgadmin related (I think)..
> 
>  The other problem is, that when I can access the database from the
> console, I can not access it via the phppgadmin interface unless I put the
> username and password in the config file, regardless of if I'm using
> adv_auth or not...
> 
>  anyone run into something similar and figure out a solution for it?
>

I just set this up on one of our servers and it worked so it is doable.
9 times out of 10 this is an issue of tcp sockets vs. unix sockets. Your
config.inc should probably look like:

$cfgServers[2]['local']         = false;
$cfgServers[2]['host']          = '192.168.0.xxx'; // IP of DB server
$cfgServers[2]['port']          = '5432';
$cfgServers[2]['adv_auth']      = true;

$cfgServers[2]['user']          = '';   // if you are not using 
$cfgServers[2]['password']      = '';   // if you are not using adv_auth
$cfgServers[2]['only_db']       = '';   // if set to a db-name, only 


also try looking in your postgres logs, you should be generating "FATAL"
errors every time login fails, they should give you better insight as to
where things are going wrong.

Robert Treat
xz...@us...
member phpPgAdmin development team

[ppa-users] login issue..

[Chris B. <exc...@hu...>]

Hi All,

 Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
attempting to configure pgadmin to allow a "user" to see all their
databases, however we use a password configuration scheme.

 the pg_hba.conf file looks like:

 host testme_database 192.168.1.2 255.255.255.255 password password_file

 However, the test account that I have specified in the password file is
not "acknowledged" by postgreSQL unless I also have the user as being
create in the system tables. I am cross posting this one to both lists
because I know part of the problem is "pgsql" related and the other half
(getting to it) is phppgadmin related (I think)..

 The other problem is, that when I can access the database from the
console, I can not access it via the phppgadmin interface unless I put the
username and password in the config file, regardless of if I'm using
adv_auth or not...

 anyone run into something similar and figure out a solution for it?


 Chris Bowlby,
 -----------------------------------------------------
 Manager of Information and Technology.
 exc...@hu...
 www.hub.org
 1-902-542-3657
 -----------------------------------------------------

Re: [ppa-users] Cannot access "all" databases with 2.4.1 on a PgSql 7.2.1 server

[Dan W. <kil...@us...>]

Is your "na" user a superuser?  If not, then be default, you would only be 
able to access databases created by that user.  You can change this behavior 
by changing the "cfgUserDatabases" setting in config.inc.php to false.

Or you can always make "na" a superuser.

-Dan

Quoting Alexander Skwar <AS...@Di...>:

> Hello.
> I'm trying to setup phpPgAdmin 2.4.1 on a Mandrake Linux server.
> phpPgAdmin should connect to a PostgreSQL 7.2.1 server running on the
> same machine.
> 
> In the PgSql server, I've created some databases which should be
> accessed with the help of phpPgAdmin.  My config.inc.php contains:
> 
> $cfgServers[1]['local']         = false;
> $cfgServers[1]['host']          = 'localhost';
> $cfgServers[1]['port']          = '5432';
> $cfgServers[1]['adv_auth']      = false;
> $cfgServers[1]['user']          = 'na';
> $cfgServers[1]['password']      = 'xx';
> $cfgServers[1]['only_db']       = '';
> 
> However, when I connect/call phpPgAdmin, it doesn't show any databases
> in the left navigation frame.  It just shows:
> 
> Home
> All Databases 
> Reports 
> 
> I don't think (although I'm not too sure...) that it is a permission
> problem, because when I set a database in the 'only_db' property, this
> database is shown.
> 
> Am I doing something wrong?
> 
> Thanks a lot,
> 
> Alexander Skwar
> -- 
> How to quote:	http://learn.to/quote (german) http://quote.6x.to (english)
> Homepage:	http://www.iso-top.de      |    Jabber: as...@a-...
>    iso-top.de - Die günstige Art an Linux Distributionen zu kommen
>                        Uptime: 5 days 19 hours 29 minutes
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> phpPgAdmin-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phppgadmin-users

[ppa-users] Cannot access "all" databases with 2.4.1 on a PgSql 7.2.1 server

[Alexander S. <AS...@Di...>]

Hello.
I'm trying to setup phpPgAdmin 2.4.1 on a Mandrake Linux server.
phpPgAdmin should connect to a PostgreSQL 7.2.1 server running on the
same machine.

In the PgSql server, I've created some databases which should be
accessed with the help of phpPgAdmin.  My config.inc.php contains:

$cfgServers[1]['local']         =3D false;
$cfgServers[1]['host']          =3D 'localhost';
$cfgServers[1]['port']          =3D '5432';
$cfgServers[1]['adv_auth']      =3D false;
$cfgServers[1]['user']          =3D 'na';
$cfgServers[1]['password']      =3D 'xx';
$cfgServers[1]['only_db']       =3D '';

However, when I connect/call phpPgAdmin, it doesn't show any databases
in the left navigation frame.  It just shows:

Home
All Databases=20
Reports=20

I don't think (although I'm not too sure...) that it is a permission
problem, because when I set a database in the 'only_db' property, this
database is shown.

Am I doing something wrong?

Thanks a lot,

Alexander Skwar
--=20
How to quote:	http://learn.to/quote (german) http://quote.6x.to (english)
Homepage:	http://www.iso-top.de      |    Jabber: as...@a-...
   iso-top.de - Die g=FCnstige Art an Linux Distributionen zu kommen
                       Uptime: 5 days 19 hours 29 minutes

[ppa-users] Beta 2.4.2

[Dan W. <kil...@us...>]

We have compiled a new minor release beta for phpPgAdmin.  Please take the 
opportunity to test some of the enhancements and bug fixes in this beta.

View the release notes:
http://sourceforge.net/project/shownotes.php?release_id=93000

Download (be sure to scroll down to the unstable branch):
http://sourceforge.net/project/showfiles.php?group_id=37132

Please report any bugs through the sourceforge tracker:
http://sourceforge.net/tracker/?group_id=37132&atid=418980

-Dan Wilson
phpPgAdmin Project Managment

Re: [ppa-users] random page errors and table errata

[Dan W. <kil...@us...>]

Yes, we are aware of these issues and we are developing the new version of 
phpPgAdmin (renamed WebDB) to be very security aware and will use the new 
superglobal variables that were introduced in php 4.1.  This will enhance our 
security as well as provide better coding structure.

Seeing as WebDB probably will not support versions of PostgreSQL prior to 7.1, 
we might need to work on re-coding phpPgAdmin to allow for register globals 
being off.  Thus still maintaining a tool that can administer 7.0 (and earlier 
version) of PostgreSQL.  We are still considering the need for this step so no 
work has begun on it.

-Dan

Quoting Brad Littlejohn <at...@us...>:

> On Tue, May 07, 2002 at 11:57:58PM -0600, Dan Wilson wrote:
> > This looks like an issue of register_globals being off.  Currently,
> phpPgAdmin 
> > requires register_globals to be turned on.
> > 
> > You can do this through php.ini, an apache directive in either the
> httpd.conf 
> > or a .htaccess file.
> > 
> > Check the php site for instructions on setting this directive: 
> > http://www.php.net/manual/en/configuration.php#configuration.file
> > 
> > -Dan
> 
>         This brings up an interesting issue. This warning is given when
> compiling php-4.2.1 (recently released):
> 
> +--------------------------------------------------------------------+
> |                          *** NOTE ***                              |
> |            The default for register_globals is now OFF!            |
> |                                                                    |
> | If your application relies on register_globals being ON, you       |
> | should explicitly set it to on in your php.ini file.               |
> | Note that you are strongly encouraged to read                      |
> | http://www.php.net/manual/en/security.registerglobals.php          |
> | about the implications of having register_globals set to on, and   |
> | avoid using it if possible.                                        |
> +--------------------------------------------------------------------+
> 
>         As phppgadmin taken what's at this link into account?
> 
>                                                         BL.
> 
> 

Re: [ppa-users] random page errors and table errata

[Brad L. <at...@us...>]

On Tue, May 07, 2002 at 11:57:58PM -0600, Dan Wilson wrote:
> This looks like an issue of register_globals being off.  Currently, phpPg=
Admin=20
> requires register_globals to be turned on.
>=20
> You can do this through php.ini, an apache directive in either the httpd.=
conf=20
> or a .htaccess file.
>=20
> Check the php site for instructions on setting this directive:=20
> http://www.php.net/manual/en/configuration.php#configuration.file
>=20
> -Dan

        This brings up an interesting issue. This warning is given when
compiling php-4.2.1 (recently released):

+--------------------------------------------------------------------+
|                          *** NOTE ***                              |
|            The default for register_globals is now OFF!            |
|                                                                    |
| If your application relies on register_globals being ON, you       |
| should explicitly set it to on in your php.ini file.               |
| Note that you are strongly encouraged to read                      |
| http://www.php.net/manual/en/security.registerglobals.php          |
| about the implications of having register_globals set to on, and   |
| avoid using it if possible.                                        |
+--------------------------------------------------------------------+

        As phppgadmin taken what's at this link into account?

                                                        BL.

Re: [ppa-users] random page errors and table errata

[Ben M. <bm...@sy...>]

Fixed.

you were right with the register_globals =3D on suggestion.

php.ini was in the wrong place.
make install=20
put the file in /etc/php.ini

I found a script which outputs all the php variables and
register_globals =3D off

moved php.ini to
/usr/local/lib and restarted apache.

IT WORKED.

Thanks
On Tue, May 07, 2002 at 11:57:58PM -0600, Dan Wilson wrote:
> This looks like an issue of register_globals being off.  Currently, phpPg=
Admin=20
> requires register_globals to be turned on.
>=20
> You can do this through php.ini, an apache directive in either the httpd.=
conf=20
> or a .htaccess file.
>=20
> Check the php site for instructions on setting this directive:=20
> http://www.php.net/manual/en/configuration.php#configuration.file
>=20
> -Dan
>=20
> Quoting Ben Moir <bm...@sy...>:
>=20
> > Hi folks,
> >=20
> > Don't see much activity on this list so not sure if anyone is out there.
> >=20
> > I recently installed phpPgAdmin 2.4-1
> > PostgreSQL 7.1.3
> > PHP 4.2
> > on a Redhat 7.2 (apache RPM)
> >=20
> > After a few hours battling with the login problems that other users see=
m to
> > be
> > having I got access to the database.=20
> > NOTE: I had to use adv_auth=3Dfalse or the login screen would reload wi=
th
> > no errors or explaination.
> >=20
> >=20
> > Now my joy disappeared quickly when I found errors on most pages.
> >=20
> > I couldn't create a table using the phpPgAdmin interface. Nothing seemed
> > to happen.
> >=20
> > Created a table on the command line.
> >=20
> > then in the phpPgAdmin when I click table>browse I get the following
> > error:
> >=20
> > Warning: Failed opening '' for inclusion
> > (include_path=3D'.:/usr/local/lib/php') in
> > /home/bmoir/public_html/phpPgAdmin/sql.php on line 130
> >=20
> >=20
> > If I try and insert into the new table I get this error:
> >=20
> > Error - /home/bmoir/public_html/phpPgAdmin/tbl_form.inc.php -- Line: 47
> > PostgreSQL said: ERROR: zero-length delimited identifier
> > Your query:
> > SELECT * FROM "" LIMIT 1
> > Back=20
> > Link: Resource id #1
> > DB: bmoir
> > Table:
> > Server: 1
> >=20
> >=20
> > It seems like the links are incorrect or there is something seriously
> > wrong with my php engine.
> >=20
> > Any ideas.
> > One theory is apache is using php3 to run .php files. how can I tell
> > which php version the interface is running on?
> >=20
> > Ben
> >=20
> > --=20
> >=20
>=20
>=20
>=20
>=20
> _______________________________________________________________
>=20
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> phpPgAdmin-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phppgadmin-users

--=20