Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] timeout reached for PID #523

Open
RiversideKid opened this issue Aug 16, 2024 · 3 comments
Open

[BUG] timeout reached for PID #523

RiversideKid opened this issue Aug 16, 2024 · 3 comments
Assignees
@grahampugh
Labels
bug Something isn't working question Further information is requested

Comments

@RiversideKid
Copy link

RiversideKid commented Aug 16, 2024 •
edited
Loading

Describe the bug
This has only happened when trying to upgrade from Monterey to Sonoma. Ventura to Sonoma works fine.
When running startosinstall the log file indicates that "could not get authorization..." and then indicates that a timeout has been reached. After reaching the same errors on several Monterey computers we pulled the requirement from all Monterey computers.

To Reproduce

  • If applicable, please provide the full command used when running the script.
    • "/Library/Management/erase-install/erase-install.sh --os 14 --update --reinstall --confirm"
  • Please describe how the script was run. [e.g. Standalone via Terminal, in Jamf Policy from the uploaded pkg, in Jamf policy from uploaded script only, via another MDM provider]
  • Erase-Install Version 35.0.pkg installed via Jamf policy and the Execute Command is "/Library/Management/erase-install/erase-install.sh --os 14 --update --reinstall --confirm"

Expected behavior
A clear and concise description of what you expected to happen.
We had expected that the OS would upgrade to Sonoma like the Ventura computers do, but the Monterey computers have all failed with the above error.

Code/log output
Please supply the full command used, and if applicable, add full output from Terminal or from /var/log/erase-install.log. Don't post a partial log - I need the whole thing. Either upload the log as a file, or paste the output in a code block like this:

[STEP 1 of 6]
Executing Policy UPGRADE-TO-SONOMA
[STEP 2 of 6]
Downloading erase-install-v35.0.pkg...
Downloading https://jss***/jcds/downloads/erase-install-v35.0.pkg...
Installing erase-install-v35.0.pkg...
Successfully installed erase-install-v35.0.pkg.
[STEP 3 of 6]
[STEP 4 of 6]
Inventory will be updated when all queued actions in Self Service are complete.
[STEP 5 of 6]
Running command /Library/Management/erase-install/erase-install.sh --os 14 --update --reinstall --confirm...
Result of command:
2024-08-13 10:56:34 | v35.0 | [log_rotate] Finished rotating logs in /Library/Management/erase-install/log

2024-08-13 10:56:34 | v35.0 | [erase-install] v35.0 script execution started: Tue Aug 13 10:56:34 EDT 2024

