issues with trytond and postgresql on different VMs

[M. Murray]

Dear Tryton Community, 

I am having a situation that I can't seem to figure out a solution for. 

I have configured two Debian based virtual machines, both running on the same host. One to run trytond and nginx and the other to run postgresql.

I had no problems running 

trytond -c /path-to/config/file -d name_of_db --all

But, when I start up the trytond to install modules, I cannot login. If I type the wrong password, I get the bad password message. If I type the correct password, I get the timeout password prompt. If I type the password again, I get an error and that appears to be entirely client side.

If I copy the database into a postgresql instance on the same VM as trytond, it works as normal.

For some additional context, the hypervisor is QEMU/KVM and i'm using Tryton 3.4 with GNU Health and a few custom modules. I can also comfortably connect to the database server from the tryton server using psql and when I use trytond -u <module> it does not give any errors. 

And I have tested it using the bridged network and using an internal network between the VMs. The result is the same. 

Any help would be appreciated.

Thanks 

-MM

[Cédric Krier]

On 2016-02-10 14:35, M. Murray wrote:
> Dear Tryton Community,
>
> I am having a situation that I can't seem to figure out a solution for.
>
> I have configured two Debian based virtual machines, both running on the
> same host. One to run trytond and nginx and the other to run postgresql.
>
> I had no problems running
> trytond -c /path-to/config/file -d name_of_db --all
>
> But, when I start up the trytond to install modules, I cannot login. If I
> type the wrong password, I get the bad password message. If I type the

> correct password, I get the *timeout* password prompt. If I type the

> password again, I get an error and that appears to be entirely client side.
>
> If I copy the database into a postgresql instance on the same VM as
> trytond, it works as normal.
>
> For some additional context, the hypervisor is QEMU/KVM and i'm using
> Tryton 3.4 with GNU Health and a few custom modules. I can also comfortably
> connect to the database server from the tryton server using psql and when I
> use trytond -u <module> it does not give any errors.
>
> And I have tested it using the bridged network and using an internal
> network between the VMs. The result is the same.
>
> Any help would be appreciated.

Maybe the problem comes from the client trying first to connect with SSL
before drop to clear connection. Maybe nginx doesn't like it.

Or maybe you have a clock issue. And so the session expires directly
after being created.

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

[M. Murray]

On Wednesday, February 10, 2016 at 6:20:04 PM UTC-5, Cédric Krier wrote:

Or maybe you have a clock issue. And so the session expires directly
after being created.

apt install ntpdate && ntpdate-debian

Problem fixed. 

Thanks.

 

[Hendrik Brandes]

Have you checked, if postgres accepts connections other than localhost? Plesse check pg_hba.conf and postmaster.conf.