Sometimes, after stopping a serial element, DataMiner doesn’t release the port. Is there a way to force the release of the port without reboot the whole system? Maybe rebooting the SLPort process?
Thanks in advance!
SLPort is a critical process and therefor can’t be restarted on its own. Doing so will result in a restart of all DataMiner modules as our SLWatchDog module will pick this up as an unexpected process disappearance and trigger a full DataMiner restart to restore the situation.
However there are tools available that can help you out with this. One of my personal favorites is Microsoft Sysinternals TCPView.
It will give you a complete overview of all processes on the system that have TCP or UDP endpoints open.
If we then look for one of the SLPort instances in the overview, we could see something like the following:
Closing it can then be done by right-clicking on it and selecting Close Connection.
That being said; SLPort should release every socket allocated to a certain element when it gets stopped though.
It would be interesting if we can look into the root cause of why it is not happening in this specific case. For ease of follow-up I suggest to contact our operations team, they’ll create an internal ticket for it and can do an in-depth investigation from there.