Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 485
  • Last Modified:

Can't start vncserver. No error given.

It acts like it starts, but then it doesn't.

--------------
[root@webpro root]# /etc/init.d/vncserver start
Starting VNC server:                                       [  OK  ]
[root@webpro root]# /etc/init.d/vncserver status
Xvnc is stopped
[root@webpro root]#
0
smetterd
Asked:
smetterd
  • 5
  • 3
  • 2
1 Solution
 
smetterdAuthor Commented:
And according to /var/logs/messages everything is fine

---------------------------------
Mar 21 11:26:58 webpro vncserver: vncserver shutdown succeeded
Mar 21 11:26:58 webpro vncserver: vncserver startup succeeded
0
 
wesly_chenCommented:
Hi,

   Please check ~/.vnc/*.log for the error messages (post here).

   Also, check ~/.xsession-errors for Xwindow errors.

   What kind or Linux do you have? RedHat/Fedora, SuSE or Mandrake?

Regards,

Wesly
0
 
pablouruguayCommented:
do a ps -ef |grep vnc and see if is working
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
smetterdAuthor Commented:
There are no logs in the .vnc folder, only a passwd file.

Here's what's in the .xsession-errors
-----------------------------------
startkde: Starting up...
kbuildsycoca running...
mcop warning: user defined signal handler found for SIG_PIPE, overriding
klipper is already running!
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
*** kdesktop got signal 1 (Exiting)
kicker: sighandler called
KLauncher: Exiting on signal 1
X connection to :0.0 broken (explicit kill or server shutdown).
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
-----------------------------------

And the output from the command suggested by pablo is

-----------------------------------

[root@webpro root]# ps -ef |grep vnc
root      4021  3621  0 09:16 pts/1    00:00:00 grep vnc
[root@webpro root]#

-----------------------------------
0
 
pablouruguayCommented:
try to run mannualy  

[root@webpro root]# vncd
0
 
smetterdAuthor Commented:
[root@webpro root]# vncd
bash: vncd: command not found
[root@webpro root]# whereis vncd
vncd:
[root@webpro root]#

0
 
smetterdAuthor Commented:
[root@webpro root]# ps -ef |grep vnc
root     27464 27402  0 10:52 ttyp1    00:00:00 grep vnc
[root@webpro root]#

0
 
pablouruguayCommented:
locate vncd
0
 
wesly_chenCommented:
What kind or Linux do you have?
Could you just run
vncserver
0
 
smetterdAuthor Commented:
Thanks Wesly that did it!!

/usr/bin/vncserver

0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now