sometimes they will continue and complete and other times you might need to release the lock if they hung up. You can check the lock to see if there is a config change lock (15) by running "symcfg -sid XXX -lockn all list"
If there is a #15 config Change lock, check the amount of time it has been running for and it could be that command. If you see the actions no longer happening in the symapi logs on the executing host, you can likely clear it and redo or call support to have them either retry the command or try to complete the script on their end.
echolaughmk
2 Intern
•
522 Posts
1
February 17th, 2016 14:00
sometimes they will continue and complete and other times you might need to release the lock if they hung up. You can check the lock to see if there is a config change lock (15) by running "symcfg -sid XXX -lockn all list"
If there is a #15 config Change lock, check the amount of time it has been running for and it could be that command. If you see the actions no longer happening in the symapi logs on the executing host, you can likely clear it and redo or call support to have them either retry the command or try to complete the script on their end.
ScotN
76 Posts
0
February 17th, 2016 17:00
Yea, it appears your pretty screwed if you want to monitor your command progression when a terminal dies.
NOTE: No matter how simple start a screen session on Linux before using symcli.
Call support or open a chat and or get on a webex.