Linux deploy vnc fail

Linux deploy vnc fail

Для функционирования программы необходимы права root пользователя.

Это приложение с открытым исходным кодом, предназначенное для автоматизации процесса установки, конфигурирования и запуска GNU/Linux дистрибутивов на платформе Android внутри контейнера chroot. Приложение создает образ диска на карте памяти или ином носителе, монтирует его и устанавливает туда выбранный Linux-дистрибутив. Поддерживается установка в файл, прямо на раздел карты памяти, в директорию с файловой системой ext2/ext3/ext4 и в оперативную память. Приложения из Linux-дистрибутива запускаются в chroot окружении, работают параллельно с основной системой и сопоставимы с ней по скорости. Все вносимые изменения на устройстве обратимы, т.е. приложение и созданные им компоненты можно полностью удалить. Установка Linux-дистрибутива осуществляется по сети с официальных зеркал в интернете. Поскольку работа Linux Deploy базируется на системном вызове ядра Linux, то в роли «гостевых» систем могут выступать только дистрибутивы Linux. Через интерфейс программы можно управлять процессом установки Linux-дистрибутива, а после установки можно запускать и останавливать сервисы установленной системы (есть поддержка запуска собственных сценариев). Процесс установки отображается в виде текстовых отчетов в главном окне приложения. Во время установки программа сама настраивает рабочее окружение, которое включает в себя базовую систему, сервер SSH, сервер VNC и графическую среду на выбор. Также через интерфейс программы можно управлять параметрами серверов SSH и VNC. Установка Linux-дистрибутива занимает около 30 минут. Рекомендованный минимальный размер образа диска без графического интерфейса — 512 МБ, а с графическим интерфейсом — 1024 МБ (для LXDE). После начальной установки пароль для доступа по SSH и VNC назначается как «changeme», который можно сменить стандартными средствами дистрибутива, либо через параметры приложения.

Характеристики:
Поддерживаемые дистрибутивы: Debian, Ubuntu, Kali Linux, Arch Linux, Fedora, CentOS, Gentoo, Slackware, RootFS (tgz, tbz2, txz)
Тип установки: файл, раздел, оперативная память, директория
Поддерживаемые файловые системы: ext2, ext3, ext4
Поддерживаемые архитектуры: ARM, ARM64, x86, x86_64, режим эмуляции архитектуры (ARM x86)
Способы подключения к контейнеру: CLI, SSH, VNC, X-сервер, фреймбуфер
Интерфейсы управления (CLI): Android-терминал (или adb), telnet, веб-интерфейс (терминал через браузер)
Окружение рабочего стола: XTerm, LXDE, Xfce, MATE, другое (ручная настройка)
Поддерживаемые языки: мультиязычный интерфейс

ВНИМАНИЕ!
Эта программа поставляется БЕЗ ВСЯКИХ ГАРАНТИЙ, а автор не несет ответственности за любые возможные последствия ее использования. Это свободное программное обеспечение, и вы можете распространять его согласно правилам лицензии GPLv3.

Источник

Fail to start services #129

Comments

marhazk commented Jun 27, 2014

any idea why my rooted android with kali installed on linux deploy app failed to start the services such as VNC and ssh?

Tablet : Galaxy Tab 2 (GT-P3100, rooted)
Kernel: 4.1.2 (currently compatible with my country network for this device)
App : Linux Deploy (latest version)
Mount: Kali Linux (latest version)

The result shown below:

begin: start
Mounting partitions:
/ . done
/proc . done
/sys . done
/sys/fs/selinux . skip
/dev/pts . done
/dev/shm . done
Updating configuration:
dns . done
mtab . done
Starting services:
SSH : 22 . fail
VNC : 5900 . fail

The text was updated successfully, but these errors were encountered:

marhazk commented Jun 29, 2014

nvm, problem solved.

solution: it’s because i «Reconfigure»-ed, not the «Install». Install works fine than reconfigure

CriticalMinds commented Mar 11, 2015

Hi bro !!
I’m having the same issue can you tell me more on what did you do to fix the issue
you mean you reconfigured then pressed install again ?
thanks in advance !!

MrFlipper commented Mar 30, 2015

@CriticalMinds just wondering if youve gotten yours working yet, im having the same problem. ive tried both reconfigure and install, neither worked for me.

MN-dev commented Apr 24, 2015

problem woth ports

] SSH :22 . fail
[19:28:55] VNC :5900 . fail
[19:28:56] >> begin: start
[19:29:43] Mounting partitions:
[19:29:43] / . skip
[19:29:43] /proc . skip
[19:29:43] /sys . skip
[19:29:43] /sys/fs/selinux . skip
[19:29:43] /dev . skip
[19:29:43] /dev/pts . skip
[19:29:43] /dev/shm . skip
[19:29:43] /proc/sys/fs/binfmt_misc . skip
[19:29:43] Updating configuration:
[19:29:43] dns . done
[19:29:43] mtab . done
[19:29:43] Starting services:
[19:29:43] SSH :22 . fail
[19:30:23] VNC :5900 . fail
[19:30:24]

MN-dev commented Apr 24, 2015

off the
SSH :22
+
VNC :5900
from setting

samtax01 commented Apr 25, 2015

please any help tooo, I have galaxy-tab p5100 and cannot start ssh or vnc in linux deploy. any solution

sahruldotid commented Sep 6, 2015

Same Issue, I have Asus Zenfone 4 & cant start VNC & SSH, I try using Complete Linux Installer but «init.sh» no such file or directory

HumanityWatcher commented Oct 23, 2015

Did anyone managed to fix this? I have Samsung Galaxy Tab S 10.5. SSH service is ok, but VNC is not. how can I fix this??

reddyes commented Nov 4, 2015

I’m with same problem , please help!

unknown011 commented Nov 11, 2015

Me too ssh and vnc fail please help ke .

o0oke commented Feb 25, 2016

same issue today on the phoenixOS 1.0 on Grouper

o0oke commented Feb 26, 2016

FYI, Finally I fixed the issue by switched to a new source «Distribution suite» like «stable» and also update a new «Mirror URL» address, reconfig and reinstall again.

AFranzo commented Mar 1, 2016

what did you change? please write it because my distribution is only sana or kali-rolling aand i don’t see »stabe»

o0oke commented Mar 2, 2016

Hi IIranz,
Please check Debian stable version on the ‘Mirror URL’ address: http://ftp.cn.debian.org/debian/

yelhamer commented Mar 2, 2016

i think the problem is something with apt, because when the system is installed it needs to install an ssh & vnc client to start these servers, what i’ve noticed is that on ubuntu it downloads some packages and do an automatic apt-get update && upgrade. while kali goes directly like this: intsall the os, and thats it

AFranzo commented Mar 3, 2016

I have to install kali linux not debian.

Darkowlz commented Mar 29, 2016

[23:51:42] Updating configuration file . done
[23:51:42] >>> start
[23:51:42] Mounting partitions:
[23:51:42] / . skip
[23:51:42] /proc . skip
[23:51:42] /sys . skip
[23:51:42] /sys/fs/selinux . skip
[23:51:42] /dev . skip
[23:51:42] /dev/tty . skip
[23:51:42] /dev/pts . skip
[23:51:42] /dev/shm . skip
[23:51:42] /proc/sys/fs/binfmt_misc . skip
[23:51:42] Configuring the container:
[23:51:42] dns . done
[23:51:42] mtab . done
[23:51:42] Starting services:
[23:51:42] SSH [:22] . ls: /data/local/linux/etc/ssh/: No such file or directory
[23:51:42] chroot: can’t execute ‘/bin/su’: No such file or directory
[23:51:42] chroot: can’t execute ‘/bin/su’: No such file or directory
[23:51:42] fail
[23:51:42] VNC [:5900] . chroot: can’t execute ‘/bin/su’: No such file or directory
[23:51:42] chroot: can’t execute ‘/bin/su’: No such file or directory
[23:51:42] fail
[23:51:42]

rahul-1903 commented Aug 21, 2016

I am getting this issue. Can anyone help
problem woth ports
] SSH :22 . fail
[19:28:55] VNC :5900 . fail
[19:28:56] >> begin: start
[19:29:43] Mounting partitions:
[19:29:43] / . skip
[19:29:43] /proc . skip
[19:29:43] /sys . skip
[19:29:43] /sys/fs/selinux . skip
[19:29:43] /dev . skip
[19:29:43] /dev/pts . skip
[19:29:43] /dev/shm . skip
[19:29:43] /proc/sys/fs/binfmt_misc . skip
[19:29:43] Updating configuration:
[19:29:43] dns . done
[19:29:43] mtab . done
[19:29:43] Starting services:
[19:29:43] SSH :22 . fail
[19:30:23] VNC :5900 . fail
[19:30:24]

Angry-br commented Sep 5, 2016

Hi Guys i’m new on this blog, but i’ve learned something about linux deploy.
After de instalation finish by nothing press start, go to properties again then click on reconfigure .
This will solve this «skips answers» but on my case the only thing that not got solve with this way is the VNC, it stills answer fail. and i didnt find the way to conf. the vnc connection to stop this issue.
May someone help me.

Источник

DNS, MTAB, SSH, and VNC all fail #374

Comments

Steveor commented Jan 5, 2016

I have been attempting to load Debian and/or Kali on my Samsung Tab 4 and trying various versions of Linux Deploy and BusyBox with no success. In my latest attempt DNS, MTAB, SSH, and VNC all fail. I wouldn’t be surprised if I left out something obvious but I have done so many iterations of directories, settings and preferences that my memory of all that I have done to this point is a blur.

My log is below. Any assistance in moving my efforts forward would be greatly appreciated.

Updating configuration file . done

status
Linux Deploy version: 1.5.3-174
Device: SM-T230
Android: 4.4.2
Architecture: armv7l
Kernel: 3.10.0-4357157
Memory: 55/1319 MB
Swap: 0/0 MB
SELinux: yes
Loop devices: yes
Support binfmt_misc: no
Supported FS: cramfs exfat ext2 ext3 ext4 fuseblk msdos vfat
Mounted system: unknown
Running services:

• SSH: no
• GUI: no
  Mounted parts on Linux:
• /
• /proc
• /sys
• /sys/fs/selinux
• /dev
• /dev/pts
• /dev/shm
  Available mount points:
• /system: 1.4/2.0 GB (ext4)
• /cache: 0.2/0.2 GB (ext4)
• /data: 2.5/4.7 GB (ext4)
• /data/sdext2: 0.4/6.8 GB (ext2)
• /efs: 0.0/0.0 GB (ext4)
• /NVM: 0.0/0.0 GB (ext4)
• /mnt/shell/emulated: 2.4/4.7 GB (sdcardfs)
• /storage/emulated/0: 2.4/4.7 GB (sdcardfs)
• /storage/emulated/0/Android/obb: 2.4/4.7 GB (sdcardfs)
• /storage/emulated/legacy: 2.4/4.7 GB (sdcardfs)
• /storage/emulated/legacy/Android/obb: 2.4/4.7 GB (sdcardfs)
• /mnt/media_rw/extSdCard: 0.5/0.5 GB (vfat)
• /mnt/secure/asec: 0.5/0.5 GB (vfat)
• /storage/extSdCard: 0.5/0.5 GB (sdcardfs)
  Available partitions:
  fdisk: can’t open ‘/dev/block/loop0’
  fdisk: can’t open ‘/dev/block/loop1’
  fdisk: can’t open ‘/dev/block/loop2’
  fdisk: can’t open ‘/dev/block/loop3’
  fdisk: can’t open ‘/dev/block/loop4’
  fdisk: can’t open ‘/dev/block/loop5’
  fdisk: can’t open ‘/dev/block/loop6’
  fdisk: can’t open ‘/dev/block/loop7’
• /dev/block/mmcblk1p1: 540 MB (Win95 FAT32 (LBA))
• /dev/block/mmcblk1p2: 7407 MB (Linux)
  Configuration file:
  DEBUG_MODE=»y»
  TRACE_MODE=»n»
  MNT_TARGET=»/data/local/linux»
  IMG_TARGET=»/storage/emulator/0/linux.img»
  IMG_SIZE=»0″
  FS_TYPE=»ext2″
  DEPLOY_TYPE=»file»
  DISTRIB=»kalilinux»
  ARCH=»armhf»
  SUITE=»sana»
  MIRROR=»http://http.kali.org/kali/»
  USER_NAME=»android»
  USER_PASSWORD=»changeme»
  SERVER_DNS=»»
  LOCALE=»en_US.UTF-8″
  DESKTOP_ENV=»xfce»
  USE_COMPONENTS=»desktop xserver vnc ssh»
  STARTUP=»ssh vnc»
  CUSTOM_SCRIPTS=»»
  CUSTOM_MOUNTS=»»
  SSH_PORT=»22″
  VNC_DISPLAY=»0″
  VNC_DEPTH=»16″
  VNC_DPI=»75″
  VNC_GEOMETRY=»1280×800″
  VNC_ARGS=»»
  XSERVER_DISPLAY=»0″
  XSERVER_HOST=»127.0.0.1″
  FB_DISPLAY=»0″
  FB_DPI=»100″
  FB_DEV=»/dev/graphics/fb0″
  FB_INPUT=»/dev/input/event2″
  FB_ARGS=»»
  FB_FREEZE=»none»

The text was updated successfully, but these errors were encountered:

FoxERM commented Jan 5, 2016

Do your kernel supports Loop Device?

Steveor commented Jan 5, 2016

It appears the kernel supports Loop since the status/log info above reads: «Loop devices: yes.» Is this a safe assumption? If not, how else would I confirm this?

scndthe2nd commented Jan 6, 2016

What rom are you using? I didn’t have any luck on my note 3 until I
switched to cm12.1.

Is symlink still a thing? I remember toggling that a lot.

Start off by using a 4 g img file with arch and lxfe/lxce. After thats
confirmed working, then try other stuff.

On Tue, Jan 5, 2016, 3:01 PM Steveor notifications@github.com wrote:

It appears the kernel supports Loop since the status/log info above reads:
«Loop devices: yes.» Is this a safe assumption? If not, how else would I
confirm this?

—
Reply to this email directly or view it on GitHub
#374 (comment).

Steveor commented Jan 7, 2016

Now I’m back to square one. When I start I get the following:

Mounting partitions:
/ . fail
mount: mounting /storage/extSdCard/linux.img on /data/local/linux failed: No such file or directory

The above path is to a 4 GB Sourceforge Kali basic image on my ext2 partition of my external SD card. I have also done dozens of different iterations of settings and preferences, read dozens of forum posts but can’t get this to work. I was able to get the aforementioned image working through the Complete Linux Installer app but I couldnt solve a VNC gray screen issue. I have a feeling I’m making a very basic mistake but dont know enough to recognize it.

On the plus side I’ve learned alot about Linux command line and file structure this past week or so.

scndthe2nd commented Jan 7, 2016

oh, youre using the wrong ui. use a different desktop environment

On Thu, Jan 7, 2016, 5:34 PM Steveor notifications@github.com wrote:

Now I’m back to square one. When I start I get the following:

/ . fail
mount: mounting /storage/extSdCard/linux.img on /data/local/linux failed:
No such file or directory

