atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <>
Subject [jira] [Commented] (ATLAS-238) the Atlas server won’t restart after improper shutdown
Date Fri, 06 Nov 2015 08:52:27 GMT


Suma Shivaprasad commented on ATLAS-238:

[~ndjouhr] the patch doesnt apply correctly. Can you pls check reattach

git apply -v ATLAS-238.patch
fatal: unrecognized input

> the Atlas server won’t restart after improper shutdown
> ----------------------------------------------------------------------
>                 Key: ATLAS-238
>                 URL:
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.6-incubating
>            Reporter: Naima Djouhri
>            Assignee: Naima Djouhri
>            Priority: Minor
>             Fix For: 0.6-incubating
>         Attachments: ATLAS-238_V0.patch
> Steps to reproduce
> 1.	Open a Windows/terminal/shell and start the Atlas server with “”
> 2.	Log in to your Atlas server http://localhost:21000/ to make sure that you can connect
> 3.	 Close the Windows/terminal/shell where the Atlas server process started –step1

> Or just kill the process - the process id can be found in a file called “”
in the logs directory (this file is created by the “” script
> 4.	Try to login to your Atlas server again and a “Unable to connect” message will
pop up
> 5.	From a command prompt Windows/ Terminal/Shell start the server ( 
> 6.	A message “ already exists, exiting” will pop up in the screen and the
server will not start
> Expected Result
> The server should start since it has been shut down
>        Actual: 
> The server can not start
> If the server is stopped using “”  , the server restart after running
"" with no issue.
> Since the server has not been stopped with “”  that kill the 
> process, and delete the “” file, the script “” will not
start the server.
> The turnaround is to delete the “” file in the logs directory but it is
not always obvious, and user friendly!!

This message was sent by Atlassian JIRA

View raw message