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

consul can't run on Centos 7 #1198

Closed
mushixun opened this issue Aug 26, 2015 · 11 comments
Closed

consul can't run on Centos 7 #1198

mushixun opened this issue Aug 26, 2015 · 11 comments

Comments

@mushixun
Copy link

uname -a

Linux test-srv01 3.10.0-229.11.1.el7.x86_64 #1 SMP Thu Aug 6 01:06:18 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

./consul

Segmentation fault (core dumped)

@slackpad
Copy link
Contributor

Hi @mushixun I can't seem to reproduce this crash. I used Vagrant to spin up the chef/centos-7.0 box and it seems to work fine (from a clean vagrant up):

sudo yum update
wget https://dl.bintray.com/mitchellh/consul/0.5.2_linux_amd64.zip
sudo yum install unzip
unzip 0.5.2_linux_amd64.zip
[vagrant@localhost ~]$ uname -a
Linux localhost.localdomain 3.10.0-229.11.1.el7.x86_64 #1 SMP Thu Aug 6 01:06:18 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[vagrant@localhost ~]$ ./consul
usage: consul [--version] [--help] <command> [<args>]

Available commands are:
    agent          Runs a Consul agent
    configtest     Validate config file
    event          Fire a new event
    exec           Executes a command on Consul nodes
    force-leave    Forces a member of the cluster to enter the "left" state
    info           Provides debugging information for operators
    join           Tell Consul agent to join cluster
    keygen         Generates a new encryption key
    keyring        Manages gossip layer encryption keys
    leave          Gracefully leaves the Consul cluster and shuts down
    lock           Execute a command holding a lock
    maint          Controls node or service maintenance mode
    members        Lists the members of a Consul cluster
    monitor        Stream logs from a Consul agent
    reload         Triggers the agent to reload configuration files
    version        Prints the Consul version
    watch          Watch for changes in Consul

[vagrant@localhost ~]$ sha256sum consul
fc35735a636f0d5c9d62ae1c537c8b2e2ed1960fb34fe810f6b9431f7646e9f1  consul

Can you provide more details and maybe confirm the version you are running (I've got the sha256 of the one I downloaded in the dump above). If that doesn't shed light you might want to fire up gdb and/or strace and see if those yield any clues.

@mushixun
Copy link
Author

Thanks for you reply,you are right,my question has solved,Thank you!!!

@slackpad
Copy link
Contributor

Out of curiosity can you share what it was?

@loslosbaby
Copy link

$ uname -a
Linux zzz 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/*release|grep TTY
PRETTY_NAME="Ubuntu 15.10"
$ bin/consul
Segmentation fault (core dumped)
$

Ideas? Not supported on 15.10?

@slackpad
Copy link
Contributor

slackpad commented Jan 8, 2016

Hi @loslosbaby which version of Consul were you running on there?

@loslosbaby
Copy link

0.6.1 sorry forgot to include that :)

@loslosbaby
Copy link

Weird: I DL'd from releases.hashicorp.com (forever RHC) one one VM, got that working. Spun two more VM's today, used the same URL (from RHC, to get 0.6.1) and I get the SEGV's. Ok, do a sum on the machines:
working$ sum consul
34948 19939
seg1$ sum consul
45513 19882
seg2$ sum consul
45513 19882

I don't have the "working" zip file, I wget'd it into /tmp and its been boot-blasted a day ago+. That's all I know :)

@loslosbaby
Copy link

Short and sweet:

$ strace ./consul
execve("./consul", ["./consul"], [/* 21 vars */]) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
$

@slackpad
Copy link
Contributor

slackpad commented Jan 8, 2016

Hmm - I was able to set up a clean 15.10 box just now and it runs fine - must have gotten a corrupted download somehow. You can use our published shasums to make sure you've got a good binary - https://releases.hashicorp.com/consul/0.6.1/consul_0.6.1_SHA256SUMS.

@stretchkennedy
Copy link

I just spent half an hour scratching my head over this before I thought to try GDB, turns I'd grabbed the download link to the freebsd version by mistake 😟

Hopefully this saves someone some time in the future.

@murphy7801
Copy link

yeah just make sure you grab the right version seems to common fix.

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

5 participants