object spwaner startup issue

[sathya66]

All, 

I tried to start the object spwaner but I am getting below warning and error. Please can you advice on this.

It looks like spwaner definition is not defined but I don't know where to define.

2020-08-25T11:45:10,914 WARN [00000030] :sas - The A5B8KJBP.AY000006 spawner definition is not defined for this machine and will be ignored.
2020-08-25T11:45:10,914 ERROR [00000030] :sas - The Object Spawner - compute spawner definition did not exist in the processed configuration. Objspawn cannot continue without a spawner definition.
2020-08-25T11:45:10,914 ERROR [00000030] :sas - CLASSFACTORY cannot be instantiated.
2020-08-25T11:45:10,915 INFO [00000009] :sas - Client connection 1 for user sastrust@saspw closed.
2020-08-25T11:45:10,915 INFO [00000009] :sas - Bridge PE SAM listen thread is exiting (0).
2020-08-25T11:45:10,915 INFO [00000007] :sas - For the IOM thread puddle, there were 26 requests processed. The maximum number of requests queued was 0. The maximum number of worker threads was 2.
2020-08-25T11:45:10,915 INFO [00000007] :sas - Bridge protocol engine has quiesced.
2020-08-25T11:45:10,915 INFO [00000007] :sas - Bridge protocol engine is unloading.
2020-08-25T11:45:10,916 ERROR [00000004] :sas - Unable to initiate the IOM run-time.

[andreas_lds]

Looks as if someone removed the object-spawner-definition from the metadata. A backup exists, hopefully. You may want to contact tech-support.

[Kurt_Bremser]

This message

The A5B8KJBP.AY000006 spawner definition is not defined for this machine and will be ignored.

lets me suspect that the definition was found, but can't be used for that particaular environment; did someone change the host's name, or did you try to run the spawner on a backup machine (that has a different name)?

[jcFranklin · Accepted solution]

Hello Sathya66,

It appears that you might have a host-name mismatch issue occurring. If the host name defined in the metadata does not match the value specified for DNSMATCH or any of the host names returned from the operating system, then there is a host-name mismatch. 

Please check out the solution starting at the bottom of page 12 from my SGF technical paper "Using the SAS® Object Spawner Log to Identify Issues More Quickly and Avoid Downtime": https://www.sas.com/content/dam/SAS/support/en/sas-global-forum-proceedings/2019/3418-2019.pdf

After going through those steps, if the issue is still not resolved, I would suggest opening up a SAS Technical Support track. 

-Jessica

[sathya66]

Thanks for this ,

Yes there is a mismatch in host names.

we launched new environment with our base image. It didn't update new hostnames/IPs for some reason.  I need to update manually.