Serviceguard Version A.11.16 Release Notes, 2nd Edition, September 2004

Serviceguard Version A.11.16 Release Notes, Second Edition
Known Problems and Workarounds
Chapter 1 53
— Halt Serviceguard on the node, then restart it. This will create
the monitor request. Then start the package.
JAGad39695 User error can result in "ghost" services:
• What is the problem? When the package was shutdown, references
for this service had already been removed, and the service failed
while the package was halting. Since the service no longer exists, it
cannot be halted manually. Any attempt to do so results in this error:
cmhaltserv : Service name oasmon is not running.
Due to the failure of the service, cmsrvassistd tries to re-start the
service since it was never halted. However, when cmsrvassistd goes
to register the re-started service, it’s status entry has been removed
by cmcld because of the package shutdown. When the customer
issues the cmapplyconf, this service is permanently removed from
cmcld although cmsrvassistd is still trying to re-start it. Therefore
after the cmapplyconf the "ghost" service still cannot be stopped
because cmcld denies its existence.
• What is the workaround? One workaround is to make sure you follow
the correct procedure when removing a service: halt the package
BEFORE you start editing any file.
Here are two ways to fix the problem, however, if you do get into this
solution:
— Follow these steps:
1. Halt the package
2. Add the service back into the ASCII file
3. Re-apply the configuration
4. Manually halt the service with cmhaltserv
5. Re-remove the service from the ASCII file
6. Re-apply the configuration
7. Re-start the package