---
Title: Manage lifecycle
URL Source: https://company-skill.com/p/alinux/alinux-manage-lifecycle
Language: en
Description: You need to configure, optimize, or recover an Alibaba Cloud Linux (Alinux) ECS instance—whether during initial setup, ongoing tuning, or when facing runtime failures like boot issues, package…
---

# Manage lifecycle

Part of **Alibaba Cloud Linux**. Route queries via `POST https://company-skill.com/api/route`.

## What You Want to Do

You need to configure, optimize, or recover an Alibaba Cloud Linux (Alinux) ECS instance—whether during initial setup, ongoing tuning, or when facing runtime failures like boot issues, package manager errors, or performance degradation.

**Typical User Questions**:
- How to configure vCPU pinning for better network performance?
- What to do if YUM fails in classic network?

## Decision Tree

Pick the best path for your situation:

- **If** you are performing initial setup or performance tuning (e.g., adjusting network, memory, or storage parameters) and prefer a graphical interface → Use (go to *alinux/alinux-instance*)
- **If** you need to script or automate tasks like applying security updates, managing cgroup v1 resources, or deploying kernel hot patches across many instances → Use CLI (go to *alinux/alinux-instance*)
- **If** your instance exhibits specific runtime failures such as Kernel panic, YUM repository connection failure, Time desynchronization, Pod deletion failure, ext4 resize fails, DNF segmentation fault, or unbound service timeout → Use (go to *alinux/alinux-instance*)
- **Otherwise (default)** → Start with if you're new to Alinux or lack command-line access; it provides safe, guided configuration via the Operating System Console.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| Console / Dashboard | medium | No | No | Requires RAM permissions including AliyunSysomFullAccess and operates only on Managed instance | `alinux/guide/alinux-instance` |
| CLI | medium | Yes | Yes | Enables kernel hot patch and memory QoS via cgroup v1 without reboot | `alinux/cli/alinux-instance` |
| Console / Dashboard | high | Yes | No | Addresses specific failures like OverlayFS dentry leak and soft lockup | `alinux/troubleshooting/alinux-instance` |

## Path Details

### Path 1: Console / Dashboard
**Brief Description**: Configure Alibaba Cloud Linux instances using the Operating System Console in the Alibaba Cloud Console, accessing features like System Diagnosis and Component Management without executing CLI commands. This path requires the instance to be a Managed instance and uses the Instance ID to link diagnostics.

**Key technical facts**:
- Billing: ECS1
- Auth method: RAMAliyunECSReadOnlyAccessAliyunSubManageFullAccessAliyunSysomFullAccess

### Path 2: CLI

**Brief Description**: Use command-line tools directly on the instance to manage security updates, apply kernel hot patches, and control resources via cgroup v1 interfaces. Commands like `yum upgrade --security` and `livepatch-mgr` enable non-disruptive maintenance and memory QoS tuning.

**Key technical facts**:
- Billing: ECSCLI
- Auth method: rootsudo

**When to Use**:
- cgroupCPU BurstQoS

- BCCyum install -y bcc-tools
- systemctl disable update-motd

### Path 3: Console / Dashboard
**Brief Description**: Diagnose and resolve specific runtime failures using CLI tools like `dmesg`, `fsck.ext4`, and `hwclock`. This path addresses documented issues including Kernel panic, OverlayFS dentry leak, YUM repository connection failure (in classic network), Time desynchronization after reboot, Pod deletion failure in Kubernetes, ext4 resize fails, DNF segmentation fault (SysAK 2.2.0), and unbound service timeout in VPCs without public access.

**Key technical facts**:
- Billing: ECS
- Auth method: rootsudo

- Kubernetes Pod'Terminating'

- DNFSysAK 2.2.0

## FAQ

Q: Which path should I start with?
A: If you're configuring a new instance or tuning performance and have console access, start with . If you're already in a broken state (e.g., can't install packages or time is wrong), go straight to .

Q: What if I need to apply a kernel hot patch across 50 instances but used the console path?
A: You'll hit a limitation: the Operating System Console doesn’t support kernel hot patch deployment. Only the CLI path supports livepatch-mgr for non-reboot updates.

Q: What if my instance has YUM repository connection failure in classic network but I tried the guide path?
A: The System Diagnosis tool won’t fix YUM repository connection failure—it’s a CLI-level issue specific to classic network. You must use the troubleshooting path with `yum clean all`.

Q: Can I use the CLI path if I don’t have root access?
A: No. Both CLI and troubleshooting paths require root or sudo permissions. Without it, you cannot execute `livepatch-mgr`, adjust cgroup v1 settings, or run `fsck.ext4`.

Q: Does the console path work for all instance types?
A: It only works for Managed instance with proper RAM permissions (AliyunSysomFullAccess). Unmanaged instances or those missing roles won’t appear in System Diagnosis.

Q: What happens if I try to resize an ext4 filesystem using the guide path?
A: The console’s disk management doesn’t handle filesystem resizing—you’ll still need to run `growpart` and `resize2fs` manually, which is covered only in the troubleshooting path under "ext4 resize fails".

Q: Is memory QoS configurable via the console?
A: No. Memory QoS requires direct manipulation of cgroup v1 files, which is only possible through the CLI path.

## Related queries

manage ecs lifecycle, configure ecs instance, ecs tuning, ecs kernel parameters, ecs troubleshooting, how to tune alinux, ecs performance tuning, ecs startup issues, fix yum failure, sync time on ecs, apply kernel hot patch, limit page cache, vcpu pinning ecs, disk partition after creation, ecs oom

---
Part of [Alibaba Cloud Linux](https://company-skill.com/p/alinux.md) · https://company-skill.com/llms.txt