Mirage2 & xmlui "file not found" error

[Sorin Solomon]

Hi, everyone.

I installed DSpace 6 on Ubuntu 18.04, following the instructions in the wiki.

All finished successfully, but when I go to [IP Address]:8080/xmlui I get the error message shown in the attached screenshot.

I searched the Support Forum and I found this issue in the past.

I checked, it's not an issue of permissions. I also tried to change permissions on the /root folder (like in this article), same result. I even tried to run mvn -U clean package -Dmirage2.on=true (like shown here), but the result is the same.

I'm pretty out of ideas here. Help?

Thank you in advance for your assistance.

Sorin Solomon

[Tim Donohue]

Hi Sorin,

To me, this sounds like a possible build issue with the Mirage 2 theme.  You might want to double check some of the warnings/notes here about building Mirage 2. 

https://wiki.duraspace.org/display/DSDOC6x/Mirage+2+Configuration+and+Customization#Mirage2ConfigurationandCustomization-ThebuildprocessandenablingMirage2 

For example, Mirage 2 has its own prerequisites listed there (for example, you need a more recent version of Maven and you must have Git installed)

Additionally, there are some other tips / hints from others who've had build issues with Mirage 2 in the past.  See this "Common build issues" section:
https://wiki.duraspace.org/display/DSDOC6x/Mirage+2+Configuration+and+Customization#Mirage2ConfigurationandCustomization-CommonBuildIssues 

If you are still encountering issues, I'd recommend giving us more information about your build environment (Operating system, version of Java, version of Maven, etc) on this mailing list.  Hopefully others here could help figure out what the issue may be.

Tim

--
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 post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

--

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

[Sorin Solomon]

 Thanks, Tim, for your prompt response.

I checked and I have git installed. Will look later into supported versions and will check that I have what's needed.

I thought that with the command mvn package -Dmirage2.on=true there's no need to install manually the prerequisites. I didn't install any of them.

I will also look into the links you gave me and come back with results. 

Thanks again.

[Sorin Solomon]

The promised update:

I tried to install manually the prerequisites following the Mirage2 instructions. It did not changed the result, I get the same error message.

Will try to look deeper in to the known issues article, but will be more than happy for ideas how to solve it.

TIA,

Sorin

[Eugene Jose Espinoza]

Hi! Has this been resolved? If it isn't, Ican share to you tomorrow morning what I did installing Dpace 6.x with Mirage2 in Ubuntu.

Thanks and cheers!

DISCLAIMER AND CONFIDENTIALITY NOTICE 

The information contained in this e-mail, including those in its attachments, is confidential and intended only for the person(s) or entity(ies) to which it is addressed. If you are not an intended recipient, you must not read, copy, store, disclose, distribute this message, or act in reliance upon the information contained in it. If you received this e-mail in error, please contact the sender and delete the material from any computer or system. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of De La Salle University. 

[Sorin Solomon]

Actually, it didn't.

Nothing worked. None of the things others did in previous posts on the same subject.

At the moment, pretty much lost.

Any help would be greatly appreciated.

Thanks in advance.

[Tim Donohue]

Hello Sorin,

If you need further help, I'd recommend sending along more information to this list about your build environment.  You said you are using Ubuntu 18.04 and DSpace 6.  But, what version of Java are you using (java -version)? What version of Maven (mvn -v)?  What version of Ant (ant -version)? Is this DSpace 6.0, 6.1, 6.2 or 6.3?

Oftentimes, build issues have something to do with invalid/incorrect dependencies.  So, it's possible you are using either an unsupported version of Maven or Java.

Take a close look at the versions of Java, Maven, etc that are listed on the DSpace 6 installation guide: https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace

- Tim

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---

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 post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[Sorin Solomon]

Hi, Tim.

I followed the instructions carefully, hope I installed the right versions.

Here's the full picture:

Ubuntu:

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic

Java:

openjdk version "1.8.0_171"
OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-0ubuntu0.18.04.1-b11)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)

Maven:

Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
Maven home: /usr/lib/apache-maven-3.5.3
Java version: 1.8.0_171, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-30-generic", arch: "amd64", family: "unix"

Ant:

Apache Ant(TM) version 1.10.3 compiled on March 24 2018

Dspace 6.2

Hope this helps. Looking forward to your ideas.

Sorin

[enes...@yahoo.com]

Hi Sorin and Tim,

I have tried to rebuild one of my instances yesterday and I am getting the same error.

mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false

My output where the error occurs looks like this:

[INFO] ------ (Mirage2) org.codehaus.mojo:exec-maven-plugin:1.4.0:exec
npm WARN deprecated bo...@1.7.9: ...psst! Your project can stop working at any moment because its dependencies can change. Prevent this by migrating to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

> Mir...@0.1.2 postinstall /home/dspace/dspace-src-fgu66/dspace/modules/xmlui-mirage2/target/themes/Mirage2
> bower install

bower jquery-ui#1.10.3         EINVRES Request to https://bower.herokuapp.com/packages/jquery-ui failed with 502
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! Mir...@0.1.2 postinstall: `bower install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the Mir...@0.1.2 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/dspace/.npm/_logs/2018-08-07T09_02_12_274Z-debug.log
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] DSpace Parent Project .............................. SUCCESS [  0.987 s]
[INFO] DSpace Services Framework :: API and Implementation  SUCCESS [  5.304 s]
[INFO] DSpace Kernel :: API and Implementation ............ SUCCESS [ 23.414 s]
[INFO] DSpace Addon Modules ............................... SUCCESS [  0.005 s]
[INFO] DSpace Kernel :: Additions and Local Customizations  SUCCESS [  7.259 s]
[INFO] DSpace XML-UI (Manakin) ............................ SUCCESS [ 12.140 s]
[INFO] DSpace XML-UI Mirage2 Theme ........................ SUCCESS [  0.416 s]
[INFO] DSpace XML-UI Mirage2 Theme :: Local Customisations  FAILURE [ 31.754 s]
[INFO] DSpace XML-UI (Manakin) :: Local Customizations .... SKIPPED
[INFO] DSpace JSP-UI ...................................... SKIPPED
[INFO] DSpace JSP-UI :: Local Customizations .............. SKIPPED
[INFO] DSpace RDF ......................................... SKIPPED
[INFO] DSpace RDF :: Local Customizations ................. SKIPPED
[INFO] DSpace REST :: API and Implementation .............. SKIPPED
[INFO] DSpace REST :: Local Customizations ................ SKIPPED
[INFO] DSpace SWORD ....................................... SKIPPED
[INFO] DSpace SWORD :: Local Customizations ............... SKIPPED
[INFO] DSpace SWORD v2 .................................... SKIPPED
[INFO] DSpace SWORD v2 :: Local Customizations ............ SKIPPED
[INFO] Apache Solr Webapp ................................. SKIPPED
[INFO] DSpace SOLR :: Local Customizations ................ SKIPPED
[INFO] DSpace OAI-PMH ..................................... SKIPPED
[INFO] DSpace OAI-PMH :: Local Customizations ............. SKIPPED
[INFO] DSpace Assembly and Configuration .................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:22 min
[INFO] Finished at: 2018-08-07T11:02:12+02:00
[INFO] Final Memory: 77M/523M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.soebes.maven.plugins:iterator-maven-plugin:0.3:iterator (default) on project xmlui-mirage2: Command execution failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1]

My debug log:

6601 silly lifecycle Mir...@0.1.2~postinstall: Args: [ '-c', 'bower install' ]
6602 silly lifecycle Mir...@0.1.2~postinstall: Returned: code: 1  signal: null
6603 info lifecycle Mir...@0.1.2~postinstall: Failed to exec postinstall script
6604 verbose stack Error: Mir...@0.1.2 postinstall: `bower install`
6604 verbose stack Exit status 1
6604 verbose stack     at EventEmitter.<anonymous> (/home/dspace/.nvm/versions/node/v8.7.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
6604 verbose stack     at emitTwo (events.js:125:13)
6604 verbose stack     at EventEmitter.emit (events.js:213:7)
6604 verbose stack     at ChildProcess.<anonymous> (/home/dspace/.nvm/versions/node/v8.7.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
6604 verbose stack     at emitTwo (events.js:125:13)
6604 verbose stack     at ChildProcess.emit (events.js:213:7)
6604 verbose stack     at maybeClose (internal/child_process.js:927:16)
6604 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
6605 verbose pkgid Mir...@0.1.2
6606 verbose cwd /home/dspace/dspace-src-fgu66/dspace/modules/xmlui-mirage2/target/themes/Mirage2
6607 verbose Linux 3.10.0-693.el7.x86_64
6608 verbose argv "/home/dspace/.nvm/versions/node/v8.7.0/bin/node" "/home/dspace/.nvm/versions/node/v8.7.0/bin/npm" "install"
6609 verbose node v8.7.0
6610 verbose npm  v5.4.2
6611 error code ELIFECYCLE
6612 error errno 1
6613 error Mir...@0.1.2 postinstall: `bower install`
6613 error Exit status 1
6614 error Failed at the Mir...@0.1.2 postinstall script.

It looks like that https://bower.herokuapp.com/packages/jquery-ui is depricated.  The new registry address is https://registry.bower.io .

When I go to https://bower.io/, I get the message that the Bower is maintained.

Regards,
Enes

[enes...@yahoo.com]

Hi Sorin,

I was able to resolve this issue:

1. Make sure that you have the latest Bower version 1.8.4 installed on your machine (npm install -g bower).

2. Change Bower version in package.json (dspace-xmlui-mirage2\src\main\webapp).

3. Build again.

mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false

Regards,

Enes

On Thursday, July 12, 2018 at 2:19:39 PM UTC+2, Sorin Solomon wrote:

[Sorin Solomon]

Thanks for the recommendation, Enes.

I will check the issue, tomorrow, I'm already out of the office for today.

Just wanted to remind you that I did manage to compile the DSpace.

It's only the css that is not loading, so the site looks odd and is unusable.

Will update tomorrow.

Sorin

[Sorin Solomon]

Sorry it took me so long. Busy days.

Installed Bower, as you suggested. Then compiled DSpace from scratch.

No luck. Still same error message when trying to access IP:8080/xmlui:

' Syntax error: File to import not found or unreadable: ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap. '

The error I get is on line 16 of styles/main.scss. That line states:

' @import "../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap"; '

I ran ' updatedb ' and then ' locate bootstrap-sass-official ' and there are no results. How come ?

Any ideas?

Sorin

On Tuesday, August 7, 2018 at 4:11:58 PM UTC+3, enes...@yahoo.com wrote:

[enes...@yahoo.com]

Hi Sorin,

Did you change Bower version to 1.8.4 in package.json file (dspace-xmlui-mirage2\src\main\webapp)?

You can also install Mirage 2 components on your server https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2 .

Then, you can run: mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false .

Regards,

Enes

[Sorin Solomon]

Thanks for the prompt response, Enes.

Can you give me the full path to the package.json? Can't find it with locate. I wonder if it's missing or I'm not using locate properly ...

TIA.

Sorin

[enes...@yahoo.com]

It is located in the [dspace-src]\dspace-xmlui-mirage2\src\main\webapp directory.

Enes

[Sorin Solomon]

No such path for me.

I installed following these instructions: https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-WindowsInstallation .

I did not want to deal with Mirage2 prerequisites, so installed it using mvn package -Dmirage2.on=true . Everything completed successfully. But it doesn't work.

Any ideas why I don't have that folders' tree?

Sorin

[enes...@yahoo.com]

Hi Sorin,

There are two options for the installation (dspace-n.x-release. and dspace-n.x-src-release.zzz).  I am using the source zip.  This is the full path to package.json is located at the https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/src/main/webapp/package.json . The other option is to  copy it to your mirage2 customization directory (dspace\modules\xmlui-mirage2\src\main\webapp).

Regards,

Enes

[Sorin Solomon]

I installed from the release, in .gzip format.

I will try to do it again, from ZIP format. Will decompress, download and copy the package.json file to the mirage2 folder and change it for the new version of bower.

Will update afterwards.

Sorin

[Juliana Vasconcelos Braga]

Hello everyone!

I have the same issue! I tried a lot of things but nothing worked....

I'm using Dspace 6.2, instaled and running on a windows 7 system.

Maven returned a error with a message about some Bower packages. Then I tried install the packages manually, but the message error from Bower indicates that the versions of packages are no  longer available (Message: bower ENOTFOUND Package not found), so I've installed the new versions of packages, but Maven continues to return the same errors.

I'm attaching a printscreen from error.

Best regards for you all,

Juliana.

[enes...@yahoo.com]

Hi Juliana,

The installation process is trying to get Bower version that is defined in the package.json (probably 1.7.4).  Try this:

1. Make sure that you have the latest Bower version 1.8.4 installed on your machine (npm install -g bower). Also, install other Mirage 2 components  https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2 .
2. Change Bower version in package.json to 1.8.4 (dspace-xmlui-mirage2\src\main\webapp).
3. Build again.

mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false

Regards,
Enes

[Juliana Vasconcelos Braga]

Hi Enes!

It worked!

The Bower version was 1.7.9.

Thank you so much... :-)

Juliana

Em quinta-feira, 12 de julho de 2018 09:19:39 UTC-3, Sorin Solomon escreveu:

[Sorin Solomon]

OK, update:

I went to install the pre-requisites for Mirage2, as instructed in the documentation. Everything completed without errors.

I created the package.json file in the path you mentioned.

Then I ran the command you gave me: mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false.

It worked for a while, then failed with this:

npm WARN Mir...@0.1.2 No description
npm WARN Mir...@0.1.2 No repository field.
npm WARN Mir...@0.1.2 No license field.
npm ERR! Linux 4.15.0-32-generic
npm ERR! argv "/home/sorin/.nvm/versions/node/v6.5.0/bin/node" "/home/sorin/.nvm/versions/node/v6.5.0/bin/npm" "install"
npm ERR! node v6.5.0
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE

npm ERR! Mir...@0.1.2 postinstall: `bower install`
npm ERR! Exit status 1
npm ERR!

npm ERR! Failed at the Mir...@0.1.2 postinstall script 'bower install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the Mirage2 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     bower install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs Mirage2
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls Mirage2
npm ERR! There is likely additional logging output above.

I ran npm -version and the result was 3.10.3. Then I ran node --version and the result was (as expected) v6.5.0.

So there's a problem with my Mirage2 package? Can it be that the whole tar.gz package I'm using is faulty? Should I go for the .zip package?

TIA.

Sorin