I have one machine (out of a couple dozen) that continues to refuse to
allow “vncserver :1” to start. It is perfectly happy with :2 - :9 but
tells me :1 is already running - yet ps tells me that there is no running
Xvnc instance.
What have I done here and how do I get that session back? I’ve cleared
the /tmp/.X11-unix entries but that did no good. Could I have checked
something in Yast that is launching an invisible session? It’s just a
nuisance but I hate unexplained things like this on just one machine.
Did you check to see if the port is already listening?
netstat -planet
Look for :5901
Good luck.
On 05/24/2010 01:01 AM, Will Honea wrote:
> I have one machine (out of a couple dozen) that continues to refuse to
> allow “vncserver :1” to start. It is perfectly happy with :2 - :9 but
> tells me :1 is already running - yet ps tells me that there is no running
> Xvnc instance.
>
> What have I done here and how do I get that session back? I’ve cleared
> the /tmp/.X11-unix entries but that did no good. Could I have checked
> something in Yast that is launching an invisible session? It’s just a
> nuisance but I hate unexplained things like this on just one machine.
>
> -
> Will Honea
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> If you enabled Yast → network services → remote administration, then
> server:1 will run constantly via xinetd
Rechecked - remote admin is NOT enabled in Yast.
For the other reply,
code<
will@grbc-server:~> netstat -planet | grep 590
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN 0 8855 -
tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN 1000 18649244 22573/Xvnc
As I read this, the port is listening but has no app has it bound. Am I
correct in assuming this makes it effectively a zombie? Or is it waiting to
bite me in the butt?
I’m reasonably certain this is a left-over from the original setup on the
machine where I had several problems. I did initially have remote admin
enabled but disabled it since I saw no immediate use for it after checking
it out. Given the initial instability of the system, I wouldn’t be
surprised if the session were a leftover from a panic abort.
Question is, where do I go with my big hammer to kill it??
No, you do not have rights to figure out which app is using that port,
probably because as swerdna mentioned it is xinetd. Become root and use
the same command and you should see the app.
Good luck.
On 05/25/2010 01:42 PM, Will Honea wrote:
> swerdna wrote:
>
>>
>> If you enabled Yast → network services → remote administration, then
>> server:1 will run constantly via xinetd
>
> Rechecked - remote admin is NOT enabled in Yast.
>
> For the other reply,
>
> code<
> ---------------------------------
> will@grbc-server:~> netstat -planet | grep 590
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN 0 8855 -
> tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN 1000 18649244 22573/Xvnc
> ---------------------------------
>
> As I read this, the port is listening but has no app has it bound. Am I
> correct in assuming this makes it effectively a zombie? Or is it waiting to
> bite me in the butt?
>
> I’m reasonably certain this is a left-over from the original setup on the
> machine where I had several problems. I did initially have remote admin
> enabled but disabled it since I saw no immediate use for it after checking
> it out. Given the initial instability of the system, I wouldn’t be
> surprised if the session were a leftover from a panic abort.
>
> Question is, where do I go with my big hammer to kill it??
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/