Expand my Community achievements bar.

SOLVED

Error Message appears when starting AEM 6.1 with Service Pack 1

Avatar

Former Community Member

Hi,

I have installed a fresh AEM 6.1, and service pack 1. Whenever I start the server, the following error message appears. The sites seems still working and as well as crxde.

20.04.2016 15:25:33.345 *INFO * [main] Setting sling.home=crx-quickstart (comman
d line)
20.04.2016 15:25:33.354 *INFO * [main] Starting Apache Sling in D:\aem6.1SP1\aut
hor\crx-quickstart
20.04.2016 15:25:33.356 *INFO * [main] Sling  Extension Lib Home : D:\aem6.1SP1\
author\crx-quickstart\launchpad\ext
20.04.2016 15:25:33.359 *INFO * [Apache Sling Control Listener@/127.0.0.1:53536]
 Apache Sling Control Listener started
20.04.2016 15:25:33.360 *INFO * [main] Checking launcher JAR in folder D:\aem6.1
SP1\author\crx-quickstart\launchpad
20.04.2016 15:25:33.371 *INFO * [main] Existing launcher is up to date, using it
: 4.6.1.2_5_8-B003 (org.apache.sling.launchpad.base.jar)
20.04.2016 15:25:33.372 *INFO * [main] Loading launcher class org.apache.sling.l
aunchpad.base.app.MainDelegate from org.apache.sling.launchpad.base.jar
20.04.2016 15:25:33.373 *INFO * [main] External Libs Home (ext) is null or does
not exists.
20.04.2016 15:25:33.396 *INFO * [main] Setting sling.launchpad=D:\aem6.1SP1\auth
or\crx-quickstart\launchpad
20.04.2016 15:25:33.405 *INFO * [main] Setting sling.home=crx-quickstart
20.04.2016 15:25:33.408 *INFO * [main] Setting sling.properties=conf/sling.prope
rties
20.04.2016 15:25:33.409 *INFO * [main] Setting org.osgi.service.http.port=4502
20.04.2016 15:25:33.409 *INFO * [main] Starting launcher ...
20.04.2016 15:25:33.410 *INFO * [main] HTTP server port: 4502
20.04.2016 15:25:34.791 *INFO* [FelixStartLevel] org.apache.sling.commons.log.lo
gback.internal.Activator LogbackManager initialized at bundle startup
20.04.2016 15:25:34.797 *INFO* [FelixStartLevel] org.apache.sling.commons.logser
vice Service [org.apache.sling.commons.logservice.internal.LogServiceFactory,18,
 [org.osgi.service.log.LogService]] ServiceEvent REGISTERED
*ERROR* [org.osgi.service.cm.ManagedServiceFactory, id=14, bundle=10/slinginstal
l:D:\aem6.1SP1\author\crx-quickstart\launchpad\startup\1\org.apache.sling.common
s.log-4.0.2.jar]: Updating property org.apache.sling.commons.log.names of config
uration org.apache.sling.commons.log.LogManager.factory.config.72c50274-fc33-418
e-93a2-1d0267e7c64a caused a problem: Category log.access already defined by con
figuration org.apache.sling.commons.log.LogManager.factory.config.72c50274-fc33-
418e-93a2-1d0267e7c64a20.04.2016 15:25:34.804 *INFO* [FelixStartLevel] org.apach
e.sling.commons.logservice Service [org.apache.sling.commons.logservice.internal
.LogReaderServiceFactory,19, [org.osgi.service.log.LogReaderService]] ServiceEve
nt REGISTERED

org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.names :
 Category log.access already defined by configuration org.apache.sling.commons.l
og.LogManager.factory.config.72c50274-fc33-418e-93a2-1d0267e7c64a
        at org.apache.sling.commons.log.logback.internal.config.LoggerManagedSer
viceFactory.updated(LoggerManagedServiceFactory.java:36)
        at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideC
onfiguration(ManagedServiceFactoryTracker.java:88)
        at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUp
date.provide(ConfigurationManager.java:1605)
        at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUp
date.run(ConfigurationManager.java:1548)
        at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)20.04
.2016 15:25:34.844 *INFO* [FelixStartLevel] org.apache.sling.installer.core Bund
leEvent RESOLVED

