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

chown on vm.tty sometimes fails #223

Open
nlf opened this issue Feb 15, 2017 · 4 comments
Open

chown on vm.tty sometimes fails #223

nlf opened this issue Feb 15, 2017 · 4 comments
Labels

Comments

@nlf
Copy link
Owner

nlf commented Feb 15, 2017

Bug Reports

  • dlite version in use (run dlite --version):
    2.0.0-beta9

  • expected behavior:
    vm.tty has correct permissions

  • actual behavior:
    vm.tty doesn't exist when chown is run, causing dlite start to exit with an error

  • steps to reproduce
    dlite start
    this is random, caused by a race condition

opening this issue for myself :)

need to add some code to make sure that vm.tty exists before attempting to change permissions on it.

@nlf nlf added the bug label Feb 15, 2017
@gherkins
Copy link

i ran across that today, too.
after rebooting my macbook with dlite still running, i was stuck with that message when trying to start dlite again.

dlite start - tty chown fails
dlite stop - done.
dlite start - tty chown fails
dlite start - CONFLICT
dlite stop - done.
...

i ended up re-running dlite init,
everything back to normal now...

:)

@bartrail
Copy link

bartrail commented Mar 15, 2017

I have this problem too. can't get dlite running at all anymore.
it worked in the past, running dlite stop dlite start several times one after another.
this is the message i get:

~ > dlite start
Starting the virtual machine: ERROR!
chown /Users/con/.dlite/vm.tty: no such file or directory

update: maybe I should add that I have just rebooted my mac. before shutdown I gracefully stoped the running container and ran dlite stop to stop the virtual machine..

@andreydeineko
Copy link

Same issue. Running

dlite init

resolved it.

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

5 participants
@bartrail @nlf @gherkins @andreydeineko and others