首页 文章

Google Stackdriver获取不成功的HTTP请求404

提问于
浏览
0

我在AWS EC2上 . 在运行stackdriver-agent以检查代理的状态时,我正在获取HTTP请求404 .

堆栈跟踪 -

sudo service stackdriver-agent status stackdriver-agent.service - LSB:启动和停止Stackdriver Agent已加载:已加载(/etc/init.d/stackdriver-agent; bad;供应商预设:已启用)活动:自上周三起激活(正在运行) 2017-03-15 07:15:24 UTC; 34s ago Docs:man:systemd-sysv-generator(8)进程:3732 ExecStop = / etc / init.d / stackdriver-agent stop(code = exited,status = 0 / SUCCESS)进程:3754 ExecStart = / etc / init .d / stackdriver-agent start(code = exited,status = 0 / SUCCESS)任务:12内存:2.1M CPU:68ms CGroup:/system.slice/stackdriver-agent.service└─3782/opt/ stackdriver / collectd / sbin / stackdriver-collectd -C /opt/stackdriver/collectd/etc/collectd.conf -P /var/run/stackdriver-agent.pid 3月15日07:15:24 ip-10-0-5-248 collectd [3781 ]:plugin_load:插件“match_throttle_metadata_keys”已成功加载 . 3月15日07:15:24 ip-10-0-5-248 collectd [3781]:plugin_load:插件“stackdriver_agent”已成功加载 . 3月15日07:15:24 ip-10-0-5-248 collectd [3781]:plugin_load:插件“聚合”成功加载 . 3月15日07:15:24 ip-10-0-5-248 stackdriver-agent [3754]:...完成 . 3月15日07:15:24 ip-10-0-5-248 systemd [1]:启动LSB:启动和停止Stackdriver Agent . 3月15日07:15:24 ip-10-0-5-248 collectd [3782]:write_gcm:json凭证解析成功 . email = stackdriver-agent-authorizatio@myproject-1.iam.gserviceaccount.com,project = log Mar 15 07:15:24 ip-10-0-5-248 collectd [3782]:write_gcm:不成功的HTTP请求404:404 - 未找到404 - 未找到3月15日07:15:24 ip-10-0-5-248 collectd [3782]:write_gcm:wg_get_from_metadata_server取错失败http://169.254.169.254/computeMetadata/v1beta1/instance/hostname 3月15日07:15:24 ip-10-0-5-248 collectd [3782]:初始化完成,进入读循环 . 3月15日07:15:24 ip-10-0-5-248 collectd [3782]:tcpconns插件:从netlink读取成功 . 从现在开始将使用netlink方法 .

当我尝试记录异常消息JSON成功创建时,会引发网络异常

ERROR RawSocketSender:199 - org.fluentd.logger.sender.RawSocketSender java.net.ConnectException:java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl . )java.net.PlainSocketImpl.socketConnect(Native Method)的连接被拒绝(连接被拒绝) . java:350)at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)at at java..Socket.connect(Socket.java:589)org.fluentd.logger.sender.RawSocketSender.connect(RawSocketSender.java:83)at org.fluentd.logger.sender.RawSocketSender.reconnect(RawSocketSender.java: 92)org.fluentd.logger.sender.RawSocketSender.flush(RawSocketSender.java:186)org.fluentd.logger.sender.RawSocketSender.send(RawSocketSender.java:177)at org.fluentd.logger.sender.RawSocketSender .emit(RawSocketSender.java:147)at org.fluentd.logger.sender.RawSocketSender.emit(RawSocketSender . java:129)org.fluentd.logger.sender.RawSocketSender.emit(RawSocketSender.java:124)atg.fluentd.logger.FluentLogger.log(FluentLogger.java:101)at org.fluentd.logger.FluentLogger.log (FluentLogger.java:86)com.rachna.interceptor.RachnaExceptionMappingInterceptor.publishException(RachnaExceptionMappingInterceptor.java:141)at com.google.inject的com.opensymphony.xwork2.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:201) . 位于org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:54)的com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:244)中的struts2.Struts2Factory $ ProvidedInterceptor.intercept(Struts2Factory.java:216) org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:564)位于org.apache.struts2.dispatcher.ng的org.apache.struts2.dispatcher.ng.ExecuteOperations.executeAction(ExecuteOperations.java:81) .filter.StrutsPrepareAndExecuteFilter.doFilter(StrutsPrepareAndExecuteFilte r.java:99)com.google.inject上的com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119) .servlet.GuiceFilter $ 1.call(GuiceFilter.java:133)atCom.google.inject.servlet.GuiceFilter $ 1.call(GuiceFilter.java:130)位于com.google.inject.servlet.GuiceFilter的com.google.inject.servlet.GuiceFilter $ Context.call(GuiceFilter.java:203) .doFilter(GuiceFilter.java:130)org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)at org . apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase . java:502)org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)at org.apache.catalina.valves .AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv) e.java:88)org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:868)atg.apache.coyote .AbstractProtocol $ AbstractConnectionHandler.process(AbstractProtocol.java:672)org.apache.tomcat.util.net.NioEndpoint $ SocketProcessor.doRun(NioEndpoint.java:1504)at org.apache.tomcat.util.net.NioEndpoint $ SocketProcessor .run(NioEndpoint.java:1460)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor $ Worker.run(ThreadPoolExecutor.java:617)

1 回答

  • 0

    你的问题是关于两个不同的问题 . 第一部分是关于Stackdriver monitoring 代理(以前是唯一的Stackdriver代理,因此在那里命名的遗憾位置) . 实际上预计会出现404错误 - 它正在尝试依次联系GCE和AWS元数据服务器,并从GCE获取404 .

    第二个是与Stackdriver logging 代理进行通信时出错,您没有提供任何详细信息 . 服务名称为 google-fluentd ,您应该可以通过运行 sudo service google-fluentd status 来获取服务状态 . 了解 google-fluentdgoogle-fluentd-catch-all-config 的已安装软件包版本也会有所帮助 .

相关问题