Invoice Ninja: Segmentation fault (CPU too old)

fx919 · October 1, 2024, 2:27pm

Hi,

I’d like to try IN and want to create an API Key. I’m doing this on a virtual machine with the current github version (commit 9941847) at date 2024/10/01.

According to the readme, this is done via:

# docker run --rm -it invoiceninja/invoiceninja php artisan key:generate --show

But this command does not output anything.

When I enter the container manually, I get …

# docker run --rm -it invoiceninja/invoiceninja /bin/sh
$ php artisan key:generate --show

Segmentation fault

$ php artisan

Segmentation fault

On a newer machine (bare metal) it is working.

Are there any hardware requirements?

Regards,
fx

hillel · October 1, 2024, 2:45pm

Hi,

Sorry, I don’t believe the app has official minimum requirements.

github.com/invoiceninja/invoiceninja

System Requirements for Hardware & Software

opened 11:33PM - 12 Feb 21 UTC

closed 06:26AM - 14 Feb 21 UTC

LoVoltage

feature request

**What version of Invoice Ninja are you running? ie v4.5 / v5** Both **What …environment are you running?** Docker Shared Hosting ZIP Other: Self hosted; Debian 10 or Ubuntu 18 LTS to Ubuntu 20 with Apache2 or Nginx 1.18.x MariaDB and PHP 7.x **Have you searched existing issues/requests?** Yes. Not totally clear. **Screenshots** If applicable, add screenshots to help explain your request/question. **Additional context** Add any other context about the request/question here. Self-hosted system and software requirements notes packaged with the source and place on the self hosted install and github pages Are the hardware requirements different between Invoice Ninja major versions? Hardware (Virtual or bare metal) - Minimum and recommended for items below - CPU (core) count and speed - Memory - HDD size Software - PHP version compatibility (7.x to 8.x?) - Preferred PHP version Other - Recommendations for scaling with user loads (1, 5, 10 and more users of a single instance) - Stability and performance tuning\optimizations - Cache tuning and adjusting memory allocation for servers with more available RAM - Make this info available in the README contained in the source zip

fx919 · October 1, 2024, 2:50pm

Hi hillel,

it definitely seems to be a hardware issue. Also the mysql - container breaks when trying to start it via

docker-compose up -d

docker logs ninja_db

Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
...

docker logs ninja_app

2024-10-01T14:40:42Z [INFO] [Entrypoint]: Initialising Invoice Ninja...
Segmentation fault
2024-10-01T14:40:44Z [INFO] [Entrypoint]: Initialising Invoice Ninja...
Segmentation fault
2024-10-01T14:40:45Z [INFO] [Entrypoint]: Initialising Invoice Ninja...
Segmentation fault
...

hillel · October 1, 2024, 2:54pm

Agreed, that seems likely

I haven’t seen this error before, maybe this will help: How To Resolve Fatal glibc error: CPU does not support x86-64-v2 | by Samuel Victor | Medium

fx919 · October 1, 2024, 3:41pm

When configuring the maximum CPU features from the VMHost (Host CPU: Xeon E5-2680 v2 introduced 2013) for the virtual machine, the mysql container comes up, but the ninja application still segfaults.

I set up a new virtual machine on newer VMHost (Host CPU: Xeon E5-2680 v4 introduced 2016). The ninja_app container works out of the box. When I activate the CPU-Feature-Set x86-64-v2 on the newer Host, the ninja_db container comes up successfully.

hillel · October 1, 2024, 4:14pm

Glad to hear it, thanks for the update!