health
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Health] Issues connecting from Tryton Client


From: Rodrigo Rodenbeek
Subject: Re: [Health] Issues connecting from Tryton Client
Date: Fri, 23 Jun 2017 17:33:11 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1

Hello, Robert.

In this case the installation of Tryton server 4.4.1 is not necessary. The installation of GNU health,

install the tryton server version 3.8. So you just have to use client 3.8. You can uninstall pip version of tryton server.


Regards,
Rodrigo

On 22/06/17 21:54, Robert Schilt wrote:
Hi,

I have just installed / setup a fresh Tryton / GNU Health Server by following standard instructions at:

Server is running Ubuntu 16.04 and is fully patched 
Postgres is version 9.5
Tryton Server installed using pip and is at version 4.4.1
GNU Health as per install instructions (https://ftp.gnu.org/gnu/health/gnuhealth-setup-latest.tar.gz) is at version 3.08

Incoming Ports open on Server are: 22 and 8000.

Installation of server components seems to have completed successfully and Tryton Server starts without any errors:

2840 139921866721024 [2017-06-23 01:46:16,562] INFO trytond.server using /home/gnuhealth/gnuhealth/tryton/server/config/trytond.conf as configuration file
2840 139921866721024 [2017-06-23 01:46:16,562] INFO trytond.server initialising distributed objects services
2840 139921866721024 [2017-06-23 01:46:16,574] INFO trytond.server starting JSON-RPC protocol on *:8000

I then installed Tryton client (v4.4.0) on my Windows 10 Laptop - again as per standard instructions - all OK.

The when I try to connect to Tryton Server from my Windows client - I get a "Could not connect to the server" error message.

My trytond.conf is as follows:

[database]
uri = postgresql://localhost:5432
#uri = postgresql://localhost:8000
path = /home/gnuhealth/attach
[session]
super_pwd = KeMDfQKVJMbYc
[jsonrpc]
listen = *:8000

My pg_hba.conf is as follows:

# Database administrative login by Unix domain socket
local   all             postgres                                peer
# TYPE  DATABASE        USER            ADDRESS                 METHOD
# "local" is for Unix domain socket connections only
#local  all             all                                     peer
local   all             all                                     trust
# IPv4 local connections:
#host    all             all             127.0.0.1/32            md5
host    all             all             127.0.0.1/32            trust
# IPv6 local connections:
host    all             all             ::1/128                 md5


Any form of assistance / guidance to get this working would be greatly appreciated.

Regards,

Robert Schilt





reply via email to

[Prev in Thread] Current Thread [Next in Thread]