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

Ansible Failing on Rpi4 to install FTS 2.0 #86

Closed
wabash2 opened this issue May 28, 2023 · 6 comments · Fixed by #109
Closed

Ansible Failing on Rpi4 to install FTS 2.0 #86

wabash2 opened this issue May 28, 2023 · 6 comments · Fixed by #109
Assignees
Labels
bug Something isn't working
Milestone

Comments

@wabash2
Copy link

wabash2 commented May 28, 2023

Below is the error that I am getting with trying to run Ansible. I have had previous success running the zero touch install on previous version of FTS. Any help would be greatly appreciated.

fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["/usr/bin/pip3", "install", "FreeTAKServer==2.0.66"], "msg": "stdout: Collecting FreeTAKServer==2.0.66\n Using cached FreeTAKServer-2.0.66-py3-none-any.whl (1.1 MB)\nCollecting python-socketio==4.6.0\n Using cached python_socketio-4.6.0-py2.py3-none-any.whl (51 kB)\nCollecting psutil==5.9.4\n Using cached psutil-5.9.4.tar.gz (485 kB)\n Installing build dependencies: started\n Installing build dependencies: finished with status 'done'\n Getting requirements to build wheel: started\n Getting requirements to build wheel: finished with status 'done'\n Preparing metadata (pyproject.toml): started\n Preparing metadata (pyproject.toml): finished with status 'done'\nCollecting SQLAlchemy==1.3.20\n Downloading SQLAlchemy-1.3.20.tar.gz (6.3 MB)\n ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.3/6.3 MB 9.4 MB/s eta 0:00:00\n Preparing metadata (setup.py): started\n Preparing metadata (setup.py): finished with status 'done'\nCollecting bcrypt==3.1.7\n Using cached bcrypt-3.1.7.tar.gz (42 kB)\n Installing build dependencies: started\n Installing build dependencies: finished with status 'error'\n\n:stderr: error: subprocess-exited-with-error\n \n × pip subprocess to install build dependencies did not run successfully.\n │ exit code: 1\n ╰─> [116 lines of output]\n Collecting setuptools>=40.8.0\n Using cached setuptools-67.8.0-py3-none-any.whl (1.1 MB)\n Collecting wheel\n Using cached wheel-0.40.0-py3-none-any.whl (64 kB)\n Collecting cffi>=1.1\n Using cached cffi-1.15.1.tar.gz (508 kB)\n Preparing metadata (setup.py): started\n Preparing metadata (setup.py): finished with status 'done'\n Collecting pycparser\n Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)\n Building wheels for collected packages: cffi\n Building wheel for cffi (setup.py): started\n Building wheel for cffi (setup.py): finished with status 'error'\n error: subprocess-exited-with-error\n \n × python setup.py bdist_wheel did not run successfully.\n │ exit code: 1\n ╰─> [36 lines of output]\n running bdist_wheel\n running build\n running build_py\n creating build\n creating build/lib.linux-armv7l-3.11\n creating build/lib.linux-armv7l-3.11/cffi\n copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/verifier.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/lock.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/model.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/commontypes.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/recompiler.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/api.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/ffiplatform.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/pkgconfig.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/init.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/cparser.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/vengine_gen.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/error.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/_cffi_include.h -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/parse_c_type.h -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/_embedding.h -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-3.11/cffi\n running build_ext\n building '_cffi_backend' extension\n creating build/temp.linux-armv7l-3.11\n creating build/temp.linux-armv7l-3.11/c\n arm-linux-gnueabihf-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DFFI_BUILDING=1 -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/usr/include/python3.11 -c c/_cffi_backend.c -o build/temp.linux-armv7l-3.11/c/_cffi_backend.o\n c/_cffi_backend.c:2:10: fatal error: Python.h: No such file or directory\n 2 | #include <Python.h>\n | ^~~~~~~~~~\n compilation terminated.\n error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1\n [end of output]\n \n note: This error originates from a subprocess, and is likely not a problem with pip.\n ERROR: Failed building wheel for cffi\n Running setup.py clean for cffi\n Failed to build cffi\n Installing collected packages: wheel, setuptools, pycparser, cffi\n Running setup.py install for cffi: started\n Running setup.py install for cffi: finished with status 'error'\n error: subprocess-exited-with-error\n \n × Running setup.py install for cffi did not run successfully.\n │ exit code: 1\n ╰─> [38 lines of output]\n running install\n /usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.\n warnings.warn(\n running build\n running build_py\n creating build\n creating build/lib.linux-armv7l-3.11\n creating build/lib.linux-armv7l-3.11/cffi\n copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/verifier.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/lock.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/model.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/commontypes.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/recompiler.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/api.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/ffiplatform.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/pkgconfig.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/init.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/cparser.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/vengine_gen.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/error.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/_cffi_include.h -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/parse_c_type.h -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/_embedding.h -> build/lib.linux-armv7l-3.11/cffi\n copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-3.11/cffi\n running build_ext\n building '_cffi_backend' extension\n creating build/temp.linux-armv7l-3.11\n creating build/temp.linux-armv7l-3.11/c\n arm-linux-gnueabihf-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DFFI_BUILDING=1 -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/usr/include/python3.11 -c c/_cffi_backend.c -o build/temp.linux-armv7l-3.11/c/_cffi_backend.o\n c/_cffi_backend.c:2:10: fatal error: Python.h: No such file or directory\n 2 | #include <Python.h>\n | ^~~~~~~~~~\n compilation terminated.\n error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1\n [end of output]\n \n note: This error originates from a subprocess, and is likely not a problem with pip.\n error: legacy-install-failure\n \n × Encountered error while trying to install package.\n ╰─> cffi\n \n note: This is an issue with the package mentioned above, not pip.\n hint: See above for output from the failure.\n [end of output]\n \n note: This error originates from a subprocess, and is likely not a problem with pip.\nerror: subprocess-exited-with-error\n\n× pip subprocess to install build dependencies did not run successfully.\n│ exit code: 1\n╰─> See above for output.\n\nnote: This error originates from a subprocess, and is likely not a problem with pip.\n"}

@brothercorvo brothercorvo transferred this issue from FreeTAKTeam/FreeTakServer May 29, 2023
@brothercorvo
Copy link
Contributor

moved to the proper project

@brothercorvo
Copy link
Contributor

We are aware of this issue that only happens with the Raspberry Pi. We will fix this after release 2.1

@brothercorvo brothercorvo added this to the 2.2 milestone May 29, 2023
@brothercorvo brothercorvo added the bug Something isn't working label May 29, 2023
@brothercorvo
Copy link
Contributor

update: the issue is that in Ubuntu 22.04 python 3.10 is installed with the python dev-tools for that version
using

sudo apt-get install python3.11-dev

you install the correct version and the you can

python3 -m pip install psutil

this will install psutil. after that you can re-run the Zero Touch or use Pip for installation

@phreed
Copy link
Contributor

phreed commented Jan 10, 2024

I am working on correcting this problem in a fork.
The PR will be forthcoming.

@phreed
Copy link
Contributor

phreed commented Jan 10, 2024

Should the change also include logic to not stop when there are failing optional components?

@nicopace
Copy link

Just wanted to let you know, that this bug is still active.
I ran the installer on a barebone ubuntu 22.04 server on a raspberry pi zero 2, and I had this issue.
I dealt with it by running python3 -m pip install psutil.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants