Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Tip box added on how to avoid the service FAILED state

...

Context: Red Hat Enterprise Linux 7.3 9 server with CHARONCharon-AXP V4.8 11 installed, as4100/pluto guest running

Image RemovedImage Added

Div
classpagebreak


Due to the absence of stop script, the service receives a SIGKILL signal and then, once stopped, is considered as failed:

Image RemovedImage Added

Image Removed

...

classpagebreak

...

Example2 - Guest start

Context: Red Hat Enterprise Linux 7.3 server with CHARON-AXP V4.8 installed, as4100/pluto guest stopped/failed (see above)

Image Removed

...

classpagebreak

Depending on preferences that have been set, the log will be displayed:

Image Removed

...

Image Removed

(info) The error message above (white/red) is expected the first time the virtual machine is started. It tells the .bin file does not exist as it is initialized when console parameters are set

Press CTRL-C at any time to leave the log file viewImage Added

Tip

The FAILED status is the result of the lack of stop script, as there's no way to know a clean shutdown of the legacy operating system was done. To solve this issue and have an INACTIVE state when a virtual machine is stopped, please define a stop script as explained below.


Div
classpagebreak


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

...

Example2 - Guest stop with stop script defined

Status
colourRed
titleTODO
To continue here...Context: Red Hat Enterprise Linux 7.3 9 server with CHARONCharon-AXP V4.8 11 installed, as4100/pluto guest running (not Tru64 and booted). Stop script created and customized, using the "rshssh" method (see "VM management - Create/Edit guest stop script") with example provided in the kit.

Image RemovedImage Added

Image RemovedImage Added

We can see below the guest has been properly stopped and is now in INACTIVE / REQUESTED and not in FAILED state:

Image Removed

(lightbulb) As we are running Red Hat Enterprise Linux 7.3 server, systemd allows us to check the status of the service.

Use option Image Added

Notes:

  • Option 4 of the menu can help seeing the result of the shutdown commands

...

Image Removed

Image Removed

We can see above, the expect utility has been used, did connect to the console, found the SRM prompt (the as4100 was not booted) and then issued a "power off" command.

(warning) This depends of what you decide to display in the guest stop script.

...

  • Option 4 can also be used to edit the .service file to allow you to specify the service description, the auto-restart settings, etc... For more, see "# man systemd.service"

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