[MGNLDEMO-198] 404 when installing Magnolia Created: 29/Nov/16  Updated: 07/Mar/21

Status: Open
Project: Magnolia Demo Projects
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Low
Reporter: Martin Schmid Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: Not Specified
Original Estimate: 0d
Environment:

OS X 10.11.6


Attachments: PNG File instal.page.png     PNG File screenshot-1.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

I followed the instructions on the “Hello Magnolia” support page. However, when I want to navigate to http://localhost:8080/magnoliaAuthor/.magnolia/admincentral, I get a 404.

Steps to reproduce

  1. Download and extract magnolia-community-demo-bundle.zip
  2. Run magnolia_control.sh start in magnolia-5.5/apache-tomcat-8.5.5/bin/
  3. Navigate to http://localhost:8080
  4. Click on “Run the Web update on the author instance”

Actual result

404 is returned for http://localhost:8080/magnoliaAuthor/.magnolia/admincentral

Expected result

Installation can be started

Additional information

$ ls -a magnolia-5.5/apache-tomcat-8.5.5/webapps/magnoliaAuthor/

lists

.
..
LICENSE.txt
META-INF
NOTICE.txt
README.txt
WEB-INF
docroot
modules

A folder “.magnolia” is missing, indeed.



 Comments   
Comment by Ervin Vystup [ 30/Nov/16 ]

Hello Michael,

During the first installation you should be redirected to the http://localhost:8080/magnoliaAuthor/.magnolia/installer page after clicking on “Run the Web update on the author instance”. Please, could you try to use this URL and tell me what will happen? You should see a page like this one:

But as it is not the typical behavior, please send me the log file (/apache-tomcat-8.5.5/logs/catalina.out) for me to see where a problem can be. An error must have occurred there which created this problem.

Please also ask your contact person from the Magnolia sales team to create a support account for you so that we could move this ticket there.  

Best regards,
Ervin

Comment by Martin Schmid [ 01/Dec/16 ]

Also http://localhost:8080/magnoliaAuthor/.magnolia/installer returns a 404.

In the catalina log file that you pointed out, I found:

Error configuring application listener of class info.magnolia.init.MagnoliaServletContextListener
java.lang.UnsupportedClassVersionError: info/magnolia/init/MagnoliaServletContextListener : Unsupported major.minor version 52.0 (unable to load class info.magnolia.init.MagnoliaServletContextListener)

I found out that tomcat was using /Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/jre as java home. Once I switched to /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home, where Java 8 is installed, it all worked fine.

Thank you for your help.

Please also ask your contact person from the Magnolia sales team to create a support account for you so that we could move this ticket there.  

I am not in contact with the sales team.

Comment by jeffry [ 24/May/17 ]

hi ,
i had the same issue when i tried to access: http://localhost:8080/magnoliaAuthor/.magnolia/installer.
i could run localhost:8080 and see the page where it asks to click the - install the AdminControl or public link.

i have the magnolia CE: magnolia-5.5.4 [latest at this moment]
tomcat : 8
java 1.7

error i saw in the log:
Error configuring application listener of class info.magnolia.init.MagnoliaServletContextListener
java.lang.UnsupportedClassVersionError: info/magnolia/init/MagnoliaServletContextListener : Unsupported major.minor version 52.0 (unable to load class info.magnolia.init.MagnoliaServletContextListener)

Solution:
To solve this issue: *i installed jdk1.8 and changed the Java_home and path to java_home/bin. *
I believe tomcat 8 works with java 8 and perhaps so is the latest magnolia CE version
https://stackoverflow.com/questions/10382929/how-to-fix-java-lang-unsupportedclassversionerror-unsupported-major-minor-versi
from the stackoverflow i found:

Comment by jeffry [ 24/May/17 ]

however, stop the server. exit the cmd promt (I would)
install the jdk 1.8
change the Environment variable :
windows : JAVA_PATH and path
unix: i believe you have to add(if not there)/change the .profile_bash or something
check the new java version and javac -version
run the magnolia provided tomcat's " ./magnolia_cotrol.sh start [unix]
go to http://localhost: 8080

    • make sure: your CATALINA_HOME is pointing to Magnolia's tomcat directory
    • mine is : CATALINA_HOME=C:\magnolia_cms\magnolia-5.5.4\apache-tomcat-8.5.5
      i hope it helps...
Comment by Martin Schmid [ 24/May/17 ]

Hi jeffry, that exactly the same cause as I described in https://jira.magnolia-cms.com/browse/MGNLDEMO-198?focusedCommentId=135699&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-135699

this ticket is resolved.

Comment by alaa salameh [ 25/Jan/21 ]

I had the same issue , its because i have JAVA_HOME points to java 15 , i fixed that setting JAVA_HOME to java 8 in magnolia-control.bat file.

 

try add this line to manolia-control.bat

SET JAVA_HOME="your java 8 installed location"

Comment by Mikhail Dosov [ 07/Mar/21 ]

I had exctly the same issue.

Win 10 64 bit, JDK 15, JAVA_HOME= JDK 15.

I've tried to install magnolia by this https://docs.magnolia-cms.com/product-docs/Getting-started-with-Magnolia/Installing-Magnolia/Installing-Magnolia-through-npm-CLI.html

All was fine up to https://docs.magnolia-cms.com/product-docs/Getting-started-with-Magnolia/Installing-Magnolia/Installing-Magnolia-through-npm-CLI.html#_logging_into_the_author_instance

Then I tried to open "Run the Web update on the author instance" in http://localhost:8080 I've got 404 error.

Follow alsalameh102 I download JDK 8 and change JAVA_HOME to JDK 8. It works!

 

 

Generated at Mon Feb 12 05:17:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.