Hi, I am facing an issue with the AEM 6.4 (no SP) instance not starting
Jetty server keeps stopping with the following error. Unable to connect to AEM. Here is the entry in the log.
09.01.2019 18:37:33.316 *ERROR* [CM Configuration Updater (ManagedService Update: pid=[org.apache.felix.http])] org.apache.felix.http.jetty Failed to start Connector: ServerConnector@705e74f6{HTTP/1.1,[http/1.1]}{13.71.3.224:4502} (java.net.BindException: Cannot assign requested address)
09.01.2019 18:37:33.318 *ERROR* [CM Configuration Updater (ManagedService Update: pid=[org.apache.felix.http])] org.apache.felix.http.jetty Jetty stopped (no connectors available)
09.01.2019 18:37:33.319 *ERROR* [CM Configuration Updater (ManagedService Update: pid=[org.apache.felix.http])] org.apache.felix.http.jetty Exception while initializing Jetty. (java.lang.NullPointerException)
I have tried compacting the repository.
Any pointers?
Solved! Go to Solution.
Views
Replies
Total Likes
can you check your box's ip, hosts and ifconfig, if it shows the same ip that you are trying to bind with?
may be try a different ip or another hostname from hosts file
shut down publish for a while and check if only one server works at a time?
Views
Replies
Total Likes
Either the ip or port is not available or it becomes unavailable as soon as jetty tries to bind it. Check via netstat if other app is already running on same
Views
Replies
Total Likes
Thanks Gaurav, tried killing the instance. Same issue. I have a publish instance running on the same box and it is working fine.
Netstat shows 4503 running
tcp6 0 0 :::4503 :::* LISTEN 66978/java
tcp6 0 0 127.0.0.1:37148 :::* LISTEN 66978/java
Views
Replies
Total Likes
can you check your box's ip, hosts and ifconfig, if it shows the same ip that you are trying to bind with?
may be try a different ip or another hostname from hosts file
shut down publish for a while and check if only one server works at a time?
Views
Replies
Total Likes
Tried it, ip address and host is the same. No luck. I tried renaming the existing crx-quickstart and reinstalled the author instance, it started working fine. I am able to hit 4502 with the fresh install
Views
Replies
Total Likes
that means the existing unpacked contents under /crx-quickstart had different bindings esp. port# against the jar name/port.
Glad to hear!
Views
Replies
Total Likes
So heres what happened
While the server was on I guess someone changed the "crx-quickstart/launchpad/config/org/apache/felix/http.config file to add the server address. Once I replaced the file with the one from the new install it started working
Thanks Gaurav
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies