1603606 : NO aklog on specific worker nodes

Created: 2026-05-26T15:04:08Z - current status: new

Summary:

A user reports inconsistent availability of aklog on reserved Maxwell worker nodes (wn143 and wn148). Specifically, wn148 lacks aklog, while wn143 has it. The user asks if this is intentional and how to ensure aklog is consistently available.

Anonymized Issue:

A user observed that on two reserved Maxwell worker nodes ([NODE_A] and [NODE_B]), the aklog utility is missing on [NODE_B] but present on [NODE_A]. They seek clarification on whether this discrepancy is expected and how to guarantee its presence on all nodes.

---

Solution Suggestion:

  1. Check Node Configuration: Verify if the absence of aklog on [NODE_B] is due to a missed software installation or misconfiguration during setup. Use package managers (e.g., rpm, dpkg) to confirm its presence: bash rpm -qa | grep krb5-workstation # Example for RHEL-based systems

  2. Reinstall/Deploy aklog: If missing, reinstall aklog (part of Kerberos client tools) on the affected node: bash sudo yum install krb5-workstation # For CentOS/RHEL Or consult Maxwell’s software stack documentation for cluster-specific deployment methods.

  3. Consistency Across Nodes: Ensure uniform provisioning across all worker nodes. If using a shared filesystem or module system (e.g., Spack), verify that aklog is loaded via: bash spack load krb5 # Hypothetical example; adjust per Maxwell’s setup

  4. Support Escalation: If the issue persists, contact Maxwell support with details (anonymized) to investigate potential node-specific anomalies.

Sources: (No direct references in provided context; general troubleshooting steps apply.)