2024-08-13 10:56:34 | v35.0 | [erase-install] Arguments provided: --os 14 --update --reinstall --confirm
2024-08-13 10:56:34 | v35.0 | [set_localisations] Set language to en-US
2024-08-13 10:56:34 | v35.0 | [erase-install] System version: 12.2.1 (Build: 21D62)
2024-08-13 10:56:35 | v35.0 | [check_for_swiftdialog_app] swiftDialog v2.5.0.4768 is installed (/Library/Application Support/Dialog/Dialog.app)
2024-08-13 10:56:35 | v35.0 | [check_for_swiftdialog_app] Creating dialog log (/var/tmp/dialog.cxv)...
2024-08-13 10:56:35 | v35.0 | [erase-install] Caffeinating this script (pid=60263)
2024-08-13 10:56:35 | v35.0 | [check_free_space] OK - 382 GB free/purgeable disk space detected
2024-08-13 10:56:35 | v35.0 | [erase-install] Looking for existing installer app or pkg
2024-08-13 10:56:35 | v35.0 | [find_existing_installer] Installer found at /Applications/Install macOS Sonoma.app.
2024-08-13 10:56:35 | v35.0 | [check_installer_is_valid] Checking validity of /Applications/Install macOS Sonoma.app.
Volume Shared Support on disk4s2 force-unmounted
2024-08-13 10:56:35 | v35.0 | [check_installer_is_valid] Mounting /Applications/Install macOS Sonoma.app/Contents/SharedSupport/SharedSupport.dmg
2024-08-13 10:56:36 | v35.0 | [check_installer_is_valid] Using Build value from com_apple_MobileAsset_MacSoftwareUpdate.xml
2024-08-13 10:56:36 | v35.0 | [check_installer_is_valid] ERROR: Installer is incompatible with system
Volume Shared Support on disk4s2 force-unmounted
2024-08-13 10:56:38 | v35.0 | [check_installer_is_valid] Installer: 23G93 >= System: 21D62 : valid build.
2024-08-13 10:56:38 | v35.0 | [erase-install] Checking for newer installer
2024-08-13 10:56:38 | v35.0 | [check_for_mist] mist-cli v2.1 is installed (/usr/local/bin/mist)
2024-08-13 10:56:38 | v35.0 | [check_newer_available] Restricting to selected OS '14'
┌──────────────────┐
│ UPDATE AVAILABLE │
└──────────────────┘
  ├─ [0;0mThere is a mist update available (current version: 2.1, latest version: 2.1.1)[0;0m
  ├─ [0;0mVisit https://github.com/ninxsoft/mist-cli to grab the latest release of mist[0;0m
┌──────────────────┐
│ INPUT VALIDATION │
└──────────────────┘
  ├─ List search string will be 'Sonoma'...
  ├─ Search only for latest (first) result will be 'true'...
  ├─ Include betas in search results will be 'false'...
  ├─ Only include compatible installers will be 'true'...
  ├─ Export path will be '/Library/Management/erase-install/mist-list.json'...
  ├─ Export path file extension is valid...
  ├─ Output type will be 'ascii'...
┌────────┐
│ SEARCH │
└────────┘
  ├─ Searching for macOS Installer versions...
  ├─ Exported list as JSON: '/Library/Management/erase-install/mist-list.json'
  └─ Found 1 macOS Installer(s) available for download

[0;0m┌────────────┬──────────────┬─────────┬───────┬──────────┬────────────┬────────────┐
│ IDENTIFIER │ NAME         │ VERSION │ BUILD │ SIZE     │ DATE       │ COMPATIBLE │
├────────────┼──────────────┼─────────┼───────┼──────────┼────────────┼────────────┤
[0;0m[0;0m│ [0;0m062-58676 [0;0m │ [0;0mmacOS Sonoma[0;0m │ [0;0m14.6.1 [0;0m │ [0;0m23G93[0;0m │ [0;0m13.68 GB[0;0m │ [0;0m2024-08-07[0;0m │ [0;0mTrue      [0;0m │
[0;0m[0;0m└────────────┴──────────────┴─────────┴───────┴──────────┴────────────┴────────────┘
[0;0m
Comparing latest build found (23G93) with cached installer build (23G93)
2024-08-13 10:56:39 | v35.0 | [check_newer_available] No newer builds found
2024-08-13 10:56:39 | v35.0 | [erase-install] Running on architecture arm64
2024-08-13 10:56:39 | v35.0 | [get_user_details] ask for user credentials (attempt 1/5)
2024-08-13 10:56:39 | v35.0 | [get_default_dialog_args] Invoking utility dialog
yes **User** is a member of everyone
2024-08-13 10:56:55 | v35.0 | [get_user_details] **User** is a Volume Owner
2024-08-13 10:56:55 | v35.0 | [check_password] Success: the password entered is the correct login password for **User**.
2024-08-13 10:56:55 | v35.0 | [erase-install] Installer is at: /Applications/Install macOS Sonoma.app
2024-08-13 10:56:55 | v35.0 | [check_free_space] OK - 382 GB free/purgeable disk space detected

2024-08-13 10:56:55 | v35.0 | [erase-install] WARNING! Running /Applications/Install macOS Sonoma.app with reinstall option

2024-08-13 10:56:55 | v35.0 | [erase-install] Sending quit message to dialog log (/var/tmp/dialog.cxv)
2024-08-13 10:56:55 | v35.0 | [get_default_dialog_args] Invoking utility dialog
{

}
2024-08-13 10:56:57 | v35.0 | [erase-install] User CONFIRMED erase-install or reinstall
PNG image data, 512 x 512, 8-bit/color RGBA, non-interlaced
2024-08-13 10:56:57 | v35.0 | [get_default_dialog_args] Invoking fullscreen dialog
2024-08-13 10:56:58 | v35.0 | [launch_startosinstall] This is the startosinstall command that will be used:
2024-08-13 10:56:58 | v35.0 | [launch_startosinstall] /Applications/Install\ macOS\ Sonoma.app/Contents/Resources/startosinstall --pidtosignal 60263 --agreetolicense --nointeraction --allowremoval --forcequitapps --stdinpass --user **User** 
2024-08-13 10:56:58 | v35.0 | [launch_startosinstall] Launching startosinstall...
File Doesn't Exist, Will Create: /Library/LaunchDaemons/com.github.grahampugh.erase-install.startosinstall.plist
2024-08-13 10:56:58 | v35.0 | [erase-install] Sending password to startosinstall
Error: could not get authorization...
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
2024-08-13 11:56:58 | v35.0 | [erase-install] Timeout reached for PID 60769!
2024-08-13 11:56:58 | v35.0 | [erase-install] Reached end of script unexpectedly. This probably means startosinstall failed to complete within 60 minutes.

2024-08-13 11:56:58 | v35.0 | [erase-install] terminating the process 'caffeinate' process

2024-08-13 11:56:58 | v35.0 | [finish] sending quit message to dialog (/var/tmp/dialog.cxv)
2024-08-13 11:56:58 | v35.0 | [finish] Script exit code: 42
[STEP 6 of 6]

Screenshots
If applicable, add screenshots to help explain your problem.
No screenshot applicable

Environment (please complete the following information):

  • OS version [e.g. 12.0.1]
    • 12.2.1, 12.3.0, 12.6.2
  • erase-install version [e.g. 24.0] - please upgrade to the latest version before submitting a bug report.
    • 35.0 is the latest version

Additional context
Add any other context about the problem here.
We have confirmed that each of the failures have occurred on computers running:

  • macOS 11+ (All failures are on 12.x)
  • Command executed via Jamf as root
  • The file system on each failed macOS computer is verified as APFS
  • Each failed macOS computer has plenty of available space for an upgrade
  • Each user has a token, but is not an administrator on their computer
  • Each hardware computer is listed in the compatible with Sonoma article: https://support.apple.com/en-us/105113.

Could this be a known issue? (I know that I am late to the party, but I expected that this would work on a Monterey computer.)
Thank you in advance for any information
@RiversideKid RiversideKid added the bug Something isn't working label Aug 16, 2024
@grahampugh
Copy link
Owner

Are you running the command from "Run Command" or from a script?

@grahampugh grahampugh added the question Further information is requested label Sep 17, 2024
@RiversideKid
Copy link
Author

Thank you for reaching out. We are using the Installer Package (recommended) method with Jamf Pro. The Execute Command in the Policy is currently (we have tried a few variations to no avail):
"/Library/Management/erase-install/erase-install.sh --os 14 --update --reinstall --current-user --depnotify"

Keep in mind that the Ventura to Sonoma works fine, the issue is only with the Monterey to Sonoma.
Thoughts?

@grahampugh
Copy link
Owner

Please can you try running the execute command from a script rather than from the "Execute Command" field and see if this makes any difference.

You can put the exact same command in a simple script and add it to the policy.

By the way, --depnotify and --current-user flags no longer exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@grahampugh grahampugh

Labels
bug Something isn't working question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grahampugh @RiversideKid