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

Unable to get a timer to start #37

Closed
rebelzach opened this issue Jun 9, 2015 · 2 comments
Closed

Unable to get a timer to start #37

rebelzach opened this issue Jun 9, 2015 · 2 comments

Comments

@rebelzach
Copy link

For what its worth, here is a bug I ran into and my steps to resolve

I noticed that glass was no longer inserting time into my commits. When running glass status I received No timer appears to be running for '/Users/...': Daemon doesn't appears to be running.

I ran glass start and got the timer started message. However glass status yielded the same error. glass stop had no effect either

When I tried to start the daemon manually I received It appears another Daemon is already running or a previous instance didn't shutdown properly, use -force to force start.

running glass-daemon -force and then terminating seems to have corrected the issue.

@advanderveer
Copy link
Contributor

Thanks for reporting, I ran into the issue myself and it will be fixed after pull request #35 is merged and released. It seems to occur when the daemon somehow didn't shutdown gracefully.

The correct way to fix it in the meantime is to restart the daemon manually using the -force flag as you mentioned.

@advanderveer
Copy link
Contributor

Fixed in v0.5.2, check it out!

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

No branches or pull requests

2 participants