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]#
LVL 2
smetterdAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
smetterdAuthor Commented:
Thanks Wesly that did it!!

/usr/bin/vncserver

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.