Dsapce 7 error on yarn start

[Mariyapillai Jayakananthan]

Dear All,

I am struggling while I am install Dspace 7. When I tried to install front-end faced following error.

yarn run v1.22.5
$ yarn run build:prod && yarn run serve:ssr
$ yarn run config:prod
$ ts-node --project ./tsconfig.ts-node.json scripts/set-env.ts --prod
Building production environment
No specific environment file found for --prod
Angular environment.ts file generated correctly at ./src/environments/environment.ts
$ yarn run build:ssr
$ yarn run build:client-and-server-bundles && yarn run compile:server
$ ng build --prod && ng run dspace-angular:server:production --bundleDependencies true
69% building 650/655 modules 5 active ...?ref--7-0!/opt/dspace-7/dspace-7-angular/node_modules/@ng-dynamic-forms/core/fesm2015/core.jsKilled
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 137.

Please guide to resolve..

Many thanks in advance.

Regards

Jaya

[euler]

Hi Jaya,

Did you create a file named environment.prod.ts in your [dspace-angular]/src/environments/ directory?

Please see step number 4 in the Frontend installation portion.

Create a Production Configuration file at [dspace-angular]/src/environments/environment.prod.ts. You may wish to use the environment.template.ts as a starting point. This environment.prod.ts file can be used to override any of the default configurations specified in the environment.common.ts (in that same directory).  At a minimum this file MUST include the "ui" and "rest" sections similar to the following (keep in mind, you only need to include settings that you need to modify)

Regards,

euler

[Mariyapillai Jayakananthan]

Dear Euler,

I have done the setting and run again the YARN START.

Still the following error occurred.

root@debian:/opt/dspace-7-angular# yarn start
yarn run v1.22.5
$ yarn run start:prod

$ yarn run build:prod && yarn run serve:ssr
$ yarn run config:prod
$ ts-node --project ./tsconfig.ts-node.json scripts/set-env.ts --prod
Building production environment

Angular environment.ts file generated correctly at ./src/environments/environment.ts

$ yarn run build:ssr
$ yarn run build:client-and-server-bundles && yarn run compile:server
$ ng build --prod && ng run dspace-angular:server:production --bundleDependencies true

69% building 658/660 modules 2 active ...der.js??ref--7-0!/opt/dspace-7-angular/node_modules/rxjs/_esm2015/internal/symbol/iterator.jsKilled

error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Please help me sort out the errors.

Thanks

Jaya

M. Jayakananthan (BSc, MSc) 
Systems Analyst cum Programmer
Eastern University, Sri Lanka
E-mail: jeyakan...@esn.ac.lk , mje...@gmail.com

Tel:  +94 65 2240213 
Mob: +94 773457556

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/62837030-7d6d-4211-86dd-945ed3c08e11n%40googlegroups.com.

[Tim Donohue]

Hi Jaya,

I googled that error, and it seems that a "exit code 137" from yarn means that you ran out of memory (and/or swap space).  See for example: https://jcutrer.com/javascript/yarn-build-exit-code-137

I think​ you are going to need at least 2GB of memory to build the app.  If somehow that doesn't work, you could try 3 or 4, but I think 2GB should be enough.

You should also verify you are running Node v12 or v14 (which is what we recommend for the UI). Older versions of Node (like v10 or below) might work, but they don't do a good job of managing memory...so you are much more likely to hit memory issues.

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Mariyapillai Jayakananthan <mje...@gmail.com>
Sent: Thursday, August 12, 2021 11:56 AM
To: euler <esn...@seafdec.org.ph>
Cc: DSpace Technical Support <dspac...@googlegroups.com>
Subject: Re: [dspace-tech] Re: Dsapce 7 error on yarn start

 

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAL7_yd6CTG6WvBZX8Tzg9%2BQ2nG3-CeY2_LJM%3DOQX16AC98WzBw%40mail.gmail.com.

[Mariyapillai Jayakananthan]

Dear Euler and Tim,

Thanks for your quick response.

I have installed Dspace 7 Now. But unfortunately when try to upload PDF or any files into the page that indicated "upload error".

Please guide me if I missed anything during the installation.

Thanks in advance

jaya

[euler]

Hi Jaya,

If your installation of frontend and backend is successful and up and running, then congratulations! I think there's a bug in DSpace 7.0. If you try at the demo frontend: https://demo7.dspace.org/home, you cannot upload a bitstream in an item. You can however upload during the submission but not when the item was already archived. I hope this will get fixed soon. My workaround for this is by importing via the command line and using the -r flag and make sure you have your intended bitstream included not only in the directory but also listed in the contents file. But this method is really for batch importing and would be cumbersome and inconvenient if you only want to upload a single file.

euler

[Nicolas Battaglia]

I have the same error running dspace on debian, and in the browser console get additional information: permission error. I cant fix that error, even change / folder permission to 777. 

I change the os 

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/e24d9d1f-9d7c-4d2b-9986-9c388b8f219dn%40googlegroups.com.

[Tim Donohue]

Hi Jaya,

We'd need you to look for a more specific error message. There's a large number of reasons why an upload may fail, and likely there was a different error that caused the failure, either in the UI or on the backend.

Here's a guide for locating errors in DSpace 7: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Mariyapillai Jayakananthan <mje...@gmail.com>

Sent: Saturday, August 14, 2021 3:12 AM
To: DSpace Technical Support <dspac...@googlegroups.com>

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/79456523-3ba1-4d79-9e3f-e8ba6111fcddn%40googlegroups.com.

[Mariyapillai Jayakananthan]

Dear Tim,

I have reinstalled Dspace 7 with Debian 11 and tried to upload an item to the interface, but the same error occurred.

Attached herewith screenshots for your reference.

Thanks

Jaya

M. Jayakananthan (BSc, MSc) 
Systems Analyst cum Programmer
Eastern University, Sri Lanka
E-mail: jeyakan...@esn.ac.lk , mje...@gmail.com

Tel:  +94 65 2240213 
Mob: +94 773457556

[Nicolas Battaglia]

I've the SAME error with Debian!! but i can't fix it. I change to Wind..

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAL7_yd7PH1gHZmJUMMkKBqMJFUardTrM%3DgKiS6QfdtyR74SqTg%40mail.gmail.com.

[Tim Donohue]

Hi Jaya,

Is there a more specific error in the backend's logs??  Check the dspace.log on the backend as well as the logs for your Tomcat and/or Apache.  That "java.io.IOException" you are seeing is saying that something has gone wrong on the backend.  It might be a permissions error, or maybe a directory didn't get auto-created as it should have.  But, we'd be able to more easily debug it if you can find the more specific error message in the log files on the backend.

If you don't know where to look for those logs, see again this troubleshooting guide...look at the section called "Finding errors messages in the REST API logs": https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

---

From: Mariyapillai Jayakananthan <mje...@gmail.com>
Sent: Thursday, August 19, 2021 10:32 AM
To: Tim Donohue <tim.d...@lyrasis.org>