I am using heroku-cli/5.7.3-35ab144 (linux-arm) go1.7.5 but wheneve I run i run any of heroku's command I get "fork/exec /home/.local/share/heroku/cli/lib/node: no such file or directory"
.
All help invited from community. Thanks
_EDIT BY @jdxcode:
This happens after an upgrade to High Sierra. You must reinstall your CLI. See my comment below for more details._
@BKubi sorry for the late response, but could you try removing the .local/share/heroku/cli directory and running heroku update and see if that fixes your problem? (I am looking at the absolute path you pasted and am guessing you removed your username from the output, if that is not true, please let me know)
I run into the same problem, running Fedora 25. I tried @ransombriggs idea but it did not fix our problem.
Here's how I fixed it.
Hi, i have the same problem with the version heroku-cli/5.10.2-c3f69fb (linux-386) go1.7.5 on ubuntu 16, any way to resolve this problem
The auto updater seemed to break my cli as well.
I attempted to update from homebrew with no luck.
I am trying to run the heroku local command and getting
/Users/craigheneveld/.local/share/heroku/client/bin/heroku: line 21: /Users/craigheneveld/.local/share/heroku/client/bin/node: No such file or directory
I have muddled with nvm recently and perhaps heroku is looking to use a homebrew node version rather than nvm...
I went ahead and uninstalled per https://devcenter.heroku.com/articles/heroku-cli#uninstalling-the-heroku-cli and reinstalling with homebrew and I'm back up
@ransombriggs I figured if out and it follow the same pattern as @JohanCodinha but heroku update is not working
heroku update shows this error message:
%n@%m:%~%# heroku update
â–¸ Get https://cli-assets.heroku.com/branches/stable/manifest.json: dial tcp: lookup cli-assets.heroku.com on [::1]:53: read udp [::1]:43877->[::1]:53: read: connection refused
@dekubi Is this is still an issue for you?
Answer from @cheneveld - is working for me on macOS High Sierra.
I went ahead and uninstalled per https://devcenter.heroku.com/articles/heroku-cli#uninstalling-the-heroku-cli and reinstalling with homebrew and I'm back up
Thanks
I had the same issue when I upgraded to High Sierra and am back online after doing the uninstall and re-install via homebrew! Thanks @cheneveld and @abhijitsinha !
This is an error coming from the v4 and v5 Go codebase which is still installed if you originally used it to install the CLI but later updated. The updated code lives in the home directory and the Go code dispatches the new code. From other reports I'm pretty certain this is an issue with High Sierra and Go but given this is code we don't ship at all anymore, we won't be investigating the full root cause.
Nothing is written in Go anymore so it's impossible for this error to be shown in the new codebase. It's also not possible to be fixed in an autoupdate since it's the non autoupdating part that is failing.
A reinstall of the CLI with any method will fix the issue so long as the old code isn't being called.
Sorry for the trouble! But OS upgrade problems like this is one of the top reasons we stopped writing the CLI in Go.
Had the same issue, seemed to just appear for no good reason.
I'm on MacOS Uninstalled per https://devcenter.heroku.com/articles/heroku-cli#uninstalling-the-heroku-cli and reinstalling with brew install heroku/brew/heroku from
https://devcenter.heroku.com/articles/heroku-cli
All good again now!
Not a directory Error when executing Heroku commands
â–¸ stat /User/xxx/.local/share/heroku/client/bin/heroku: not a directory
â–¸ fork/exec /User/xxx/.local/share/heroku/client/bin/heroku: not a directory
Solution is to remove previous directory
rm -rf ~/.local/share/heroku/client
I had to delete my Github credentials (still unknown??) from my keychain. See https://help.github.com/articles/updating-credentials-from-the-osx-keychain/
I had this issue after updating my Mac to High Sierra
Pebble2016 soultion worked for me.
I had this issue after updating my Mac to High Sierra
Pebble2016 solution worked for me.
Pebble2016 solution also worked for me.
Most helpful comment
I went ahead and uninstalled per https://devcenter.heroku.com/articles/heroku-cli#uninstalling-the-heroku-cli and reinstalling with homebrew and I'm back up