web console log support error | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Hi,

the replication errors are not related to your problem.

The fact, that you have only this small number of entries in the /system/console/slinglog screen (only 1 logger and 1 appender) is interesting, because a default AEM comes with some more entries (it writes a request.log, an access.log, update.log etc). So either you have messed with the default configuration (I would never remove loggers, but only add new ones) or the system you are working is in a way broken.

The exception "org.osgi.service.cm.ConfigurationException: oauth.config.id : Config Id must be unique" shows me that you have played with this instance quite a bit, so maybe rebuilding it from scratch is much faster than diagnosing strange issues which arose out of experiments with AEM.

Jörg

12 replies

Show previous replies
AdobeID24
AdobeID24Author
Level 5
September 19, 2018

Som more error lines from error.log file ..if you can hlp please:-)

18.09.2018 16:00:48.813 *ERROR* [FelixDispatchQueue] org.apache.aries.subsystem.core FrameworkEvent ERROR (org.osgi.service.coordinator.CoordinationException: Coordination failed)

18.09.2018 16:01:36.809 *ERROR* [CM Configuration Updater (ManagedServiceFactory Update: factoryPid=[com.adobe.granite.auth.oauth.provider])] org.apache.felix.configadmin Service [org.apache.felix.cm.ConfigurationAdmin,9, [org.osgi.service.cm.ConfigurationAdmin]] [org.osgi.service.cm.ManagedServiceFactory, id=546, bundle=149/launchpad:resources/install/0/com.adobe.granite.auth.oauth-1.0.44.jar]: Updating property oauth.config.id of configuration com.adobe.granite.auth.oauth.provider.c1ed00e1-d5bd-432d-bf81-be3006530a78 caused a problem: Config Id must be unique. (org.osgi.service.cm.ConfigurationException: oauth.config.id : Config Id must be unique.)

org.osgi.service.cm.ConfigurationException: oauth.config.id : Config Id must be unique.

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish Error while sending request: java.net.ConnectException: Connection refused: connect

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish Replication (DELETE) of /content/mymsmfolder not successful: java.net.ConnectException: Connection refused: connect Conversation follows

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish ------------------------------------------------

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish Sending message to localhost:4503

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish >> POST /bin/receive HTTP/1.0

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish >> Action: Delete

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish >> Path: /content/mymsmfolder

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish >> Handle: /content/mymsmfolder

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish >> Referer: about:blank

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish >> Content-Length: 0

18.09.2018 16:01:56.306 *ERROR* [FelixStartLevel] com.day.cq.replication.Agent.publish >> Content-Type: application/octet-stream

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
September 19, 2018

Hi,

the replication errors are not related to your problem.

The fact, that you have only this small number of entries in the /system/console/slinglog screen (only 1 logger and 1 appender) is interesting, because a default AEM comes with some more entries (it writes a request.log, an access.log, update.log etc). So either you have messed with the default configuration (I would never remove loggers, but only add new ones) or the system you are working is in a way broken.

The exception "org.osgi.service.cm.ConfigurationException: oauth.config.id : Config Id must be unique" shows me that you have played with this instance quite a bit, so maybe rebuilding it from scratch is much faster than diagnosing strange issues which arose out of experiments with AEM.

Jörg

Terms & ConditionsAccessibility statement

Loading footer...