RE: "A VNC server is already running as :10", but it isn't!
On Wed, 11 Dec 2002, Mike Miller wrote: > It's on Solaris 8. We now believe the problem is caused by ssh-X11 port > forwarding occupying port 6010. Port 6010 (DISPLAY :10) is the first > used by ssh. I have finally demonstrated that this was exactly the problem. My computer was connected to the server via PuTTY ssh. It had X11 port forwarding on and was occupying port 6010. When I killed PuTTY at home, port 6010 opened and I was then able to run vncserver :10 without trouble. Problem solved. Thanks to Corni Beerse for his detective work. Mike ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
I usually find that one side of the socket is being kept open... Make sure the server's not running (or stalled) in background somewhere... and make sure the client isn't hidden in nirvana either! Just a minute... (Wishing you where here, Chicago is playing...) okay back... Where was I? I suspect the client check for him extra carefully... On Wed, 2002-12-11 at 18:37, [EMAIL PROTECTED] wrote: > I'd assumed that there weren't any operating systems vulverable to "dead > socket"s, but that sure sounds like what you've got. A socket isn't > closed properly when a program exits, and the IP stack doesn't make it > available. Only cure - reboot (or stop/restart stack, on really old > systems with add-on IP stacks). > > Tim Conway > [EMAIL PROTECTED] reorder name and reverse domain > 303.682.4917 office, 303.921.0301 cell > Philips Semiconductor - Longmont TC > 1880 Industrial Circle, Suite D > Longmont, CO 80501 > Available via SameTime Connect within Philips, caesupport2 on AIM > "There are some who call me Tim?" > > > > > > > > > > Mike Miller <[EMAIL PROTECTED]> > Sent by: > [EMAIL PROTECTED] > 12/04/02 12:49 PM > > > To: David Howe <[EMAIL PROTECTED]> > cc: [EMAIL PROTECTED] > (bcc: Tim Conway/LMT/SC/PHILIPS) > Subject:RE: "A VNC server is already running as :10", but it isn't! > Classification: > > > > On Wed, 4 Dec 2002, David Howe wrote: > > > Possibly the .pid file (that vncserver checks to see if a instance is > > already running) is still in the user's ~/.vnc? > > > No. It's perplexing. There is no sign of a pid file and vncserver -kill > :10 won't work because it can't find the pid! I don't know why Xvnc > thinks something is running on :10. > > Some of you made the helpful suggestion that /tmp/.X11-unix/ is causing > the problem. Maybe so, but I don't see evidence of that. The same user > was able to run :11 and create the X11 lock file in the /tmp/.X11-unix/ > directory. There is no X10 file in that directory. > > Subsequently, I have gotten users running :12, :13, :14, and all of them > have the same group/user permissions as the user who couldn't run on :10. > It was only 10 that had a problem, not 9, 11, etc.!! Strange. > > Mike > > -- > Michael B. Miller, Ph.D. > Assistant Professor > Division of Epidemiology > University of Minnesota > http://taxa.epi.umn.edu/~mbmiller/ > ___ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list > ___ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
On Wed, 11 Dec 2002 [EMAIL PROTECTED] wrote: > I'd assumed that there weren't any operating systems vulverable to "dead > socket"s, but that sure sounds like what you've got. A socket isn't > closed properly when a program exits, and the IP stack doesn't make it > available. Only cure - reboot (or stop/restart stack, on really old > systems with add-on IP stacks). It's on Solaris 8. We now believe the problem is caused by ssh-X11 port forwarding occupying port 6010. Port 6010 (DISPLAY :10) is the first used by ssh. Mike > On Wed, 4 Dec 2002, David Howe wrote: > > > Possibly the .pid file (that vncserver checks to see if a instance is > > already running) is still in the user's ~/.vnc? > > > No. It's perplexing. There is no sign of a pid file and vncserver -kill > :10 won't work because it can't find the pid! I don't know why Xvnc > thinks something is running on :10. > > Some of you made the helpful suggestion that /tmp/.X11-unix/ is causing > the problem. Maybe so, but I don't see evidence of that. The same user > was able to run :11 and create the X11 lock file in the /tmp/.X11-unix/ > directory. There is no X10 file in that directory. > > Subsequently, I have gotten users running :12, :13, :14, and all of them > have the same group/user permissions as the user who couldn't run on :10. > It was only 10 that had a problem, not 9, 11, etc.!! Strange. > > Mike ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
I'd assumed that there weren't any operating systems vulverable to "dead
socket"s, but that sure sounds like what you've got. A socket isn't
closed properly when a program exits, and the IP stack doesn't make it
available. Only cure - reboot (or stop/restart stack, on really old
systems with add-on IP stacks).
Tim Conway
[EMAIL PROTECTED] reorder name and reverse domain
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me Tim?"
Mike Miller <[EMAIL PROTECTED]>
Sent by:
[EMAIL PROTECTED]
12/04/02 12:49 PM
To: David Howe <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
(bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: RE: "A VNC server is already running as :10", but it isn't!
Classification:
On Wed, 4 Dec 2002, David Howe wrote:
> Possibly the .pid file (that vncserver checks to see if a instance is
> already running) is still in the user's ~/.vnc?
No. It's perplexing. There is no sign of a pid file and vncserver -kill
:10 won't work because it can't find the pid! I don't know why Xvnc
thinks something is running on :10.
Some of you made the helpful suggestion that /tmp/.X11-unix/ is causing
the problem. Maybe so, but I don't see evidence of that. The same user
was able to run :11 and create the X11 lock file in the /tmp/.X11-unix/
directory. There is no X10 file in that directory.
Subsequently, I have gotten users running :12, :13, :14, and all of them
have the same group/user permissions as the user who couldn't run on :10.
It was only 10 that had a problem, not 9, 11, etc.!! Strange.
Mike
--
Michael B. Miller, Ph.D.
Assistant Professor
Division of Epidemiology
University of Minnesota
http://taxa.epi.umn.edu/~mbmiller/
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
On Thu, 5 Dec 2002, David Howe wrote: > Is it possible a non-vnc x-server is running on 10? or that port 5910 is > in use by some other app? It looks like something is running on 6010, and that must be the problem. Thanks to Corni Beerse for pointing it out! Now to figure out what's using 6010!! Many thanks to everyone, especially Corni Beerse, for helping me figure this out! Mike -- Michael B. Miller, Ph.D. Assistant Professor Division of Epidemiology University of Minnesota http://taxa.epi.umn.edu/~mbmiller/ ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
Is it possible a non-vnc x-server is running on 10? or that port 5910 is in use by some other app? ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
On Wed, 4 Dec 2002, David Howe wrote: > Possibly the .pid file (that vncserver checks to see if a instance is > already running) is still in the user's ~/.vnc? No. It's perplexing. There is no sign of a pid file and vncserver -kill :10 won't work because it can't find the pid! I don't know why Xvnc thinks something is running on :10. Some of you made the helpful suggestion that /tmp/.X11-unix/ is causing the problem. Maybe so, but I don't see evidence of that. The same user was able to run :11 and create the X11 lock file in the /tmp/.X11-unix/ directory. There is no X10 file in that directory. Subsequently, I have gotten users running :12, :13, :14, and all of them have the same group/user permissions as the user who couldn't run on :10. It was only 10 that had a problem, not 9, 11, etc.!! Strange. Mike -- Michael B. Miller, Ph.D. Assistant Professor Division of Epidemiology University of Minnesota http://taxa.epi.umn.edu/~mbmiller/ ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
Possibly the .pid file (that vncserver checks to see if a instance is already running) is still in the user's ~/.vnc? ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
Yes it does, The other thing that can be tried is, if you have root access run a ps -ef | grep vnc and kill the process on 10. Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of William Hooper Sent: Tuesday, December 03, 2002 2:34 PM To: 'VNC List' Subject: RE: "A VNC server is already running as :10", but it isn't! > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Miller > I'm still using old Xvnc version 3.3, running on Solaris 8. > I set up VNC > for a student and had him start it up on :10. It prompted > for password, > which he entered, then I had him run vncserver :10 again to > create the VNC > session. It refused saying "A VNC server is already running > as :10", but > it was lying! ;-) There is no server on :10. Then I had him > run one on > :11, and it worked without a problem. I've had him try, > hours later, to > start one on :10, but it won't work -- same error message. > > Any tips? Would an upgrade be a good idea? > > Mike > Doesn't VNC start the session you requested after you set the password (you don't need to run it a second time)? Are you sure that there isn't a server running on :10? Have you tried to connect to it with a viewer? It might be useful to look for logs and PID files in the ~/.vnc directory. Does Solaris have a "netstat -a" that can show you if a port has a program listening on port 5910? -- William Hooper ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: 'A VNC server is already running as :10', but it isn't!
I see this all the time on my Linux box when I reboot the computer without running a "vncserver -kill :10". It usually complains that there is a .pid file not in ~/.vnc but in "/tmp/.X11/" or something like that. Deleting the appropriate lock file fixes the problem. Greg > On Tue, 3 Dec 2002, William Hooper wrote: >> Are you sure that there isn't a server running on :10? > > Yes. Using appropriate 'ps' commands I can see all of the other vnc processes, > but there isn't one for :10. ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
On Tue, 3 Dec 2002, William Hooper wrote: > Doesn't VNC start the session you requested after you set the password > (you don't need to run it a second time)? No, you do have to run it a second time, at least with Xvnc 3.3. > Are you sure that there isn't a server running on :10? Yes. Using appropriate 'ps' commands I can see all of the other vnc processes, but there isn't one for :10. > Have you tried to connect to it with a viewer? Not until you suggested it (because it isn't running ;-), but I did just try it and it responds as if there is nothing running on :10 (it does not prompt for a password and a pop-up box says "Failed to connect to server"). > It might be useful to look for logs and PID files in the ~/.vnc > directory. I had done that. There is no log for :10. When I try to kill :10, it tells me it doesn't know the PID, of course, so it fails. > Does Solaris have a "netstat -a" that can show you if a port has a > program listening on port 5910? Good idea. Yes, it does. I looked and I found nothing on 5910. So it's still a mystery. Thanks for your efforts. You had some good ideas and I really appreciate your help. Mike -- Michael B. Miller, Ph.D. Assistant Professor Division of Epidemiology University of Minnesota http://taxa.epi.umn.edu/~mbmiller/ > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Miller > > I'm still using old Xvnc version 3.3, running on Solaris 8. I set up > > VNC for a student and had him start it up on :10. It prompted for > > password, which he entered, then I had him run vncserver :10 again to > > create the VNC session. It refused saying "A VNC server is already > > running as :10", but it was lying! ;-) There is no server on :10. > > Then I had him run one on :11, and it worked without a problem. I've > > had him try, hours later, to start one on :10, but it won't work -- > > same error message. > > > > Any tips? Would an upgrade be a good idea? > > > > Mike ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
RE: "A VNC server is already running as :10", but it isn't!
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Miller > I'm still using old Xvnc version 3.3, running on Solaris 8. > I set up VNC > for a student and had him start it up on :10. It prompted > for password, > which he entered, then I had him run vncserver :10 again to > create the VNC > session. It refused saying "A VNC server is already running > as :10", but > it was lying! ;-) There is no server on :10. Then I had him > run one on > :11, and it worked without a problem. I've had him try, > hours later, to > start one on :10, but it won't work -- same error message. > > Any tips? Would an upgrade be a good idea? > > Mike > Doesn't VNC start the session you requested after you set the password (you don't need to run it a second time)? Are you sure that there isn't a server running on :10? Have you tried to connect to it with a viewer? It might be useful to look for logs and PID files in the ~/.vnc directory. Does Solaris have a "netstat -a" that can show you if a port has a program listening on port 5910? -- William Hooper ___ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
