I am facing 503 AuthenticationSupport service missing. Cannot authenticate request error every time server is started. This happened many times. There is no such broken error information on the error log file. I have even deleted the repository but didn't help much. I even use oak but still no use. I had set up it multiple times to skip this error but I don't feel confident with this approach. For better information, I am attaching the latest error log file.
https://drive.google.com/file/d/1aXEcZP_Tvk1ebBxfOmR9Q1ffk2KLeW66/view?usp=sharing
NOTE: I am a beginner in AEM. Please be gentle
java -Xmx6000m -jar oak-run-1.8.0.jar check --bin=-1 C:\Users\mahinder.singh\Documents\Projects\Adobe\author\crx-quickstart\repository\segmentstore
This is usual. Might be taking a little longer time than usual to load. Wait for a while.
If the issue still persists reinstall the instance and allow the aem to get kicked up on it's own.
Related
I am new to Bluemix and running into trouble when attempting to "View App" while it is running. This is using the Watson IoT Starter boilerplate. Git is connected.
I have deleted and recreated that application multiple times but continue to encounter the same issue.
"404 Not Found: Requested route ('courserastartapp.mybluemix.net') does not exist."
Is anyone else having the problem? Any suggestions?
Sometimes the boilerplate, especially the npm part, takes a while to complete and make the route viewable. Are you restarting without giving it enough time to complete the process? Try waiting about 5 minutes after deploy to view the route. If it still does not work then check the deployment logs and let us know what errors you see.
Edited to add: we hope to have a fix in place soon
The presence insight server on bluemix has been quite unstable now. Cannot get access to the server.
Is there any way to deploy the instance on softlayer server for production?
There were definitely some problems with PI last evening, but the team worked until early this morning to get them resolved. It looks like the system is back up and functioning. Are you still seeing the issue?
Also, as a general reference, this page has service status details on it that may be of help if you notice a problem.
My application is developed in Grails 2.4.4. It uses MongoDB-3.0.2 plugin. I use Hudson as my CI system.
Sometimes when the job in hudson tries to build the application war, I get the below error.
Error | Resolve error obtaining dependencies: Failed to read artifact
descriptor for
org.grails:grails-datastore-gorm-plugin-support:jar:3.1.3.BUILD-SNAPSHOT
(Use --stacktrace to see the full trace)
It doesn't happen all the time. Many times the war was built successfully. Recently I am facing this problem more frequently.
In one of the question similar to this this, someone has suggested to change the Snapshot version to Release version. I tried it but didn't help me.
I also faced this problem in dev environment few times.
Can anyone let me know what could be the issuse? Could it be connectivity problem between the repository and my system?
Our SSL certificate expired this morning. We are working to get it addressed. An option to use as a workaround would be to use http instead of https. See comments at https://github.com/grails/grails-core/issues/9200.
The process is almost complete to get the new cert in place. Sorry for the trouble.
I cannot seem to get anything but a 404 in the browser or a timeout message in eclipse when trying to access this file
http://dl.google.com/eclipse/plugin/core/4.3/zips/gpe-e43-latest-updatesite.zip
Can anyone else reach it, maybe I'm just blocked for some reason now at work? I was able to download the plugin once, during my first week. Now I cannot check for updates or anything.
I followed a few other posts about the subject and have come up with nothing.
When running memcached, after a few minutes of use it starts throwing the following errors and memcache stops responding.
mcm_server_connect_next_avail():2328
I have searched the Google, and it seems many people are having this issue, but the only solution I have found was 'restart the server'.
Anyone have any insight?
It seems this is a limitation with using the cmemcache library. If we use python-libmemcache everything is fine.