VNC Server Not Working on Two App Servers, SSH Too on One
by des_a from LinuxQuestions.org on (#4Z9VZ)
My VNC quit working on two of my app servers. I've even gone so far as to restore from images, and the problem somehow persists. I would like some input as to what could be going wrong and how I can quickly fix it from the Linux command line without any complicated commands to do things quick.
The message I get from a version of tightvnc server on a windows 10 machine is that it's taking too long to respond. I get this for both servers.
My 3rd app server on that machine works just fine now. These are 3 machines running in VirtualBox VMs.
The first of the App servers that's not working is vmandrakelinux, which runs Mandrake Linux Community 10.1 from a for Dummies book called Linux for Dummies.
The second App server is vsuselinux, which runs SuSe Linux 9.0 Proffessional. On this machine I'm also having trouble with SSH.
Could rebooting the underlying Windows 10 machine again solve this problem? Not the current version of Windows 10 yet, I believe 1803. It made the other one work last time I rebooted the machine. I believe I will try this just to see what happens.
I'm always locating junk in /tmp/.X11-unix, which holds some kind of instance for VNC. It keeps trying to run multiple versions of the VNC server. Also in the directory ~/.vnc.
This is the same with both machines what it tends to do. One machine however is new enough that the service command works, as in service [service] restart or start or stop.
The other, you have to run the scripts manually, because it's too old. That's the SuSe Linux machine.
The message I get from a version of tightvnc server on a windows 10 machine is that it's taking too long to respond. I get this for both servers.
My 3rd app server on that machine works just fine now. These are 3 machines running in VirtualBox VMs.
The first of the App servers that's not working is vmandrakelinux, which runs Mandrake Linux Community 10.1 from a for Dummies book called Linux for Dummies.
The second App server is vsuselinux, which runs SuSe Linux 9.0 Proffessional. On this machine I'm also having trouble with SSH.
Could rebooting the underlying Windows 10 machine again solve this problem? Not the current version of Windows 10 yet, I believe 1803. It made the other one work last time I rebooted the machine. I believe I will try this just to see what happens.
I'm always locating junk in /tmp/.X11-unix, which holds some kind of instance for VNC. It keeps trying to run multiple versions of the VNC server. Also in the directory ~/.vnc.
This is the same with both machines what it tends to do. One machine however is new enough that the service command works, as in service [service] restart or start or stop.
The other, you have to run the scripts manually, because it's too old. That's the SuSe Linux machine.