[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6995D12PBG5BXRHZ8KCY7DW":3,"skill-same:01M6995D12PBG5BXRHZ8KCY7DW":107},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6995D12PBG5BXRHZ8KCY7DW","google-cloud-filestore-log-troubleshooting",null,"Diagnoses and resolves Filestore client mount failures on Google Cloud, permission errors (EACCES), and network timeouts (ETIMEDOUT). Use when an NFS mount hangs or fails from a Compute Engine VM, GKE pod, Cloud Run service, or Vertex AI workload, when `mount.nfs` reports \"Connection timed out\" or \"access denied by server\", when checking whether VPC ingress firewall rules or `nfsExportOptions` allow a client IP, or when a previously working Filestore share suddenly stops mounting after an administrative change. Don't use for Cloud Storage (GCS) buckets, Persistent Disk, or Cloud NetApp Volumes, and don't use for Filestore capacity scaling or backup and export-policy auditing.","google\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",24122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,9,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"google cloud filestore log troubleshooting","google cloud","log","troubleshooting","cloud","vm","use","for","cloud run","nfs","run","gke","change","server","disk","Cloud Storage","vpc","firewall","policy","vertex ai","2026-11-10 10:12:30",false,"---\nname: google-cloud-filestore-log-troubleshooting\nmetadata:\n  version: \"1.0.2\"\n  category: Storage\ndescription: >-\n  Diagnoses and resolves Filestore client mount failures on Google Cloud,\n  permission errors (EACCES), and network timeouts (ETIMEDOUT). Use when an NFS\n  mount hangs or fails from a Compute Engine VM, GKE pod, Cloud Run service, or\n  Vertex AI workload, when `mount.nfs` reports \"Connection timed out\" or \"access\n  denied by server\", when checking whether VPC ingress firewall rules or\n  `nfsExportOptions` allow a client IP, or when a previously working Filestore\n  share suddenly stops mounting after an administrative change. Don't use for\n  Cloud Storage (GCS) buckets, Persistent Disk, or Cloud NetApp Volumes, and\n  don't use for Filestore capacity scaling or backup and export-policy auditing.\n---\n\n\u003C!-- disableFinding(LINE_OVER_80) -->\n\n# Filestore Log-Based Troubleshooting\n\nDiagnoses, troubleshoots, and remediates Filestore client mount failures, permission errors (`EACCES`), and network timeouts (`ETIMEDOUT`) across projects.\n\n## Prerequisites & Quick Start\n\nRequired IAM roles on target project(s) (and Shared VPC host project if applicable):\n*   **Read**: `roles\u002Ffile.viewer` (instance & export ACLs), `roles\u002Fcompute.networkViewer` (VPC firewall rules), `roles\u002Flogging.viewer` (Cloud Audit & GKE CSI logs), `roles\u002Fmcp.toolUser` (if using MCP tools).\n*   **Write (Remediation only)**: `roles\u002Ffile.editor` (export ACL updates), `roles\u002Fcompute.securityAdmin` (firewall rule creation).\n\nAuthenticate, verify billing\u002FAPIs, and configure your environment:\n\n```bash\ngcloud auth login && gcloud auth application-default login\ngcloud billing projects describe {project_id} --format=\"value(billingEnabled)\"\ngcloud services enable file.googleapis.com compute.googleapis.com logging.googleapis.com --quiet\ngcloud config set project {project_id} && gcloud config set compute\u002Fregion {region}\n```\n\n## Usage Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read and follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## Conceptual & Informational Queries (CRITICAL)\n\nFor purely conceptual, architectural, or educational questions (e.g., \"What causes EACCES on Filestore?\", \"Why does GKE Node IP appear instead of Pod IP?\", \"What ports does Filestore require?\", \"Explain root squash\"):\n*   **Rule**: **Answer immediately using pre-trained knowledge and the workflow rules below.** Answering directly minimizes tool latency and token usage when the user only seeks architectural guidance.\n*   **Constraint**: **Do not execute external tool calls or API requests** for basic knowledge questions.\n\n## Handling \"No-Command\" Constraints (CRITICAL)\n\nIf the user prompt contains constraints like \"Do not execute commands\", \"without executing\", or \"read-only\":\n*   **Rule**: **Strictly avoid calling `run_command`** to execute any shell, Python, or `gcloud` commands.\n*   **Discovery**:\n    1.  Always read [Usage Attribution](references\u002Fattribution.md) first so every recommended `gcloud` command includes the required attribution environment variable.\n    2.  Check if Filestore MCP tools (`get_instance`, `list_instances`) are available and use them (API calls, not command executions).\n    3.  If MCP tools are unavailable, read `references\u002Fmock-fleet-data.md` **only if** the requested instance matches one of the evaluation scenarios (`finance-share`, `shared-nfs`, `ml-data`, `data-hub`, `prod-share`). Never report mock data as live production state. If the instance is not listed there, state that live access is required and provide the exact attributed commands for the user to run.\n    4.  **Fast-Path Stop Rule**: Once you have read [Usage Attribution](references\u002Fattribution.md) and located the target instance in `references\u002Fmock-fleet-data.md`, **stop reading additional files immediately** and formulate your response with the attributed `gcloud` remediation command. Do **NOT** read `scripts\u002Fquick_diagnose.py`, `scripts\u002Fdiagnose_lib.py`, `_internal\u002Fquick_diagnose_test.py`, or `EVAL.*` files when command execution is disabled, as inspecting code\u002Ftest files wastes turns and triggers timeouts.\n*   **Mandatory User Confirmation Requirement**: Even when command execution is disabled or the user asks only for recommendations, your response **MUST STILL end with a clear question prompting the user for explicit confirmation** before applying any remediation (e.g., *\"Would you like me to proceed with creating the VPC ingress firewall rule `[rule_name]`? Please confirm to proceed.\"*).\n\n## Multi-Runtime Execution Options\n\n### Option 1: Bundled Python CLI Script (Recommended for CLI \u002F Terminal Agents)\n\n```bash\n# Single instance diagnosis\npython3 scripts\u002Fquick_diagnose.py --instance=\"\u003CINSTANCE_ID>\" --location=\"\u003CLOCATION_OR_ZONE>\" \\\n    [--project=\"\u003CPROJECT_ID>\"] [--client-ip=\"\u003CCLIENT_IP>\"] [--client-subnet=\"\u003CCLIENT_SUBNET_CIDR>\"]\n\n# Bulk project-wide fleet diagnosis\npython3 scripts\u002Fquick_diagnose.py --all --project=\"\u003CPROJECT_ID>\" [--json]\n```\n\n| Flag | Purpose |\n| :--- | :--- |\n| `--instance`, `--location` | Filestore instance ID and region\u002Fzone (`--zone` is a legacy alias). Required unless `--all`. |\n| `--project` | GCP project ID (defaults to active `gcloud` project). |\n| `--client-ip` \u002F `--client-subnet` | Client IP or CIDR to evaluate against export ACLs and ingress firewall rules. |\n| `--json` | Emit machine-readable JSON on stdout (narrative report goes to stderr). |\n| `--apply-fix` | Execute generated remediation commands. **Only pass after explicit user confirmation.** |\n\n### Option 2: Filestore MCP Tools \u002F REST API \u002F `gcloud` CLI\n*   **MCP Tools**: Call `get_instance(name='projects\u002F{project_id}\u002Flocations\u002F{location}\u002Finstances\u002F{instance_id}')` and inspect `fileShares[0].nfsExportOptions` and `networks[0].network`.\n*   **Native REST API (`call_gcp_api`)**: Invoke `service=\"file\"`, `version=\"v1\"`, `resource_path=\"projects\u002F{project_id}\u002Flocations\u002F{location}\u002Finstances\u002F{instance_id}\"`.\n*   **Standard `gcloud`**:\n    ```bash\n    gcloud filestore instances describe {instance_id} --location={location} --project={project_id} --format=json\n    ```\n\n--------------------------------------------------------------------------------\n\n## Core Operational Workflow\n\n### Step 1: Parameter Extraction & GKE Node Architecture\n*   Extract `instance`, `location` (region\u002Fzone), `project`, and `client_ip` \u002F `client_subnet`. If target parameters are missing, list instances or ask the user to confirm.\n*   **GKE Architecture Rule**: PersistentVolumes are mounted by the Linux kernel on the **GKE Worker Node**, not inside the Pod network namespace. Even if Pod IPs (`10.4.0.0\u002F14`) are allowlisted, the NFS server sees traffic originating from the **GKE Node Internal IP**. Always evaluate and allowlist the **GKE Node Subnet CIDR** in `nfsExportOptions` and VPC firewall rules.\n\n### Step 2: Instance Metadata & Shared VPC Resolution\n1.  Verify instance `state` is `READY` (report state blocker if `CREATING`, `DELETING`, or `ERROR`).\n2.  Extract primary Filestore IP (`networks[0].ipAddresses[0]`) and VPC network URI.\n3.  If `networks[0].network` references `projects\u002F{host_project}\u002Fglobal\u002Fnetworks\u002F{network}`, resolve `{host_project}` as the Shared VPC host project for firewall queries.\n\n### Step 3: Export ACL Evaluation (`EACCES` vs `EROFS`)\n1.  Inspect `fileShares[0].nfsExportOptions` (if empty, default `0.0.0.0\u002F0` `READ_WRITE` `NO_ROOT_SQUASH` applies).\n2.  **`EACCES (Permission Denied by Server)`**: Triggered when the client IP or subnet CIDR is not covered by any `ipRanges` entry.\n    *   **Remediation**: Non-destructively append the client IP\u002Fsubnet CIDR to `nfsExportOptions`, preserving all existing export rules to avoid breaking active mounts.\n3.  **`EROFS (Read-only file system)`**: Triggered when `accessMode` is `READ_ONLY` but client writes are attempted.\n\n### Step 4: VPC Ingress Firewall Inspection (`ETIMEDOUT`)\n1.  Query ingress firewall rules in the VPC network (in the host project if Shared VPC).\n2.  **`ETIMEDOUT (Connection Timed Out)`**: Triggered when priority-sorted ingress rules block or fail to allow TCP port `2049` (NFS) and TCP\u002FUDP port `111` (rpcbind) from the client CIDR.\n    *   **Remediation**: Create an ingress firewall rule (`ALLOW` `tcp:2049,udp:2049,tcp:111,udp:111`) from the client subnet CIDR.\n\n### Step 5: Cloud Audit Logs & Configuration Drift Scanning\nQuery Cloud Audit Admin Activity logs (`file.googleapis.com`) over the past 24 hours to check if an `UpdateInstance` operation modified export ACLs or networks:\n\n```bash\ngcloud logging read 'logName=\"projects\u002F{project_id}\u002Flogs\u002Fcloudaudit.googleapis.com%2Factivity\" AND protoPayload.serviceName=\"file.googleapis.com\" AND protoPayload.resourceName=~\".*{instance}.*\"' \\\n    --project=\"{project_id}\" --freshness=\"1d\" --limit=5 --format=\"json\"\n```\n\n*   **Scope to Admin Activity**: Always include `cloudaudit.googleapis.com%2Factivity` in `logName` so read-only `GetInstance`\u002F`ListInstances` calls (`data_access`) are not falsely flagged as administrative drift.\n*   **Drift is Informational**: Recent `UpdateInstance` events explain *when* and *by whom* (`principalEmail`, `timestamp`) configuration changed, but only a failed export ACL or firewall check constitutes a mount blocker.\n*   **Single Bulk Query Rule**: When scanning multiple instances (`--all`), issue a single project-wide audit log query rather than per-instance queries in a loop.\n*   **GKE CSI Driver Logs**: Optionally inspect `resource.labels.container_name=\"gcp-filestore-driver\"` (`severity>=ERROR`) for client-side mount errors.\n\n--------------------------------------------------------------------------------\n\n## Output Format & Mandatory Confirmation Gate\n\nEvery diagnostic report MUST include a structured summary table and root cause analysis:\n\n````markdown\n### Filestore Diagnostic Report: `[instance-name]`\n\n| Parameter | Value |\n| :--- | :--- |\n| **Instance ID** | `[instance-name]` (`[location]`, Tier: `[tier]`, State: `READY`) |\n| **Filestore IP & Network** | `[filestore-ip]` on VPC `[network-name]` (Host Project: `[host-project]`) |\n| **Port 2049 & Export ACL** | Port 2049: `OPEN \u002F BLOCKED` \\| Export ACL: `PASS \u002F REJECTED` |\n| **Diagnostic Verdict** | **HEALTHY** or **BLOCKED: [Root Cause]** |\n\n#### Root Cause Analysis & Recommended Remediation\n- [Explanation of ETIMEDOUT (missing firewall rule on port 2049) vs EACCES (missing export ACL rule) and any recent UpdateInstance audit drift]\n\n```bash\ngcloud compute firewall-rules create ...\n```\n````\n\n### Interactive Remediation Confirmation Gate (MANDATORY)\n*   **NEVER execute write or remediation commands without explicit user confirmation.**\n*   Always conclude your response with an explicit confirmation question:\n    > *\"Would you like me to proceed with executing this remediation command for you? Please confirm to proceed.\"*\n\n## References & Bundled Scripts\n*   [Usage Attribution](references\u002Fattribution.md)\n*   [Error Signatures & Architecture Matrix](references\u002Ferror-signatures.md)\n*   [Cloud Logging & Audit Drift Queries](references\u002Flogging-and-audit-queries.md)\n*   [VPC Network & Firewall Specification](references\u002Fnetwork-firewall-spec.md)\n*   [Mock Fleet Data for Evaluations](references\u002Fmock-fleet-data.md)\n*   `scripts\u002Fquick_diagnose.py` & `scripts\u002Fdiagnose_lib.py`: Zero-dependency CLI runner and pure-Python evaluation engine.\n","\u003C!-- disableFinding(LINE_OVER_80) -->\n\n# Filestore Log-Based Troubleshooting\n\nDiagnoses, troubleshoots, and remediates Filestore client mount failures, permission errors (`EACCES`), and network timeouts (`ETIMEDOUT`) across projects.\n\n## Prerequisites & Quick Start\n\nRequired IAM roles on target project(s) (and Shared VPC host project if applicable):\n*   **Read**: `roles\u002Ffile.viewer` (instance & export ACLs), `roles\u002Fcompute.networkViewer` (VPC firewall rules), `roles\u002Flogging.viewer` (Cloud Audit & GKE CSI logs), `roles\u002Fmcp.toolUser` (if using MCP tools).\n*   **Write (Remediation only)**: `roles\u002Ffile.editor` (export ACL updates), `roles\u002Fcompute.securityAdmin` (firewall rule creation).\n\nAuthenticate, verify billing\u002FAPIs, and configure your environment:\n\n```bash\ngcloud auth login && gcloud auth application-default login\ngcloud billing projects describe {project_id} --format=\"value(billingEnabled)\"\ngcloud services enable file.googleapis.com compute.googleapis.com logging.googleapis.com --quiet\ngcloud config set project {project_id} && gcloud config set compute\u002Fregion {region}\n```\n\n## Usage Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read and follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## Conceptual & Informational Queries (CRITICAL)\n\nFor purely conceptual, architectural, or educational questions (e.g., \"What causes EACCES on Filestore?\", \"Why does GKE Node IP appear instead of Pod IP?\", \"What ports does Filestore require?\", \"Explain root squash\"):\n*   **Rule**: **Answer immediately using pre-trained knowledge and the workflow rules below.** Answering directly minimizes tool latency and token usage when the user only seeks architectural guidance.\n*   **Constraint**: **Do not execute external tool calls or API requests** for basic knowledge questions.\n\n## Handling \"No-Command\" Constraints (CRITICAL)\n\nIf the user prompt contains constraints like \"Do not execute commands\", \"without executing\", or \"read-only\":\n*   **Rule**: **Strictly avoid calling `run_command`** to execute any shell, Python, or `gcloud` commands.\n*   **Discovery**:\n    1.  Always read [Usage Attribution](references\u002Fattribution.md) first so every recommended `gcloud` command includes the required attribution environment variable.\n    2.  Check if Filestore MCP tools (`get_instance`, `list_instances`) are available and use them (API calls, not command executions).\n    3.  If MCP tools are unavailable, read `references\u002Fmock-fleet-data.md` **only if** the requested instance matches one of the evaluation scenarios (`finance-share`, `shared-nfs`, `ml-data`, `data-hub`, `prod-share`). Never report mock data as live production state. If the instance is not listed there, state that live access is required and provide the exact attributed commands for the user to run.\n    4.  **Fast-Path Stop Rule**: Once you have read [Usage Attribution](references\u002Fattribution.md) and located the target instance in `references\u002Fmock-fleet-data.md`, **stop reading additional files immediately** and formulate your response with the attributed `gcloud` remediation command. Do **NOT** read `scripts\u002Fquick_diagnose.py`, `scripts\u002Fdiagnose_lib.py`, `_internal\u002Fquick_diagnose_test.py`, or `EVAL.*` files when command execution is disabled, as inspecting code\u002Ftest files wastes turns and triggers timeouts.\n*   **Mandatory User Confirmation Requirement**: Even when command execution is disabled or the user asks only for recommendations, your response **MUST STILL end with a clear question prompting the user for explicit confirmation** before applying any remediation (e.g., *\"Would you like me to proceed with creating the VPC ingress firewall rule `[rule_name]`? Please confirm to proceed.\"*).\n\n## Multi-Runtime Execution Options\n\n### Option 1: Bundled Python CLI Script (Recommended for CLI \u002F Terminal Agents)\n\n```bash\n# Single instance diagnosis\npython3 scripts\u002Fquick_diagnose.py --instance=\"\u003CINSTANCE_ID>\" --location=\"\u003CLOCATION_OR_ZONE>\" \\\n    [--project=\"\u003CPROJECT_ID>\"] [--client-ip=\"\u003CCLIENT_IP>\"] [--client-subnet=\"\u003CCLIENT_SUBNET_CIDR>\"]\n\n# Bulk project-wide fleet diagnosis\npython3 scripts\u002Fquick_diagnose.py --all --project=\"\u003CPROJECT_ID>\" [--json]\n```\n\n| Flag | Purpose |\n| :--- | :--- |\n| `--instance`, `--location` | Filestore instance ID and region\u002Fzone (`--zone` is a legacy alias). Required unless `--all`. |\n| `--project` | GCP project ID (defaults to active `gcloud` project). |\n| `--client-ip` \u002F `--client-subnet` | Client IP or CIDR to evaluate against export ACLs and ingress firewall rules. |\n| `--json` | Emit machine-readable JSON on stdout (narrative report goes to stderr). |\n| `--apply-fix` | Execute generated remediation commands. **Only pass after explicit user confirmation.** |\n\n### Option 2: Filestore MCP Tools \u002F REST API \u002F `gcloud` CLI\n*   **MCP Tools**: Call `get_instance(name='projects\u002F{project_id}\u002Flocations\u002F{location}\u002Finstances\u002F{instance_id}')` and inspect `fileShares[0].nfsExportOptions` and `networks[0].network`.\n*   **Native REST API (`call_gcp_api`)**: Invoke `service=\"file\"`, `version=\"v1\"`, `resource_path=\"projects\u002F{project_id}\u002Flocations\u002F{location}\u002Finstances\u002F{instance_id}\"`.\n*   **Standard `gcloud`**:\n    ```bash\n    gcloud filestore instances describe {instance_id} --location={location} --project={project_id} --format=json\n    ```\n\n--------------------------------------------------------------------------------\n\n## Core Operational Workflow\n\n### Step 1: Parameter Extraction & GKE Node Architecture\n*   Extract `instance`, `location` (region\u002Fzone), `project`, and `client_ip` \u002F `client_subnet`. If target parameters are missing, list instances or ask the user to confirm.\n*   **GKE Architecture Rule**: PersistentVolumes are mounted by the Linux kernel on the **GKE Worker Node**, not inside the Pod network namespace. Even if Pod IPs (`10.4.0.0\u002F14`) are allowlisted, the NFS server sees traffic originating from the **GKE Node Internal IP**. Always evaluate and allowlist the **GKE Node Subnet CIDR** in `nfsExportOptions` and VPC firewall rules.\n\n### Step 2: Instance Metadata & Shared VPC Resolution\n1.  Verify instance `state` is `READY` (report state blocker if `CREATING`, `DELETING`, or `ERROR`).\n2.  Extract primary Filestore IP (`networks[0].ipAddresses[0]`) and VPC network URI.\n3.  If `networks[0].network` references `projects\u002F{host_project}\u002Fglobal\u002Fnetworks\u002F{network}`, resolve `{host_project}` as the Shared VPC host project for firewall queries.\n\n### Step 3: Export ACL Evaluation (`EACCES` vs `EROFS`)\n1.  Inspect `fileShares[0].nfsExportOptions` (if empty, default `0.0.0.0\u002F0` `READ_WRITE` `NO_ROOT_SQUASH` applies).\n2.  **`EACCES (Permission Denied by Server)`**: Triggered when the client IP or subnet CIDR is not covered by any `ipRanges` entry.\n    *   **Remediation**: Non-destructively append the client IP\u002Fsubnet CIDR to `nfsExportOptions`, preserving all existing export rules to avoid breaking active mounts.\n3.  **`EROFS (Read-only file system)`**: Triggered when `accessMode` is `READ_ONLY` but client writes are attempted.\n\n### Step 4: VPC Ingress Firewall Inspection (`ETIMEDOUT`)\n1.  Query ingress firewall rules in the VPC network (in the host project if Shared VPC).\n2.  **`ETIMEDOUT (Connection Timed Out)`**: Triggered when priority-sorted ingress rules block or fail to allow TCP port `2049` (NFS) and TCP\u002FUDP port `111` (rpcbind) from the client CIDR.\n    *   **Remediation**: Create an ingress firewall rule (`ALLOW` `tcp:2049,udp:2049,tcp:111,udp:111`) from the client subnet CIDR.\n\n### Step 5: Cloud Audit Logs & Configuration Drift Scanning\nQuery Cloud Audit Admin Activity logs (`file.googleapis.com`) over the past 24 hours to check if an `UpdateInstance` operation modified export ACLs or networks:\n\n```bash\ngcloud logging read 'logName=\"projects\u002F{project_id}\u002Flogs\u002Fcloudaudit.googleapis.com%2Factivity\" AND protoPayload.serviceName=\"file.googleapis.com\" AND protoPayload.resourceName=~\".*{instance}.*\"' \\\n    --project=\"{project_id}\" --freshness=\"1d\" --limit=5 --format=\"json\"\n```\n\n*   **Scope to Admin Activity**: Always include `cloudaudit.googleapis.com%2Factivity` in `logName` so read-only `GetInstance`\u002F`ListInstances` calls (`data_access`) are not falsely flagged as administrative drift.\n*   **Drift is Informational**: Recent `UpdateInstance` events explain *when* and *by whom* (`principalEmail`, `timestamp`) configuration changed, but only a failed export ACL or firewall check constitutes a mount blocker.\n*   **Single Bulk Query Rule**: When scanning multiple instances (`--all`), issue a single project-wide audit log query rather than per-instance queries in a loop.\n*   **GKE CSI Driver Logs**: Optionally inspect `resource.labels.container_name=\"gcp-filestore-driver\"` (`severity>=ERROR`) for client-side mount errors.\n\n--------------------------------------------------------------------------------\n\n## Output Format & Mandatory Confirmation Gate\n\nEvery diagnostic report MUST include a structured summary table and root cause analysis:\n\n````markdown\n### Filestore Diagnostic Report: `[instance-name]`\n\n| Parameter | Value |\n| :--- | :--- |\n| **Instance ID** | `[instance-name]` (`[location]`, Tier: `[tier]`, State: `READY`) |\n| **Filestore IP & Network** | `[filestore-ip]` on VPC `[network-name]` (Host Project: `[host-project]`) |\n| **Port 2049 & Export ACL** | Port 2049: `OPEN \u002F BLOCKED` \\| Export ACL: `PASS \u002F REJECTED` |\n| **Diagnostic Verdict** | **HEALTHY** or **BLOCKED: [Root Cause]** |\n\n#### Root Cause Analysis & Recommended Remediation\n- [Explanation of ETIMEDOUT (missing firewall rule on port 2049) vs EACCES (missing export ACL rule) and any recent UpdateInstance audit drift]\n\n```bash\ngcloud compute firewall-rules create ...\n```\n````\n\n### Interactive Remediation Confirmation Gate (MANDATORY)\n*   **NEVER execute write or remediation commands without explicit user confirmation.**\n*   Always conclude your response with an explicit confirmation question:\n    > *\"Would you like me to proceed with executing this remediation command for you? Please confirm to proceed.\"*\n\n## References & Bundled Scripts\n*   [Usage Attribution](references\u002Fattribution.md)\n*   [Error Signatures & Architecture Matrix](references\u002Ferror-signatures.md)\n*   [Cloud Logging & Audit Drift Queries](references\u002Flogging-and-audit-queries.md)\n*   [VPC Network & Firewall Specification](references\u002Fnetwork-firewall-spec.md)\n*   [Mock Fleet Data for Evaluations](references\u002Fmock-fleet-data.md)\n*   `scripts\u002Fquick_diagnose.py` & `scripts\u002Fdiagnose_lib.py`: Zero-dependency CLI runner and pure-Python evaluation engine.\n",{"name":5,"metadata":49,"description":7},{"version":50,"category":51},"1.0.2","Storage","main","4c6800d20130b5a3233e414609f1241013cec8cc","skills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting",2005,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 01:51:35",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add google\u002Fskills --skill google-cloud-filestore-log-troubleshooting",{"tool":67,"command":68},"bunx","bunx skills add google\u002Fskills --skill google-cloud-filestore-log-troubleshooting",{"tool":70,"command":71},"pnpm","pnpm dlx skills add google\u002Fskills --skill google-cloud-filestore-log-troubleshooting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002FSKILL.md",true,[75,81,85,89,93,97,103],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fattribution.md","REFERENCE","参考文档",1978,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002Freferences\u002Fattribution.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Ferror-signatures.md",9673,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002Freferences\u002Ferror-signatures.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Flogging-and-audit-queries.md",5222,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002Freferences\u002Flogging-and-audit-queries.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fmock-fleet-data.md",7000,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002Freferences\u002Fmock-fleet-data.md",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fnetwork-firewall-spec.md",8189,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002Freferences\u002Fnetwork-firewall-spec.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fdiagnose_lib.py","SCRIPT","脚本",15185,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002Fscripts\u002Fdiagnose_lib.py",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fquick_diagnose.py",13705,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-filestore-log-troubleshooting\u002Fscripts\u002Fquick_diagnose.py",[108,142,172,201,228,252],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":120,"publishedAt":44},"01M6998S2EZKD3GEJ7F943RZTE","sign-in-with-google-web","Implement, configure, and secure Sign In With Google (SiwG) using Google Identity Services (GIS \u002F `https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fclient`) across web architectures. Use when creating Google sign-in buttons, implementing Google One Tap with FedCM, integrating GIS in React\u002FNext.js\u002FAngular\u002FHTML, verifying ID tokens on backend runtimes (Python\u002FNode.js\u002FGo\u002FJava), enforcing Google Workspace domain restrictions (`hd`), securing client-side ID tokens via WebCrypto nonces or encrypted IndexedDB, embedding in cross-origin iframes via the Intermediate Iframe API (`https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fintermediate`), configuring Content Security Policy (CSP), COOP, and Permissions Policy (`identity-credentials-get`) headers, or handling sign-out and revocation. Don't use for legacy Google Sign-In (`gapi.auth2`), Google Cloud IAM service accounts, or Android\u002FiOS native Credential Manager.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fsign-in-with-google-web\u002FSKILL.md",[114,117],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[9,121,122,123,124,125,126,127,128,25,129,42,130,131,132,133,134,135,136,137,138,139,140,141],"sign in with google web","sign","with","web","android","go","security","google workspace","implement","python","implementing","react","iam","permissions","buttons","secure","manager","identity","architectures","domain","runtimes",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":155,"publishedAt":44},"01M6998PHPDCAD684VW5WRG83D","dpop-adoption","Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com\u002Ftoken. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM \u002F service account authentication.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fdpop-adoption\u002FSKILL.md",[148,149,150],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[156,157,9,25,158,159,160,161,162,163,133,164,165,166,167,168,169,138,141,170,171],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform","when",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":184,"publishedAt":44},"01M6998M72TC73EEAQH4XC7EXW","retrieving-developer-knowledge","Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI\u002FGemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fretrieving-developer-knowledge\u002FSKILL.md",[178,179,182,183],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},[185,186,187,188,25,189,190,191,192,193,194,195,196,171,197,198,199,133,200,134],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":44},"01M6998J2CZEXS9BES9S3WWFKC","migrate-to-rust","Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure\u002Ffix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fmigrate-to-rust\u002FSKILL.md",[],[208,209,210,211,212,213,214,215,130,216,217,218,219,220,221,194,222,223,224,171,225,226,199,227],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":237,"publishedAt":44},"01M6998GCC3K29WZ82KXMB9E02","finding-google-skills","Google platform decision and setup guidance, loaded on demand from Google's skill catalog. Use when a developer is choosing or setting up part of their stack, such as where to run a service, a database, storage, messaging, authentication, analytics, ads, or AI model serving, and a Google product is a reasonable candidate - whether or not a vendor is named - or when a request names a Google product or API. Brings in the matching Google skill so the answer can weigh Google options, their trade-offs, and when they are not the right fit. Skip when the stack is already settled on another provider and no Google product is named, or the task involves no platform choice.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Ffinding-google-skills\u002FSKILL.md",[234,235,236],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},[9,238,239,240,241,170,242,243,244,245,246,160,247,248,249,195,30,250,171,251,198],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","up","decision","database","candidate",{"skillNo":253,"name":254,"nameZh":6,"description":255,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":256,"categories":257,"keywords":260,"publishedAt":44},"01M6998DWNHTH0BS6W1CY8ZXMP","workload-manager-basics","Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fworkload-manager-basics\u002FSKILL.md",[258,259],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[261,262,137,263,9,188,264,25,189,265,40,266,267,171,268,198,133,269,270,37,34],"workload manager basics","workload","basics","cli","review","resources","inspect","you","create","libraries"]