使用 Ubuntu 服务器的 Digital Ocean 上的领域对象服务器
Realm Object Server on Digital Ocean using Ubuntu Server
我在 Digital Ocean 上使用领域对象服务器 运行 Ubuntu 服务器上的最低选项（$5/月）。我不断收到连接被拒绝的错误；而且我不知道错误是来自DO还是ROS。
我不是Ubuntu方面的专家；因此，我进入并清除了 /var/log 中的所有日志并尝试重新连接。当有大量记录要同步时，我不断收到以下错误（在 iOS，客户端）：
2017-07-05 18:55:46.983543+0300 Torba[1783:2024434] Sync: Connection[1]: Resolving '207.154.251.37:9080'
2017-07-05 18:55:46.986087+0300 Torba[1783:2024434] Sync: Connection[1]: Connecting to endpoint '207.154.251.37:9080' (1/1)
2017-07-05 18:55:47.045242+0300 Torba[1783:2024434] Sync: Connection[1]: Failed to connect to endpoint '207.154.251.37:9080': Connection refused
2017-07-05 18:55:47.045387+0300 Torba[1783:2024434] Sync: Connection[1]: Failed to connect to '207.154.251.37:9080': All endpoints failed
2017-07-05 18:55:47.125378+0300 Torba[1783:2024434] Sync: Connection[3]: Resolving '207.154.251.37:9080'
2017-07-05 18:55:47.126805+0300 Torba[1783:2024434] Sync: Connection[3]: Connecting to endpoint '207.154.251.37:9080' (1/1)
2017-07-05 18:55:47.178626+0300 Torba[1783:2024434] Sync: Connection[3]: Failed to connect to endpoint '207.154.251.37:9080': Connection refused
2017-07-05 18:55:47.178830+0300 Torba[1783:2024434] Sync: Connection[3]: Failed to connect to '207.154.251.37:9080': All endpoints failed
2017-07-05 18:55:49.677104+0300 Torba[1783:2024434] Sync: Connection[1]: Resolving '207.154.251.37:9080'
2017-07-05 18:55:49.678640+0300 Torba[1783:2024434] Sync: Connection[1]: Connecting to endpoint '207.154.251.37:9080' (1/1)
2017-07-05 18:55:49.727078+0300 Torba[1783:2024434] Sync: Connection[1]: Failed to connect to endpoint '207.154.251.37:9080': Connection refused
2017-07-05 18:55:49.727283+0300 Torba[1783:2024434] Sync: Connection[1]: Failed to connect to '207.154.251.37:9080': All endpoints failed
在ubuntu这边，清除所有日志后，当我尝试连接到服务器时，又创建了一个日志，appport.log，内容如下：
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: called for pid 32448, signal 6, core limit 18446744073709551615
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: executable: /usr/lib/realm-object-server-developer/node/bin/node (command line "/usr/lib/realm-object-server-developer/node/bin/node /usr/bin/realm-object-server -c /etc/realm/configuration.yml")
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: apport: report /var/crash/_usr_lib_realm-object-server-developer_node_bin_node.999.crash already
从日志中我无法确定错误是在 Realm 端还是 Digital Ocean 端。任何人都可以帮忙，有什么想法吗？
仔细阅读日志后，我发现是 Realm Object Server 崩溃了。我还不知道为什么，但现在我知道问题出在 ROS 上。
* 编辑 *
由于内存不足，应用程序崩溃了。通过增加服务器的内存，一切都按预期开始工作。
Jul 05 15:55:33 torba-test systemd[1]: realm-object-server.service: Main process exited, code=killed, status=6/ABRT
Jul 05 15:55:33 torba-test systemd[1]: realm-object-server.service: Unit entered failed state.
Jul 05 15:55:33 torba-test systemd[1]: realm-object-server.service: Failed with result 'signal'.
Jul 05 15:55:34 torba-test systemd[1]: realm-object-server.service: Service hold-off time over, scheduling restart.
Jul 05 15:55:34 torba-test systemd[1]: Stopped Realm Object Server.
我在 Digital Ocean 上使用领域对象服务器 运行 Ubuntu 服务器上的最低选项（$5/月）。我不断收到连接被拒绝的错误；而且我不知道错误是来自DO还是ROS。
我不是Ubuntu方面的专家；因此，我进入并清除了 /var/log 中的所有日志并尝试重新连接。当有大量记录要同步时，我不断收到以下错误（在 iOS，客户端）：
2017-07-05 18:55:46.983543+0300 Torba[1783:2024434] Sync: Connection[1]: Resolving '207.154.251.37:9080'
2017-07-05 18:55:46.986087+0300 Torba[1783:2024434] Sync: Connection[1]: Connecting to endpoint '207.154.251.37:9080' (1/1)
2017-07-05 18:55:47.045242+0300 Torba[1783:2024434] Sync: Connection[1]: Failed to connect to endpoint '207.154.251.37:9080': Connection refused
2017-07-05 18:55:47.045387+0300 Torba[1783:2024434] Sync: Connection[1]: Failed to connect to '207.154.251.37:9080': All endpoints failed
2017-07-05 18:55:47.125378+0300 Torba[1783:2024434] Sync: Connection[3]: Resolving '207.154.251.37:9080'
2017-07-05 18:55:47.126805+0300 Torba[1783:2024434] Sync: Connection[3]: Connecting to endpoint '207.154.251.37:9080' (1/1)
2017-07-05 18:55:47.178626+0300 Torba[1783:2024434] Sync: Connection[3]: Failed to connect to endpoint '207.154.251.37:9080': Connection refused
2017-07-05 18:55:47.178830+0300 Torba[1783:2024434] Sync: Connection[3]: Failed to connect to '207.154.251.37:9080': All endpoints failed
2017-07-05 18:55:49.677104+0300 Torba[1783:2024434] Sync: Connection[1]: Resolving '207.154.251.37:9080'
2017-07-05 18:55:49.678640+0300 Torba[1783:2024434] Sync: Connection[1]: Connecting to endpoint '207.154.251.37:9080' (1/1)
2017-07-05 18:55:49.727078+0300 Torba[1783:2024434] Sync: Connection[1]: Failed to connect to endpoint '207.154.251.37:9080': Connection refused
2017-07-05 18:55:49.727283+0300 Torba[1783:2024434] Sync: Connection[1]: Failed to connect to '207.154.251.37:9080': All endpoints failed
在ubuntu这边，清除所有日志后，当我尝试连接到服务器时，又创建了一个日志，appport.log，内容如下：
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: called for pid 32448, signal 6, core limit 18446744073709551615
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: executable: /usr/lib/realm-object-server-developer/node/bin/node (command line "/usr/lib/realm-object-server-developer/node/bin/node /usr/bin/realm-object-server -c /etc/realm/configuration.yml")
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 32499) Wed Jul 5 15:55:15 2017: apport: report /var/crash/_usr_lib_realm-object-server-developer_node_bin_node.999.crash already
从日志中我无法确定错误是在 Realm 端还是 Digital Ocean 端。任何人都可以帮忙，有什么想法吗？
仔细阅读日志后，我发现是 Realm Object Server 崩溃了。我还不知道为什么，但现在我知道问题出在 ROS 上。
* 编辑 * 由于内存不足，应用程序崩溃了。通过增加服务器的内存，一切都按预期开始工作。
Jul 05 15:55:33 torba-test systemd[1]: realm-object-server.service: Main process exited, code=killed, status=6/ABRT
Jul 05 15:55:33 torba-test systemd[1]: realm-object-server.service: Unit entered failed state.
Jul 05 15:55:33 torba-test systemd[1]: realm-object-server.service: Failed with result 'signal'.
Jul 05 15:55:34 torba-test systemd[1]: realm-object-server.service: Service hold-off time over, scheduling restart.
Jul 05 15:55:34 torba-test systemd[1]: Stopped Realm Object Server.