Tryton客户端无法通过Internet端口8000连接

时间:2014-03-05 17:53:06

标签: port ubuntu-12.04 tryton

我让Tryton ERP在VM上本地运行,运行正常。

但是,客户端无法通过互联网连接到它。

nmap报告端口8000被“关闭”,也就是说,没有什么东西在那里听。

~# nmap -PN -p 8000 <IP>

Starting Nmap 5.21 ( http://nmap.org ) at 2014-03-05 12:29 EST
Nmap scan report for <IP>
Host is up (0.00017s latency).
PORT     STATE  SERVICE
8000/tcp closed http-alt

但是,我的trytond.conf文件看起来是正确的,有

jsonrpc = *:8000

和数据库连接参数。 (在Azure上类似的其他VM设置正常工作。) 完整的连接文件如下。

AFAIK,netstat报告它只在localhost上侦听8000端口:

~# netstat -tupan | grep 8000
tcp        0      0 127.0.0.1:8000          0.0.0.0:*               LISTEN    
        10051/python
tcp        0      0 127.0.0.1:8000          127.0.0.1:58296         ESTABLISHED 
        10051/python
tcp        0      0 127.0.0.1:58296         127.0.0.1:8000          ESTABLISHED       
        13842/python

因为在我的其他一切都很好的VM上,netstat输出是不同的:

root@Tryton:~# netstat -tupan | grep 8000
tcp6       0      0 :::8000                 :::*                    LISTEN
        1310/python

但是我做错了什么? 我唯一更改内容的参考点是trytond.conf文件,对吗?

这是:

#This file is part of Tryton.  The COPYRIGHT file at the top level of
#this repository contains the full copyright notices and license terms.
[options]

# Activate the json-rpc protocol
jsonrpc = *:8000
#ssl_jsonrpc = False

# This is the hostname used when generating tryton URI
#hostname_jsonrpc =

# Configure the path of json-rpc data
#jsondata_path = /var/www/localhost/tryton

# Activate the xml-rpc protocol
#xmlrpc = *:8069
#ssl_xmlrpc = False

# Activate the webdav protocol
#webdav = *:8080
#ssl_webdav = False

# This is the hostname used when generating WebDAV URI
#hostname_webdav =

# Configure the database type
# allowed values are postgresql, sqlite, mysql
db_type = postgresql

# Configure the database connection
#    # Note: Only databases owned by db_user will be displayed in the connection dialog
#    # of the Tryton client. db_user must have create permission for new databases
#    # to be able to use automatic database creation with the Tryton client.
db_host = localhost
db_port = 5432
db_user = postgres
db_password = postgres_password
db_minconn = 1
db_maxconn = 64

# Configure the postgresql path for the executable
#pg_path = None

# Configure the Tryton server password
admin_passwd = admin_password

# Configure the path of the files for the pid and the logs
#pidfile = False
#logfile = False

#privatekey = server.pem
#certificate = server.pem

# Configure the SMTP connection
#smtp_server = localhost
#smtp_port = 25
#smtp_ssl = False
#smtp_tls = False
#smtp_password = False
#smtp_user = False
#smtp_default_from_email = False

# Configure the path to store attachments and sqlite database
data_path = /var/lib/tryton

# Allow to run more than one instance of trytond
#multi_server = False

# Configure the session timeout (inactivity of the client in sec)
#session_timeout = 600

# Enable auto-reload of modules if changed
#auto_reload = True

# Prevent database listing
#prevent_dblist = False

# Enable cron
# cron = True

# unoconv connection
#unoconv = pipe,name=trytond;urp;StarOffice.ComponentContext

# Number of retries on database operational error
# retry = 5

# Default language code
# language = en_US

# Timezone of the server
timezone = 0

2 个答案:

答案 0 :(得分:1)

事实证明配置文件完全正确,正如我想的那样。

整个问题只是因为重新启动后Tryton服务器在更改后没有正确读取它。

Unity桌面报告它需要“重新启动以安装更新”(我不知道是从Windows?),在我这样做之后,端口会自动打开。

在系统重启之前,重新启动Tryton服务器只会产生:

sudo /etc/init.d/tryton—server restart
* Restarting Tryton Application Platform trytond
start—stop—daemon: warning: failed to kill 18175: No such process    
[ 0K ]

我已经[OK]暗示服务器已经重启了。 但不,它没有!

系统重启后,我收到了正确的消息:

sudo /etc/init.d/tryton—server restart
* Restarting Tryton Application Platform trytond
[ 0K ]

现在netstat输出也正确,客户端连接成功:

# netstat -tupan | grep 8000
tcp6       0      0 :::8000                 :::*                    LISTEN
1792/python

答案 1 :(得分:0)

我遇到了同样的问题,这实际上是我遇到麻烦的原因:

  

但是,我的trytond.conf文件看起来是正确的,有

jsonrpc = *:8000

correct syntax(至少对于最新版本,3.4到3.8)如下:

[jsonrpc]
listen = *:8000

作为旁注,使用trytond标记运行--verbose可以在控制台中进行调试(或者您也可以使用logfiles进行调整,向trytond提供--logconf logconf.conf