Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-238

atlas_start.py- the Atlas server won’t restart after improper shutdown

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 0.6-incubating
    • 0.6-incubating
    • None
    • None

    Description

      Steps to reproduce
      1. Open a Windows/terminal/shell and start the Atlas server with “atlas_start.py” script
      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 “atlas.pid” in the logs directory (this file is created by the “atlas_start.py” 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 (atlas_start.py)
      6. A message “atlas.pid 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 “atlas_stop.py” , the server restart after running "atlas_start.py" with no issue.
      Since the server has not been stopped with “atlas_stop.py” that kill the
      process, and delete the “atlas.pid” file, the script “atlas_start.py” will not start the server.
      The turnaround is to delete the “atlas.pid” file in the logs directory but it is not always obvious, and user friendly!!

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ndjouhr Naima Djouhri
            ndjouhr Naima Djouhri
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment