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

oh no! Jeeze, something went wrong #5928

Open
franjea opened this issue Jan 17, 2022 · 3 comments
Open

oh no! Jeeze, something went wrong #5928

franjea opened this issue Jan 17, 2022 · 3 comments
Labels
bug stale

Comments

@franjea
Copy link

franjea commented Jan 17, 2022 •
edited
Loading

Describe the bug

Trying to install nix on macOS Monterey version 12.1 on my iMacPro (2017) Processor 3,2 GHz 8 Core Intel Xeon W.

Steps To Reproduce

  1. Open new terminal session
  2. Type at prompt % sh <(curl -L https://nixos.org/nix/install) --daemon
  3. See complete output with error message

Expected behavior

installation successfull

nix-env --version output

Add any other context about the problem here.

output :
jean-mariefranziskus@192 ~ % sh % Total % Received % Xferd
<(curl -L https://nixos.org/nix/install) --daemon Average Speed Time Time Time Current Dload Upload Total Spent Left Speed
000000 0 0 --:--:-- --:--:-- --:--:-- 0
100 4046 100 4046 0 0
downloading Nix 2.5.1 binary tarball for x86_64-darwin from 'https://releases.nixos.org/nix/nix-2.5.1/nix-2.5.1- x86_64-darwin.tar.xz' to '/var/folders/57/5h37l1x11zd2j34h322dqb7c0000gp/T/nix-binary-tarball- unpack.XXXXXXXXXX.VWyCzqTR'...
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed
100 33.5M 100 33.5M 0 0 41.5M 0 --:--:-- --:--:-- --:--:-- 41.8M
Switching to the Multi-user Installer
Welcome to the Multi-User Nix Installation
This installation tool will set up your computer with the Nix package manager. This will happen in a few stages:

  1. Make sure your computer doesn't already have Nix. If it does, I will show you instructions on how to clean up your old install.
  2. Show you what I am going to install and where. Then I will ask if you are ready to continue.
  3. Create the system users and groups that the Nix daemon uses to run builds.
  4. Perform the basic installation of the Nix files daemon.
  5. Configure your shell to import special Nix Profile files, so you can use Nix.
  6. Start the Nix daemon.
    Would you like to see a more detailed list of what I will do?
    [y/n] y
    I will:
  • make sure your computer doesn't already have Nix files (if it does, I will tell you how to clean them up.)
  • create local users (see the list above for the users I'll make)
  • create a local group (nixbld)
  • install Nix in to /nix
  • create a configuration file in /etc/nix
  • set up the "default profile" by creating some Nix-related files in /var/root
  • back up /etc/bashrc to /etc/bashrc.backup-before-nix
  • update /etc/bashrc to include some Nix configuration
  • back up /etc/zshrc to /etc/zshrc.backup-before-nix
  • update /etc/zshrc to include some Nix configuration
  • create a Nix volume and a LaunchDaemon to mount it
  • create a LaunchDaemon (at /Library/LaunchDaemons/org.nixos.nix-daemon.plist) for nix-daemon
    Ready to continue?
    [y/n] y
    ---- let's talk about sudo -----------------------------------------------------
    This script is going to call sudo a lot. Every time I do, it'll output exactly what it'll do, and why.
    Just like this:
    ---- sudo execution ------------------------------------------------------------
    I am executing: $ sudo echo
    to demonstrate how our sudo prompts look
    This might look scary, but everything can be undone by running just a few commands. I used to ask you to confirm each time sudo ran, but it was too many times. Instead, I'll just ask you this one time:
    Can I use sudo?
    [y/n] y
    Yay! Thanks! Let's get going!
    ~~> Fixing any leftover Nix volume state
    Before I try to install, I'll check for any existing Nix volume config and ask for your permission to remove it (so that the installer can start fresh). I'll also ask for permission to fix any issues I spot.
    ~~> Checking for artifacts of previous installs
    Before I try to install, I'll check for signs Nix already is or has been installed on this system.
    6323 0 --:--:-- --:--:-- --:--:-- 6323
    ---- Nix config report ---------------------------------------------------------
    Temp Dir:
    Nix Root: Build Users: Build Group ID: Build Group Name:
    build users:
    Username: UID _nixbld1: 301 _nixbld2: 302 _nixbld3: 303 _nixbld4: 304 _nixbld5: 305 _nixbld6: 306 _nixbld7: 307 _nixbld8: 308 _nixbld9: 309 _nixbld10: 310 _nixbld11: 311 _nixbld12: 312 _nixbld13: 313 _nixbld14: 314 _nixbld15: 315 _nixbld16: 316 _nixbld17: 317 _nixbld18: 318 _nixbld19: 319 _nixbld20: 320 _nixbld21: 321 _nixbld22: 322 _nixbld23: 323 _nixbld24: 324 _nixbld25: 325 _nixbld26: 326 _nixbld27: 327 _nixbld28: 328 _nixbld29: 329 _nixbld30: 330 _nixbld31: 331 _nixbld32: 332
    Ready to continue?
    [y/n] y
    /var/folders/57/5h37l1x11zd2j34h322dqb7c0000gp/T/tmp.6b0Fy7KsrX /nix
    32
    30000
    nixbld
    ---- Preparing a Nix volume ----------------------------------------------------
    Nix traditionally stores its data in the root directory /nix, but macOS now (starting in 10.15 Catalina) has a read-only root directory. To support Nix, I will create a volume and configure macOS to mount it at /nix.
    ~~> Configuring /etc/synthetic.conf to make a mount-point at /nix
    ---- sudo execution ------------------------------------------------------------
    I am executing:
    $ sudo /usr/bin/ex --noplugin /etc/synthetic.conf
    to add Nix to /etc/synthetic.conf
    Password:
    ~~> Creating a Nix volume
    ---- sudo execution ------------------------------------------------------------
    I am executing:
    $ sudo /usr/sbin/diskutil apfs addVolume disk1 APFS Nix Store -nomount
    to create a new APFS volume 'Nix Store' on disk1
    ---- sudo execution ------------------------------------------------------------
    I am executing:
    $ sudo /usr/sbin/diskutil unmount force disk1s7
    to ensure the Nix volume is not mounted
    disk1s7 was already unmounted
    ~~> Configuring /etc/fstab to specify volume mount options
    ---- sudo execution ------------------------------------------------------------
    I am executing:
    $ sudo /usr/sbin/vifs
    to add nix to fstab

~~> Configuring LaunchDaemon to mount 'Nix Store'
---- sudo execution ------------------------------------------------------------
I am executing:
$ sudo /usr/bin/ex --noplugin /Library/LaunchDaemons/org.nixos.darwin-store.plist
to install the Nix volume mounter
---- sudo execution ------------------------------------------------------------
I am executing:
$ sudo launchctl bootstrap system /Library/LaunchDaemons/org.nixos.darwin-store.plist
to launch the Nix volume mounter
---- sudo execution ------------------------------------------------------------
I am executing:
$ sudo launchctl kickstart -k system/org.nixos.darwin-store
to launch the Nix volume mounter
~~> Setting up the build group nixbld
---- sudo execution ------------------------------------------------------------
I am executing:
$ sudo /usr/sbin/dseditgroup -o create -r Nix build group for nix-daemon -i 30000 nixbld
Create the Nix build group, nixbld Created: Yes
~~> Setting up the build user _nixbld1
---- sudo execution ------------------------------------------------------------
I am executing:
$ sudo /usr/bin/dscl . create /Users/_nixbld1 UniqueID 301
Creating the Nix build user (#1), _nixbld1

attribute status: eDSRecordAlreadyExists DS Error: -14135 (eDSRecordAlreadyExists) ---- oh no! -------------------------------------------------------------------- Jeeze, something went wrong. If you can take all the output and open an issue, we'd love to fix the problem so nobody else has this issue. :( We'd love to help if you need it. You can open an issue at https://github.com/nixos/nix/issues Or feel free to contact the team: - Matrix: #nix:nixos.org - IRC: in #nixos on irc.libera.chat - twitter: @nixos_org - forum: https://discourse.nixos.org jean-mariefranziskus@192 ~ %
@franjea franjea added the bug label Jan 17, 2022
@abathur
Copy link
Member

abathur commented Jan 17, 2022

Going forward, please try to either copy the output into the post, or attach an actual plain-text log file. Since PDFs are capable of containing exploits (and the fact that your comment says you attached an rtf, but the actual attachment claims to be a pdf), I had to go find a converter to ensure this was clean before I could take a look.

For reference, the error happens here:

~~> Setting up the build group nixbld
---- sudo execution -----------------------------------------------------------
I am executing:
$ sudo /usr/sbin/dseditgroup -o create -r Nix build group for nix-daemon -i 30000 nixbld
Create the Nix build group, nixbld
Created: Yes
~~> Setting up the build user _nixbld1
---- sudo execution -----------------------------------------------------------
I am executing:
$ sudo /usr/bin/dscl . create /Users/_nixbld1 UniqueID 301
Creating the Nix build user (#1), _nixbld1
<main> attribute status: eDSRecordAlreadyExists
<dscl_cmd> DS Error: -14135 (eDSRecordAlreadyExists)

I imagine you already have a user with the UID the installer is trying to use. There may be a better way to do this (I'm not terribly familiar with the macOS user-management commands), but I think you can run /usr/bin/dscl . search /Users UniqueID 301 to directly check.

Let me know what you find, but I imagine the most-likely cases and next steps are:

  1. If you have already had Nix on the system before and the command matches a user that is named _nixbld1, we'll need to do a little more digging. (AFAIK the installer should handle existing nixbld users just fine, so we'll need to figure out why it isn't.)
  2. If it is some other user, I think you'll have to find an open ID range. You can run something like /usr/bin/dscl . list /Users UniqueID | sort -n -k 2 and check it to see if you can find a sequence of available UIDs in the 200-400 range.
    • To actually use a different starting ID you'll need to either download+modify the install scripts to use it (I can outline the basics if you are you comfortable doing this?), or pre-create _nixbld* users (which the installer should hopefully pick up).

@franjea
Copy link
Author

franjea commented Jan 18, 2022 via email

@abathur
Copy link
Member

abathur commented Jan 18, 2022 •
edited
Loading

Thanks. I think there are 2 main ways to proceed. I would pick whichever you feel most confident about...

  1. I'm not sure what your SonosDMS user is for, but if you think you can change its UID without much hassle, I would try relocating it (perhaps to UID 300?). If you think this will be okay, I think it is fairly simple, something like: sudo dscl . change /Users/SonosDMSUniqueID 301 300
  2. Download the installer script bundle, edit the script to change the minimum UID set in NIX_FIRST_BUILD_UID, and then run the installer locally. This will be a little do-it-yourself, but I do have a rough outline of the steps in install-multi-user.sh asks user to "edit this script" when it's invoked by the curl | sh script #4915 (comment)

You could also technically pre-create the build users if you aren't comfortable with the options above, but it will probably take more work all around.

@abathur abathur mentioned this issue Mar 15, 2022
Open
@stale stale bot added the stale label Aug 12, 2022
@Asqiir Asqiir mentioned this issue Oct 2, 2023
Open
@geffgh geffgh mentioned this issue Jan 4, 2024
Open
@abhillman abhillman mentioned this issue Jul 14, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@abathur @franjea