Content
You are here:
openproject configure failing with 13.0.8
Added by Chris Croome 10 months ago
On Debian Bullseye with the latest version of OpenProject:
Package: openproject
Filename: pool/main/openproject_13.0.8-1701787976.eec6c6da.bullseye_amd64.deb
Size: 225061522
MD5sum: a8c9c7cdb7f8b100af23910e32a5d89c
SHA1: 34e7c89961ceaddb659df522bb9fa0d01b5f0f28
SHA256: 4117d52ea49a3a012fa4330288ac5fb16ab9b94613b0d76537612c053da15005
Version: 13.0.8-1701787976.eec6c6da.bullseye
License: GPL
Vendor: Packager.io <https://packager.io>
Architecture: amd64
Maintainer: operations+packaging@openproject.com
Installed-Size: 621620
Depends: libpq5, libsqlite3-0, openssl, libxml2, libxslt1.1, unzip, poppler-utils, unrtf, tesseract-ocr, catdoc, imagemagick, dialog, bash, debianutils
Provides: openproject
Section: default
Priority: optional
Homepage: https://www.openproject.org
Description: OpenProject
Description-md5: 2cf58da8edd6144f86aef832419a5aa0
Running openproject configure
fails with:
Building angular frontend
npm run build
> openproject-frontend@0.1.0 build
> node --max_old_space_size=4096 ./node_modules/@angular/cli/bin/ng build --configuration production --named-chunks --source-map
Option "deployUrl" is deprecated: Use "baseHref" option, "APP_BASE_HREF" DI token or a combination of both instead. For more information, see https://angular.io/guide/deployment#the-deploy-url.
⠋ Generating browser application bundles (phase: setup)... TypeScript compiler options "target" and "useDefineForClassFields" are set to "ES2022" and "false" respectively by the Angular CLI. To control ECMA version and features use the Browerslist configuration. For more information, see https://angular.io/guide/build#configuring-browser-compatibility
NOTE: You can set the "target" to "ES2022" in the project's tsconfig to remove this warning.
⠙ Generating browser application bundles (phase: setup)... Components styles sourcemaps are not generated when styles optimization is enabled.
{
main: [ '/opt/openproject/frontend/src/main.ts' ],
polyfills: [ '/opt/openproject/frontend/src/polyfills.ts' ]
}
⠋ Generating browser application bundles (phase: sealing)...Killed
rake aborted!
Failed to compile angular frontend: 137
/opt/openproject/lib/tasks/assets.rake:75:in `block (4 levels) in <top (required)>'
/opt/openproject/lib/tasks/assets.rake:74:in `block (3 levels) in <top (required)>'
/opt/openproject/lib/tasks/assets.rake:64:in `chdir'
/opt/openproject/lib/tasks/assets.rake:64:in `block (2 levels) in <top (required)>'
/opt/openproject/lib/tasks/packager.rake:52:in `block (2 levels) in <top (required)>'
/opt/openproject/vendor/bundle/ruby/3.2.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/opt/openproject/bin/bundle:110:in `load'
/opt/openproject/bin/bundle:110:in `<main>'
Tasks: TOP => assets:precompile => assets:compile_environment => assets:prepare_op => assets:angular
(See full trace by running task with --trace)
In the past I have had to run openproject configure
several time before it works without an error but this time it seems that however many times it is runs it fails, does anyone have any suggestions regarding how to could debug and fix this?
Replies (2)
I've opened a bug for this issue.
This issue has been solved by increasing the RAM available to the server from 3GB to 4GB.