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
SSH substituter with nologin as shell should not result in serialized integer error #37287
Comments
I added some debug echo messages to my profile scripts and I got this error as well (with a different number). To fix it, I had to remove any output from the profiles ... |
Just stumbled into this too. I figured user.users.builder = {
isNormalUser = false;
openssh.authorizedKeys.keys = [ builderSshKey ];
}; should be enough on the server part, but alas. |
Thank you for your contributions.
|
I'm >90% sure this issue is still valid. |
It is. |
1 similar comment
It is. |
I marked this as stale due to inactivity. → More info |
Probably still |
…is "nologin" Instead of error: serialised integer 7161674624452356180 is too large for type 'j' we now get error: 'nix-store --serve' protocol mismatch from 'sshtest@localhost', got 'This account is currently not available.' Fixes NixOS/nixpkgs#37287.
Made NixOS/nix#5290 to show a better error message. But I feel that |
I just run into this error running |
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
Issue description
When the user of the SSH connection used by the SSH substituter does not have a shell configured it defaults to
nologin
, which causes the following error:Which actually is the decimal representation of the first few letters of the following error reported by
nologin
(thanks @cleverca22 for figuring that out).Since with the release of Nix 2.0 it has become easy to setup a SSH substituter, so I expect that more people might run into this problem. I know of at least another that reported it on the IRC.
Instead of the serialized integer error it should just have reported the actual error, or at least it should have given a more specific error about the response being bogus.
Steps to reproduce
Forget to set
users.users.<name>.shell
for the user of the SSH substituter connection.Technical details
"x86_64-linux"
Linux 4.4.116, NixOS, 17.09.git.4daffb9 (Hummingbird)
yes
yes
nix-env (Nix) 2.0
(from nixos-unstable around 5 Mar)""
""
/wheel/fork/nixpkgs
(nixos-17.09 around 22 Feb)The text was updated successfully, but these errors were encountered: