本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。
# 问题排查
本节包含有关如何监控系统以及如何解决特定问题的信息。
**Topics**
+ [常规调试和监控](res-troubleshooting-general.md)
+ [问题 RunBooks](res-troubleshooting-issue-runbooks.md)
+ [已知问题](res-troubleshooting-known-issues.md)
详细内容：
+ [常规调试和监控](res-troubleshooting-general.md)
+ [有用的日志和事件信息来源](res-troubleshooting-general.md#res-troubleshooting-general-info)
+ [在哪里可以找到环境变量](res-troubleshooting-general.md#res-troubleshooting-general-info-env-vars)
+ [环境 Amazon EC2 实例上的日志文件](res-troubleshooting-general.md#res-troubleshooting-general-info-logs)
+ [CloudFormation 堆栈](res-troubleshooting-general.md#res-troubleshooting-cf-stacks)
+ [由于问题导致的系统故障，并反映在 Amazon EC2 Auto Scaling 组活动中](res-troubleshooting-general.md#res-troubleshooting-asg-activity)
+ [典型的亚马逊 EC2 控制台外观](res-troubleshooting-general.md#res-troubleshooting-ec2-console)
+ [基础架构主机](res-troubleshooting-general.md#res-troubleshooting-ec2-console-infra)
+ [基础架构主机和虚拟桌面](res-troubleshooting-general.md#res-troubleshooting-ec2-console-virtual)
+ [处于终止状态的主机](res-troubleshooting-general.md#res-troubleshooting-ec2-console-hosts-terminated)
+ [有用的活动目录 (AD) 相关命令供参考](res-troubleshooting-general.md#res-troubleshooting-ec2-console-active-dir)
+ [Windows DCV 调试](res-troubleshooting-general.md#res-troubleshooting-windows-dcv)
+ [查找 Amazon DCV 版本信息](res-troubleshooting-general.md#res-troubleshooting-find-nice-dcv)
+ [问题 RunBooks](res-troubleshooting-issue-runbooks.md)
+ [安装问题](res-troubleshooting-issue-runbooks.md#installation-issues)
+ [CloudFormation 堆栈创建失败，并显示消息 “” WaitCondition 已收到失败消息。 Error:States.TaskFailed”](res-troubleshooting-issue-runbooks.md#cf-stack-fails)
+ [成功创建 CloudFormation 堆栈后未收到电子邮件通知](res-troubleshooting-issue-runbooks.md#email-invitation-not-received)
+ [实例正在循环或 vdc 控制器处于故障状态](res-troubleshooting-issue-runbooks.md#instances-cycling)
+ [由于依赖对象错误，无法删除环境 CloudFormation 堆栈](res-troubleshooting-issue-runbooks.md#object-error)
+ [创建环境时遇到 CIDR 块参数错误](res-troubleshooting-issue-runbooks.md#cidr-block-error)
+ [CloudFormation 创建环境期间堆栈创建失败](res-troubleshooting-issue-runbooks.md#cf-stack-creation-fails)
+ [创建外部资源（演示）堆栈失败，并显示 AdDomainAdminNode CREATE\_FAILED](res-troubleshooting-issue-runbooks.md#demo-environment-stack-fails)
+ [身份管理问题](res-troubleshooting-issue-runbooks.md#troubleshooting-identity-management)
+ [我无权执行 iam：PassRole](res-troubleshooting-issue-runbooks.md#res-troubleshooting-issue-runbooks-unauth-passrole)
+ [我想允许 AWS 账户以外的人通过 AWS 资源访问我的研究与工程工作室](res-troubleshooting-issue-runbooks.md#res-troubleshooting-issue-runbooks-outside-acct)
+ [登录环境后，我会立即返回登录页面](res-troubleshooting-issue-runbooks.md#return-to-login)
+ [尝试登录时出现 “未找到用户” 错误](res-troubleshooting-issue-runbooks.md#user-not-found)
+ [用户已添加到活动目录中，但在 RES 中丢失](res-troubleshooting-issue-runbooks.md#user-missing)
+ [创建会话时用户不可用](res-troubleshooting-issue-runbooks.md#session-user-unavailable)
+ [CloudWatch 集群管理器日志中出现超出大小限制错误](res-troubleshooting-issue-runbooks.md#sizelimit-exceeded-error)
+ [仓储服务](res-troubleshooting-issue-runbooks.md#res-troubleshooting-storage)
+ [我通过 RES 创建了文件系统，但它没有挂载到 VDI 主机上](res-troubleshooting-issue-runbooks.md#res-troubleshooting-storage-created)
+ [我通过 RES 加载了一个文件系统，但它没有挂载到 VDI 主机上](res-troubleshooting-issue-runbooks.md#res-troubleshooting-storage-onboarded)
+ [我无法从 VDI 主机 read/write 上打开](res-troubleshooting-issue-runbooks.md#res-troubleshooting-storage-rw)
+ [权限处理用例示例](res-troubleshooting-issue-runbooks.md#res-troubleshooting-storage-rw-example)
+ [我从 RES 创建了适用于 NetApp ONTAP 的 Amazon FSx 但它没有加入我的域名](res-troubleshooting-issue-runbooks.md#res-troubleshooting-storage-join)
+ [快照](res-troubleshooting-issue-runbooks.md#res-troubleshooting-snapshots)
+ [快照的状态为 “失败”](res-troubleshooting-issue-runbooks.md#res-troubleshooting-snapshots-failed)
+ [快照应用失败，日志显示无法导入表。](res-troubleshooting-issue-runbooks.md#res-troubleshooting-snapshots-not-imported)
+ [Infrastructure](res-troubleshooting-issue-runbooks.md#res-troubleshooting-infrastructure)
+ [负载均衡器目标群组没有运行正常的实例](res-troubleshooting-issue-runbooks.md#res-troubleshooting-infrastructure-load-balancer)
+ [启动虚拟桌面](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops)
+ [我需要在 RES 门户网站上启动/恢复大量 VDI](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-resume-vdis)
+ [Windows 虚拟桌面的登录帐户设置为管理员](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-windows-admin)
+ [使用外部资源时证书过期 CertificateRenewalNode](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-certificate-expires)
+ [以前运行的虚拟桌面无法再成功连接](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-was-working)
+ [我只能启动 5 个虚拟桌面](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-only-five)
+ [桌面 Windows 连接尝试失败，并显示 “连接已关闭”。传输错误”](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-transport-error)
+ [VDI 停留在配置状态](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-stuck-prov)
+ [VDI 在启动后进入错误状态](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-error-after)
+ [登录后 VDI 会话进入空白屏幕](res-troubleshooting-issue-runbooks.md#res-troubleshooting-virtual-desktops-vdi-blank-screen)
+ [虚拟桌面组件](res-troubleshooting-issue-runbooks.md#res-troubleshooting-vd-component)
+ [Amazon EC2 实例在控制台中反复显示已终止](res-troubleshooting-issue-runbooks.md#res-troubleshooting-vd-component-ec2-terminated)
+ [由于无法加入 AD/eVDi 模块显示 API Health Check 失败，vdc-controller 实例正在循环](res-troubleshooting-issue-runbooks.md#res-troubleshooting-vd-component-cycling)
+ [编辑软件堆栈以添加项目时，项目不会出现在下拉列表中](res-troubleshooting-issue-runbooks.md#res-troubleshooting-vd-component-not-in-pulldown)
+ [cluster-manager Amazon CloudWatch 日志显示 “账户尚不可用。正在等待用户同步”（其中账户是用户名）](res-troubleshooting-issue-runbooks.md#res-troubleshooting-vd-component-acct-unavailable)
+ [尝试登录时的 Windows 桌面显示 “您的帐户已被禁用。请咨询您的管理员”](res-troubleshooting-issue-runbooks.md#res-troubleshooting-vd-component-acct-disabled)
+ [external/customer AD 配置的 DHCP 选项问题](res-troubleshooting-issue-runbooks.md#res-troubleshooting-vd-component-dhcp)
+ [Firefox 错误 MOZILLA\_PKIX\_ERROR\_REQUIRED\_TLS\_FEATURE\_MISSING](res-troubleshooting-issue-runbooks.md#res-troubleshooting-vd-firefox)
+ [环境删除](res-troubleshooting-issue-runbooks.md#res-troubleshooting-env-deletion)
+ [res-xxx-cluster 堆栈处于 “DELETE\_FAILED” 状态，由于 “角色无效或无法假设” 错误，无法手动删除](res-troubleshooting-issue-runbooks.md#res-troubleshooting-env-deletion-role-invalid)
+ [收集日志](res-troubleshooting-issue-runbooks.md#res-troubleshooting-env-deletion-collect-logs)
+ [正在下载 VDI 日志](res-troubleshooting-issue-runbooks.md#res-troubleshooting-env-deletion-download-logs)
+ [从 Linux EC2 实例下载日志](res-troubleshooting-issue-runbooks.md#res-troubleshooting-env-deletion-linux-ec2-logs)
+ [从 Windows EC2 实例下载日志](res-troubleshooting-issue-runbooks.md#res-troubleshooting-env-deletion-windows-ec2-logs)
+ [正在收集 WaitCondition 错误的 ECS 日志](res-troubleshooting-issue-runbooks.md#res-troubleshooting-env-deletion-waitcondition)
+ [演示环境](res-troubleshooting-issue-runbooks.md#res-troubleshooting-demo-env)
+ [处理对身份提供商的身份验证请求时出现演示环境登录错误](res-troubleshooting-issue-runbooks.md#demo-environment-login-error)
+ [演示堆栈 keycloak 不起作用](res-troubleshooting-issue-runbooks.md#demo-environment-stack-keycloak)
+ [活动目录问题](res-troubleshooting-issue-runbooks.md#active-directory-issues)
+ [我的 VDI 长时间处于配置状态，或者在 VDI 准备就绪后我无法以 AD 用户身份登录 VDI](res-troubleshooting-issue-runbooks.md#active-directory-issues-vdi-stuck)
+ [配置 SSO 后我无法登录 RES 门户网站](res-troubleshooting-issue-runbooks.md#active-directory-issues-res-web-portal)
+ [即使成功启动 Linux VDI，AD 用户也无法使用文件浏览器访问主目录](res-troubleshooting-issue-runbooks.md#active-directory-issues-home-directory-access)
+ [启用 SSH 访问后，AD 管理员用户无法访问堡垒主机](res-troubleshooting-issue-runbooks.md#active-directory-issues-bastion-host-access)
+ [查看和管理由 RES 外部资源堆栈部署的 Active Directory](res-troubleshooting-issue-runbooks.md#active-directory-issues-external-resource-stack)
+ [2024.x 已知问题](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x)
+ [（2024.12 和 2024.12.01）注册新的 Cognito 用户时正则表达式失败](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-regex-failure-cognito)
+ [（2024.12.01 及更早版本）使用自定义域连接到 VDI 时出现无效的错误证书错误](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-invalid-bad-cert)
+ [（2024.12 和 2024.12.01）Active Directory 用户无法通过 SSH 连接到堡垒主机](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-ad-users-cannot-ssh)
+ [(2024.10) 部署在隔离 VPC 中的 RES 环境的 VDI auto stop 中断](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-vdi-auto-stop-broken)
+ [（2024.10 及更早版本）无法为图形增强型实例类型启动 VDI](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-fail-to-launch-vdi)
+ [(2024.08) 准备基础设施 AMI 故障](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-prep-infra-ami-fail)
+ [(2024.08) 虚拟桌面无法挂载带有根存储桶 ARN 和自定义前缀的 read/write Amazon S3 存储桶](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-vdi-fails-to-mount-s3)
+ [(2024.06) 当 AD 组名称包含空格时，应用快照失败](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-apply-snapshot-fails)
+ [（2024.06 及更早版本）在 AD 同步期间，群组成员未与 RES 同步](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-group-not-synced)
+ [（2024.06 及更早版本） CVE-2024-6387、RegressHion、RHEL9 和 Ubuntu VDI 中的安全漏洞](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-regresshion)
+ [(2024.04-2024.04.02) 提供的 IAM 权限边界未附加到 VDI 实例的角色](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-iam-boundary)
+ [（2024.04.02 及更早版本）ap-southeast-2（悉尼）中的 Windows NVIDIA 实例无法启动](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-nvidia-instances)
+ [(2024.04 和 2024.04.01) RES 删除失败 GovCloud](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-delete-fail)
+ [(2024.04-2024.04.02) Linux 虚拟桌面在重启时可能处于 “恢复” 状态](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-linux-stuck-resuming)
+ [(2024.04.02 及更早版本) 无法同步 SAMAccountName 属性包含大写字母或特殊字符的 AD 用户](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-samaccountname)
+ [（2024.04.02 及更早版本）用于访问堡垒主机的私钥无效](res-troubleshooting-known-issues.md#res-troubleshooting-known-issues-2024x-private-key)