SLResourceManager – what’s the function of this process?

Solved390 viewsadl2099 RTEs SL Services SLResourceManager
2
2 Comments

Please, dojo, what's the function of this SL process named SLResourceManager?

Got some RTEs on two servers of our staging system - we don't use SRM, so I believe it is unrelated.

Thanks

PS: When attempting from System Center / Logging we get just a 404

Alberto De Luca [DevOps Enabler] Selected answer as best 22nd June 2024
Jorge Dias [SLC] [DevOps Enabler] commented

Hi Alberto, can you reupload the image? Doesn’t seem to be available.
Alberto De Luca [DevOps Enabler] commented

Sure – let me try again – not sure what happened – usually images are “in-line” in the body of the post – this seems to have been uploaded as link

1 Answer

2
264 3 Comments

Hi Alberto,

I can't seem to access your screenshot, but I'm guessing you have an RTE in the alarm console that says something along the lines of 'An unexpected exception has occured while initializing Resource Manager. Please check the SLResourceManager logging for more information'.

The 'SLResourceManager' in that RTE message means the SLResourceManager.txt logfile (or in the logging module in Cube: 'Resource Manager'). There is no separate SLResourceManager process, ResourceManager is part of SLNet.

SLNet will only try to initialize ResourceManager if necessary licenses are present on the system. If I understand correctly the system does not use ResourceManager so it is not even expected to initialize? Is there anything in the logfile I mentioned above?

Alberto De Luca [DevOps Enabler] Posted new comment 22nd June 2024
Alberto De Luca [DevOps Enabler] commented

Thanks Seppe – indeed that’s the case – I’ve re-uploaded the image.

May need to check the licensing type with some more admins as this is a DEV/staging environment – is the log file available also via SystemCenter/Logging?

If not, what’s path if we need to RDP on the agent and check the txt file locally?
Seppe Vanhee [SLC] [DevOps Advocate] commented

From the screenshot it looks like this is the midnight sync that fails. If one agent in the cluster (assuming it is a cluster) has the ResourceManager license, it will try to sync with all other agents int the cluster. It could be that you have this issue because the other agents don’t have the ResourceManager license.
You can check the licenses in cube: profile (top right) -> about -> licenses (fourth tab).
The ResourceManager logfile you can check either on disk (c:skyline dataminerloggingSLResourceManager.txt) or like you tried in cube (not sure why that is not working for you).

In a cluster environment it is required that either all agents have the ResourceManager license, or none of them should have it.
Alberto De Luca [DevOps Enabler] commented

Thanks for all the info, Seppe – marking this as solved
You are viewing 1 out of 1 answers, click here to view all answers.