I am running Ubuntu Server 14 (64bit) as a vm. It has VMware tools installed. Whenever I reboot it it gets stuck at “stopping system v run level compatibility”
Here is a screenshot: http://www.internetlinked.com/tmp/Reboot%20Error.jpg
There are many post around this type of issue but I can’t find any workable solution or how to approach the issue.
What Chipset do you have set? As I don’t have this issue and I’m using PIIX3
It is a virtual machine. I have two of them running different services. Both created at the same time. One works the other does not, The one with the issue is running Redis, MongoDB and NodeJs
Sorry, I should have been more specific. I was referring to the VirtualBox Settings for the VM, under System > Chipset
Hi
I am using VMware but found the following which show my current settings as well as changes that I can make: http://www.internetlinked.com/tmp/CPU2.PNG
Okay, I may be going in the wrong direction… seems this issue can exist for a variety of reasons 
One thing that keeps coming up is to check the .Xauthority permissions placed in your /home/username folder. I’ve seen that in the past, but I can’t for the life of me remember why I had to deal with that issue.
Hi thanks for your patience as this must be painful for you as my Linux knowledge is very average.
sysadmin@s-server-01:~$ ls -a
. .bash_history .bashrc .nano_history .rediscli_history
… .bash_logout .cache .profile vmware-tools-distrib
sysadmin@s-server-01:~$
Man, I’m just stumped.
So I’m re-reading this topic to see if I miss anything important, and I have another question: “gets stuck” gets stuck when shutting down or starting back up?
Does it actually get to the reboot step and then it fails to start back up properly? Or is it failing to shutdown so it can start itself back up?
I’m just completely baffled by this.
Hi so I think I have something. I decided to do a screen cast to show you what was happening. Usually I reboot using the VM console option of “restart guest” and this is what showed http://www.internetlinked.com/tmp/Reboot%20Error.jpg. This time for the screencast I looked on as an admin and ran reboot from the command line. This time I got the following:
The system is going down for reboot N OW!
wait-for-state stop/waiting
Stopping redis-server:
And here it stays.
It seems that the redis-server is preventing the reboot. I will investigate this further and see what is happening.
Cool, that’s a bit more info 
So I’ve found the following:
http://stackoverflow.com/questions/15088053/stop-redis-server-neither-shutdown-nor-stop-works
http://stackoverflow.com/questions/18163839/upgrade-redis-2-4-14-to-redis-2-6-14-command-service-redis-start-always-hangs
http://serverfault.com/questions/359006/redis-wont-shutdown
All of the above approach the problem from different angles, so hopefully one of them is the exact scenario you have! 
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.
