Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Incorrect Status #214

Closed
cobbspur opened this issue Jun 19, 2017 · 2 comments
Closed

Bug: Incorrect Status #214

cobbspur opened this issue Jun 19, 2017 · 2 comments
Assignees
Labels
Milestone

Comments

@cobbspur
Copy link
Member

So I have started using ghost-cli again for the first time in a long time.

I created a local install which is working nicely then created another instance in a different directory just to see what happens.

The result was 3 ghost instance with apparently 2 instances using port 2368.

So I guess at one point I killed the the old ghost service manually or restarted laptop etc but it report its status of still running.

For testing purposes I killed a new process (that was running on port 2369) and created a new ghost instance on the same port.

Here is a screenshot: https://puu.sh/wopYj/2afff4f46c.png

Note: It is possible to navigate to the correct directory and use ghost stop but we probably should determine the status in a different manner

@acburdine
Copy link
Member

@cobbspur some of this will be solved by #207

@acburdine acburdine self-assigned this Jun 19, 2017
@acburdine acburdine added the bug label Jun 19, 2017
@acburdine acburdine added this to the 1.0.0-beta.1 milestone Jun 19, 2017
@cobbspur
Copy link
Member Author

Ah I didn't notice that issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants