vps交流

甲骨文安装哪吒探针,客户端启动失败,连接不上


> 获取Agent日志
— Logs begin at Wed 2021-11-24 17:48:27 GMT. —
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: Stopped Nezha Agent.
— Subject: Unit nezha-agent.service has finished shutting down
— Defined-By: systemd
— Support: https://access.redhat.com/support

— Unit nezha-agent.service has finished shutting down.
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: Started Nezha Agent.
— Subject: Unit nezha-agent.service has finished start-up
— Defined-By: systemd
— Support: https://access.redhat.com/support

— Unit nezha-agent.service has finished starting up.

— The start-up result is done.
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: nezha-agent.service: Main process exited, code=exited, status=203/EXEC
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: nezha-agent.service: Failed with result ‘exit-code’.
— Subject: Unit failed
— Defined-By: systemd
— Support: https://access.redhat.com/support

— The unit nezha-agent.service has entered the ‘failed’ state with result ‘exit-code’.
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: nezha-agent.service: Service RestartSec=100ms expired, scheduling restart.
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: nezha-agent.service: Scheduled restart job, restart counter is at 5.
— Subject: Automatic restarting of a unit has been scheduled
— Defined-By: systemd
— Support: https://access.redhat.com/support

— Automatic restarting of the unit nezha-agent.service has been scheduled, as the result for
— the configured Restart= setting for the unit.
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: Stopped Nezha Agent.
— Subject: Unit nezha-agent.service has finished shutting down
— Defined-By: systemd
— Support: https://access.redhat.com/support

— Unit nezha-agent.service has finished shutting down.
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: nezha-agent.service: Start request repeated too quickly.
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: nezha-agent.service: Failed with result ‘exit-code’.
— Subject: Unit failed
— Defined-By: systemd
— Support: https://access.redhat.com/support

— The unit nezha-agent.service has entered the ‘failed’ state with result ‘exit-code’.
Nov 24 18:05:25 instance-20210921-0143 systemd[1]: Failed to start Nezha Agent.
— Subject: Unit nezha-agent.service has failed
— Defined-By: systemd
— Support: https://access.redhat.com/support

— Unit nezha-agent.service has failed.

— The result is failed.

其他小鸡鸡正常,为什么甲骨文连不上呢?奇了怪了,谁能教一下呢?

甲骨文正常 跟甲骨文没关系

Marlene 发表于 2021-11-25 02:14
甲骨文正常 跟甲骨文没关系

我也觉得很奇怪,又不知道哪里出问题了,其他小鸡鸡用同个方法就没问题,甲骨文试了两个主机都不行

supermson 发表于 2021-11-25 02:17
我也觉得很奇怪,又不知道哪里出问题了,其他小鸡鸡用同个方法就没问题,甲骨文试了两个主机都不行 …

看你这日志 不是ubuntu吧
ubuntu反正一点问题都没

Marlene 发表于 2021-11-25 02:22
看你这日志 不是ubuntu吧
ubuntu反正一点问题都没

不是Arm架构的小鸡鸡,系统是Centos

supermson 发表于 2021-11-25 02:39
不是Arm架构的小鸡鸡,系统是Centos

虽然我centos也是好的 但我盲猜换个系统就好了

Marlene 发表于 2021-11-25 02:54
虽然我centos也是好的 但我盲猜换个系统就好了

谢谢了,我试一下

supermson 发表于 2021-11-25 07:56
谢谢了,我试一下

我只遇到过能安装但是数据接收不到。 遇到这种 填服务端ip地址就行了甲骨文安装哪吒探针,客户端启动失败,连接不上

aws 发表于 2021-11-25 07:57
我只遇到过能安装但是数据接收不到。 遇到这种 填服务端ip地址就行了

试过了,不填域名,填ip也是一样,监控端是安装完成的,但是看日志启用不成功的样子

最近Sanjose速度是不是很慢?