PAMSC / UNAB - cannot unload syscall (need to unload syscall before upgrading PAMSC/UNAB on a server)
Article ID: 402743
Updated On:
Products
Issue/Introduction
We can't Unload syscall anymore on some server with CP06 release :
| # SEOS_load -u SEOS_load: Executing un/load exit file, / <PAMSC_HOME>/SEOS_unload_int.always -pre Ports - nothing to do ... SEOS_load: Executing un/load exit file, <PAMSC_HOME>SEOS_unload_unab.always -pre ERROR: cannot unload SEOS_syscall. There are active system calls. Run secons -scl to list active system calls. # |
So I checked to see if there were any differences between the CP05 and CP06 releases.
I found "exit 0" command in CP06 release in / <PAMSC_HOME>/SEOS_unload_unab.always / <PAMSC_HOME>/SEOS_unload_unab.opt
Then I try to comment it :
| [# grep "exit 0" SEOS_unload_unab* SEOS_unload_unab.always:#exit 0 # do not interrupt UNAB operation SEOS_unload_unab.opt:#exit 0 # do not interrupt UNAB operation # |
And I notice I can unload syscall :
|
# SEOS_load -u successfully disabled module seos_1410_60_186. |
We need to know how to correctly unload the syscall on cp06 release
Environment
PAMSC 14.1 cp06 / UNAB
Cause
That change was made because UNAB was recycled every time they manipulated PIM 14.10.60.xxx
Resolution
Use solution 1 for all releases since cp6.
The solution 2 is in case customer manages PIM as a service, since systemctl stop seos would previously initiate SEOS_syscall unload terminating UNAB as part of its operation.
They will need to make change #2 below in that case.
One-line change will be required in the following files (for default installation location):
1.
/<PAMSC_HOME>/SEOS_unload_unab.always <-- the opening line "exit 0" should be deleted
<PAMSC_HOME>/SEOS_unload_unab.opt <-- the opening line "exit 0" should be deleted
/etc/systemd/system/seos.service <-- the line "ExecStopPost=/<PAMSC_HOME>/SEOS_load -u" should be commented out or deleted
2.
systemctl daemon-reload
Feedback
