Raju further reported that he was unable to start vncserver process and was getting errors:
$ perl /usr/local/bin/vncserver :55
New 'X' desktop is prod2039:55
Starting applications specified in /export/home/applmgr/.vnc/xstartup
Log file is /export/home/applmgr/.vnc/prod2039:55.log
$ cat /export/home/applmgr/.vnc/prod2039:55.log
_XSERVTransSocketCreateListener: failed to bind listener
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: failed to create listener for local
Fatal server error:
Failed to establish all listening sockets
xrdb: Connection refused
xrdb: Can't open display 'prod2039:55'
I did a truss perl /usr/local/bin/vncserver and found that it was unable to write to /tmp/.X11-unix
I logged in as root and changed the permissions of
chmod 777 /tmp/.X11-unix
It worked after that.
Sometimes when you are unable to start vnc on a specified port the reason is that the socket for that port is owned by some other user:
$ cd /tmp/.X11-unix
$ ls -ltr
srwxrwxrwx 1 root root 0 Nov 25 17:42 X0
The format is Xn where n is the port number. For example the file X0 for port 0, X1 for port 1.
You should login as that user and remove the /tmp/.X11-unix/Xn