cancel
Showing results for 
Search instead for 
Did you mean: 

Can't login after Ubuntu release update 9.10 to 10.04

ttownsend
Champ on-the-rise
Champ on-the-rise
Hello everyone,

I'm running Alfresco 3.4.e on Ubuntu 9.10x64 as a VM under VirtualBox 4.1.6 Release 74713.  Everything is smoooooth and stable except for no SSL/HTTPS.
Since Ubuntu 9.10 is deprecated I did "do-release-update" to bring the release up to 10.04LTSx64.  But when I do this, I can not longer log into Share and receive "The remote server may be unavailable or your authentication details have not been recognized."  when using the correct credentials.  Tomcat's base page at 8080 shows, but 8080/Alfresco returns a 404.

Since this is running as a VM, I reverted to a previous snapshot and all is running well again.  But I won't access this from outside until I get SSL working, which I think requires a release upgrade, so I'm trying to figure out a course of action from here.

Any help is certainly very welcome.

Since this is my first time posting an error here, I hope I do this correctly.
Here's my catalina.out
12-Dec-2011 12:33:38 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/alfresco-3.4.e/java/jre/lib/amd64/server:/opt/alfres$
12-Dec-2011 12:33:38 AM org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.BindException: Address already in use <null>:8080
        at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:549)
        at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:176)
        at org.apache.catalina.connector.Connector.initialize(Connector.java:1014)
        at org.apache.catalina.core.StandardService.initialize(StandardService.java:680)
        at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:795)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:548)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.net.BindException: Address already in use
        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at java.net.ServerSocket.<init>(ServerSocket.java:141)
        at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:50)
        at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:538)
        … 12 more
12-Dec-2011 12:33:38 AM org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
LifecycleException:  Protocol handler initialization failed: java.net.BindException: Address already in use <null>:8080
        at org.apache.catalina.connector.Connector.initialize(Connector.java:1016)
        at org.apache.catalina.core.StandardService.initialize(StandardService.java:680)
        at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:795)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:548)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
12-Dec-2011 12:33:38 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 676 ms
12-Dec-2011 12:33:38 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
12-Dec-2011 12:33:38 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.29
12-Dec-2011 12:33:38 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor manager.xml
12-Dec-2011 12:33:38 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor alfresco.xml
12-Dec-2011 12:33:39 AM org.apache.catalina.core.StandardContext addApplicationListener
INFO: The listener "org.apache.myfaces.webapp.StartupServletContextListener" is already configured for this context. The duplicate definition has been ignored.
4 REPLIES 4

mikeh
Star Contributor
Star Contributor
You need to stop the server that's already listening on port 8080 before trying to start Alfresco's Tomcat server.

Mike

ttownsend
Champ on-the-rise
Champ on-the-rise
Hi Mike,

Thanks for taking the time to reply. 

I'm curious - I didn't have any apps/services installed under 9.10 that would collide on port 8080, and I thought that do-release-upgrade only upgraded the kernel and installed package versions.  I can reinstate a snapshot and hunt around for whatever is causing a port 8080 conflict.

I'll report back with what I learn.

Many thanks,
Trevor

ttownsend
Champ on-the-rise
Champ on-the-rise
Hi Mike,

Thanks for taking the time to reply. 

I'm curious - I didn't have any apps/services installed under 9.10 that would collide on port 8080, and I thought that do-release-upgrade only upgraded the kernel and installed package versions.  I can reinstate a snapshot and hunt around for whatever is causing a port 8080 conflict.

I'll report back with what I learn.

Many thanks,
Trevor

vamirr
Champ on-the-rise
Champ on-the-rise
A process has to be running that has that port open.  You should be able to find it with ps.

Post the output of ps -Af.