---
Title: Troubleshoot issues
URL Source: https://company-skill.com/p/ecs/ecs-troubleshoot-issues
Language: en
Description: You're encountering unexpected behavior or errors on your ECS instance at the operating system level—either because something is broken (e.g., GNOME panel missing, sysctl -p fails) or because you…
---

# Troubleshoot issues

Part of **Elastic Compute Service (ECS)**. Route queries via `POST https://company-skill.com/api/route`.

## What You Want to Do

You're encountering unexpected behavior or errors on your ECS instance at the operating system level—either because something is broken (e.g., GNOME panel missing, `sysctl -p` fails) or because you want to proactively configure system policies (e.g., enforce account lockout or skip Windows privacy prompts).

**Typical User Questions**:
- How to fix missing GNOME top panel on Ubuntu?
- Why does sysctl -p show 'unknown key' for IPv6 settings?
- How to disable privacy setup on first Windows login?
- How to set up account lockout policy on Ubuntu 20.04?

## Decision Tree

Pick the best path for your situation:

- **If** you are trying to **proactively configure system behavior** such as an **account lockout policy using `pam_faillock.so`** or disable **Windows OOBE privacy setup via Group Policy** → Use (go to *ecs/ecs-system*)
- **If** you are **fixing a specific OS error**, such as `sysctl -p` reporting **"unknown key" for `net.ipv6.conf.all.disable_ipv6`** or needing to run `modprobe ipv6` to restore IPv6 functionality → Use (go to *ecs/ecs-system*)
- **Otherwise (default)** → Start with ****, as most user-reported issues involve diagnosing and repairing unexpected system behavior rather than proactive policy configuration.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| Console / Dashboard | low | No | No | Requires domain-joined Windows instances for GPO-based privacy suppression | `ecs/guide/ecs-system` |
| Alibaba Cloud LinuxUbuntuWindows | medium | No | No | Only covers documented errors like `net.ipv6.conf.all.disable_ipv6 is an unknown key` | `ecs/troubleshooting/ecs-system` |

## Path Details

### Path 1: Console / Dashboard
**Best For**: behavior 

**Brief Description**: This path uses system-level tools like the PAM module `pam_faillock.so` and its configuration file `faillock.conf` to enforce an **account lockout policy** on Ubuntu 20.04. On Windows, it leverages the **Group Policy Management Console (GPMC)** to apply the policy **"Don’t launch privacy settings experience on user logon"**, which skips the **OOBE (Out-of-Box Experience)** privacy setup during first login.

**Key technical facts**:
- Billing: free

**When to Use**:
- Ubuntu 20.04
- Windows ECS
- Active DirectoryGPO

**When NOT to Use**:
- Ubuntu 20.04Windows

- Root`even_deny_root`
- Ubuntu 20.04WindowsECS

### Path 2: Console / Dashboard
**Best For**: Alibaba Cloud LinuxUbuntuWindows

**Brief Description**: This path addresses concrete OS-level failures, such as when running `sysctl -p` returns an **"unknown key"** error for the parameter `net.ipv6.conf.all.disable_ipv6`. The fix typically involves verifying that the **IPv6** kernel module is loaded (via `modprobe ipv6`) and ensuring correct syntax in `sysctl.conf`. It focuses on adjusting **kernel parameters** for known, documented issues.

**Key technical facts**:
- Billing: free

**When to Use**:
- `sysctl -p``net.ipv6.conf.all.disable_ipv6 is an unknown key`
- IPv6`sysctl.conf`
- Linuxroot shell

**When NOT to Use**:
- IPv6`sysctl`

## FAQ

Q: Which path should I start with?
A: Start with **** unless you are explicitly setting up an **account lockout policy** or disabling **Windows privacy setup on first login**—those are the only clear triggers for the configuration path.

Q: What if I’m using Ubuntu 18.04 but try to use the account lockout policy path?
A: You’ll hit a limitation: the configuration path **does not support non-Ubuntu 20.04 systems**, so `pam_faillock.so` behavior may differ or lack documentation.

Q: What if my Windows ECS instance is not joined to a domain but I try to disable OOBE privacy via Group Policy?
A: The setting **"Don’t launch privacy settings experience on user logon"** will have no effect—this method **only works on domain-joined devices**, per the limitations.

Q: Can I use the troubleshooting path to fix GNOME panel disappearance on Ubuntu?
A: Yes—if the issue matches a documented OS-specific problem (like desktop environment corruption), it falls under this path. However, note that the fact cards only explicitly validate coverage for **IPv6/sysctl** errors; other issues may not be covered.

Q: What happens if I try to use the policy path to fix an "unknown key" error from `sysctl -p`?
A: You’ll waste time—the policy path deals with **authentication and login behavior**, not **kernel parameter** errors like `net.ipv6.conf.all.disable_ipv6`. The fix requires `modprobe ipv6` and `sysctl.conf` edits, which are in the troubleshooting path.

Q: Does the troubleshooting path work for Windows registry issues?
A: No—the fact card states it **does not cover Windows generic faults** unless tied to documented scenarios (which currently focus on Linux). Windows issues outside OOBE privacy setup are not addressed.

Q: Is there a risk of locking myself out when configuring `even_deny_root` in `faillock.conf`?
A: Yes—enabling `even_deny_root` can **lock the root account** after failed attempts, creating serious **operational risk**. Always keep a second active root session during testing.

## Related queries

troubleshoot ECS system issues, fix system errors on ECS, ECS instance system troubleshooting, resolve OS-level problems, diagnose ECS system behavior, how to fix missing GNOME panel, sysctl unknown key error, disable privacy setup on first Windows login, configure account lockout policy Ubuntu, pam

---
Part of [Elastic Compute Service (ECS)](https://company-skill.com/p/ecs.md) · https://company-skill.com/llms.txt