20.04.2016 15:25:34.846 *INFO* [FelixStartLevel] org.apache.sling.installer.core
 BundleEvent STARTING
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.sling.commons.log.logback.internal.config.ConfigurationExc
eption:
        at org.apache.sling.commons.log.logback.internal.LogConfigManager.update
LoggerConfiguration(LogConfigManager.java:514)
        at org.apache.sling.commons.log.logback.internal.config.LoggerManagedSer
viceFactory.updated(LoggerManagedServiceFactory.java:34)
        ... 5 more
Attempting to load ESAPI.properties via file I/O.
Attempting to load ESAPI.properties as resource file via file I/O.
Not found in 'org.owasp.esapi.resources' directory or file not readable: D:\aem6
.1SP1\author\ESAPI.properties
Not found in SystemResource Directory/resourceDirectory: .esapi\ESAPI.properties

Not found in 'user.home' (C:\Users\Chen Qian) directory: C:\Users\Chen Qian\esap
i\ESAPI.properties
Loading ESAPI.properties via file I/O failed. Exception was: java.io.FileNotFoun
dException
Attempting to load ESAPI.properties via the classpath.
SUCCESSFULLY LOADED ESAPI.properties via the CLASSPATH from '/ (root)' using cla
ss loader for DefaultSecurityConfiguration class!
Attempting to load validation.properties via file I/O.
Attempting to load validation.properties as resource file via file I/O.
Not found in 'org.owasp.esapi.resources' directory or file not readable: D:\aem6
.1SP1\author\validation.properties
Not found in SystemResource Directory/resourceDirectory: .esapi\validation.prope
rties
Not found in 'user.home' (C:\Users\Chen Qian) directory: C:\Users\Chen Qian\esap
i\validation.properties
Loading validation.properties via file I/O failed.
Attempting to load validation.properties via the classpath.
SUCCESSFULLY LOADED validation.properties via the CLASSPATH from '/ (root)' usin
g class loader for DefaultSecurityConfiguration class!
RAWProcessor succesfully installed

Thanks in advance.

1 Accepted Solution

Avatar

Correct answer by
Employee

Nothing to worry for *ERROR* [org.osgi.service.cm.ManagedServiceFactory, id=14, bundle=10/slinginstal
l:D:\aem6.1SP1\author\crx-quickstart\launchpad\startup\1\org.apache.sling.common
s.log-4.0.2.jar]: Updating property org.apache.sling.commons.log.names of config
uration org.apache.sling.commons.log.LogManager.factory.config.72c50274-fc33-418
e-93a2-1d0267e7c64a caused a problem: Category log.access already defined by con
figuration org.apache.sling.commons.log.LogManager.factory.config.72c50274-fc33-
418e-93a2-1d0267e7c64a20.04.2016 15:25:34.804 

As this is just looking for access log configuration which has been already defined. Check system/console/slinglog it will have the configuration for access log. 

View solution in original post

5 Replies

Avatar

Level 10

Can you access AEM when you login? 

Avatar

Former Community Member

No, I can access the AEM after the login.  

I just install AEM 6.1, then use the package manager to upload and install Service pack 1. When I start the server, I noticed this exception messages.

Avatar

Level 10

Everything works - but your concern is the log messages --That is correct right? 

Avatar

Level 10

I have asked AEM suport to take a look at this thread. 

Avatar

Correct answer by
Employee

Nothing to worry for *ERROR* [org.osgi.service.cm.ManagedServiceFactory, id=14, bundle=10/slinginstal
l:D:\aem6.1SP1\author\crx-quickstart\launchpad\startup\1\org.apache.sling.common
s.log-4.0.2.jar]: Updating property org.apache.sling.commons.log.names of config
uration org.apache.sling.commons.log.LogManager.factory.config.72c50274-fc33-418
e-93a2-1d0267e7c64a caused a problem: Category log.access already defined by con
figuration org.apache.sling.commons.log.LogManager.factory.config.72c50274-fc33-
418e-93a2-1d0267e7c64a20.04.2016 15:25:34.804 

As this is just looking for access log configuration which has been already defined. Check system/console/slinglog it will have the configuration for access log.