Will restarting SLPort processes have consequences on a production system?

Solved1.60K viewsSLPort
3
0 Comments

Is it possible to just restart SLPort processes without having to restart the DMA? Will that be harmful on a production system?

We have SLPort that is stuck listening to TCP 514, and we are wanting to restart the process(es) to try and fix the issue:

Alex Johnson [SLC] [DevOps Advocate] Selected answer as best 14th July 2020

1 Answer

5
8.78K 5 Comments

The SLPort process can't be restarted, if you stop this process then it will trigger a full restart of the DMA. See SLWatchdog2 logfile:

2020-07-14 07:45:01 14372|-> Process with PID 15016 (SLPort.exe) stopped.
2020-07-14 07:45:01 14372|Queueing FULL DataMiner Restart in 2 minutes (SLPort.exe)

Matthijs Favorel [SLC] [DevOps Advocate] Posted new comment 16th July 2020
Wouter Demuynck [SLC] [DevOps Advocate] commented

As additional info:

These processes can be restarted without fully restarting DataMiner:

– SLScripting
– SLASPConnection
– SLAutomation
– SLScheduler
– SLAnalytics

(these will be registered as a process disappearance by SLWatchDog though)
Laurens Moutton [SLC] [DevOps Enabler] commented

Be careful when restarting such a process.
In the past I was restarting SLScripting processes to recover from a deadlock situation, but these restarts were “counted”.
Later there was a real process disappearance of SLProtocol and because the SLScripting processes got restarted, the conclusion was not to automatically restart the DMA, leaving it in a strange state with elements that don’t have an SLProtocol process anymore. Something like this:
2020-07-14 09:49:41 2700|-> Process with PID 21696 (SLScripting.exe) stopped.
2020-07-14 09:49:41 2700|Remove Threads(0) (SLScripting.exe) succeeded.
2020-07-14 09:49:41 12964|–> Added process watch for PID 5424 process SLScripting.exe (Reset allowed)
2020-07-14 09:49:41 2700|–> Process 5424 SLScripting.exe registered
2020-07-14 09:50:26 14372|-> Process with PID 19212 (SLProtocol.exe) stopped.
2020-07-14 09:50:26 14372|Stopping restart timer (more than 2 processes stopped)
Wouter Demuynck [SLC] [DevOps Advocate] commented

Should be better since RN26440 [10.0.10/10.0 CU5/9.6 CU17], which makes sure the agent does restart in this scenario.
Alex Johnson [SLC] [DevOps Advocate] commented

Thanks for the info! We have decided we will have to arrange a test window to restart the DMA.
Matthijs Favorel [SLC] [DevOps Advocate] commented

Although restarting the SLASPConnection process won’t cause an automatic DataMiner restart, it might cause issues in some specific reports, so it’s not advised to restart it on a live system. (ref Task 73627)
You are viewing 1 out of 1 answers, click here to view all answers.