topic Re: Fresh 4.2.c CE on fresh Ubuntu server (12.04 x64) in Alfresco Archive

Fresh 4.2.c CE on fresh Ubuntu server (12.04 x64)

ttownsend — Wed, 20 Feb 2013 01:52:32 GMT

Hi all,I've just created a VM running Ubuntu 12.04 server x64 and installed Alfresco CE 4.2.c. The installer completes, but I am unable to log into Share using the administrator credentials.I have uninstalled and re-installed twice and have downloaded again and re-installed, but the condition persis

Re: Fresh 4.2.c CE on fresh Ubuntu server (12.04 x64)

bisana — Wed, 20 Feb 2013 04:49:05 GMT

Possible causes:-
Alfresco Repository is not properly started up as it fails to export a specific service via RMI. This may be due to port conflicts on your machine
or
A previous instance is not properly shut down, some process is using the port

soltuion:-

netstat -a to check for used ports before you attempt to start Alfresco and check for ports
ps aux | grep alf and see any process active before starting the instance

Re: Fresh 4.2.c CE on fresh Ubuntu server (12.04 x64)

kazishariar — Wed, 20 Feb 2013 17:39:56 GMT

There is a step in the install where it starts the service then stops it improperly. I think the steps in which it does this conflicts with the ports being used. A simple sleep command in the init script fixes this I've noticed. Basically restart the server:

<code>For now your fix is: sudo service alfresco stop && sleep 10 && sudo service alfresco start

Re: Fresh 4.2.c CE on fresh Ubuntu server (12.04 x64)

ttownsend — Fri, 22 Feb 2013 02:18:00 GMT

No luck - I've tried both of your suggestions and there is no evident effect. Catalina.out still shows the same bucket of errors - can the installer be repaired?

EDIT: I was not able to resolve this before my operational needs caused me to move onwards. I'm now using the Bitnami Alfresco stack for 4.2.c with no problems, however I am still interested in a solution for this, and will continue exploring it when time permits.

Re: Fresh 4.2.c CE on fresh Ubuntu server (12.04 x64)

ttownsend — Thu, 28 Feb 2013 18:52:06 GMT

I spent some time on this and discovered that stopping the Alfresco service will leave port 50500 in a TIME_WAIT state. If it is still in this state (claimed) when Alfresco starts it will report the errors I provided above. Using a suitable wait time between Alfresco stop and Alfresco start will eliminate this error.