Help!! starter paused at win10

# 1 year ago
peipei	OS: win10 pro 21H2 64bit tango-9.2.2-64x MYSQL 5.7 JAVA 1.8.0.281 nssm 2.24 TANGO_HOST=localhost:20211 MYSQL_USER=tango MYSQL_PASSWORD=tango2020 my computer name :ZPY JAVA_HOME TANGO_ROOT all set well Tango-Databaseds running well ,JIVE and astor can connect to tangoDB, AS FIG.1 show the question is: when i use astor–command—add a new host i imput like these: HOST NAME: ZPY Device Servers PATH: C:\DeviceServers\bin push create and tell me A starter server has been created in TANGO databased you can now start it on ZPY machine ————————————————– BUT when i start it at command line : C:\Program Files\tango\bin>start-starter.bat zpy Starter::Starter() init device tango/admin/ZPY UseEvents = False interStartupLevelWait = 1 serverStartupTimeout = 1 fireFromDbase = 1 logFileHome = c:\temp StartServersAtStartup = 1 AutoRestartDuration = 0 Tango exception Severity = ERROR Error reason = BAD_PARAM Desc : This server must run on zpy and not on activate Origin : Starter::check_host() Received a CORBA_Exception Exiting as fig.2 show ——————————– when i uses nssm.exe install Tango-Starter, with argument:ZPY environment variables input TANGO_HOST=localhost:20211 The Tango-starter is always paused, as fig.3 show please tell me how to fix this problem, many thanks! Attachments:

# 1 year ago

OS: win10 pro 21H2 64bit
tango-9.2.2-64x
MYSQL 5.7
JAVA 1.8.0.281
nssm 2.24
TANGO_HOST=localhost:20211
MYSQL_USER=tango
MYSQL_PASSWORD=tango2020
my computer name :ZPY
JAVA_HOME TANGO_ROOT all set well

Tango-Databaseds running well ,JIVE and astor can connect to tangoDB,
AS FIG.1 show
the question is:

when i use astor–command—add a new host
i imput like these:
HOST NAME: ZPY
Device Servers PATH: C:\DeviceServers\bin
push create and tell me
A starter server has been created in TANGO databased
you can now start it on ZPY machine
————————————————–
BUT when i start it at command line :
C:\Program Files\tango\bin>start-starter.bat zpy
Starter::Starter() init device tango/admin/ZPY
UseEvents = False
interStartupLevelWait = 1
serverStartupTimeout = 1
fireFromDbase = 1
logFileHome = c:\temp
StartServersAtStartup = 1
AutoRestartDuration = 0
Tango exception
Severity = ERROR
Error reason = BAD_PARAM
Desc : This server must run on zpy and not on activate
Origin : Starter::check_host()

Received a CORBA_Exception
Exiting
as fig.2 show
——————————–

when i uses nssm.exe install Tango-Starter, with argument:ZPY
environment variables input TANGO_HOST=localhost:20211
The Tango-starter is always paused, as fig.3 show

please tell me how to fix this problem, many thanks!

# 1 year ago
Reynald	Hi, The Starter is checking at startup that its instance name really matches the real name of the host where it is running. See https://gitlab.com/tango-controls/starter/-/blob/main/Starter.cpp#L207 and https://gitlab.com/tango-controls/starter/-/blob/main/Starter.cpp#L1429-1459 This means that `Starter.exe ZPY` must run on a host named ZPY, recognized with this name on the current network. From what you're writing, you computer name is indeed ZPY but I don't know why, the Starter found another name for it: "activate". Could it be that your PC network name is actually "activate" instead of ZPY? If not, maybe you're facing a bug of cppTango on Windows because the Starter is getting the hostname by using Tango::Util::instance()->get_host_name() method. The hostname used by Tango is then the one computed by Tango::Util::init_host_name() method : https://gitlab.com/tango-controls/cppTango/-/blob/9.3.5/cppapi/server/utils.cpp#L1349-1519 There might be a bug in cppTango 9.2.2 which might not be compatible with recent Windows versions and some network setups? As a work-around, it looks like you can define the DEBUG environment variable to avoid this host check. This is normally used only by the Starter/Astor developers for debugging purposes and I'm not sure of the consequences of using this hack. Please note that there is currently a work done by Observatory Sciences Ltd for the Tango Community to create a new Tango distribution installer on Windows. You can get a beta version from the link given by Aya on the following gitlab comment: https://gitlab.com/tango-controls/TangoTickets/-/issues/61#note_1047813549 Please give it a try if you can and report any issue you encounter with this beta version on https://gitlab.com/tango-controls/TangoTickets/-/issues/61. Kind regards, Reynald Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 1 year ago

Reynald

Hi,

The Starter is checking at startup that its instance name really matches the real name of the host where it is running.
See https://gitlab.com/tango-controls/starter/-/blob/main/Starter.cpp#L207 and https://gitlab.com/tango-controls/starter/-/blob/main/Starter.cpp#L1429-1459

This means that

Starter.exe ZPY

must run on a host named ZPY, recognized with this name on the current network.

From what you're writing, you computer name is indeed ZPY but I don't know why, the Starter found another name for it: "activate". Could it be that your PC network name is actually "activate" instead of ZPY?

If not, maybe you're facing a bug of cppTango on Windows because the Starter is getting the hostname by using Tango::Util::instance()->get_host_name() method.

The hostname used by Tango is then the one computed by Tango::Util::init_host_name() method :
https://gitlab.com/tango-controls/cppTango/-/blob/9.3.5/cppapi/server/utils.cpp#L1349-1519

There might be a bug in cppTango 9.2.2 which might not be compatible with recent Windows versions and some network setups?

As a work-around, it looks like you can define the DEBUG environment variable to avoid this host check. This is normally used only by the Starter/Astor developers for debugging purposes and I'm not sure of the consequences of using this hack.

Please note that there is currently a work done by Observatory Sciences Ltd for the Tango Community to create a new Tango distribution installer on Windows. You can get a beta version from the link given by Aya on the following gitlab comment:
https://gitlab.com/tango-controls/TangoTickets/-/issues/61#note_1047813549

Please give it a try if you can and report any issue you encounter with this beta version on https://gitlab.com/tango-controls/TangoTickets/-/issues/61.

Kind regards,
Reynald

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 1 year ago
peipei	Thank you very much!!! Your reply gave me a hint I went and searched the hosts file carefully to see if there was any problem and I found that I installed Navicat Premium 12, it changed the host file like this: # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost 127.0.0.1 activate.navicat.com when i fix this ,the astor running well i will try the new version on a new machine thanks again

# 1 year ago

peipei

Thank you very much!!!
Your reply gave me a hint
I went and searched the hosts file carefully to see if there was any problem
and I found that I installed Navicat Premium 12, it changed the host file like this:

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 activate.navicat.com

when i fix this ,the astor running well smile

i will try the new version on a new machine

thanks again

# 1 year ago
peipei	Thank you very much!!! Your reply gave me a hint I went and searched the hosts file carefully to see if there was any problem and I found that I installed Navicat Premium 12, it changed the host file like this: # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost 127.0.0.1 activate.navicat.com when i fix this ,the astor running well i will try the new version on a new machine thanks again

# 1 year ago

peipei

i will try the new version on a new machine

thanks again