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

Eye stopped working until the .eye dir was deleted #229

Open
rgaufman opened this issue Sep 26, 2019 · 4 comments
Open

Eye stopped working until the .eye dir was deleted #229

rgaufman opened this issue Sep 26, 2019 · 4 comments

Comments

@rgaufman
Copy link

rgaufman commented Sep 26, 2019

Eye suddenly stopped working, running "eye i" just showed an empty string, as if eye was started without applications. Rebooting the machine did not resolve the problem.

I had to remove the old .eye folder in order for eye load to work again.

The broken .eye folder has 2 files:

~/.eye-old$ ls -ltra
total 12
-rw-r--r--  1 deployer sudo        4 Sep 26 22:38 pid
srwxr-xr-x  1 deployer sudo        0 Sep 26 22:38 sock
drwxr-xr-x  2 deployer sudo     4096 Sep 26 22:38 .
drwxr-xr-x 10 deployer deployer 4096 Sep 26 23:24 ..
~/.eye-old$ cat sock
cat: sock: No such device or address
:~/.eye-old$ cat pid
4722

Any ideas what could be the issue?

@kostya
Copy link
Owner

kostya commented Sep 27, 2019

strange case, may be there was two eye's? ps aux | grep eye

@rgaufman
Copy link
Author

This is after rebooting the server, so there shouldn't be 2 eye processes, but maybe. Is there anyway to force eye to only allow 1 process?

@kostya
Copy link
Owner

kostya commented Sep 27, 2019

this folder already force for 1 eye. but maybe you have another eye under other user.

@rgaufman
Copy link
Author

There is only 1 user on this system, deployer, there are no other eye processes started by any other user. It is very strange, so I did:

  1. Try to eye quit and eye load, nothing.
  2. Tried to reboot server and run eye load, nothing.
  3. Tried to move the .eye folder to a different folder, this time eye started correctly.

Any ideas at all what could have caused this behaviour?

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