Hello. I have the problem with SwardAgent/ Engine build from source branch 4.8
This is sward agent log.
Starting up SwarmAgent …
… registering SwarmAgent with remoting service
… registering SwarmAgent network channels
… initializing SwarmAgent
… checking certificate
… certificate check has failed
… initializing cache
… using cache folder ‘W:/UnrealEngine/Engine/Saved/Swarm/SwarmCache’
… recreating SwarmAgent cache staging area
… initializing connection to SwarmCoordinator
… using SwarmCoordinator on RENDER-01
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] Coordinator ping failed
… SwarmCoordinator failed to be initialized
… initializing local performance monitoring subsystem
… initialization successful, SwarmAgent now running
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] Coordinator ping failed
[GetUniqueHandle] Communication with the coordinator failed, job distribution will be disabled until the connection is established
[GetUniqueHandle] Exception: System.Net.Sockets.SocketException (0x80004005): Этот хост неизвестен
Server stack trace:
в System.Net.Dns.GetAddrInfo(String name)
в System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
в System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
в System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
в System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
в System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
в System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
в System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
в System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
в System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
в SwarmCoordinatorInterface.ISwarmCoordinator.GetUniqueHandle()
в Agent.Agent.GetUniqueHandle()
[PingCoordinator] Determined that we couldn't ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Interface:TryOpenConnection] Local connection established
[Interface:OpenJob] Error: Недопустимый класс
[PingCoordinator] Determined that we couldn't ping the coordinator
[PingCoordinator] CoordinatorResponding is false
the WMI repository on your monitored server is corrupt.
To repair the WMI repository on Windows Vista or 2008:
Open an Administrator command prompt and run the following command:
winmgmt /salvagerepository
To repair the WMI repository on Windows 2003 or earlier:
Close any open WBEMTest processes on the monitored server.
Open an Administrator command prompt and run the following commands:
cd /d %windir%\system32\wbem
for %i in (*.dll) do RegSvr32 -s %i
for %i in (*.exe) do %i /RegServer
net stop winmgmt /y
Wait five seconds and then run the following commands:
c:
cd c:\windows\system32\wbem
rd /S /Q repository
Note:: If the repository directory refuses to be deleted, try to rename it instead.
Open a text editor program, copy and paste the following script, and then save the file as a .bat file.
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
mofcomp exwmi.mof
mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
mofcomp exmgmt.mof
Run the .bat file from an Administrator command prompt.
Note:You may ignore any errors that appear in the script unless these steps do not solve the WMI issue. If the WMI issue is not resolved after completing all these steps, re-run this script, record the output, and then attach it to a SolarWinds support case.
Run WBEMTest on the application server and run the failing query. For example:
SELECT * from Win32_PerfRawData_PerfProc_Process where NAME <> '_Total'
If the "Invalid Class" error persists, close any WBEMTest processes, open an Administrator command prompt, and then run these commands:
cd c:\windows\system32\wbem
ren repository repository_old
winmgmt /resyncperf
Retry either the WBEMTest query or the Orion APM monitor. If the issue persists, contact SolarWinds support.
Opening an administrator command prompt
Press WINDOWS + R to open the Run dialog box.
Type runas /user:admin cmd where admin is the administrator user name.
Enter the administrator password.
For my version solution was:
Stop winmgmt
Delete reposiory folder
start winmgmt
exec winmgmt /salvagerepository
exec winmgmt /resyncperf