Server crash when hedgedoc container infrastructure is missing avx cpu flag with "Illegal instruction" #5229
Comments
|
I've tried to get a dump core of the app using the flag : "--abort-on-uncaught-exception", but without success. NODE_DEBUG=cluster,net,http,fs,tls,module,timers nodejs --report-uncaught-exception --report-on-signal --report-on-fatalerror --report-compact --abort-on-uncaught-exception --report-filename="/hedgedoc/public/uploads/report.json" app.js >public/uploads/logs.txt 2>&1Here a tail of the 50 last lines before crashing with the previous flags : |
|
Wasn't that fixed some time back? I remember we had that issue about 2019 or so? I can research deeper if info needed |
|
If you found the old issue maybe it could help, also this post from the forum seems to have similar symptoms : https://community.hedgedoc.org/t/cannot-cut-copy-paste/996/4 |
So, I looked up similar old issues to try to find out the issue you were talking about :
However, they seem to be related to configuration issues with unset CMD_DOMAIN, CMD_PROTOCOL_USESSL, and CMD_URL_ADDPORT. In my case, they are set up, as you can see in the configuration specified above. Only the CMD_URL_ADDPORT hasn't been specified because the default value is already false. If you have any ideas, it would be helpful. On my side, I'll try to obtain more logs or traces from Hedgedoc. |
|
The issue we were observing seems related to hedgedoc container image provided at https://docs.hedgedoc.org/setup/docker/, likely requiring use of AVX extension in the CPU instruction set, see full details into https://github.com/orange-cloudfoundry/paas-templates/issues/2195 The problem does not reproduce after modifying the container infrastructure with a linux kernel properly exposing the CPU avx capabilities. If other hedgedoc users are running old cpus without the avx capability, then it would be helpful to confirm which nodejs library is requiring avx to consider alternatives. For our part, the lack of avx capability is rather an infrastructure-specific issue which can be best addressed at the infrastructure level. |
Guilamb
changed the title
Description
Issue Description
We are currently transitioning from Etherpad to Hedgedoc as our primary note taking tool.
During the migration, we encountered an issue where copying and pasting bullet points from Etherpad into a Hedgedoc note, as well as uploading images, have been consistently resulting in a server crash.
As an example the following text always triggers a server crash :
For the images, they are correctly uploaded on the server before the crash, but not displayed when the server restart.
We have successfully used the migration tool for old notes, and although the final layout requires some adjustments, no crashes occurred during the migration process.
Steps to reproduce
Expected behaviour
Content from Etherpad should be pasted into Hedgedoc notes without causing server crashes, and image uploads should work as expected.
Logs
Config
apiVersion: helm.toolkit.fluxcd.io/v2beta1 kind: HelmRelease metadata: name: hedgedoc spec: interval: 3m chart: spec: chart: charts/hedgedoc version: 0.3.1 sourceRef: kind: GitRepository name: adfinis-helmcharts-git-repo interval: 1m values: image: tag: "1.9.9" postgresql: enabled: false externalDatabase: type: "mysql" username: "XXX" password: ${db_password} host: ${db_host} port: 3306 database: "XXX" hedgedoc: persistentStorage: storageClass: "local-path" env: CMD_DOMAIN: hedgedoc.${cloudfoundry_ops_domain} CMD_PROTOCOL_USESSL: true CMD_DOCUMENT_MAX_LENGTH: 500000 CMD_ALLOW_FREEURL: true CMD_DB_DIALECT: mariadb CMD_DB_HOST: ${db_host} CMD_DB_PORT: 3306 CMD_DB_DATABASE: XXX CMD_DB_USERNAME: XXX CMD_DB_PASSWORD: ${db_password} CMD_LOGLEVEL: debug DEBUG: true ## MariaDB --- +--------------+-----------------------------------------+----------------------------+------------------------+----------+----------------+ | CATALOG_NAME | SCHEMA_NAME | DEFAULT_CHARACTER_SET_NAME | DEFAULT_COLLATION_NAME | SQL_PATH | SCHEMA_COMMENT | +--------------+-----------------------------------------+----------------------------+------------------------+----------+----------------+ | def | information_schema | utf8mb3 | utf8mb3_general_ci | NULL | | | def | cf_b7c7ea3f_bcbe_4c50_a9a6_888427c79d4d | utf8mb4 | utf8mb4_unicode_ci | NULL | | +--------------+-----------------------------------------+----------------------------+------------------------+----------+----------------+Your Setup
hedgedoc-0.3.1@sha1:2a36e588196b6b06e86c318e266dff8d0c96aece
The chart use the official docker image : https://quay.io/repository/hedgedoc/hedgedoc
as we can see here : https://github.com/adfinis/helm-charts/blob/44765d55692c21a7e08b34a88bafde6dfc69e4e2/charts/hedgedoc/values.yaml#L9
Same error encountered using this other chart :
https://artifacthub.io/packages/helm/truecharts/hedgedoc/9.0.9
Additional context
More information about our intended use of hedgedoc : https://github.com/orange-cloudfoundry/paas-templates/issues/1979
The text was updated successfully, but these errors were encountered: