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.

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

go build signal: killed #32

Open
ghost opened this issue Jul 30, 2014 · 14 comments
Open

go build signal: killed #32

ghost opened this issue Jul 30, 2014 · 14 comments

Comments

@ghost
Copy link

ghost commented Jul 30, 2014

When I run : go get -u github.com/astaxie/beego
It will prompt : go build github.com/astaxie/beego: signal: killed

What should I do ?

@astaxie
Copy link
Member

astaxie commented Jul 30, 2014

can you post all the error infomation

@ghost
Copy link
Author

ghost commented Jul 30, 2014

Only one msg output to the terminal
1, go build github.com/astaxie/beego: signal: killed

WHERE can I get more infomation to verify this error?

I was run it on one of my VPS , and other golang applications work normally.

@astaxie
Copy link
Member

astaxie commented Jul 30, 2014

go get -u -x github.com/astaxie/beego

what's your go version & go env

@ghost
Copy link
Author

ghost commented Jul 30, 2014

Still the same msg prompt at last.

@astaxie
Copy link
Member

astaxie commented Jul 30, 2014

what's your go version & go env. maybe your system not support Go.

@ghost
Copy link
Author

ghost commented Jul 30, 2014

centos 6

go version
go version go1.3 linux/amd64

go env
GOARCH="amd64" GOBIN="" GOCHAR="6" GOEXE="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux" GOPATH="/root/go" GORACE="" GOROOT="/usr/local/go" GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64" CC="gcc" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0" CXX="g++" CGO_ENABLED="1"

It is able to run other Go app.

@astaxie
Copy link
Member

astaxie commented Jul 30, 2014

I have no idea on this error. never encounter this error before

@korya
Copy link

korya commented Nov 12, 2014

Just in case, this happened me few times when memory ran out. Usually when running go build/get in a VM with 512MB or less, or in docker container with limited and low RAM.

@alecthomas
Copy link

I had the same error in another project and the issue was RAM, as @korya mentioned. Bumping from 512M to 1G fixed the issue.

@foreversmart
Copy link

yes, It's just the memory problem

@rahulrajaram
Copy link

I can confirm increasing RAM fixed it for me too.

@carlsue
Copy link

carlsue commented Dec 27, 2019

yes ram size too small
dmesg
[ 146.882582] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/[email protected],task=compile,pid=4339,uid=1000
[ 146.882598] Out of memory: Killed process 4339 (compile) total-vm:8936312kB, anon-rss:7221596kB, file-rss:52kB, shmem-rss:0kB
[ 147.291861] oom_reaper: reaped process 4339 (compile), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

@carlsue
Copy link

carlsue commented Dec 27, 2019

image

@cgthayer
Copy link

Thanks, I hit the same issue on a macbook with docker-desktop. Increasing memory from 2GB to 8GB worked

---> Making bundle: binary (in /go/src/github.com/traefik/traefik/script)
go build github.com/traefik/yaegi/stdlib: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed
go build github.com/aliyun/alibaba-cloud-sdk-go/services/alidns: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed
go build github.com/softlayer/softlayer-go/services: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed
go build github.com/aws/aws-sdk-go/service/ec2: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants