| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
| Method | Comments |
|---|---|
expect | Requires you pass user and password to the script so that it can connect to the OPA0 console via "
This method is useful if the virtual machine has no telnet connection available and cannot handle " Important notes:
|
rsh | Requires:
|
ssh | Requires:
|
...
| class | pagebreak |
|---|
...
|
...
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:
|
...
More information can be found using the "# man systemd.service" command on your Linux server
Options
...
- Options 1 to 5 are explanations on how to setup and prepare the virtual machine and the Charon Linux server (if necessary) to use the three available methods.
- Option 6 edits the script. This script is in a form of "case in <configuration filename> do ..."
- Option 7 is used to test the script. Use with caution on production machines.
...
You'll find in options 1 to 5 all the details to setup the remote connection: packages to install, proxy settings for rsh, key pair definition for ssh (password and passphrase free), the necessary firewall settings if needed, etc...
| Include Page | ||||
|---|---|---|---|---|
|
...
When the script is initialized using option 6 or when a new virtual machine is added, the following lines are added:
...
...
|
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.
...
The editor defined in the Preferences is used to edit the script.
...
|
| Div | ||
|---|---|---|
| ||
Stop script execution example with "ssh" on Red Hat Enterprise Linux 7.59:
| Include Page | ||||
|---|---|---|---|---|
|
Provided shutdown scripts explanation
...
| title | Note for Red Hat Enterprise Linux 7.x and CentOS 7.x |
|---|
...
Please note: whatever the shutdown script execution result is, the stop request sent by the systemctl command will stop the emulator. It is very important then to ensure the stop script has been tested and validated.
charon_gstop_expect
- Check if there's an active connection to the console on the local host, kill if any.
- Execute the /opt/charon/utils/guest_shutdown.exp expect script with the values provided: username (root), password, prompt, operating system (either TRU64 or VMS). This script is able to send the shutdown command depending on the returned characters on the console. This can be the SRM prompt ">>>", the "login:" or "username:" prompts or the prompt of the logged in user.
- Report all output to
/opt/charon/log/console.stop.<guest name>.log.
...
Check the guest can be reached via ping, if yes:
Issue the
shutdowncommand 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 Use the
service killcommand (RHEL 7.x and CentOS 7. x).
The shutdown commands does not power off nor stop the emulator process, that's why this operation is neededReport the stop information within the guest log file
| Div | ||
|---|---|---|
| ||
charon_gstop_ssh
Check the guest can be reached via ping, if yes:
Issue the
shutdowncommand 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 killcommand (RHEL 7.x and CentOS 7.x). The shutdown commands does not power off nor stop the emulator process, that's why this operation is neededReport the stop information within the guest log file
...
Optional guest display status script
It is possible to create a script, "/opt/charon/utils/charon_gstart.chkrun" (an example is provided in the 'charon_gstart.chkrun.example' file) that will add a status line while displaying the guests list for running guests only. This script, if needed, has to be created manually and must be executable.
This status line is the result of the command you executed for that guest (known by its configuration file), for example a ping, an ssh command displaying uptime (Tru64) or boottime (OpenVMS).
Display output example from the "vmlist" command:
...
In this example, we use "ssh" to display the guest "uptime".
The last 2 lines containing the RETVAL variable are mandatory
To create the script, the following commands were executed to copy the provided example to the one that will be used:
...
# cp /opt/charon/utils/charon_gstart.chkrun.example /opt/charon/utils/charon_gstart.chkrun# chmod 744 /opt/charon/utils/charon_gstart.chkrun# vim /opt/charon/utils/charon_gstart.chkrun
Example file provided (contains example for Tru64 and OpenVMS):
...
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 you 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}'` ... |
A clean shutdown of the legacy OS is highly recommended.
| Include Page | ||||
|---|---|---|---|---|
|