Google Cloud Filestore Log Troubleshooting
GoogleOfficialPublished by Google
- Skill
- Workflow
- Cloud and DevOps
- Apache-2.0
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured diagnostic workflow for troubleshooting Google Cloud Filestore mount issues. It helps identify the root causes of common NFS errors like EACCES (permission denied) and ETIMEDOUT (network timeouts) occurring on Compute Engine VMs, GKE pods, Cloud Run, or Vertex AI workloads. The workflow includes steps for verifying VPC ingress firewall rules, inspecting nfsExportOptions, and checking Cloud Audit Logs for recent configuration drift, ensuring a systematic approach to restoring connectivity.
What it does
- Identifies root causes for NFS mount failures including EACCES and ETIMEDOUT.
- Evaluates nfsExportOptions to ensure client IP or subnet access is correctly configured.
- Inspects VPC ingress firewall rules for required NFS ports 2049 and 111.
- Scans Cloud Audit Logs to detect recent administrative configuration changes.
- Provides remediation commands for firewall and export ACL updates.
- Supports GKE-specific troubleshooting by accounting for node-level network architecture.
When to use it
- When an NFS mount hangs or fails with 'Connection timed out' or 'access denied by server'.
- After an administrative change causes a previously working Filestore share to stop mounting.
- When verifying if VPC firewall rules or export ACLs allow access from a specific client IP.
- When troubleshooting GKE CSI driver mount errors in the kube-system namespace.
Advantages
- Reduces mean time to resolution for common Filestore connectivity issues.
- Prevents destructive changes by requiring explicit user confirmation for all remediations.
- Provides clear, attributed commands for consistent diagnostic execution.
- Distinguishes between administrative drift and persistent configuration errors.
Usage examples
- “My GKE pod cannot mount the Filestore instance 'finance-share' in 'us-central1-a'. It reports ETIMEDOUT.”
- The agent will extract the instance details, verify the VPC firewall rules for port 2049, and check if the GKE node subnet is correctly allowlisted.
- “Why am I getting EACCES when mounting my Filestore instance from a new VM?”
- The agent will inspect the instance's nfsExportOptions to determine if the client VM's IP or subnet is missing from the allowed ranges.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/google/google-cloud-filestore-log-troubleshooting/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip google-cloud-filestore-log-troubleshooting.zip -d .agents/skills
Documentation by Google
<!-- disableFinding(LINE_OVER_80) -->
Filestore Log-Based Troubleshooting
Diagnoses, troubleshoots, and remediates Filestore client mount failures, permission errors (EACCES), and network timeouts (ETIMEDOUT) across projects.
Prerequisites & Quick Start
Required IAM roles on target project(s) (and Shared VPC host project if applicable):
Read:
roles/file.viewer(instance & export ACLs),roles/compute.networkViewer(VPC firewall rules),roles/logging.viewer(Cloud Audit & GKE CSI logs),roles/mcp.toolUser(if using MCP tools).Write (Remediation only):
roles/file.editor(export ACL updates),roles/compute.securityAdmin(firewall rule creation).
Authenticate, verify billing/APIs, and configure your environment:
gcloud auth login && gcloud auth application-default login
gcloud billing projects describe {project_id} --format="value(billingEnabled)"
gcloud services enable file.googleapis.com compute.googleapis.com logging.googleapis.com --quiet
gcloud config set project {project_id} && gcloud config set compute/region {region}Attribution
Prefix every gcloud command provided or executed with the skill metrics environment:
CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-log-troubleshooting)" \
gcloud filestore instances describe ...On direct REST API calls, append HTTP header: User-Agent: gcs-skills/1.0 (skill:google-cloud-filestore-log-troubleshooting).
Conceptual & Informational Queries (CRITICAL)
For 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"):
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.
Constraint: Do not execute external tool calls or API requests for basic knowledge questions.
Handling "No-Command" Constraints (CRITICAL)
If the user prompt contains constraints like "Do not execute commands", "without executing", or "read-only":
Rule: Strictly avoid calling
run_commandto execute any shell, Python, orgcloudcommands.Discovery:
First, check if Filestore MCP tools (
get_instance,list_instances) are available and use them (API calls, not command executions).If MCP tools are unavailable, read
references/mock-fleet-data.mdonly 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 commands for the user to run.Fast-Path Stop Rule: Once you locate the target instance in
references/mock-fleet-data.md, stop reading additional files immediately and formulate your response. Do NOT readscripts/quick_diagnose.py,scripts/diagnose_lib.py,_internal/quick_diagnose_test.py, orEVAL.*files when command execution is disabled, as inspecting code/test files wastes turns and triggers timeouts.Explain the required diagnostic steps and output the exact attributed commands for manual execution.
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.").
Multi-Runtime Execution Options
Option 1: Bundled Python CLI Script (Recommended for CLI / Terminal Agents)
# Single instance diagnosis
python3 scripts/quick_diagnose.py --instance="<INSTANCE_ID>" --location="<LOCATION_OR_ZONE>" \
[--project="<PROJECT_ID>"] [--client-ip="<CLIENT_IP>"] [--client-subnet="<CLIENT_SUBNET_CIDR>"]
# Bulk project-wide fleet diagnosis
python3 scripts/quick_diagnose.py --all --project="<PROJECT_ID>" [--json]| Flag | Purpose |
|---|---|
--instance, --location | Filestore instance ID and region/zone (--zone is a legacy alias). Required unless --all. |
--project | GCP project ID (defaults to active gcloud project). |
--client-ip / --client-subnet | Client IP or CIDR to evaluate against export ACLs and ingress firewall rules. |
--json | Emit machine-readable JSON on stdout (narrative report goes to stderr). |
--apply-fix | Execute generated remediation commands. Only pass after explicit user confirmation. |
Option 2: Filestore MCP Tools / REST API / gcloud CLI
MCP Tools: Call
get_instance(name='projects/{project_id}/locations/{location}/instances/{instance_id}')and inspectfileShares[0].nfsExportOptionsandnetworks[0].network.Native REST API (
call_gcp_api): Invokeservice="file",version="v1",resource_path="projects/{project_id}/locations/{location}/instances/{instance_id}".Standard
gcloud:CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-log-troubleshooting)" \ gcloud filestore instances describe {instance_id} --location={location} --project={project_id} --format=json
Core Operational Workflow
Step 1: Parameter Extraction & GKE Node Architecture
Extract
instance,location(region/zone),project, andclient_ip/client_subnet. If target parameters are missing, list instances or ask the user to confirm.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/14) are allowlisted, the NFS server sees traffic originating from the GKE Node Internal IP. Always evaluate and allowlist the GKE Node Subnet CIDR innfsExportOptionsand VPC firewall rules.
Step 2: Instance Metadata & Shared VPC Resolution
Verify instance
stateisREADY(report state blocker ifCREATING,DELETING, orERROR).Extract primary Filestore IP (
networks[0].ipAddresses[0]) and VPC network URI.If
networks[0].networkreferencesprojects/{host_project}/global/networks/{network}, resolve{host_project}as the Shared VPC host project for firewall queries.
Step 3: Export ACL Evaluation (EACCES vs EROFS)
Inspect
fileShares[0].nfsExportOptions(if empty, default0.0.0.0/0READ_WRITENO_ROOT_SQUASHapplies).EACCES (Permission Denied by Server): Triggered when the client IP or subnet CIDR is not covered by anyipRangesentry.Remediation: Non-destructively append the client IP/subnet CIDR to
nfsExportOptions, preserving all existing export rules to avoid breaking active mounts.
EROFS (Read-only file system): Triggered whenaccessModeisREAD_ONLYbut client writes are attempted.
Step 4: VPC Ingress Firewall Inspection (ETIMEDOUT)
Query ingress firewall rules in the VPC network (in the host project if Shared VPC).
ETIMEDOUT (Connection Timed Out): Triggered when priority-sorted ingress rules block or fail to allow TCP port2049(NFS) and TCP/UDP port111(rpcbind) from the client CIDR.Remediation: Create an ingress firewall rule (
ALLOWtcp:2049,udp:2049,tcp:111,udp:111) from the client subnet CIDR.
Step 5: Cloud Audit Logs & Configuration Drift Scanning
Query Cloud Audit Admin Activity logs (file.googleapis.com) over the past 24 hours to check if an UpdateInstance operation modified export ACLs or networks:
CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-log-troubleshooting)" \
gcloud logging read 'logName="projects/{project_id}/logs/cloudaudit.googleapis.com%2Factivity" AND protoPayload.serviceName="file.googleapis.com" AND protoPayload.resourceName=~".*{instance}.*"' \
--project="{project_id}" --freshness="1d" --limit=5 --format="json"Scope to Admin Activity: Always include
cloudaudit.googleapis.com%2FactivityinlogNameso read-onlyGetInstance/ListInstancescalls (data_access) are not falsely flagged as administrative drift.Drift is Informational: Recent
UpdateInstanceevents explain when and by whom (principalEmail,timestamp) configuration changed, but only a failed export ACL or firewall check constitutes a mount blocker.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.GKE CSI Driver Logs: Optionally inspect
resource.labels.container_name="gcp-filestore-driver"(severity>=ERROR) for client-side mount errors.
Output Format & Mandatory Confirmation Gate
Every diagnostic report MUST include a structured summary table and root cause analysis:
### Filestore Diagnostic Report: `[instance-name]`
| Parameter | Value |
| :--- | :--- |
| **Instance ID** | `[instance-name]` (`[location]`, Tier: `[tier]`, State: `READY`) |
| **Filestore IP & Network** | `[filestore-ip]` on VPC `[network-name]` (Host Project: `[host-project]`) |
| **Port 2049 & Export ACL** | Port 2049: `OPEN / BLOCKED` \| Export ACL: `PASS / REJECTED` |
| **Diagnostic Verdict** | **HEALTHY** or **BLOCKED: [Root Cause]** |
#### Root Cause Analysis & Recommended Remediation
- [Explanation of ETIMEDOUT (missing firewall rule on port 2049) vs EACCES (missing export ACL rule) and any recent UpdateInstance audit drift]
```bash
CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-log-troubleshooting)" \
gcloud compute firewall-rules create ...
```Interactive Remediation Confirmation Gate (MANDATORY)
NEVER execute write or remediation commands without explicit user confirmation.
Always conclude your response with an explicit confirmation question:
"Would you like me to proceed with executing this remediation command for you? Please confirm to proceed."
References & Bundled Scripts
scripts/quick_diagnose.py&scripts/diagnose_lib.py: Zero-dependency CLI runner and pure-Python evaluation engine.
Files
- ATTRIBUTION.mdAdded by AutoGineer902 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md11.5 KiB
- references/error-signatures.md9.4 KiB
- references/logging-and-audit-queries.md5.4 KiB
- references/mock-fleet-data.md6.9 KiB
- references/network-firewall-spec.md8.1 KiB
- scripts/diagnose_lib.pyScript14.2 KiB
- scripts/quick_diagnose.pyScript13.4 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs a command-line tool, Needs Python
Security
What our scanner noticed· Low risk
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/google-cloud-filestore-log-troubleshooting · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google or Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download google-cloud-filestore-log-troubleshooting.zip