Hi Bob - I'm hours limited as a part time contractor, hence my delayed response. The default log for my postgresql is in my 8.3 install location /opt/PostgreSQL/8.3/data/pg_log The last log file from 11/23 contains a Fatal: "2009-11-23 10:17:42 MSTFATAL: database "daemon" does not exist" It also appears my postgresql.conf file has most of the logging related entries commented out by default. Should other statements beyond "log_statement" be turned on, and in the case of "log_statement" be set to "all"? After setting "log_statement = all" I restarted postgresql and the new log file contains: 2009-11-23 10:50:52 MSTLOG: database system was shut down at 2009-11-23 10:50:48 MST 2009-11-23 10:50:52 MSTLOG: database system is ready to accept connections 2009-11-23 10:50:52 MSTLOG: autovacuum launcher started 2009-11-23 10:55:50 MSTFATAL: database "daemon" does not exist 2009-11-23 10:55:58 MSTFATAL: database "daemon" does not exist Additionally I'm seeking to verify the instructions in 2.2.3 item 1 which states the need to have user apache or www-data added to the group fossy, which I do not recall performing explicitly or the postinstall script doing that. I'm also seeking some admin assistance in attempting to verify all of the setup & configuration steps in this section of the documentation. I suspect the root of my issue having something to do with the apache, postgresql, and fossology database interaction and setup related tasks related to those. Thanks -- Bill
________________________________ From: Gobeille, Robert [mailto:[email protected]] Sent: Thu 11/19/2009 1:53 PM To: Bill Armstrong Cc: [email protected] Subject: Re: [FOSSology] Post Install issue: Initial Login attempt failed Hi Bill, I assume you did, but just to confirm, you tried to login with NO password, right? We will have to remember to reset the fossy password later so that the value in Db.conf is correct. I should have told you to create a new user with psql and not mess with fossy. My mistake. But for now, let's focus on the login problem. When you are logging in you are authenticating against your fossology user/pass (not the db or system user/pass). The fossology user/pass is stored in the fossology users table. If you have any error accessing the users table, you will see the behavior you do. So what we need to know is if postgres attempted to excecute the query (select * from users ...). If it did not, then the problem is pg_hba blocking access from your webserver. If it did attempt to execute that query, then we need to know if the query failed. Did you look for errors in the postgresql log file: /var/log/postgresql/postgresql-8.3-main.log The easiest way is to tail -f /var/log/postgresql/postgresql-8.3-main.log and then attempt to log in. If you see an error, then that will tell us what the problem is. However, you might not see anything depending on your pg_hba.conf and/or postgresql.conf. pg_hba.conf (/etc/postgresql/8.3/main/pg_hba.conf) can prevent the client from other connecting to the db. This is talked about in section 2.2.3 in the install doc. The postgresql.conf has settings to control what is being logged. /etc/postgresql/8.3/main//postresql.conf http://www.postgresql.org/docs/8.3/interactive/runtime-config-logging.html we would want "log_statement" to be on. Bob On Nov 19, 2009, at 12:25 PM, Bill Armstrong wrote: Bob - bash-3.2# psql -U fossy fossology Welcome to psql 8.1.18 (server 8.3.8), the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit WARNING: You are connected to a server with major version 8.3, but your psql client is major version 8.1. Some backslash commands, such as \d, might not work properly. fossology=> update users set user_pass='',user_seed='' where user_name='fossy'; UPDATE 1 fossology=> Reload http:// <http:///> <hostname>/repo/ Still unable to login, just returns me back to login prompt. This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
_______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
