Re: [GENERAL] Access Problem After Version Upgrade -- Update

2006-01-30 Thread George Woodring
We had the same problem after re-compiling on 8.1.2. We had to edit the /etc/ld.so.conf file and add "/usr/local/pgsql/lib" manually. There is a mention to this in the DBD::Pg readme file. Woody iGLASS Networks 211-A S. Salem St Apex NC 27502 (919) 387-3

Re: [GENERAL] Access Problem After Version Upgrade -- FIXED

2006-01-26 Thread Doug McNaught
Rich Shepard <[EMAIL PROTECTED]> writes: > On Thu, 26 Jan 2006, Joshua D. Drake wrote: > >> Although I am glad you were able to get up and running, typically you don't >> want to "move" libs like that. Instead update your /etc/ld.so.conf and run >> ldconfig. > >True, Josh. What I'd prefer to d

Re: [GENERAL] Access Problem After Version Upgrade -- FIXED

2006-01-26 Thread Rich Shepard
On Thu, 26 Jan 2006, Joshua D. Drake wrote: Although I am glad you were able to get up and running, typically you don't want to "move" libs like that. Instead update your /etc/ld.so.conf and run ldconfig. True, Josh. What I'd prefer to do is remove /usr/local/pgsql/ once I know that nothing

Re: [GENERAL] Access Problem After Version Upgrade -- FIXED

2006-01-26 Thread Joshua D. Drake
Here, it was the move from /usr/local/pgsql to /var/lib/pgsql that caused me all this grief. A huge "thank you" to all of you -- and especially Jim. Although I am glad you were able to get up and running, typically you don't want to "move" libs like that. Instead update your /etc/ld.so.c

Re: [GENERAL] Access Problem After Version Upgrade -- FIXED

2006-01-26 Thread Rich Shepard
On Thu, 26 Jan 2006, Rich Shepard wrote: What do I do to trace the source of this problem and fix it? Thanks to Jim I found that libpq.so.3 were in the old directory. As soon as I moved them to /usr/lib (with libpq.so.4), SQL-Ledger allowed me to log in. All of this reminds me of the tim

Re: [GENERAL] Access Problem After Version Upgrade -- Update

2006-01-26 Thread Rich Shepard
On Thu, 26 Jan 2006, Jim Buttafuoco wrote: looks like perl/DBD::Pg is looking for libpq.so.3 but postgresql 8.1.X supplies libpq.so.4. You need to rebuild DBD::Pg to get this to work (atleast that is what I have been doing for my upgrades from 7.4.X to 8.1.2) Jim, I thought I had mentioned

Re: [GENERAL] Access Problem After Version Upgrade -- Update

2006-01-26 Thread Tom Lane
Rich Shepard <[EMAIL PROTECTED]> writes: > install_driver(Pg) failed: Can't load > '/usr/lib/perl5/site_perl/5.8.7/i486-linux/auto/DBD/Pg/Pg.so' for module > DBD::Pg: libpq.so.3: cannot open shared object file: No such file or > directory at /usr/lib/perl5/5.8.7/i486-linux/DynaLoader.pm line 230

Re: [GENERAL] Access Problem After Version Upgrade -- Update

2006-01-26 Thread Jim Buttafuoco
AIL PROTECTED]> To: Doug McNaught <[EMAIL PROTECTED]> Cc: pgsql-general@postgresql.org Sent: Thu, 26 Jan 2006 09:30:05 -0800 (PST) Subject: Re: [GENERAL] Access Problem After Version Upgrade -- Update > On Thu, 26 Jan 2006, Doug McNaught wrote: > > > That's a webserver error

Re: [GENERAL] Access Problem After Version Upgrade

2006-01-26 Thread Rich Shepard
On Thu, 26 Jan 2006, Tom Lane wrote: That's got the wrong ownership (should be postgres not root) Tom, I wondered about that. and the wrong permissions (should be world-writable). Did somebody do something silly like chown everything in /tmp? Not me ... intentionally. You could manu

Re: [GENERAL] Access Problem After Version Upgrade -- Update

2006-01-26 Thread Rich Shepard
On Thu, 26 Jan 2006, Doug McNaught wrote: That's a webserver error usually meaning a CGI script crashed or gave bad output. Look in the webserver error log file to see what happened. Doug, Sigh. All I see there are references to SQL-Ledger scripts not finding libraries (which are installed

Re: [GENERAL] Access Problem After Version Upgrade -- Update

2006-01-26 Thread Doug McNaught
Rich Shepard <[EMAIL PROTECTED]> writes: >So, now I can see the tables in the various databases, but SQL-Ledger still > cannot: > > Internal Server Error > The server encountered an internal error or misconfiguration and was unable > to complete your request. > >How do I get this fixed, pl

Re: [GENERAL] Access Problem After Version Upgrade

2006-01-26 Thread Tom Lane
Rich Shepard <[EMAIL PROTECTED]> writes: > Now, I don't know that the server is accepting connections, but > srwxr-xr-x 1 root root 0 2006-01-21 14:53 /tmp/.s.PGSQL.5432= > exists as a socket. >What do I do to trace the source of this problem and fix it? That's got the wrong ownership (shoul

Re: [GENERAL] Access Problem After Version Upgrade

2006-01-26 Thread Rich Shepard
On Thu, 26 Jan 2006, Sean Davis wrote: You did start the server? Did you fix the pg_hba.conf file? Does your postgresql.conf file allow tcp connections? Those are the places I would look. Sean, Thank you. Yes, the server is running: 21839 ?S 0:00 /usr/bin/postmaster -D /v

Re: [GENERAL] Access Problem After Version Upgrade -- Update

2006-01-26 Thread Rich Shepard
On Thu, 26 Jan 2006, Rich Shepard wrote: psql: could not connect to server: Permission denied What do I do to trace the source of this problem and fix it? Some progress to report. A Google search found a reply from Tom Lane last month to someone reporting the same error. I changed permis

Re: [GENERAL] Access Problem After Version Upgrade

2006-01-26 Thread Sean Davis
On 1/26/06 11:53 AM, "Rich Shepard" <[EMAIL PROTECTED]> wrote: >Last week I upgraded from -7.4.3 to -8.1.2. I had some problems moving data > because of both my ignorance of the proper syntax and the move from > /usr/local/pgsql to /var/lib/pgsql. Now I cannot access the server: > > [EMAIL

[GENERAL] Access Problem After Version Upgrade

2006-01-26 Thread Rich Shepard
Last week I upgraded from -7.4.3 to -8.1.2. I had some problems moving data because of both my ignorance of the proper syntax and the move from /usr/local/pgsql to /var/lib/pgsql. Now I cannot access the server: [EMAIL PROTECTED] ~]$ psql -l psql: could not connect to server: Permission denied