Description
Bug Reports
-
dlite version in use (run
dlite --version):
dlite version 2.0.0-beta8 -
expected behavior:
dlite should start correctly after reboot and make my day the best day ever. -
actual behavior:
dlite doesn't start correctly after reboot and makes the reboot day the worst day ever. -
steps to reproduce
I haven't got a clue
TL;DR
Something seems to be wrong with extractUser, lookupUser or proxy on my machine, I don't really know...
My story
After the first install dlite starts without any problems and runs great, but after a reboot it won't start correctly.
Directly after I log in I can find a dlite process but no hyperkit process in Activity Monitor.
The dlite process is using 1-2 MB of RAM, which sounds small but probably isn't anything weird.
docker ps returns an error
$ docker ps
Error response from daemon: Unable to connect to the virtual machinedlite start runs into a timeout. (two dlite processes during this time and when it's done one process is terminated and the original process persists)
$ dlite start
Starting the virtual machine: ERROR!
Timed out waiting for virtual machinedlite stop runs into infinity and beyond until I press ctrl-c. (the dlite process is still running)
Running dlite stop again after this:
$ dlite stop
Stopping the virtual machine: done(the dlite process is still running)
Debug mode activated
So I start digging and I find out that a some commands makes a HTTP POST request to http://127.0.0.1:1050/[command].
Running curl -X POST http://127.0.0.1:1050/start returns Unauthorized
Running curl -X POST --header "X-Username: emil" http://127.0.0.1:1050/start returns Timed out waiting for virtual machine
Running curl -X POST http://127.0.0.1:1050/stopreturns Virtual machine is not running (which is expected)
Using Chrome and visiting http://127.0.0.1:1050/status also returns Unauthorized.
It seems like there's something wrong with extractUser, lookupUser or proxy.
I have tried to uninstall everything (I think) and reinstall dlite but with the same results.
I have tried to unload local.docker.plist and loading it again but with the same results.