summaryrefslogtreecommitdiffstats
path: root/health/guides/systemdunits/systemd_automount_unit_failed_state.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 02:57:58 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 02:57:58 +0000
commitbe1c7e50e1e8809ea56f2c9d472eccd8ffd73a97 (patch)
tree9754ff1ca740f6346cf8483ec915d4054bc5da2d /health/guides/systemdunits/systemd_automount_unit_failed_state.md
parentInitial commit. (diff)
downloadnetdata-be1c7e50e1e8809ea56f2c9d472eccd8ffd73a97.tar.xz
netdata-be1c7e50e1e8809ea56f2c9d472eccd8ffd73a97.zip
Adding upstream version 1.44.3.upstream/1.44.3upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'health/guides/systemdunits/systemd_automount_unit_failed_state.md')
-rw-r--r--health/guides/systemdunits/systemd_automount_unit_failed_state.md58
1 files changed, 58 insertions, 0 deletions
diff --git a/health/guides/systemdunits/systemd_automount_unit_failed_state.md b/health/guides/systemdunits/systemd_automount_unit_failed_state.md
new file mode 100644
index 00000000..eb3024a9
--- /dev/null
+++ b/health/guides/systemdunits/systemd_automount_unit_failed_state.md
@@ -0,0 +1,58 @@
+### Understand the alert
+
+This alert is triggered when a `systemd` automount unit enters the `failed` state. It means that a mounted filesystem has failed or experienced an error and thus is not available for use.
+
+### What is an automount unit?
+
+An automount unit is a type of `systemd` unit that handles automounting filesystems. It defines when, where, and how a filesystem should be automatically mounted on the system. Automount units use the `.automount` file extension and are typically located in the `/etc/systemd/system` directory.
+
+### Troubleshoot the alert
+
+1. Identify the failed automount unit(s)
+
+To list all `systemd` automount units and their states, run the following command:
+
+```
+systemctl list-units --all --type=automount
+```
+
+Look for the unit(s) with a `failed` state.
+
+2. Check the automount unit file
+
+Examine the failed unit's configuration file in `/etc/systemd/system/` or `/lib/systemd/system/` (depending on your system). If there is an error in the configuration, fix it and reload the `systemd` configuration.
+
+```
+sudo systemctl daemon-reload
+```
+
+3. Check the journal for errors
+
+Use the `journalctl` command to check for any system logs related to the failed automount unit:
+
+```
+sudo journalctl -u [UnitName].automount
+```
+
+Replace `[UnitName]` with the name of the failed automount unit. Analyze the logs to identify the root cause of the failure.
+
+4. Attempt to restart the automount unit
+
+After identifying and addressing the cause of the failure, try to restart the automount unit:
+
+```
+sudo systemctl restart [UnitName].automount
+```
+
+Check the unit's status:
+
+```
+systemctl status [UnitName].automount
+```
+
+If it's in the `active` state, the issue has been resolved.
+
+### Useful resources
+
+1. [Arch Linux Wiki: systemd automount](https://wiki.archlinux.org/title/Fstab#systemd_automount)
+2. [systemd automount unit file example](https://www.freedesktop.org/software/systemd/man/systemd.automount.html#Examples)