VNC Error #2
Comments
|
It works fine on boot2docker.
How did you start it ?
docker run --name=nicotine -v /Users/Music/:/home/nicotine/Music -v /Users/Downloads:/home/nicotine/Downloads -p 5900:5900 -d danielguerra/nicotine
What is the platform you are running on?
When you do 'docker ps -a’ do you see any port 5900 running on your machine.
Maybe try -p 5910:5900 instead …
… On 24 Jan 2017, at 04:28, TuRDMaN ***@***.***> wrote:
I've tried both this and your Nicotine dockers, and they end up giving me the same error. Everything starts up okay, but then VNC keeps erroring out and restarting.
2017-01-23 21:52:32,383 INFO spawned: 'x11vnc' with pid 833 2017-01-23 21:52:39,621 INFO supervisord started with pid 5 2017-01-23 21:52:41,155 INFO spawned: 'xvfb' with pid 8 2017-01-23 21:52:41,160 INFO spawned: 'openbox' with pid 9 2017-01-23 21:52:41,169 INFO spawned: 'x11vnc' with pid 10 2017-01-23 21:52:41,247 INFO spawned: 'soulseek' with pid 11 2017-01-23 21:52:42,293 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-01-23 21:52:42,293 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-01-23 21:52:42,293 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-01-23 21:52:42,293 INFO success: soulseek entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-01-23 21:52:43,970 INFO exited: soulseek (exit status 126; not expected) 2017-01-23 21:52:44,638 INFO spawned: 'soulseek' with pid 40 2017-01-23 21:52:44,649 INFO exited: xvfb (exit status 1; not expected) 2017-01-23 21:52:44,674 INFO spawned: 'xvfb' with pid 41 2017-01-23 21:52:44,698 INFO exited: x11vnc (exit status 1; not expected) 2017-01-23 21:52:44,744 INFO spawned: 'x11vnc' with pid 43 2017-01-23 21:52:45,017 INFO exited: soulseek (exit status 126; not expected) 2017-01-23 21:52:46,018 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-01-23 21:52:46,019 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-01-23 21:52:46,020 INFO spawned: 'soulseek' with pid 73 2017-01-23 21:52:46,112 INFO exited: soulseek (exit status 126; not expected) 2017-01-23 21:52:48,739 INFO spawned: 'soulseek' with pid 103 2017-01-23 21:52:48,893 INFO exited: soulseek (exit status 126; not expected) 2017-01-23 21:52:49,474 INFO exited: x11vnc (exit status 2; expected) 2017-01-23 21:52:50,478 INFO spawned: 'x11vnc' with pid 132 2017-01-23 21:52:52,259 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-01-23 21:52:52,263 INFO spawned: 'soulseek' with pid 133 2017-01-23 21:52:52,326 INFO exited: x11vnc (exit status 2; expected) 2017-01-23 21:52:52,328 INFO spawned: 'x11vnc' with pid 160 2017-01-23 21:52:52,340 INFO exited: soulseek (exit status 126; not expected) 2017-01-23 21:52:52,372 INFO gave up: soulseek entered FATAL state, too many start retries too quickly 2017-01-23 21:52:54,221 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-01-23 21:52:55,473 INFO exited: x11vnc (exit status 2; expected)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#2>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALzmMklKM5WztnrQHpZMqkfuKeCpgfi8ks5rVW_ygaJpZM4Lr0x9>.
|
|
I am doing this on my UnRAID box. I have many docker containers running, but I made sure to use a port that's not in use by anything else. I was trying to get it to run through my VPN container (using the same configuration as a bunch of other dockers I have running). I just now tried using the run command that you gave. Using your options, everything boots fine and seems to work, but whenever I attempt to connect with a VNC client, the VNC server crashes. 2017-01-25 21:56:44,889 INFO supervisord started with pid 1 |
|
Your vnc server doesn’t stay up. When your container is running do this.
docker exec -ti <containerid> /bin/bash
cd /tmp
ls -al
Look in the x11vnc logs the size will tell wich file you want to see.
Supervisor creates these logs
Can you run any other vnc server?
For instance ..
https://hub.docker.com/r/kaixhin/vnc/
… On 25 Jan 2017, at 23:06, TuRDMaN ***@***.***> wrote:
I was trying to get it to run through my VPN container (using the same configuration as a bunch of other dockers I have running).
I just now tried using the run command that you gave. Using your options, everything boots fine and seems to work, but whenever I attempt to connect with a VNC client, the VNC server crashes.
2017-01-25 21:56:44,889 INFO supervisord started with pid 1
2017-01-25 21:56:46,396 INFO spawned: 'xvfb' with pid 7
2017-01-25 21:56:46,398 INFO spawned: 'openbox' with pid 8
2017-01-25 21:56:46,760 INFO spawned: 'nicotine' with pid 9
2017-01-25 21:56:46,763 INFO spawned: 'x11vnc' with pid 10
2017-01-25 21:56:47,764 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-25 21:56:47,765 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-25 21:56:47,766 INFO success: nicotine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-25 21:56:47,767 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-25 21:56:53,447 INFO exited: x11vnc (exit status 1; not expected)
2017-01-25 21:56:54,289 INFO spawned: 'x11vnc' with pid 12
2017-01-25 21:56:55,621 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-25 21:57:39,428 CRIT reaped unknown pid 33)
2017-01-25 21:57:59,867 INFO exited: x11vnc (exit status 2; expected)
2017-01-25 21:58:00,877 INFO spawned: 'x11vnc' with pid 40
2017-01-25 21:58:01,901 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-25 21:58:09,529 INFO exited: x11vnc (exit status 2; expected)
2017-01-25 21:58:10,532 INFO spawned: 'x11vnc' with pid 42
2017-01-25 21:58:11,999 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-25 21:58:36,504 INFO exited: x11vnc (exit status 2; expected)
2017-01-25 21:58:37,510 INFO spawned: 'x11vnc' with pid 46
2017-01-25 21:58:38,511 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALzmMsDO4mBfY1kmKykS5cOEESnvLO25ks5rV8dwgaJpZM4Lr0x9>.
|
|
I have the same problem in a Synology NAS.
I have tested kaixhin/vnc container and works fine, but when I try to connect soulseek container, VNC client keeps trying to connect forever. @TuRDMaN has you find any solution? Anyway, @danielguerra69 , thanks for your work. |
|
@TuRDMaN have you find any fix for this ? |
I've tried both this and your Nicotine dockers, and they end up giving me the same error. Everything starts up okay, but then VNC keeps erroring out and restarting.
Edit: actually, nevermind, it's all the services that are restarting, not just VNC
2017-01-23 21:52:32,383 INFO spawned: 'x11vnc' with pid 833
2017-01-23 21:52:39,621 INFO supervisord started with pid 5
2017-01-23 21:52:41,155 INFO spawned: 'xvfb' with pid 8
2017-01-23 21:52:41,160 INFO spawned: 'openbox' with pid 9
2017-01-23 21:52:41,169 INFO spawned: 'x11vnc' with pid 10
2017-01-23 21:52:41,247 INFO spawned: 'soulseek' with pid 11
2017-01-23 21:52:42,293 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-23 21:52:42,293 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-23 21:52:42,293 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-23 21:52:42,293 INFO success: soulseek entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-23 21:52:43,970 INFO exited: soulseek (exit status 126; not expected)
2017-01-23 21:52:44,638 INFO spawned: 'soulseek' with pid 40
2017-01-23 21:52:44,649 INFO exited: xvfb (exit status 1; not expected)
2017-01-23 21:52:44,674 INFO spawned: 'xvfb' with pid 41
2017-01-23 21:52:44,698 INFO exited: x11vnc (exit status 1; not expected)
2017-01-23 21:52:44,744 INFO spawned: 'x11vnc' with pid 43
2017-01-23 21:52:45,017 INFO exited: soulseek (exit status 126; not expected)
2017-01-23 21:52:46,018 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-23 21:52:46,019 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-23 21:52:46,020 INFO spawned: 'soulseek' with pid 73
2017-01-23 21:52:46,112 INFO exited: soulseek (exit status 126; not expected)
2017-01-23 21:52:48,739 INFO spawned: 'soulseek' with pid 103
2017-01-23 21:52:48,893 INFO exited: soulseek (exit status 126; not expected)
2017-01-23 21:52:49,474 INFO exited: x11vnc (exit status 2; expected)
2017-01-23 21:52:50,478 INFO spawned: 'x11vnc' with pid 132
2017-01-23 21:52:52,259 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-23 21:52:52,263 INFO spawned: 'soulseek' with pid 133
2017-01-23 21:52:52,326 INFO exited: x11vnc (exit status 2; expected)
2017-01-23 21:52:52,328 INFO spawned: 'x11vnc' with pid 160
2017-01-23 21:52:52,340 INFO exited: soulseek (exit status 126; not expected)
2017-01-23 21:52:52,372 INFO gave up: soulseek entered FATAL state, too many start retries too quickly
2017-01-23 21:52:54,221 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-01-23 21:52:55,473 INFO exited: x11vnc (exit status 2; expected)
The text was updated successfully, but these errors were encountered: