Versions Compared

Old Version 35

changes.mady.by.user Bruno Miretti

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Forcing service status to INACTIVE without shutdown script added

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

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 "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

  • Use the service kill command. (question) 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
    ;;
...

(warning) A clean shutdown of the legacy OS is highly recommended.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc