Can no longer run tightvncviewer in most current Kali Light armhf image for rpi2/3
About a month ago, i loaded an SD card up with the kali-linux-light-2016.2-armhf.img image. I used a tutorial for installing tightvncserver. ( http://www.catonrug.net/2014/05/how-to- ... ry-pi.html )
I had absolutely no issues whatsoever. This image still works perfectly fine. I made a backup image of this using Win32DiskImager.
Last week i bought some more SD cards and tried to image my backup image to them. Unfortunately, the cards are not identical and have too many sectors on them to flash to my new cards, even though they are all 16GB. Either way, this is not the issue i am posting about. i know i can get around that at a later point, but it is not a worry to me rigth now. My issue is this:
I started from scratch using 2 images (one on each card)- kali-linux-light-2016.2-armhf.img and kali-2.1.2-rpi2.img (Kali Full image)
In both, i am having the same issue. Steps i've done are below:
with both images, ive imaged the SD card, modified cmdline.txt to assign static IP to pi. SSH into device, and follow tutorial from http://www.catonrug.net/2014/05/how-to- ... ry-pi.html.
After installing tightvncserver, i try to run tightvncserver, but am returned with "command not found".
After some googling i decided to run "vncviewer" and i am returned with :
Code:
Cleaning stale pidfile '/root/.vnc/kali:1.pid'!
New 'kali:1 (root)' desktop at :1 on machine kali
Starting applications specified in /etc/X11/Xvnc-session
Log file is /root/.vnc/kali:1.log
Use xtigervncviewer -SecurityTypes VncAuth -passwd /root/.vnc/passwd :1 to connect to the VNC server.
now, when i try to connect through my tightvncviewer on my win7x64 system, i am greeted with
"Error in TightVNC Ciewer: No connection could be made because the target machine actively refused it."
I had seen that error previously about a month ago when i was building the first (working) image, but fixed it quickly by adding :1 to the end of the IP of my kaliPi.
This is not working now.
Im not certain that these issues are connected, but i have tinkered with the use of :5901, ::5901, ;1, ::1, and ive also launched vncserver with other session IDs like :2, :5, :9, etc, and still cannot connect. I am at the point of being frustrated enough that i am turning to the forums for help.
I'd like to get back to using tightvncserver instead of vncserver or tigervncserver. Not sure why there is all of a asudden an issue running tightvncserver.
Please help!!! Thanks!
Solved: Can not run tightvncserver on amdhf image of raspberry pi 2
Quote:
Originally Posted by
Javier
Hi just to add to the issue. this is the full log output.
=================== tail -15 /root/.vnc/kali:1.log ===================
Xvnc TigerVNC 1.7.0 - built Jan 5 2017 22:35:23
Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt)
See
http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11900000, The X.Org Foundation
Fri Jan 27 23:15:34 2017
vncext: VNC extension running!
vncext: Listening for VNC connections on local interface(s), port 5901
vncext: created VNC server for screen 0
mesg: ttyname failed: Inappropriate ioctl for device
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
after 173 requests (173 known processed) with 0 events remaining.
Killing Xtigervnc process ID 897... which seems to be deadlocked. Using SIGKILL!
================================================== ====================
Starting applications specified in /etc/X11/Xvnc-session has failed.
I found that in my /etc/X11/Xvnc-session, the last line of the file was a vncserver -kill command.
I commented that out and my vncserver now works.
I suspect the exec command is returning after the server initializes and not blocking was desired by the script's author.
