Select to view content in your preferred language

Monitor 2025 Agent service not starting on server

3701
31
Jump to solution
06-10-2025 10:06 PM
LachlanWainwright
Occasional Contributor

Hi

OS: Windows Server 2019 Datacenter

I upgraded the Monitor agent to 2025 on 2 machines and neither agent service will start.

Agent installs without error and then when the service tries to start it stops immediately.

This machine worked and works for all other versions of the monitor agents and I reinstalled 2024.1.1 back and have no issues, fires on up.

Did all the usual stuff of unregistering, removing every reference in the install folder, the service account folder running it etc.

Nothing of relevance in Event Viewer

I am outta ideas, anyone got a thought?

I'll lodge a ticket with ESRI AU now and keep you all posted.

Please & thanks 😊

Lachlan

 

When I updated the log to append following these instructions XML Configuration file for winsw I get the following:

server names & ip addresses changed

arcgis-monitor-agent-service.err

*** xyzxy.x.x.au can't find 0.0.0.1: Non-existent domain

*** YYYYY.y.y.au can't find 0.0.0.2: Non-existent domain

arcgis-monitor-agent-service.out
Error:
Command
failed:
for
/f
"tokens=2
delims=:"
%a
in
('nslookup
0.0.0.1
^|
findstr
/B
Name:')
do
@echo
%a

***
xyzxy.x.x.au
can't
find
172.26.24.16:
Non-existent
domain

at execSync pkg/prelude/bootstrap.js:2115

⁃ Module._compile
pkg/prelude/bootstrap.js:1930


Error:
Command
failed:
for
/f
"tokens=2
delims=:"
%a
in
('nslookup
0.0.0.1
^|
findstr
/B
Name:')
do
@echo
%a

***
xyzx.x.x.au
can't
find
0.0.0.1:
Non-existent
domain

at execSync pkg/prelude/bootstrap.js:2115

⁃ Module._compile
pkg/prelude/bootstrap.js:1930

 

 

 

 

Tags (4)
31 Replies
JeffClough
Occasional Contributor

Having the same issue so eagerly awaiting your resolution to be posted. 

0 Kudos
JeffMertzXcel
Occasional Contributor

@LachlanWainwright @JeffClough Sorry about that, I guess I made too many edits and the post went into "review by moderator" mode. It should be visible now. Your server needs to be able to successfully return from the nslookup <ipaddress> call, so the Monitor code can grab the hostname.

LachlanWainwright
Occasional Contributor

Good to see my Agent logs (first post) are exactly the same at your Server logs @JeffMertzXcel . 👍👍👍

I believe it's a code bug and eluded that in my last response to ESRI AU yesterday.

Reiterating Jeff's sentiment, given all the previous versions of Monitor, don't have the problem or require this and none of the other ESRI software that I work either with requires it....specific to 2025 server & agent

FYI, for the Agent, I changed 'none' to 'append' in the ..\ArcGIS\Monitor\Agent\bin\arcgis-monitor-agent-service.yml file) then starting the service...well trying to start the service...lol

2 new log files appear to peruse: arcgis-monitor-agent-service.err.log & arcgis-monitor-agent-service.out.log with the existing arcgis-monitor-agent-service.wrapper.log.  That hold the 1st post error messages.

I also tried this with 2024.1 on the same server, obviously it started and nothing entered the logs like 2025.

I eagerly await 2025.1.......or do I.....

Thanks for the help Jeff 😀

LachlanWainwright
Occasional Contributor

Out of interest @JeffMertzXcel  & @OlivieroVitale where are your servers?

Mine are on AZURE.

0 Kudos
JeffMertzXcel
Occasional Contributor

@LachlanWainwright my main servers are on premise with the utility I work at and are maintained by their IT department, thus no big issues there (with the exception of Notebook server :-)). My other sandboxes are on a standalone Dell Server using Proxmox virtualization, thus I have full control over everything. Glad I was able to contribute to this conversation.

OlivieroVitale
Esri Contributor

Hello @LachlanWainwright ,  VM hosted locally

LachlanWainwright
Occasional Contributor

thx @JeffMertzXcel  and @OlivieroVitale 

dam, was hoping it might have just been an AZURE problem

enjoy the weekend gents,

we have a lovely couple of sunny winter days down here in Melbourne Town, Australia

Royce_Simpson
Frequent Contributor

Add another to this list:  I've got Agent on 17 servers.  All started and are running except for one server.  It installs without error, but the service won't come out of the "stopped" state.  

0 Kudos
LachlanWainwright
Occasional Contributor

Hi everyone


Thanks for everyone posting they are having an issue only with 2025.

I was on a call yesterday with ESRI Australia and ESRI Inc. looking about the setup I am on.  Nothing came to light...yet...but any news I'll keep you all posted.

Where people have been changing/altering their DNS, can you provide more info please (what changes you made) as I'd like to pass the info on to my IT dept to see what they might be able to do to help test.

Please & thanks.

Lachlan

 

JeffMertzXcel
Occasional Contributor

@LachlanWainwright I am not in Azure, but this link might be of help: Reverse DNS for Azure services - Azure DNS | Microsoft Learn