The above path is to a 4 GB Sourceforge Kali basic image on my ext2
partition of my external SD card. I have also done dozens of different
iterations of settings and preferences, read dozens of forum posts but
can’t get this to work. I was able to get the aforementioned image working
through the Complete Linux Installer app but I couldnt solve a VNC gray
screen issue. I have a feeling I’m making a very basic mistake but dont
know enough to recognize it.

On the plus side I’ve learned alot about Linux command line and file
structure this past week or so.

—
Reply to this email directly or view it on GitHub
#374 (comment).

Steveor commented Jan 7, 2016

I had it initially set to LXDE. But then I cycled through all of them and got the same results.

My output:
Mounting partitions:

• / . mount_part root
• msg -n / .
• echo -n / .
• grep -c /data/local/linux /proc/mounts
• local is_mnt=0
• [ 0 -eq 0 ]
• [ -d /data/local/linux ]
• [ -d /storage/extSdCard/linux.img ]
• local mnt_opts=rw,relatime
• mount -o rw,relatime /storage/extSdCard/linux.img /data/local/linux
• mount: mounting /storage/extSdCard/linux.img on /data/local/linux failed: No such file or directory

I was trying to understand the coding where the error occurs but I’m not a programmer. The hiccup seems to occur on the lines in bold below. I vaguely understand the mounting process. What could cause the error?

mount_part()
<
case «$1» in
root)
msg -n «/ . »
local is_mnt=$(grep -c » $ » /proc/mounts)
if [ «$» -eq 0 ]; then
[ -d «$» ] || mkdir -p $
[ -d «$» ] && local mnt_opts=»bind» || local mnt_opts=»rw,relatime»
mount -o $ $ $
[ $? -eq 0 ] && msg «done» ||
else
msg «skip»
fi
;;

meefik commented Jan 8, 2016

If you’re using SuperSU, you can try to disable the «separate mount namesace» option in SuperSU.

Steveor commented Jan 8, 2016

Did that and received the same result. After disabling «separate mount namespace» I had to reboot and neglected to remount my external SD card. So now I’ve successfully mounted and moved the ball forward. I have a password error but I’ll attempt to figure that out on my own.

What exactly happens when my image target is mounted to the mount target? And what does mnt_opts=»bind» do? What does separate mount namespace do?

Steveor commented Jan 8, 2016

I used a back-asswards way to accomplish the installation but it worked. For the sake of other noobs and to document my process in the event I need to retrace my path, I did the following:

Instead of using the application to download the image I got mine, kalilinux.BASIC.ext4.20131012.zip, from the following link: http://sourceforge.net/projects/linuxonandroid/files/Kali%20Linux/. I formatted my 16GB SD card with Gparted with a 512MB Fat32 partition and a second 14GB ext2 partition that has the following path on my device: /storage/extSdCard. I placed the the unzipped image and renamed it linux.img. In my Android terminal emulator I mounted the SD card with the following command: mount -t ext2 /dev/block/mmcblk1p2 /storage/extSdCard.

It is at this stage that I was unable to get the partitions to mount. Then per Mr. Skshidlevsky’s advice above I disabled the «Mount namespace separation» option in the SuperSU settings on my Android device, rebooted, remounted the SD card in my terminal emulator and voilà, I was able to open Kali via SSH and VNC. The only hitch through VNC was I had to use the password «kalilinux» instead of «toor» or «changeme» which I learned from this post: http://forum.xda-developers.com/showpost.php?p=51705302&postcount=1993 .

My Linux Deploy configuration:

Linux Deploy version: 1.5.3-174
Device: SM-T230
Android: 4.4.2
Architecture: armv7l
Kernel: 3.10.0-4357157
Memory: 48/1319 MB
Swap: 0/0 MB
SELinux: yes
Loop devices: yes
Support binfmt_misc: no
Supported FS: cramfs exfat ext2 ext3 ext4 fuseblk msdos vfat
Mounted system: Kali GNU/Linux 1.0
Running services:

Источник