| Include Page |
|---|
| KBCOMMON:KB-CSSstyle |
|---|
| KBCOMMON:KB-CSSstyle |
|---|
|
...
| Method | Comments |
|---|
expect | Requires you pass user and password to the script so that it can connect to the OPA0 console via "telnet" and execute the shutdown commands. The "guest_shutdown.exp" script, located in the /opt/charon/utils folder, can perform operations to: - log off a user connected on the console if the prompt is detected,
- enter a username/password to login if "
login:" or "username:" is detected, - execute the shutdown command if the prompt is detected,
- detect the SRM prompt (
>>>) to issue the "power off" command (AXP) or send the F6 key (AXP & VAX) if enabled.
This method is useful if the virtual machine has no telnet connection available and cannot handle "rsh" and "ssh" remote connections. For more, please read Tips and Tricks - Shutdown guests with Expect tool. Important notes: - Note any local existing connection to the console has to be killed before executing the expect script.
- If the console is locked from an external connection or if the prompt is not detected after sending a carriage return, the expect script will fail.
|
rsh | Requires: - a trust to be created between the Linux server and the Tru64 or OpenVMS guest (proxy) to issue password free remote commands. For more, please read the Tips and Tricks chapter dedicated to rsh trusts.
- if the virtual machine is running OpenVMS, the CHARON_SHUTDOWN.COM script, located in the /opt/charon/utils folder, has to be copied in the SYS$MANAGER folder on the OpenVMS machine.
|
ssh | Requires: - a secured trust to be created between the Linux server and the Tru64 or OpenVMS guest (key pair) to issue password and passphrase free remote commands. For more, please read the Tips and Tricks chapter dedicated to ssh trusts.
- if the virtual machine is running OpenVMS, the CHARON_SHUTDOWN.COM script, located in the /opt/charon/utils folder, has to be copied in the SYS$MANAGER folder on the OpenVMS machine.
|
| Info |
|---|
title | Note for Red Hat Enterprise Linux/CentOS 7 and 8 |
|---|
If your application and server need time to shutdown, it could be necessary to give more time in the service definition to prevent from the service stop procedure to fail due to timeout. To do so, open the "Manage 'systemd' services" option and edit the service configuration file. You can then add the TimeoutStopSec= parameter in the Service section. The default value is 20 minutes and can be changed in the preferences menu options. Example: [Service]
...
TimeoutStopSec=3min
|
 More information can be found using the "# man systemd.service" command on your Linux server
|
...
When the script is initialized using option 6 or when a new virtual machine is added, the following lines are added:
... # Parameter $1: contains full path to cfg file
# Parameter $2: contains full path to emulator exe file
#
# Important notes:
# - comments & commands must be on separate lines
# - respect the structure of the file with case/in/esac
# - only place your commands between the selection and the ';;' line
#
. /opt/charon/utils/charon_common
#
case "$1"
in
<configuration file>)
#-- Uncomment and complete one of the following lines:
#${CHARONDIR}/utils/charon_gstop_expect \$1 \$2 root <password> "<prompt>" <TRU64/VMS>
#${CHARONDIR}/utils/charon_gstop_rsh \$1 \$2 <hostname> <TRU64/VMS>
#${CHARONDIR}/utils/charon_gstop_ssh \$1 \$2 <hostname> <TRU64/VMS>
#/<path>/<myscript>
;;
... esac
|
One of the blue colored lines above has to be uncommented depending on the method chosen. Other lines can remain in the script or can be deleted.
...
Check the guest can be reached via ping, if yes:
Issue the shutdown command via "rsh" (depends on the operating system),
Wait for a few seconds
Check if the guest can be "pinged" and repeat with an interval of 5 seconds
If the guest cannot be pinged, assume the shutdown procedure is complete
Kill the emulator process (Red Hat Enterprise Linux 6.x) or use the Use the service kill command (RHEL/CentOS 7 and 8). 
The shutdown commands does not power off nor stop the emulator process, that's why this operation is needed
Report the stop information within the guest log file
...
Check the guest can be reached via ping, if yes:
Issue the shutdown command via "ssh" (depends on the operating system),
Wait for a few seconds
Check if the guest can be "pinged" and repeat with an interval of 5 seconds
If the guest cannot be pinged, assume the shutdown procedure is complete
Kill the emulator process (Red Hat Enterprise Linux 6.x) or use Use the service kill command (RHEL/CentOS 7 and 8). The shutdown commands does not power off nor stop the emulator process, that's why this operation is needed
Report the stop information within the guest log file
Forcing service status to INACTIVE without shutdown script
If a shutdown script is not defined, stopping the service will let it in a FAILED state. In case your perform the legacy OS shutdown manually and then stops the virtual machine, you can use the following method to force the service state to INACTIVE.
Example provided for uranus virtual machine (lines to add in blue color):
...
/charon/uranus.cfg)
PID=`ps -ef|grep "$2 -d $1"|grep -v grep|awk '{print $2}'`
if test -n "${PID}"
then
kill -9 ${PID}
sleep 2
SVC=`basename $1 | sed "s=\.cfg==g"`
systemctl reset-failed charon_${SVC}
fi
exit 0
;;
...
|
A clean shutdown of the legacy OS is highly recommended.
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|