Shell init ошибка получения текущей директории getcwd

I have a simple script:

#!/bin/bash
for server in $(~/.ansible/ansible_hosts)
do
    ssh $server "hostname; readlink /opt/mydir/mylink;"
done

It works fine — the program returns the correct hostname and link — except that I get the following error on some but not all of the servers:

shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

All the directories exist. One of the most common suggestions has been to add a cd, a cd -, or a cd /. All that happens when that step is added is an additional:

chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

I tried kickstarting the nfs daemon on the off chance that there was some confusion about my homedir and substituted /etc/init.d in case the problem was with /opt. No difference

This would simply be an annoyance except that when I try to use an ansible playbook instead of a simple ssh command it fails for that server.

Any insights would appreciated.

Describe the bug

When direnv is loading a .envrc file, it prints these messages and does not load the .envrc file

shell-init: error retrieving current directory: getcwd: cannot access parent directories: Bad file descriptor
pushd: error retrieving current directory: getcwd: cannot access parent directories: Undefined error: 0
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: Undefined error: 0

To Reproduce
Steps to reproduce the behavior:

I’ve simplified my zsh configs down to the following:

.zshrc

eval "$(direnv hook zsh)"

.zshenv

path=("/usr/local/bin" $path)  # this is where homebrew installs direnv
export -U PATH

~/workspace/.envrc

export AWS_PROFILE=development

Install direnv

Then start a new shell and cd into ~/workspace and permit the envrc file to be loaded

$ cd ~/workspace
$ direnv allow

Expected behavior

I expect direnv to set AWS_PROFILE with the value development, but I see AWS_PROFILE is still unset and there are errors printed to the console, described above.

Environment

• OS: macOS Big Sur, and also macOS 10.15.7
• Shell: zsh 5.8 (x86_64-apple-darwin20.1.0) from homebrew, and also zsh 5.8 (x86_64-apple-darwin20.0) stock with macOS
• Direnv version: 2.24.0 from homebrew, and also 2.23.1 (built from source) and 2.23.0 (built from source) and 2.22.0 (built from source)

Additional context

I have been using direnv on this same machine for some time, I’m not sure exactly what broke it. I thought at first it was one of my configs but after stripping away all my configs, removing and re-installing direnv, and still running into this issue I fear I’m in above my head.

I have isolated the messages to be coming from the shell hook, which on my machine is defined as

$ direnv hook zsh
_direnv_hook() {
  trap -- '' SIGINT;
  eval "$("/usr/local/bin/direnv" export zsh)";
  trap - SIGINT;
}
typeset -ag precmd_functions;
if [[ -z ${precmd_functions[(r)_direnv_hook]} ]]; then
  precmd_functions=( _direnv_hook ${precmd_functions[@]} )
fi
typeset -ag chpwd_functions;
if [[ -z ${chpwd_functions[(r)_direnv_hook]} ]]; then
  chpwd_functions=( _direnv_hook ${chpwd_functions[@]} )
fi

I’m not familiar enough with zsh to know what the hooks are doing, however when I run direnv export zsh manually I get no output 🤔 seems like nothing would be evald then

Here’s an error reported by one of our regular reader Anu. She says, cluster-fork  w command ends up with an error “shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory“.

Here’s the complete snapshot of the error:

$cluster-fork w
compute-0-0: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
down
compute-0-1: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

Solution:

This error mostly occurs when the directory in which this command was executed does not exist anymore. For example, assume that you had changed directory to 'test' and issued cluster-fork command. During the execution of cluster-fork, if the directory test was removed (may be a program that regularly cleans disk space or mistakenly deleted from a different terminal), then 'getcwd' will not be able to return the current working directory. Hence, cluster-fork will return an error “getcwd: cannot access parent directories: No such file or directory”.

To fix this error, one has to just get out of that non-existent directory. Usually by issuing 'cd' command to get to the home directory and execute cluster-fork command.