-
Notifications
You must be signed in to change notification settings - Fork 51
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.
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
"launchctl" "bootout" "system" "/Library/LaunchDaemons/systems.determinate.nix-installer.nix-hook.plist" Boot-out failed: 5: Input/output error #1187
Comments
I'd like to note that I can get the installation to succeed if I allow the script to undo what it tried to do, restart my Mac, and then run the script as one of the first things I do after logging in. |
That's interesting... If you see this again, I'd be interested in the output of (I wish launchctl was more verbose with what actually went wrong) |
Ok. I will post the result here if I have to reinstall again. |
@cole-h this is how it looks for me (with same error happening, albeit still on Sonoma):
|
Thanks! Does the plist path in that output exist as a file...? |
I actually got it fixed by reboot 😅 And now that I tried uninstalling / reinstalling nix a couple of times, I don't seem to get that problem anymore. |
Command and output: $ launchctl print system/systems.determinate.nix-installer.nix-hook
system/systems.determinate.nix-installer.nix-hook = {
active count = 1
path = /Library/LaunchDaemons/systems.determinate.nix-installer.nix-hook.plist
type = LaunchDaemon
state = running
program = /bin/sh
arguments = {
/bin/sh
-c
/bin/wait4path /nix/nix-installer && /nix/nix-installer repair
}
stdout path = /nix/.nix-installer-hook.out.log
stderr path = /nix/.nix-installer-hook.err.log
default environment = {
PATH => /usr/bin:/bin:/usr/sbin:/sbin
}
environment = {
XPC_SERVICE_NAME => systems.determinate.nix-installer.nix-hook
}
domain = system
minimum runtime = 10
exit timeout = 5
runs = 124
pid = 6074
immediate reason = semaphore
forks = 1
execs = 2
initialized = 1
trampolined = 1
started suspended = 0
proxy started suspended = 0
last exit code = 78: EX_CONFIG
semaphores = {
successful exit => 0
}
spawn type = daemon (3)
jetsam priority = 40
jetsam memory limit (active) = (unlimited)
jetsam memory limit (inactive) = (unlimited)
jetsamproperties category = daemon
jetsam thread limit = 32
cpumon = default
probabilistic guard malloc policy = {
activation rate = 1/1000
sample rate = 1/0
}
properties = inferred program | managed LWCR | has LWCR
} Also, not sure how relevant, but I've had to install / uninstall / reboot / install Nix on every reboot so far. It hasn't "stayed" installed for whatever reason. The error that leads to the above reinstall cycle is because the Nix suite of commands aren't found and then the install fails because |
@szicari-streambit Does
That's certainly strange, but probably bears investigation in another ticket. (A few things to try before that: does starting up a new terminal window make the nix commands show up? What if you ssh into the machine, if you're able to set that up? And finally: what if you run |
Thanks for all this. I have my task list for the next time this occurs. |
I had the same issue on macOS 15.0 (24A335). Installing immediately after a reboot fixed the issue for me as well. |
Good morning, @cole-h. After shutting down my computer, I have again found Nix unavailable. The result of your steps above: After the first failed install, neither of the log files were present: The Here is the full output from the failure:
A new terminal did not cause the I'm not sure if this is relevant, but I see the Nix volume was attached as expected when the system booted up. |
@szicari-streambit That is intriguing... Thank for the info! I think we may just need to check if that file exists before trying to do any launchctl funsies on it. Is it possible that trying to install again works for you in the interim? If not, I'll write a patch for you to try ASAP. Additionally, is this an MDM-managed device? I'm having a hard time figuring out why Nix would just disappear on reboot, since we have that hook (when it successfully installs....). Next time that happens, I'd be interested in seeing your |
Error
Metadata
The text was updated successfully, but these errors were encountered: