On 10/15/2013 05:58 PM, Stuart Cracraft wrote:
More to the point:
telnet localhost 5432
on the box works to connect to port 5432 and postgres.
However,
telnet fully-qualified-name-of-localhost 5432
gets a Connection Refused.
Making the assumption that you have a single DB and Web server and are
not splitting them between two boxen, and further assuming that you are
not on the box when you run this command, then this would not be unusual
- in such a configuration, you'd want it to only listen on localhost.
If you are on the box doing the telnet then the issue is most likely
that your `/etc/hosts` is lacking a line for the machine's native host
name. Essentially, a machine always needs to be able to resolve its own
name, regardless of whether DNS is working or not. So, it's customary to
have lines like:
127.0.0.1 localhost
127.0.1.1 fully-qualified-name-of-localhost
unqualified-name-of-localhost
The fix here was in postgresql.conf to update the
listen_addresses = '*'
(for development only)
field appropriately (uncommenting it) and port = 5432 lines
and restarting postgresql with
/etc/init.d/postgresql restart
then retesting with the above telnets...
Okay, and once that is done (and the telnet connection works), is trac
now able to connect?
If not, does the postgres log happen to report anything useful?
Also if not, what happens if you attempt to connect to that port using
the same credentials and the normal psql client?
--
Matthew Caron, Software Build Engineer
Red Lion Controls | www.redlion.net
+1 (518) 877-5173 x138 office
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/groups/opt_out.