Tee output so we can see it in journald logs#346
Merged
pantherman594 merged 1 commit intomasterfrom Mar 25, 2026
Merged
Conversation
june-hua
approved these changes
Mar 25, 2026
june-hua
added a commit
that referenced
this pull request
Mar 31, 2026
…proc This partially reverts commit 9bd46a1. Root Cause: 1. The exec > >(tee -a "${POST_STARTUP_OUTPUT_FILE}") creates a tee subprocess that remains alive 2. The background process that waits for Jupyter inherits file descriptors from tee 3. When the main startup script exits, tee subprocess stays alive because the background process still has the pipes open 4. google-startup-scripts.service remains stuck in "activating" state indefinitely, waiting for all child processes 5. google-dataproc-agent.service has After=google-startup-scripts.service, so it never starts 6. This creates a race condition where the background Jupyter configuration runs while Dataproc is still writing its config Symptoms: - google-startup-scripts.service stuck in "activating" for hours - google-dataproc-agent.service never starts (ConditionResult=no)
june-hua
added a commit
that referenced
this pull request
Mar 31, 2026
…proc (#354) This partially reverts commit 9bd46a1. Root Cause: 1. The exec > >(tee -a "${POST_STARTUP_OUTPUT_FILE}") creates a tee subprocess that remains alive 2. The background process that waits for Jupyter inherits file descriptors from tee 3. When the main startup script exits, tee subprocess stays alive because the background process still has the pipes open 4. google-startup-scripts.service remains stuck in "activating" state indefinitely, waiting for all child processes 5. google-dataproc-agent.service has After=google-startup-scripts.service, so it never starts 6. This creates a race condition where the background Jupyter configuration runs while Dataproc is still writing its config Symptoms: - google-startup-scripts.service stuck in "activating" for hours - google-dataproc-agent.service never starts (ConditionResult=no)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Output is getting redirected to log files, which means they don’t show up in the app logs. We should send it to both places
PHP-138078