Amazon EC2上的Neo4j-无法从远程计算机访问 [英] Neo4j on Amazon EC2 - Not accessible from remote machines

查看:119
本文介绍了Amazon EC2上的Neo4j-无法从远程计算机访问的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我目前正在尝试使用RHEL在EC2实例上正确安装neo4j.目前,我无法从浏览器访问端口7474上的服务器来查看neo4j Webadmin或浏览器.截至目前,我可以成功访问localhost:7474,这使我相信这是远程连接的某种程度的访问问题.

I am currently attempting to get neo4j installed properly on an EC2 instance with RHEL. Currently I can not hit the server on port 7474 from a browser to see the neo4j webadmin or browser. As of right now I can successfully access localhost:7474 which leads me to believe it is some level of access issue with remote connections.

到目前为止我所做的:

  1. 在EC2实例上安装了Oracle Java 1.7
  2. 已安装neo4j-community-2.0.1
  3. 将org.neo4j.server.webserver.address = 0.0.0.0添加到neo4j-server.properties
  4. 在EC2 UI中为端口7474添加了自定义TCP规则,允许0.0.0.0/0
  5. 为iptables添加了7474
  6. 重新启动实例
  7. 运行neo4j start

在查看netstat时,我看到该进程正在侦听端口7474,因此我不确定还有什么会阻止外部流量访问端口7474上服务器的公共EC2 DNS.

Looking at netstat I see the process listening on port 7474, so I am unsure what else would be preventing external traffic from hitting the public EC2 DNS for the server on port 7474.

console.log

console.log

2014-02-24 20:25:24.572+0000 INFO  [API] Setting startup timeout to: 120000ms based on -1
2014-02-24 20:25:27.226+0000 INFO  [API] Successfully started database
2014-02-24 20:25:28.924+0000 INFO  [API] Starting HTTP on port :7474 with 10 threads available
2014-02-24 20:25:29.387+0000 INFO  [API] Enabling HTTPS on port :7473
2014-02-24 20:25:30.077+0000 INFO  [API] Mounted discovery module at [/]
2014-02-24 20:25:30.088+0000 INFO  [API] Mounted REST API at [/db/data/]
2014-02-24 20:25:30.097+0000 INFO  [API] Mounted management API at [/db/manage/]
2014-02-24 20:25:30.099+0000 INFO  [API] Mounted webadmin at [/webadmin]
2014-02-24 20:25:30.100+0000 INFO  [API] Mounted Neo4j Browser at [/browser]
2014-02-24 20:25:30.202+0000 INFO  [API] Mounting static content at [/webadmin] from [webadmin-html]
2014-02-24 20:25:30.326+0000 INFO  [API] Mounting static content at [/browser] from [browser]
15:25:30.328 [main] WARN  o.e.j.server.handler.ContextHandler - o.e.j.s.ServletContextHandler@164cc9b7{/,null,null} contextPath ends with /
15:25:30.328 [main] WARN  o.e.j.server.handler.ContextHandler - Empty contextPath
15:25:30.331 [main] INFO  org.eclipse.jetty.server.Server - jetty-9.0.5.v20130815
15:25:30.387 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.s.h.MovedContextHandler@5e9c3ce7{/,null,AVAILABLE}
15:25:30.780 [main] INFO  o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /webadmin, did not find org.apache.jasper.servlet.JspServlet
15:25:30.802 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext@488a358e{/webadmin,jar:file:/opt/neo4j-community-2.0.1/system/lib/neo4j-server-2.0.1-static-web.jar!/webadmin-html,AVAILABLE}
15:25:31.964 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@750e589{/db/manage,null,AVAILABLE}
15:25:32.759 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@1480606f{/db/data,null,AVAILABLE}
15:25:32.787 [main] INFO  o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /browser, did not find org.apache.jasper.servlet.JspServlet
15:25:32.789 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext@3f773163{/browser,jar:file:/opt/neo4j-community-2.0.1/system/lib/neo4j-browser-2.0.1.jar!/browser,AVAILABLE}
15:25:33.047 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@164cc9b7{/,null,AVAILABLE}
15:25:33.078 [main] INFO  o.e.jetty.server.ServerConnector - Started ServerConnector@14cfe45e{HTTP/1.1}{0.0.0.0:7474}
15:25:34.498 [main] INFO  o.e.jetty.server.ServerConnector - Started ServerConnector@44590060{SSL-HTTP/1.1}{0.0.0.0:7473}
2014-02-24 20:25:34.500+0000 INFO  [API] Remote interface ready and available at [http://0.0.0.0:7474/]

neo4j.0.0.log:

neo4j.0.0.log:

Feb 24, 2014 3:25:24 PM org.neo4j.server.logging.Logger log
INFO: Setting startup timeout to: 120000ms based on -1
Feb 24, 2014 3:25:27 PM org.neo4j.server.logging.Logger log
INFO: Successfully started database
Feb 24, 2014 3:25:28 PM org.neo4j.server.logging.Logger log
INFO: Starting HTTP on port :7474 with 10 threads available
Feb 24, 2014 3:25:29 PM org.neo4j.server.logging.Logger log
INFO: Enabling HTTPS on port :7473
Feb 24, 2014 3:25:30 PM org.neo4j.server.logging.Logger log
INFO: Mounted discovery module at [/]
Feb 24, 2014 3:25:30 PM org.neo4j.server.logging.Logger log
INFO: Mounted REST API at [/db/data/]
Feb 24, 2014 3:25:30 PM org.neo4j.server.logging.Logger log
INFO: Mounted management API at [/db/manage/]
Feb 24, 2014 3:25:30 PM org.neo4j.server.logging.Logger log
INFO: Mounted webadmin at [/webadmin]
Feb 24, 2014 3:25:30 PM org.neo4j.server.logging.Logger log
INFO: Mounted Neo4j Browser at [/browser]
Feb 24, 2014 3:25:30 PM org.neo4j.server.logging.Logger log
INFO: Mounting static content at [/webadmin] from [webadmin-html]
Feb 24, 2014 3:25:30 PM org.neo4j.server.logging.Logger log
INFO: Mounting static content at [/browser] from [browser]
Feb 24, 2014 3:25:31 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.9 09/02/2011 11:17 AM'
Feb 24, 2014 3:25:31 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.9 09/02/2011 11:17 AM'
Feb 24, 2014 3:25:32 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.9 09/02/2011 11:17 AM'
Feb 24, 2014 3:25:34 PM org.neo4j.server.logging.Logger log
INFO: Remote interface ready and available at [http://0.0.0.0:7474/]

推荐答案

您的EC2实例是否是VPC内安全组的一部分? 作为一种故障排除技术,您可以尝试将nginx用作可以执行80 <->> 7474的代理,并查看它是否为您提供一种至少可以在解决问题时访问它的方法...

Is your EC2 instance part of a security group within a VPC? As a troubleshooting technique - you can try to put nginx as a proxy that does 80<->7474, and see if that gives you a way to at least access it while you work through the issues...

这篇关于Amazon EC2上的Neo4j-无法从远程计算机访问的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