Printable View
Hello,
I have problem with Kali 2016.1 on VMware.
When I shutdown Kali I have information like below:
A stop job is running for User Manager for UID [...]
A stop job is running for Session c1 of User Debian-gdm [...]
I must wait 90 seconds everytime.
Sounds like something in the background isn't shutting down. Have you tried top or ps -ef to see the processes?
Edit the file /etc/systemd/system.conf and change these lines:
#DefaultTimeoutStartSec=10s
#DefaultTimeoutStopSec=10s
this is not a solution of the problem but his camuflage.Quote:
Originally Posted by Crash
I work with VMware, I noticed that the problem start when I install "open-vm-tools" and "fuse" :(
Kali 2016.6 not work with vmware-tools properly.
So, if you take a fast look in google, you can see that is not a specific Kali problem.
When the responsible devels solve it, it will be applied in Kali.
I know this may sound really dumb and I do not know the reason why it solves it but I found it on another thread for Arch Linux.
The solution is to open shell and "shutdown now" then when the machine comes back on then do a "reboot" and the message goes away and future reboots do not hang anymore.
I just tested this with the latest Kali 2017.2 VirtualBox image. The behavior is consistent. i.e. It corrects the 90s shutdown.Quote:
Originally Posted by IronMan
"this may sound really dumb" kind of has the same ring to it as,
"""
The most exciting phrase to hear in science, the one that heralds new discoveries, is not “Eureka!” (I found it!) but “That’s funny …”
— Isaac Asimov
""" -fortune(Unix), 1987, according to quoteinvestigator.com
I had this issue when installing Kali 2017.3 on VirtualBox, running on Mint.
Reading through several articles and posts, I saw a list of several options - one more exotic then the other.
I have no idea if this is reproducible for anybody, but it appeared I had my time-zone in Kali set differently then my host machine.
Just to be able to check my journal and other logs, I corrected that.
After rebooting yet another time, I suddenly came to the bservation that this "a stop job is running ..." had gone.
Really, this is the only thing I changed other then sifting trough some logs and options before.
Anyway - maybe this is of some help to anybody.
Cheers.
No, I'm sorry to say it's still there.Quote:
Originally Posted by amzker
Windows 10 Pro Host, Kali Linux 2017.3 Guest (fully updated as of 2 minutes ago) in VirtualBox 5.2.6. VirtualBox extensions and Guest Additions 'VBoxLinuxAdditions.run' version 5.2.7 installed.
Used apt-get update, apt-get upgrade, and apt-get dist-upgrade to update.
Exact same message as OP. I tried the "shutdown now", then "reboot" but the problem persists. It's no big deal, I guess, if you don't mind waiting two minutes.
I looked through the logs but I'm not experienced enough to know what I'm looking for if it's not a glaring error like 'FAIL' or 'missing package' or something like that.
Anyone have any tips to try?
.
Also not just virtual software. Occationally when I live boot fron a dvd this happens.Quote:
Originally Posted by ThinkingMonkey
Experiencing same behavior on my VMs.
I am running Kali Linux 2018.1 on a Windows Home host machine using VirtualBox. I had the same issue and this is how I fixed it.
Log in normally as you would in Kali and then, before shutting down, make sure to log out all users (click on the top-right corner and select the user, then log out).
Only after that you shutdown. This made an instant shutdown for me and all subsequently normal shutdowns (without logging out) as well
Thank you camba.. this resolved my issue on VirtualBox Kali 2018.1 (no update, upgrades)
Camba's advice worked for me as well. Thank you.