rustfs/rustfs · error · LifecycleError

System has not been initialized

Error message

System has not been initialized

What it means

Notification-system lifecycle guard: an operation required the global notification system, but it has not been initialized yet (sentinel NotInitialized). Fired when targets/rules are used before the system's init completed or after a failed init.

Source

Thrown at crates/notify/src/error.rs:28

//  distributed under the License is distributed on an "AS IS" BASIS,
//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
//  See the License for the specific language governing permissions and
//  limitations under the License.

use rustfs_targets::{TargetError, arn::TargetID};
use std::io;
use thiserror::Error;
use tokio::task::JoinError;

/// Errors related to the notification system's lifecycle.
#[derive(Debug, Error)]
pub enum LifecycleError {
    /// Error indicating the system has already been initialized.
    #[error("System has already been initialized")]
    AlreadyInitialized,

    /// Error indicating the system has not been initialized yet.
    #[error("System has not been initialized")]
    NotInitialized,
}

/// Error types for the notification system
#[derive(Debug, Error)]
pub enum NotificationError {
    #[error("Target error: {0}")]
    Target(#[from] TargetError),

    #[error("Configuration error: {0}")]
    Configuration(String),

    #[error("ARN not found: {0}")]
    ARNNotFound(String),

    #[error("Invalid ARN: {0}")]
    InvalidARN(String),

View on GitHub (pinned to 35af688cd9)

Solutions

1. Initialize the notification system before issuing notification operations
2. Check startup logs for an earlier initialization failure and fix it

When it happens

Trigger: Thrown at crates/notify/src/error.rs:28 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of rustfs/rustfs@35af688cd9 (2026-08-20). Data as JSON: /api/errors/5e46fa8e9014505a. Report an issue: GitHub.