Forum OpenACS Q&A: ::sigh:: More port 80 related errors :(

Collapse
1: ::sigh:: More port 80 related errors :(
Posted by David Lee on 03/23/06 05:20 AM
So this time I turned my debug on true so I could get more detailed analysis of the problem...so this is what's wrong:

I ran the command: /var/lib/aolserver/mathing/etc/daemontools/run
I changed the run file according to instructions (changing the -u and -g and adding -b 192.168.123.196:80)

These are the errors from error.log
Error: NsPgOpenDb(postgres): Could not connect to localhost::mathing: FATAL: IDENT authentication failed for user "mathing"
Error: dbdrv: failed to open database 'postgres:localhost::mathing'
Warning: Database API: couldn't allocate a handle from database pool "pool2".
Error: Database API: RDBMS type could not be determined for any pool.
Error: Bootstrap:

The following database pools generated errors:

  • OpenACS could not allocate a handle from database pool "pool2".

Possible causes might include:

  • The database is not running.
  • The database driver has not been correctly installed.
  • The datasource or database user/password are incorrect.
  • You didn't define any database pools.

Collapse
2: Re: ::sigh:: More port 80 related errors :( (response to 1)
Posted by Steve Manning on 03/23/06 10:03 AM
David

I dont think thats a port 80 problem. I think it can't connect to your Postgres server. Probably becuase the user your trying to connect with doesn't exist on Postgres. ( NsPgOpenDb(postgres): Could not connect to localhost::mathing: FATAL: IDENT authentication failed for user "mathing").

Also check that you have tcp sockets enabled in the postgresql.conf file and that you have permission in the pg_hba.conf file.

- Steve