# Troubleshooting systemd with SystemTap

DevFeed: [Troubleshooting systemd with SystemTap](<https://devfeed.tech/articles/troubleshooting-systemd-with-systemtap-20218.md>)

Original publisher: [Read original article](<https://blog.janestreet.com/troubleshooting-systemd-with-systemtap/>)

Author: Mark R Bannister

Published: 2020-02-03T00:00:00Z

Content type: tutorial

Language: en

Sources: [Jane Street](<https://devfeed.tech/sources/jane-street.md>)

Topics: [systemd](<https://devfeed.tech/topics/systemd.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [mount](<https://devfeed.tech/topics/mount.md>), [Processes](<https://devfeed.tech/topics/processes.md>)

Tags: [commands](<https://devfeed.tech/tags/commands.md>), [linux](<https://devfeed.tech/tags/linux.md>), [logs](<https://devfeed.tech/tags/logs.md>), [mount](<https://devfeed.tech/tags/mount.md>), [processes](<https://devfeed.tech/tags/processes.md>), [systemd](<https://devfeed.tech/tags/systemd.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

## AI overview

This article investigates Linux login and cron failures associated with systemd. It traces the issue to systemd choking during rapid successive automounts, known as a mount storm, and describes using SystemTap to inspect kernel and process behavior.

## Source excerpt

When we set up a schedule on a computer, such as a list of commands to run every day at particular times via Linux cron jobs, we expect that schedule to execute reliably. Of course we'll check the logs to see whether the job has failed, but we never question whether the cron daemon itself will function. We always assume that it will, as it always has done; we are not expecting mutiny in the ranks of the operating system.