Skip to content
This repository has been archived by the owner on Nov 16, 2021. It is now read-only.

Problem running Fabric from within a virtualenv #202

Closed
alexmuller opened this issue Jan 26, 2016 · 4 comments
Closed

Problem running Fabric from within a virtualenv #202

alexmuller opened this issue Jan 26, 2016 · 4 comments

Comments

@alexmuller
Copy link
Contributor

Can anyone let me know if they've seen this before or can reproduce it? I'm banging my head against a wall.

  • OS X 10.10.5
  • Homebrew
brew info python # python: stable 2.7.11, HEAD
pip --version # pip 8.0.2 from /opt/boxen/homebrew/lib/python2.7/site-packages (python 2.7)
virtualenv --version # 14.0.1

Inside a new virtualenv:

which python # /Users/alexmuller/.virtualenvs/fabric-scripts/bin/python
which pip # /Users/alexmuller/.virtualenvs/fabric-scripts/bin/pip
pip install -r requirements_for_tests.txt
which fab # /Users/alexmuller/.virtualenvs/fabric-scripts/bin/fab
fab -l # works fine!
fab integration
# Illegal instruction: 4

Using Fabric without a virtualenv is fine.

@alexmuller
Copy link
Contributor Author

Also reproduced exactly using pip 7.1.2 and virtualenv 13.1.2. It must be something wrong with my setup but I've got no idea what.

@alexmuller
Copy link
Contributor Author

Aha, making progress. I can reproduce with:

$ python
>>> import paramiko
>>> paramiko.common.logging.basicConfig(level=paramiko.common.DEBUG)
>>> h = paramiko.SSHClient()
>>> h.connect('jumpbox.integration.publishing.service.gov.uk', username='alexmuller', key_filename='~/.ssh/id_rsa.pub')
DEBUG:paramiko.transport:starting thread (client mode): 0xf4d4ad0L
INFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.6.1p1)
DEBUG:paramiko.transport:kex algos:['curve25519-sha256@libssh.org', 'ecdh-sha2-nistp256', 'ecdh-sha2-nistp384', 'ecdh-sha2-nistp521', 'diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-gcm@openssh.com', 'aes256-gcm@openssh.com', 'chacha20-poly1305@openssh.com', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-cbc@lysator.liu.se'] server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-gcm@openssh.com', 'aes256-gcm@openssh.com', 'chacha20-poly1305@openssh.com', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-cbc@lysator.liu.se'] client mac:['hmac-md5-etm@openssh.com', 'hmac-sha1-etm@openssh.com', 'umac-64-etm@openssh.com', 'umac-128-etm@openssh.com', 'hmac-sha2-256-etm@openssh.com', 'hmac-sha2-512-etm@openssh.com', 'hmac-ripemd160-etm@openssh.com', 'hmac-sha1-96-etm@openssh.com', 'hmac-md5-96-etm@openssh.com', 'hmac-md5', 'hmac-sha1', 'umac-64@openssh.com', 'umac-128@openssh.com', 'hmac-sha2-256', 'hmac-sha2-512', 'hmac-ripemd160', 'hmac-ripemd160@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hmac-md5-etm@openssh.com', 'hmac-sha1-etm@openssh.com', 'umac-64-etm@openssh.com', 'umac-128-etm@openssh.com', 'hmac-sha2-256-etm@openssh.com', 'hmac-sha2-512-etm@openssh.com', 'hmac-ripemd160-etm@openssh.com', 'hmac-sha1-96-etm@openssh.com', 'hmac-md5-96-etm@openssh.com', 'hmac-md5', 'hmac-sha1', 'umac-64@openssh.com', 'umac-128@openssh.com', 'hmac-sha2-256', 'hmac-sha2-512', 'hmac-ripemd160', 'hmac-ripemd160@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client compress:['none', 'zlib@openssh.com'] server compress:['none', 'zlib@openssh.com'] client lang:[''] server lang:[''] kex follows?False
DEBUG:paramiko.transport:Ciphers agreed: local=aes128-ctr, remote=aes128-ctr
DEBUG:paramiko.transport:using kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local none, remote none
Illegal instruction: 4

@alexmuller
Copy link
Contributor Author

paramiko/paramiko#665

@deanwilson
Copy link
Contributor

Hi @alexmuller, thank you for your interest in this issue and for raising the issue. As it's been a few months without activity I'm going to assume everything is working correctly and invite you to reopen the issue if it's still an issue.

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

No branches or pull requests

2 participants