server集群的某台从服务器无法启动

在维护server集群的时候发现某台从服务器站点已经获取到了集群配置了,但是状态为“已停止”,手动启动时报错
Dingtalk_20240123190629.jpg

 
server/usr/logs的信息和截图一样,都是“无法启动机器,因为它没有参与任何集群。”
将这台从服务器与另一台正常的从服务器的配置做了对比,没有发现什么区别
framework/etc/service/logs的日志如下:

Tue Jan 23 18:11:29.106 CST 2024 Start invoked
Tue Jan 23 18:11:29.113 CST 2024 Start NodeAgent.start().
Tue Jan 23 18:11:29.127 CST 2024 Loading all observers.
Tue Jan 23 18:11:29.200 CST 2024 arcgis_cloud_platform=null
Tue Jan 23 18:11:29.201 CST 2024 arcgis_cloud_platform=null
Tue Jan 23 18:11:29.202 CST 2024 NodeAgent loaded observer 'HostnameObserver'.
Tue Jan 23 18:11:29.203 CST 2024 NodeAgent loaded observer 'LogServiceObserver'.
Tue Jan 23 18:11:29.206 CST 2024 NodeAgent loaded observer 'ServerUninstallObserver'.
Tue Jan 23 18:11:29.210 CST 2024 NodeAgent loaded observer 'ServerConfigObserver'.
Tue Jan 23 18:11:29.210 CST 2024 NodeAgent loaded observer 'AutomaticMachineRenameObserver'.
Tue Jan 23 18:11:29.211 CST 2024 NodeAgent loaded observer 'VerifyMachineRegistrationObserver'.
Tue Jan 23 18:11:29.212 CST 2024 NodeAgent loaded observer 'Server upgrader'.
Tue Jan 23 18:11:29.214 CST 2024 NodeAgent loaded observer 'PlatformServicesPluginObserver'.
Tue Jan 23 18:11:29.214 CST 2024 NodeAgent loaded observer 'RelationalDatastoreObserver'.
Tue Jan 23 18:11:29.221 CST 2024 NodeAgent loaded observer 'PatchAction'.
Tue Jan 23 18:11:29.221 CST 2024 Regular startup of Server.
Tue Jan 23 18:11:29.221 CST 2024 Starting RMI connector for NodeAgent.
Tue Jan 23 18:11:29.449 CST 2024 Invoking beforeStart() for all observers.
Tue Jan 23 18:11:29.489 CST 2024 WARNING: Could not connect to Log service. Writing log message to console.
Tue Jan 23 18:11:29.490 CST 2024 <Msg time="2024-01-23T18:11:29,220" type="INFO" code="10106" source="Server" process="86575" thread="1" methodName="" machine="" user="" elapsed="">Loaded Plugin for configuration of Patch Actions.</Msg>
Tue Jan 23 18:11:29.621 CST 2024 Registering and starting log service on 从服务器的hostname.
Tue Jan 23 18:11:30.819 CST 2024 Registering NodeAgent as JMX bean.
Tue Jan 23 18:11:30.821 CST 2024 Loading all plugins.
Tue Jan 23 18:11:30.825 CST 2024 arcgis_cloud_platform=null
Tue Jan 23 18:11:30.825 CST 2024 NodeAgent loaded plugin 'ProcessMonitor'.
Tue Jan 23 18:11:30.827 CST 2024 NodeAgent loaded plugin 'DirectoryCleaner'.
Tue Jan 23 18:11:30.827 CST 2024 NodeAgent loaded plugin 'UlimitMonitor'.
Tue Jan 23 18:11:30.828 CST 2024 NodeAgent loaded plugin 'LogFileLimiter'.
Tue Jan 23 18:11:30.829 CST 2024 NodeAgent loaded plugin 'ConfigSynchronizer'.
Tue Jan 23 18:11:30.830 CST 2024 Loading plugin.. com.esri.arcgis.discovery.admin.plugins.ServiceInstanceMonitor
Tue Jan 23 18:11:30.830 CST 2024 Props {PeriodicInterval=1, NodeAgentCustomPlugin=false}
Tue Jan 23 18:11:30.830 CST 2024 Loaded plugin com.esri.arcgis.discovery.admin.plugins.ServiceInstanceMonitor
Tue Jan 23 18:11:30.830 CST 2024 NodeAgent loaded plugin 'ServiceInstanceMonitor'.
Tue Jan 23 18:11:30.830 CST 2024 NodeAgent loaded plugin 'PlatformServicesPluginObserver'.
Tue Jan 23 18:11:30.831 CST 2024 NodeAgent loaded plugin 'DiskspaceMonitor'.
Tue Jan 23 18:11:30.831 CST 2024 Starting all plugins.arcgis
Tue Jan 23 18:11:30.850 CST 2024 StartRMID - arg: -J-Djava.security.policy=file:////home/arcgis/arcgis/server/framework/etc/rmid.policy
Tue Jan 23 18:11:30.850 CST 2024 StartRMID - arg: -J-Dsun.rmi.activation.execPolicy=com.esri.arcgis.discovery.servicelib.impl.RMIDPolicyChecker
Tue Jan 23 18:11:30.850 CST 2024 StartRMID - arg: -J-Djava.class.path=/home/arcgis/arcgis/server/framework/lib/server/arcgis-servicelib.jar:/home/arcgis/arcgis/server/framework/lib/server/arcgis-common.jar
Tue Jan 23 18:11:30.850 CST 2024 StartRMID - arg: -J-Dsun.rmi.activation.execTimeout=60000
Tue Jan 23 18:11:30.850 CST 2024 StartRMID - arg: -J-Djava.rmi.server.useCodebaseOnly=true
Tue Jan 23 18:11:30.850 CST 2024 StartRMID - arg: -port
Tue Jan 23 18:11:30.850 CST 2024 StartRMID - arg: 1098
Tue Jan 23 18:11:36.139 CST 2024 Invoking afterStart() for all observers.
Tue Jan 23 18:11:36.719 CST 2024 End NodeAgent.start().
 
已邀请:

谢军

赞同来自:

可能是这个sever节点丢失了集群信息,登录站点manger或者admin页面,查看集群信息确认下,如果集群中缺少这个server节点,就把这个server节点添加到集群中。

要回复问题请先登录注册