Error Exit Status 126
Contents |
>ExampleComments1Catchall for general errorslet "var1 = 1/0"Miscellaneous errors, such as "divide by zero" and other impermissible operations2Misuse of shell builtins (according to Bash documentation)empty_function() {}Missing bash exit code check keyword or command, or permission problem (and diff return code on a failed binary file comparison).126Command invoked cannot execute/dev/nullPermission problem or command is not an executable127"command not found"illegal_commandPossible problem with $PATH or
Exit Code 137
a typo128Invalid argument to exitexit 3.14159exit takes only integer args in the range 0 - 255 (see first footnote)128+nFatal error signal "n"kill -9 $PPID of script$? returns 137 (128 + 9)130Script terminated by Control-CCtl-CControl-C autosys exit codes is fatal error signal 2, (130 = 128 + 2, see above)255*Exit status out of rangeexit -1exit takes only integer args in the range 0 - 255
and 255, though, as explained below, the shell may use values windows exit code above 125 specially. Exit statuses from shell builtins and
Exit Code 255 Windows
compound commands are also limited to this range. Under certain circumstances, the shell will
Exit Code Python
use special values to indicate specific failure modes. For the shell’s purposes, a command which exits with a zero exit status has succeeded. http://tldp.org/LDP/abs/html/exitcodes.html A non-zero exit status indicates failure. This seemingly counter-intuitive scheme is used so there is one well-defined way to indicate success and a variety of ways to indicate various failure modes. When a command terminates on a fatal signal whose number is N, Bash uses the https://www.gnu.org/s/bash/manual/html_node/Exit-Status.html value 128+N as the exit status. If a command is not found, the child process created to execute it returns a status of 127. If a command is found but is not executable, the return status is 126. If a command fails because of an error during expansion or redirection, the exit status is greater than zero. The exit status is used by the Bash conditional commands (see Conditional Constructs) and some of the list constructs (see Lists). All of the Bash builtins return an exit status of zero if they succeed and a non-zero status on failure, so they may be used by the conditional and list constructs. All builtins return an exit status of 2 to indicate incorrect usage, generally invalid options or missing arguments. Next: Signals, Previous: Environment, Up: Executing Commands [Contents][Index]
Sign in Pricing Blog Support Search GitHub This repository Watch 81 Star 1,628 Fork 157 kubernetes/minikube Code Issues 73 https://github.com/kubernetes/minikube/issues/519 Pull requests 8 Projects 0 Pulse Graphs New issue Error getting state for host: exit status 126 #519 Closed waprin opened this Issue Aug 24, 2016 · 16 https://forums.docker.com/t/docker-for-mac-is-unable-start-the-default-vm/8375 comments Projects None yet Labels kind/bug Milestone No milestone Assignees r2d4 4 participants waprin commented Aug 24, 2016 Minikube version (use minikube version): minikube exit code version: v0.8.0 Environment: OS (e.g. from /etc/os-release): OS X El Capitan 10.11.6 VM Driver (e.g. cat ~/.minikube/machines/minikubeVM/config.json | grep DriverName): "DriverName": "virtualbox", Docker version (e.g. docker -v): Docker version 1.12.0, build 8eab29e (Docker for Mac) Install tools: OS X binary package What happened: (docsamples10) waprin-macbookpro:django_postgres_redis waprin$ minikube start --vm-driver=xhyve E0824 15:32:51.389622 30129 start.go:89] Error starting linux exit code host: Error getting state for host: exit status 126 Error getting state for host: exit status 126 (docsamples10) waprin-macbookpro:django_postgres_redis waprin$ minikube docker-env E0824 15:23:04.955046 29839 env.go:247] Error setting machine env variable(s): exit status 126 What you expected to happen: Don't get errors or get errors that make it clear how to fix. Make it clearer how to blow away any config that might be breaking things How to reproduce it (as minimally and precisely as possible): OS X, Docker for Mac, download minikube OS X binary and do minikube start Anything else do we need to know: I think minikube start might have succeeded the first time and then all the commands started giving the 126, but I'm having problems digging up the bash history. Either way now start fails right away. waprin commented Aug 24, 2016 I do see that my minikube config file has the VirtualBox driver, which isn't good because I deleted VirtualBox to get Docker for Mac to install corr
ran for an hour and started returning error when we try to run any containers. $ docker-machine ipError getting IP address: exit status 126 Information $ docker versionClient: Version: 1.10.3 API version: 1.22 Go version: go1.5.3 Git commit: 20f81dd Built: Thu Mar 10 21:49:11 2016 OS/Arch: darwin/amd64 Server: Version: 1.10.3 API version: 1.22 Go version: go1.5.3 Git commit: 20f81dd Built: Thu Mar 10 21:49:11 2016 OS/Arch: linux/amd64 Steps to reproduce the behavior Installed Docker for Mac, native app Try to run a container and list docker-machin ip, it returns the following error. Error getting IP address: exit status 126 jaiboom (Jaiboom) 2016-04-05 05:48:34 UTC #2 This error persisted till I rebooted my mac and tried to start the containers using kitematic dashboad, not sure what is co-relation here. It looks like though the containers were running the "docker.local" was not getting resolved or was not pingable. justincormack (Justin Cormack) 2016-04-05 13:14:22 UTC #3 docker-machine ip will not work with docker for mac, as it is not configured as a docker machine. You can use docker.local as the address, or docker port will show you where to connect. Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled SuccessCenter KnowledgeBase Documentation CommunityForums TechnicalSupport Status Docs Events Community Support Training Partners Blog What is Docker? Enterprise Get Docker Pricing Open Source Company