Unsolved
This post is more than 5 years old
76 Posts
0
1573
symcli terminal closed after symconfigure commit
If your vpn terminal closes on the symcli host after sending a symconfigure command how can you see if it completed ? I thought these would safely continue in the event of a terminal disconnect.
My log file seems to have stopped after the connection closed.
tail /usr/emc/API/symapi/log/symapi-20160217.log
02/17/2016 15:31:21.002 946 Step 070, substep 125.......................................Executing.
02/17/2016 15:33:23.843 946 Step 070, substep 126.......................................Executing.
02/17/2016 15:35:26.680 946 Step 070, substep 127.......................................Executing.
02/17/2016 15:37:29.519 946 Step 070, substep 128.......................................Executing.
02/17/2016 15:39:32.360 946 Step 070, substep 129.......................................Executing.
02/17/2016 15:41:35.200 946 Step 070, substep 130.......................................Executing.
02/17/2016 15:43:07.329 946 Step 070, substep 131.......................................Executing.
02/17/2016 15:45:10.175 946 Step 070, substep 132.......................................Executing.
02/17/2016 15:47:14.187 946 Step 070, substep 133.......................................Executing.
02/17/2016 15:49:17.025 946 Step 070, substep 134.......................................Executing.
echolaughmk
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.