Checking Server connection on a text-only installation
35 views
Skip to first unread message
Axel Braun
Nov 30, 2017, 12:39:15 AM11/30/17
to tryton-dev
Morning,
I can access a server with a working Tryton installation remote per SSH - no
GUI installed.
Is there a way to check if connections to the server are accepted? means, Can I
simulate the server connection from the commandline somehow? Proteus maybe?
(connection check via telnet is not working...)
Thanks
Axel
Nicolas Évrard
Nov 30, 2017, 1:51:23 AM11/30/17
to tryton-dev
* Axel Braun [2017-11-30 06:39 +0100]:
>Morning,
Hello,
If the server is running and listening and if telnet does not work
then you can not reach the server and it's probably a network
configuration issue.
--
Nicolas Évrard - B2CK SPRL
E-mail/Jabber: nicolas...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
>Morning,
Hello,
then you can not reach the server and it's probably a network
configuration issue.
--
Nicolas Évrard - B2CK SPRL
E-mail/Jabber: nicolas...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
Sergi Almacellas Abellana
Nov 30, 2017, 3:21:13 AM11/30/17
to tryto...@googlegroups.com
El 30/11/17 a les 07:51, Nicolas Évrard ha escrit:
curl -H "Content-Type: application/json" -d '{"method":
"common.db.list", "params": []}' -X POST http://localhost:8000/
This will validate that the server is up and it can connect to the
database.
Hope it helps.
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
> * Axel Braun [2017-11-30 06:39 +0100]:
>> Morning,
>
> Hello,
>
>> I can access a server with a working Tryton installation remote per
>> SSH - no
>> GUI installed.
>> Is there a way to check if connections to the server are accepted?
>> means, Can I
>> simulate the server connection from the commandline somehow? Proteus
>> maybe?
>> (connection check via telnet is not working...)
>
> If the server is running and listening and if telnet does not work
> then you can not reach the server and it's probably a network
> configuration issue.
You can also use curl to list all the databases with the following comand:
>> Morning,
>
> Hello,
>
>> I can access a server with a working Tryton installation remote per
>> SSH - no
>> GUI installed.
>> Is there a way to check if connections to the server are accepted?
>> means, Can I
>> simulate the server connection from the commandline somehow? Proteus
>> maybe?
>> (connection check via telnet is not working...)
>
> If the server is running and listening and if telnet does not work
> then you can not reach the server and it's probably a network
> configuration issue.
curl -H "Content-Type: application/json" -d '{"method":
"common.db.list", "params": []}' -X POST http://localhost:8000/
This will validate that the server is up and it can connect to the
database.
Hope it helps.
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
Axel Braun
Dec 5, 2017, 4:45:54 PM12/5/17
to tryton-dev
Am Donnerstag, 30. November 2017 07:51:23 UTC+1 schrieb Nicolas Évrard:
> * Axel Braun [2017-11-30 06:39 +0100]:
> >Morning,
>
> Hello,
>
> >I can access a server with a working Tryton installation remote per SSH - no
> >GUI installed.
> >Is there a way to check if connections to the server are accepted? means, Can I
> >simulate the server connection from the commandline somehow? Proteus maybe?
> >(connection check via telnet is not working...)
>
> If the server is running and listening and if telnet does not work
> then you can not reach the server and it's probably a network
> configuration issue.
no....try
> * Axel Braun [2017-11-30 06:39 +0100]:
> >Morning,
>
> Hello,
>
> >I can access a server with a working Tryton installation remote per SSH - no
> >GUI installed.
> >Is there a way to check if connections to the server are accepted? means, Can I
> >simulate the server connection from the commandline somehow? Proteus maybe?
> >(connection check via telnet is not working...)
>
> If the server is running and listening and if telnet does not work
> then you can not reach the server and it's probably a network
> configuration issue.
telnet localhost 8000
on a working installation. You should get:
> telnet localhost 8000
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Axel Braun
Dec 5, 2017, 4:49:09 PM12/5/17
to tryton-dev
Thanks!
Nicolas Évrard
Dec 5, 2017, 5:30:23 PM12/5/17
to tryton-dev
* Axel Braun [2017-12-05 22:45 +0100]:
telnet tries to connect in IPv6 to localhost
>telnet: connect to address ::1: Connection refused
He was not able to do it
>Trying 127.0.0.1...
^^^^^^^^^
Now telnet is trying IPv4
>Connected to localhost.
And the connection is successful.
That's why you were able to use curl from pokoli's answer.
>Am Donnerstag, 30. November 2017 07:51:23 UTC+1 schrieb Nicolas Évrard:
>> * Axel Braun [2017-11-30 06:39 +0100]:
>> >Morning,
>>
>> Hello,
>>
>> >I can access a server with a working Tryton installation remote per SSH - no
>> >GUI installed.
>> >Is there a way to check if connections to the server are accepted? means, Can I
>> >simulate the server connection from the commandline somehow? Proteus maybe?
>> >(connection check via telnet is not working...)
>>
>> If the server is running and listening and if telnet does not work
>> then you can not reach the server and it's probably a network
>> configuration issue.
>
>no....try
>telnet localhost 8000
>on a working installation. You should get:
>> telnet localhost 8000
>Trying ::1...
^^^
>> * Axel Braun [2017-11-30 06:39 +0100]:
>> >Morning,
>>
>> Hello,
>>
>> >I can access a server with a working Tryton installation remote per SSH - no
>> >GUI installed.
>> >Is there a way to check if connections to the server are accepted? means, Can I
>> >simulate the server connection from the commandline somehow? Proteus maybe?
>> >(connection check via telnet is not working...)
>>
>> If the server is running and listening and if telnet does not work
>> then you can not reach the server and it's probably a network
>> configuration issue.
>
>no....try
>telnet localhost 8000
>on a working installation. You should get:
>> telnet localhost 8000
>Trying ::1...
telnet tries to connect in IPv6 to localhost
>telnet: connect to address ::1: Connection refused
>Trying 127.0.0.1...
^^^^^^^^^
Now telnet is trying IPv4
>Connected to localhost.
And the connection is successful.
That's why you were able to use curl from pokoli's answer.
Reply all
Reply to author
Forward
0 new messages