Hi all,
I'm facting a issue on AEM 6.2 SP1 on a Author instance.
After a reboot of the server, my author instance won't start well, and all the Author URL give me a "Service Unavailable" 503 error.
I'm have no idea what is going wrong, no change were made.
Here the stdout.log when I start the Author :
The first error is :
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
15.06.2017 15:02:20.713 *INFO * [main] Setting sling.home=crx-quickstart (command line)
15.06.2017 15:02:20.723 *INFO * [main] No Apache Sling running at /127.0.0.1:46003
15.06.2017 15:02:20.724 *INFO * [main] Starting Apache Sling in /opt/adobe/aem/6.2/crx-quickstart
15.06.2017 15:02:20.725 *INFO * [Apache Sling Control Listener@/127.0.0.1:41173] Apache Sling Control Listener started
15.06.2017 15:02:20.726 *INFO * [main] Sling Extension Lib Home : /opt/adobe/aem/6.2/crx-quickstart/launchpad/ext
15.06.2017 15:02:20.729 *INFO * [main] Checking launcher JAR in folder /opt/adobe/aem/6.2/crx-quickstart/launchpad
15.06.2017 15:02:20.739 *INFO * [main] Existing launcher is up to date, using it: 5.4.0.2_6_10-B004 (org.apache.sling.launchpad.base.jar)
15.06.2017 15:02:20.740 *INFO * [main] Loading launcher class org.apache.sling.launchpad.base.app.MainDelegate from org.apache.sling.launchpad.base.jar
15.06.2017 15:02:20.740 *INFO * [main] External Libs Home (ext) is null or does not exists.
15.06.2017 15:02:20.750 *INFO * [main] Setting sling.properties=conf/sling.properties
15.06.2017 15:02:20.750 *INFO * [main] Setting sling.home=crx-quickstart
15.06.2017 15:02:20.750 *INFO * [main] Setting sling.launchpad=/opt/adobe/aem/6.2/crx-quickstart/launchpad
15.06.2017 15:02:20.750 *INFO * [main] Setting org.osgi.service.http.port=4502
15.06.2017 15:02:20.750 *INFO * [main] Starting launcher ...
15.06.2017 15:02:20.757 *INFO * [main] HTTP server port: 4502
ERROR: Error parsing system bundle export statement: org.osgi.dto; version=1.0.0, org.osgi.framework; version=1.8.0, org.osgi.framework.dto; version=1.8.0, org.osgi.framework.hooks.bundle; version=1.1.0, org.osgi.fram
ework.hooks.resolver; version=1.0.0, org.osgi.framework.hooks.service; version=1.1.0, org.osgi.framework.hooks.weaving; version=1.1.0, org.osgi.framework.launch; version=1.2.0, org.osgi.framework.namespace; version=1.
1.0, org.osgi.framework.startlevel; version=1.0.0, org.osgi.framework.startlevel.dto; version=1.0.0, org.osgi.framework.wiring; version=1.2.0, ! !org.osgi.framework.wiring.dto; version=1.2.0, org.osgi.resource; version=1
.0.0, org.osgi.resource.dto; version=1.0.0, org.osgi.service.packageadmin; version=1.2.0, org.osgi.service.resolver; version=1.0.0, org.osgi.service.startlevel; version=1.1.0, org.osgi.service.url; version=1.0.0, org.
osgi.util.tracker; version=1.5.1, org.apache.sling.launchpad.api;version=1.2.0, javax.accessibility;uses:="javax.swing.text";version="0.0.0.1_008_JavaSE", javax.activity;version="0.0.0.1_008_JavaSE", javax.annotation.
processing;uses:="javax.tools,javax.lang.model,javax.lang.model.element,javax.lang.model.util";version="0.0.0.1_008_JavaSE", javax.annotation;version="0.0.0.1_008_JavaSE", javax.crypto.interfaces;uses:="javax.crypto.s
pec,javax.crypto";version="0.0.0.1_008_JavaSE", javax.crypto.spec;uses:="javax.crypto";version="0.0.0.1_008_JavaSE", javax.crypto;uses:="javax.crypto.spec";version="0.0.0.1_008_JavaSE", javax.imageio.event;uses:="java
x.imageio";version="0.0.0.1_008_JavaSE", javax.imageio.metadata;uses:="org.w3c.dom,javax.imageio";version="0.0.0.1_008_JavaSE", javax.imageio.plugins.bmp;uses:="javax.imageio";version="0.0.0.1_008_JavaSE", javax.image
io.plugins.jpeg;uses:="javax.imageio";version="0.0.0.1_008_JavaSE", javax.imageio.spi;uses:="javax.imageio.stream,javax.imageio,javax.imageio.metadata";version="0.0.0.1_008_JavaSE", javax.imageio.stream;uses:="javax.i
mageio";version="0.0.0.1_008_JavaSE", javax.imageio;uses:="javax.imageio.metadata,javax.imageio.stream,...
and then: There is a lot of error with bundle:
15.06.2017 15:02:21.363 *ERROR* [FelixStartLevel] ERROR: Bundle '1' Error starting slinginstall:org.apache.sling.installer.provider.file-1.1.0.jar (org.osgi.framework.BundleException: Unable to resolve org.apache.sling.installer.provider.file [1](R 1.0): missing requirement [org.apache.sling.installer.provider.file [1](R 1.0)] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.4.0)(!(version>=2.0.0))) Unresolved requirements: [[org.apache.sling.installer.provider.file [1](R 1.0)] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.4.0)(!(version>=2.0.0)))])
org.osgi.framework.BundleException: Unable to resolve org.apache.sling.installer.provider.file [1](R 1.0): missing requirement [org.apache.sling.installer.provider.file [1](R 1.0)] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.4.0)(!(version>=2.0.0))) Unresolved requirements: [[org.apache.sling.installer.provider.file [1](R 1.0)] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.4.0)(!(version>=2.0.0)))]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2117)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:745)
.......
15.06.2017 15:02:21.669 *ERROR* [FelixStartLevel] ERROR: Bundle '138' Error starting launchpad:resources/install/30/org.apache.sling.startupfilter.disabler-0.0.1-Rev1387008.jar (org.osgi.framework.BundleException: Unable to resolve org.apache.sling.startupfilter.disabler [138](R 138.0): missing requirement [org.apache.sling.startupfilter.disabler [138](R 138.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.startupfilter)(version>=0.0.0)(!(version>=1.0.0))) [caused by: Unable to resolve org.apache.sling.startupfilter [48](R 48.0): missing requirement [org.apache.sling.startupfilter [48](R 48.0)] osgi.wiring.package; (osgi.wiring.package=javax.servlet.http) [caused by: Unable to resolve org.apache.felix.http.servlet-api [37](R 37.0): missing requirement [org.apache.felix.http.servlet-api [37](R 37.0)] osgi.ee; (&(osgi.ee=JavaSE)(version=1.7))]] Unresolved requirements: [[org.apache.sling.startupfilter.disabler [138](R 138.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.startupfilter)(version>=0.0.0)(!(version>=1.0.0)))])
org.osgi.framework.BundleException: Unable to resolve org.apache.sling.startupfilter.disabler [138](R 138.0): missing requirement [org.apache.sling.startupfilter.disabler [138](R 138.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.startupfilter)(version>=0.0.0)(!(version>=1.0.0))) [caused by: Unable to resolve org.apache.sling.startupfilter [48](R 48.0): missing requirement [org.apache.sling.startupfilter [48](R 48.0)] osgi.wiring.package; (osgi.wiring.package=javax.servlet.http) [caused by: Unable to resolve org.apache.felix.http.servlet-api [37](R 37.0): missing requirement [org.apache.felix.http.servlet-api [37](R 37.0)] osgi.ee; (&(osgi.ee=JavaSE)(version=1.7))]] Unresolved requirements: [[org.apache.sling.startupfilter.disabler [138](R 138.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.startupfilter)(version>=0.0.0)(!(version>=1.0.0)))]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2117)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:745)
15.06.2017 15:02:21.669 *INFO * [main] Startup completed
any ideas ?
Thanks
Julien
Solved! Go to Solution.
Views
Replies
Total Likes
I have also faced this issue of getting 503 error once, incase your tar files are corrupted like I mine, best is to re-install the instance.
Views
Replies
Total Likes
Hi Julien,
Apologies for the obvious question, but did you wait for the SP package to complete in the logs before restarting the instance?
I'm guessing that not all the bundles have started?
Any issues on other instances that you installed SP2 on?
Regards,
Opkar
Views
Replies
Total Likes
I have also faced this issue of getting 503 error once, incase your tar files are corrupted like I mine, best is to re-install the instance.
Views
Replies
Total Likes
Hi Julien,
Some how manually manipulated some files at cq_home/crx-quickstart/install can cause such issue. Validate the bundles at http://www.aemstuff.com/tools/coi.html
Thanks,
Views
Replies
Total Likes
Depending on the environment, wouldn't it be better to restore a backup, which should have been taken before the installation of the SP?
If this is a local environment, I would still have expected a backup to be taken, but if not, then you could reinstall.
Regards,
Opkar
Views
Replies
Total Likes