While conducting a network scan of the Automate 7 server, the cpu remains mostly unnafected. However, during the scanner's third attempt at identifying the service running on port 1743 (amts), the CPU utilization spikes at 99% and remains at that percentage until the service is restarted.

I've attached the packet capture of the network scan prior to the cpu spike.

  

Thank you,
Kyle

Category Survey

Hi Kyle,

Can you please confirm what version of AutoMate 7 you are running?

Can you also confirm your OS?

Category Survey

-------------------------

Ricardo Castaneda | Principal Support Analyst
AutoMate | Division of HelpSystems
HelpSystems, LLC | T: +1.213.738.1700

Hi Ricardo, 

The Automate 7 version is 7.1.3.0, running on Windows Server 2008 x86.

I should also mention that this problem occured on a different Automate 9 server as well, which runs on Windows Server 2008 R2 x64.

Thank you,
Kyle 

 

 

Category Survey

Kyle,

You are posting in the AutoMate forums but mentioning server so I just want to make sure that we are looking at AutoMate and not BPA Server. Also, the task service for AM7 is am7ts.exe and not amts.exe. You mentioned amts which would apply to all versions of AutoMate except v7. AutoMate 7's default port is 7877. How are you determining that 1743 is an AM7 port? From a command line please type the following:

netstat -aon | find ":1743"

The results should contain a PID. Please match the PID in Task Manager to the appropriate process and let me know what you find. Also, please let me know the parameters that you are using for Nmap to cause the CPU spike as well as what you are using to determine that port 1743 references AM7.

Category Survey AutoMate 7 version: Windows version:

-------------------------

Leonard Amabile | Director, Cross Platform Support
AutoMate | InterMapper | Skybot | Divisions of HelpSystems
T: +1.213.738.1700 | F: +1.213.738.7665

Hi Leonard, 

I appreciate your assistance. Port 1743 is being used by bpnetd.exe, a backup agent from Unitrends. 

For clarification, I did mean am7ts earlier when refering to the Automate service as "amts".  

Lastly, the nmap parameters used were: 

nmap -sS -sV -p 1-65535 -v -v --version-intensity 1 192.168.10.58

Thank you,

Kyle 

Category Survey

Hi Kyle,

Unfortunately I am not able to reproduce your issue. Do you have tasks running during the scan? If so how may tasks are running during the scan?

Category Survey

-------------------------

Ricardo Castaneda | Principal Support Analyst
AutoMate | Division of HelpSystems
HelpSystems, LLC | T: +1.213.738.1700