BookmarkSubscribeRSS Feed
SASavid
Calcite | Level 5

Hello SAS forum,

 

I am in the middle of SAS upgrade from SAS 9.4 M7 to 9.4 M8. I completed the metadata (install & configure) and compute (install). While doing the "configuration" part for compute. I got an error while it was trying to start the object spawner.  

 

No Object Spawner listener was detected. Host=abcd.local.local. Port=8581.

 

I tried to start the Object spawner manually and it started just fine. No issues. I tried to retry the configuration and got the error - 

 

There was an error in attempting to start this host as the requested port

is already in use.

 

So the script is having issues starting Object spawner. Any insights ?

 

Thanks

11 REPLIES 11
gwootton
SAS Super FREQ

Stop the one you started and click "Retry", then see if it's able to start the service itself.

--
Greg Wootton | Principal Systems Technical Support Engineer
SASavid
Calcite | Level 5

That's what I did and got the error 

 

No Object Spawner listener was detected. Host=abcd.local.com Port=8581

gwootton
SAS Super FREQ
I would check the Object Spawner log from the start attempt by the Deployment Wizard for errors starting up.
--
Greg Wootton | Principal Systems Technical Support Engineer
SASavid
Calcite | Level 5
Yes, the logs says - No Object Spawner listener was detected.
gwootton
SAS Super FREQ
That would appear in the Deployment Wizard's log but not in the Object Spawner log.

The Deployment Wizard is attempting to start the Object Spawner, then checking to see if the Object Spawner is running. Presumably the start is failing, so then the check fails. When the Spawner was already running, this failure was because there was already another spawner running so the bind port was in use. If you stopped the Object Spawner first and then told it to retry the start, it should be successful in starting. If not, the Object Spawner should create a log (in <SASConfig>/Lev1/ObjectSpawner/Logs/ by default) should have a new log that indicates why the start failed. I think the Deployment Wizard uses the Deployment Manager Agent to perform this start, so that log may also have detail on the failure.

You may wish to engage SAS Technical Support so they can work with you on resolving the issue.
--
Greg Wootton | Principal Systems Technical Support Engineer
SASavid
Calcite | Level 5

Yes. I have reached out to SAS Tech support. I don't see a Object spawner log. I only see a "objectspawnr_startServer_2024-04-02-07.22.29.log" log in the path /opt/sas/config/Lev1/Logs/Configure. 

AhmedAl_Attar
Ammonite | Level 13

@SASavid 

Did you have the Metadata Server up & running when you tried to configure your Compute-Tier?

That's where information are extracted/read by the configuration wizard/deployment manager. 

SASavid
Calcite | Level 5

Yes. The metadata server is up and running. Any other thought s what must be causing this error?

SASKiwi
PROC Star

I suggest you open a Tech Support track for this if you haven't already. Diagnosing of server logs is probably the next step and that is best progressed with TS.

Key123
Fluorite | Level 6

@SASavid : Can you post the solution on this, I am getting the same exact error for compute node configuration while starting ObjectSpawner

SASKiwi
PROC Star

Getting exactly the same error doesn't necessarily mean the same cause and solution applies. As already mentioned, opening a Tech Support track is the best way to make progress.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 11 replies
  • 1808 views
  • 0 likes
  • 5 in conversation