DB on Linux server?

[fyl2u]

you using "trust" instead of md5 encryption?


susan

yes. shouldn't I be?

[keggler]

post up your pg_hba.conf & postgressql.conf from the server and an ipconfig /all (or linux) equivalent; from both server and clients...


susan

[fyl2u]

Code: Select all

gate:/etc/postgresql# vi pg_hba.conf
# work since the configuration files are only symlinked from
# POSTGRES_DATA.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect, or use
# "pg_ctl reload".
#
# Upstream default configuration
#
# The following configuration is the upstream default, which allows
# unrestricted access to amy database by any user on the local machine.
#
# TYPE  DATABASE    USER        IP-ADDRESS        IP-MASK           METHOD
#
#local   all         all                                             trust
# IPv4-style local connections:
#host    all         all         127.0.0.1         255.255.255.255   trust
# IPv6-style local connections:
#
# Put your actual configuration here
# ----------------------------------
#
# This default configuration allows any local user to connect as himself
# without a password, either through a Unix socket or through TCP/IP; users
# on other machines are denied access.
#
# If you want to allow non-local connections, you need to add more
# "host" records before the final line that rejects all TCP/IP connections.
# Also, remember TCP/IP connections are only enabled if you enable
# "tcpip_socket" in /etc/postgresql/postgresql.conf.
#
# DO NOT DISABLE!
# If you change this first entry you will need to make sure the postgres user
# can access the database using some other method.  The postgres user needs
# non-interactive access to all databases during automatic maintenance
# (see the vacuum command and the /usr/lib/postgresql/bin/do.maintenance
# script).
#
# TYPE  DATABASE    USER        IP-ADDRESS        IP-MASK           METHOD
# Database administrative login by UNIX sockets
local   all         postgres                                        ident sameuser
#
# All other connections by UNIX sockets
local   all         all                                             ident sameuser
#
# All IPv4 connections from localhost
host    all         all         127.0.0.1         255.255.255.255   ident sameuser
host    all         all         192.168.70.155    255.255.255.0     trust
host    all         all         192.168.70.159    255.255.255.0     trust
#
# All IPv6 localhost connections
host    all         all         ::1               ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff        ident sameuser
host    all         all         ::ffff:127.0.0.1/128                ident sameuser
#
# reject all other connection attempts
host    all         all         0.0.0.0           0.0.0.0           reject


[fyl2u]

^^ that one works on the laptop but for some reason I can't get my desktop to connect to the registration server at the moment, so I can only attempt the connection from the startup of PT3 in trial mode (does trial mode allow db connections over a network?)

[fyl2u]

Also, do I need to install postgress on my PC for my first startup of PT3, then uninstall it after I've configured PT for networked db or should I be able to get into PT without postgres being setup or a default db anyway?

[keggler]

so what have you changed since: host all all 192.168.70.155 255.255.255.0 trust

worked?

is this still the ip of the laptop?

i think trial versions still allow network access...

to answer your last post; either...


susan

[fyl2u]

host all all 192.168.70.155 255.255.255.0 trust <-laptop
host all all 192.168.70.159 255.255.255.0 trust <-desktop

It works on the laptop, but still not on the desktop.
I can't get PT to start on the desktop - I've tried putting in the server info in the box that appears requesting login to a postgresql service at startup of PT, but it's not having it - PT simply refuses to boot up without any postgresql service present.

...and I still can't connect to the registration server to register it as a full version of PT on the desktop.

[keggler]

on the desktop then, uninstall pt, download the pt + postgres bundle and install; this will crete an empty db on the desktop, but at least pt will start, then you just browse to the debian db and set as active/default.


susan

[fyl2u]

on the desktop then, uninstall pt, download the pt + postgres bundle and install; this will crete an empty db on the desktop, but at least pt will start, then you just browse to the debian db and set as active/default.


susan

Yeah, looks like I'll have to.

I was hoping it wouldn't come to that :)

[fyl2u]

Hmmn.

Trying to install PT3 B14 with postgres... PT install process seemed fine, but then I've tried to start PT and as expected, it's started to install postgres, but when it gets to "start service" it pauses for ages then says "postgres service failed to start. Verify that you have sufficient privileges to start a service. retry / cancel" - I'm on my 3rd retry now, but it's not looking hopeful.

Any ideas, anyone?