My Oracle Support Banner

HSM (SAM-QFS): sam-amld Daemon Becomes Unresponsive And Has init As a Parent (Doc ID 1908038.1)

Last updated on JULY 21, 2022

Applies to:

Oracle Hierarchical Storage Manager (HSM) and StorageTek QFS Software - Version 5.3 and later
Information in this document applies to any platform.

Symptoms

When stopping the samfs archiving daemons by running a samd stop, the sam-amld(1M) daemon does not get killed and it's parent becomes the init(1M) process.

In the above output, there are also 3 <defunct> processes, each with the parent process ID pointing to the runaway sam-amld(1M). These defunct processes correspond to its childprocesses sam-catserverd(1M), sam-scannerd(1M) and sam-robotsd(1M) respectively.

As a result, the archiving daemons can not he restarted, as a (rogue) sam-amld(1) is already running, and the sam-fsd(1) primary daemon verifies that only 1 sam-amld(1M) process is running at any time.

Changes

 Customer changed the partitioning of the robot without first logically offline the library and drives in samfs.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.