[gelöst] Probleme mit Ansible und ausrollen eines Gateways


#1

Hallo zusammen.
Ich wollte gerade unser eines Gateway einmal neu installieren, da dort einige Dinge nicht mehr so richtig funktioniert haben.
Leider lässt mich Ansible den Tunneldigger nicht mehr ausrollen.
Folgende Meldungen erscheinen:

TASK [gateways_l2tp : git für tunneldigger] ************************************
changed: [gw03]

TASK [gateways_l2tp : patch für l2tp_broker.py] ********************************
changed: [gw03]

TASK [gateways_l2tp : Python-Abhängigkeiten installieren] **********************
fatal: [gw03]: FAILED! => {"changed": false, "cmd": "/srv/tunneldigger/bin/pip2 install -r /srv/tunneldigger/broker/requirements.txt", "failed": true, "msg": "stdout: Requirement already satisfied (use --upgrade to upgrade): construct==2.5.2 in /srv/tunneldigger/lib/python2.7/site-packages (from -r /srv/tunneldigger/broker/requirements.txt (line 1))
Downloading/unpacking gevent==1.0.2 (from -r /srv/tunneldigger/broker/requirements.txt (line 2))
 Running setup.py (path:/tmp/pip-build-nPUi8n/gevent/setup.py) egg_info for package gevent
 
Downloading/unpacking greenlet==0.4.9 (from -r /srv/tunneldigger/broker/requirements.txt (line 3))
 Running setup.py (path:/tmp/pip-build-nPUi8n/greenlet/setup.py) egg_info for package greenlet
 
Downloading/unpacking netfilter==0.6.2 (from -r /srv/tunneldigger/broker/requirements.txt (line 4))
 Downloading netfilter-0.6.2.tar.gz
 Running setup.py (path:/tmp/pip-build-nPUi8n/netfilter/setup.py) egg_info for package netfilter
 
Downloading/unpacking repoze.lru==0.6 (from -r /srv/tunneldigger/broker/requirements.txt (line 5))
 Downloading repoze.lru-0.6.tar.gz
 Running setup.py (path:/tmp/pip-build-nPUi8n/repoze.lru/setup.py) egg_info for package repoze.lru
 
Downloading/unpacking six==1.9.0 (from -r /srv/tunneldigger/broker/requirements.txt (line 6))
 Downloading six-1.9.0-py2.py3-none-any.whl
Installing collected packages: gevent, greenlet, netfilter, repoze.lru, six
 Running setup.py install for gevent
 configure: error: in /tmp/pip-build-nPUi8n/gevent/build/temp.linux-x86_64-2.7/libev':
 configure: error: no acceptable C compiler found in $PATH
 Seeconfig.log' for more details
 Running '/bin/sh /tmp/pip-build-nPUi8n/gevent/libev/configure > configure-output.txt' in /tmp/pip-build-nPUi8n/gevent/build/temp.linux-x86_64-2.7/libev
 building 'gevent.core' extension
 x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -DLIBEV_EMBED=1 -DEV_COMMON= -DEV_CLEANUP_ENABLE=0 -DEV_EMBED_ENABLE=0 -DEV_PERIODIC_ENABLE=0 -Ibuild/temp.linux-x86_64-2.7/libev -Ilibev -I/usr/include/python2.7 -c gevent/gevent.core.c -o build/temp.linux-x86_64-2.7/gevent/gevent.core.o
 unable to execute 'x86_64-linux-gnu-gcc': No such file or directory
 error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
 Complete output from command /srv/tunneldigger/bin/python2 -c \"import setuptools, tokenize;file='/tmp/pip-build-nPUi8n/gevent/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r
', '
'), file, 'exec'))\" install --record /tmp/pip-a4LHJE-record/install-record.txt --single-version-externally-managed --compile --install-headers /srv/tunneldigger/include/site/python2.7:
 running install

running build

running build_py

creating build

creating build/lib.linux-x86_64-2.7

creating build/lib.linux-x86_64-2.7/gevent

copying gevent/coros.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/lock.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/server.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/greenlet.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/timeout.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/select.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/win32util.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/resolver_ares.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/queue.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/resolver_thread.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/local.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/threadpool.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/threading.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/_threading.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/wsgi.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/baseserver.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/util.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/pywsgi.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/socket.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/_sslgte279.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/__init__.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/pool.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/os.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/subprocess.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/ssl.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/thread.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/hub.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/monkey.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/event.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/_ssl2.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/backdoor.py -> build/lib.linux-x86_64-2.7/gevent

copying gevent/fileobject.py -> build/lib.linux-x86_64-2.7/gevent

running build_ext

configure: error: in /tmp/pip-build-nPUi8n/gevent/build/temp.linux-x86_64-2.7/libev':

configure: error: no acceptable C compiler found in $PATH

Seeconfig.log' for more details

Running '/bin/sh /tmp/pip-build-nPUi8n/gevent/libev/configure > configure-output.txt' in /tmp/pip-build-nPUi8n/gevent/build/temp.linux-x86_64-2.7/libev

building 'gevent.core' extension

creating build/temp.linux-x86_64-2.7/gevent

x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -DLIBEV_EMBED=1 -DEV_COMMON= -DEV_CLEANUP_ENABLE=0 -DEV_EMBED_ENABLE=0 -DEV_PERIODIC_ENABLE=0 -Ibuild/temp.linux-x86_64-2.7/libev -Ilibev -I/usr/include/python2.7 -c gevent/gevent.core.c -o build/temp.linux-x86_64-2.7/gevent/gevent.core.o

unable to execute 'x86_64-linux-gnu-gcc': No such file or directory

error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

----------------------------------------
Cleaning up...
Command /srv/tunneldigger/bin/python2 -c \"import setuptools, tokenize;file='/tmp/pip-build-nPUi8n/gevent/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r
', '
'), file, 'exec'))\" install --record /tmp/pip-a4LHJE-record/install-record.txt --single-version-externally-managed --compile --install-headers /srv/tunneldigger/include/site/python2.7 failed with error code 1 in /tmp/pip-build-nPUi8n/gevent
Storing debug log for failure in /root/.pip/pip.log
"}
to retry, use: --limit @/opt/ansible-ffhp/gateways.retry

PLAY RECAP *********************************************************************
gw03 : ok=53 changed=3 unreachable=0 failed=1

Hat hier jemand einen Plan von euch oder mache ich da irgend etwas verkehrt?
Vg
Christoph
PS: Ich hoffe, mein Logfile kann man einigermaßen lesen.


#2

Ich bin gerade verwirrt. Was kompilieren wir denn da in der L2TP-Rolle?


#3

Der Tunneldigger installiert seine Abhängigkeiten mittels pip. Dabei werden manche Pakete lokal auf dem Rechner gebaut.


@Einsteiger007 Magst du mal das Paket build-essential installieren und es dann erneut probieren? Welche Distribution, Version und Umfang der Installation verwendet ihr?


#4

Hi @descilla
Danke für die schnelle Hilfe, das wars.
Diese Rolle Läuft jetzt ordentlich durch.
Thema kann geschlossen werden g
Danke nochmal.
Grüße


#5

Das sollten wir als Abhängigkeit mit reinnehmen. @descilla, meinst du in diese Rolle? Oder in die common?


#6

Klingt als ob du common meinst, ich mach das mal eben.

Ist jetzt durch Commit #9d296b0 drin.