Chapter 5. General Troubleshooting

Table of Contents
I created a project, but it does not show up in the Project list on the Enter Problem Report dialog. What is going on?
I want to assign a problem report to someone, but there is no one in the Responsible drop down list. What is going on?
I created a PRepS user, but they cannot log on. Why not?
Why is PRepS complaining about database schema versions?
The create_prepsdb or update_prepsdb script asks for passwords and then fails?

I created a project, but it does not show up in the Project list on the Enter Problem Report dialog. What is going on?

You have not selected yourself as a submitter for the project. Edit the project. Go to the Submitters tab and select yourself as a submitter.

If you are sure that you are selected as a submitter for the project, and the project still does not show up, make sure the project is active.

I want to assign a problem report to someone, but there is no one in the Responsible drop down list. What is going on?

You have not selected any project members for the project. Edit the project. Go to the Project Members tab and select some project members.

I created a PRepS user, but they cannot log on. Why not?

Did you remember to also create a PostgreSQL account for that user? To make sure, use psql to determine if the user is in pg_shadow. For example, to see if user 'zab' is in pg_shadow, you would do something similar to the following. Please note that the following commands must be run by the PostgreSQL super user.
% psql myprs
Welcome to psql, the PostgreSQL interactive terminal.
 
Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help on internal slash commands
       \g or terminate with semicolon to execute query
       \q to quit                                                               

myprs=# select usename from pg_shadow;
 usename
----------
 postgres
 stuffle
 lasode
 zab
(4 rows)
 
myprs=# 
Make sure the login ID for the user you are interested in is listed.

Why is PRepS complaining about database schema versions?

The version of PRepS you are running is not compatible with the PRepS database you are attempting to connect to. One of two things happened: your database was updated, but you never installed a newer version of PRepS, or you installed a new version of PRepS but did not run update_prepsdb on the existing PRepS databases. In the former case, install a newer version of PRepS. In the latter case, update your database.

The create_prepsdb or update_prepsdb script asks for passwords and then fails?

Your PostgreSQL security is set to tight. These scripts use some PostgreSQL tools that are not very well behaved if you have the security set to anything other than "trust". Edit your pg_hba.conf file, and set the security for "local" to "trust" (at least for the time being, you can tighten it up again after you are done running your creates/updates). If you are going to use security other than trust, I suggest using settings similar to the following:
local        all                                           trust
host         all         127.0.0.1     255.255.255.255     crypt
host         all         192.168.93.2  255.255.255.255     crypt

For details, refer to the appropriate PostgreSQL documents.