Can't telnet localhost 11100
-
Good morning everybody,
I use Veyon 4.5.2 on an ubuntu 18.04.03 LTS school lab. I face this issue: panel only shows if PC is up or down (gray, yellow).If I try to telnet both localhost or remote PCs port 11100 I get "connection refused".
I enabled debug log, but both teacher and student site nothing is logged at all.
If I netstat, I can't find veyon listening on any port: it seems died, even if systemctl claims it's alive.I can see SYN packets leaving the teacher side, but it never gets answers.
The lab was working, then at a certain moment all PCs stopped working together.
Software updates are administratively disabled.
I use local users and keypair authentication; keys are fine.Thanks for help!
Davide -
Hello Davide,
I just wanted to chime in here. I have the same problem using 20.04. I was installed using the PPA, but I installed the deb package for 4.5.3 to see if it was working. I got the same results with the new package.
On the teacher or master side, I see
2021-02-27T18:26:47.768: [DEBUG] VncConnection::rfbClientLogDebug(): 0x7f25c1ffb700 ConnectClientToTcpAddr6: connect 2021-02-27T18:26:47.768: [DEBUG] VncConnection::rfbClientLogDebug(): 0x7f25c1ffb700 Unable to connect to VNC serverThe student devices just say that the vnc server was started on 11100. No idea what is going on...
-
@davidemorellato There are two components involved: Veyon Service (which you can control and observe via systemctl) and Veyon Server. The Veyon Service is responsible for starting Veyon Server instances for user sessions (if multi session mode is enabled, one instance for each session is started, otherwise only for instance for the most-recently opened session is started and previous instances are stopped). So what seems to happen in your case is that either the Veyon Server instances are not started at all for some reason or crash during startup or normal operation.
For further troubleshooting, first please update to the latest version available in our PPA (4.5.3-2) which contains additional fixes regarding session management. If it does not help, set the log level in Veyon Configurator to Debug, reboot, login and paste the output of
/tmp/VeyonServ*.loghere so we can examine it in detail. -
@davidemorellato There are two components involved: Veyon Service (which you can control and observe via systemctl) and Veyon Server. The Veyon Service is responsible for starting Veyon Server instances for user sessions (if multi session mode is enabled, one instance for each session is started, otherwise only for instance for the most-recently opened session is started and previous instances are stopped). So what seems to happen in your case is that either the Veyon Server instances are not started at all for some reason or crash during startup or normal operation.
For further troubleshooting, first please update to the latest version available in our PPA (4.5.3-2) which contains additional fixes regarding session management. If it does not help, set the log level in Veyon Configurator to Debug, reboot, login and paste the output of
/tmp/VeyonServ*.loghere so we can examine it in detail.@tobydox said in Can't telnet localhost 11100:
For further troubleshooting, first please update to the latest version available in our PPA (4.5.3-2) which contains additional fixes regarding session management. If it does not help, set the log level in Veyon Configurator to Debug, reboot, login and paste the output of
/tmp/VeyonServ*.loghere so we can examine it in detail.I'm jumping in this thread as I have exactly the same issue.
$ telnet localhost 11100 Trying ::1... Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refusedHere are the debug logs:
$ sudo tail /tmp/VeyonServ*.log ==> /tmp/VeyonServer.log <== 2021-03-15T21:49:52.409: [DEBUG] PluginManager::loadPlugins(): discovered plugin "SystemUserGroups" at "/usr/lib/x86_64-linux-gnu/veyon/systemusergroups.so" 2021-03-15T21:49:52.410: [DEBUG] PluginManager::loadPlugins(): discovered plugin "TextMessage" at "/usr/lib/x86_64-linux-gnu/veyon/textmessage.so" 2021-03-15T21:49:52.411: [DEBUG] PluginManager::loadPlugins(): discovered plugin "UserSessionControl" at "/usr/lib/x86_64-linux-gnu/veyon/usersessioncontrol.so" 2021-03-15T21:49:52.412: [DEBUG] PluginManager::loadPlugins(): discovered plugin "WebAPI" at "/usr/lib/x86_64-linux-gnu/veyon/webapi.so" 2021-03-15T21:49:52.412: [DEBUG] VeyonCore::initSystemInfo(): "4.5.4" "potter" "linux" "5.4.0-67-generic" "Ubuntu 20.04.2 LTS" "ubuntu" "20.04" 2021-03-15T21:49:52.413: [DEBUG] FeatureWorkerManager::startUnmanagedSessionWorker(): Starting worker (unmanaged session process) for feature QUuid("{8e997d84-ebb9-430f-8f72-d45d9821963d}") 2021-03-15T21:49:52.418: [DEBUG] VncProxyServer::start(): started on port 11100 2021-03-15T21:49:52.418: [DEBUG] VncServer::prepare(): 2021-03-15T21:49:52.420: [DEBUG] VncServer::run(): running 2021-03-15T21:49:52.423: [DEBUG] VeyonCore::exec(): Running ==> /tmp/VeyonService.log <== 2021-03-15T21:49:12.526: [DEBUG] PlatformSessionManager::PlatformSessionManager(): 2021-03-15T21:49:12.527: [DEBUG] LinuxServiceCore::connectToLoginManager(): connected to login manager 2021-03-15T21:49:12.530: [ERR] LinuxServiceCore::startServer(): Can't start Veyon Server in Wayland sessions as this is not yet supported. Please switch to X11-based sessions! 2021-03-15T21:49:49.276: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" still opening - retrying in 1000 msecs 2021-03-15T21:49:50.297: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs 2021-03-15T21:49:52.323: [DEBUG] --- 2021-03-15T21:49:52.324: [DEBUG] Last message repeated 1 times 2021-03-15T21:49:52.324: [DEBUG] --- 2021-03-15T21:49:52.324: [DEBUG] PlatformSessionManager::openSession(): Opening session 0 for platform session "/org/freedesktop/login1/session/_32" 2021-03-15T21:49:52.325: [INFO] LinuxServiceCore::startServer(): Starting server for new x11 session "/org/freedesktop/login1/session/_32" with ID 0 at seat "/org/freedesktop/login1/seat/seat0"Regarding the "Wayland ERR", it's not true!
$ echo $XDG_SESSION_TYPE x11Anyway, what could be the next step in resolving this issue? Thank you for any help you could bring in.
-
Can you please have a look at the journal of the
veyonservice, i.e.journalctl -u veyon? It might contain additional messages, especially from the x11vnc server.@tobydox said in Can't telnet localhost 11100:
Can you please have a look at the journal of the
veyonservice, i.e.journalctl -u veyon? It might contain additional messages, especially from the x11vnc server.Here you are:
avril 22 13:28:16 myhostname systemd[1]: Started Veyon Service. avril 22 13:28:18 myhostname veyon-service[57904]: Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is created. avril 22 13:28:18 myhostname veyon-service[57904]: 2021-04-22T13:28:18.705: [DEBUG] PluginManager::loadPlugins(): discovered plugin "AuthKeys" at "/usr/lib/x86_64-linux-gnu/veyon/authkeys.so" avril 22 13:28:18 myhostname veyon-service[57904]: 2021-04-22T13:28:18.946: [DEBUG] PluginManager::loadPlugins(): discovered plugin "BuiltinX11VncServer" at "/usr/lib/x86_64-linux-gnu/veyon/builtin-x11vnc-server.so" avril 22 13:28:18 myhostname veyon-service[57904]: 2021-04-22T13:28:18.964: [DEBUG] PluginManager::loadPlugins(): discovered plugin "BuiltinDirectory" at "/usr/lib/x86_64-linux-gnu/veyon/builtindirectory.so" avril 22 13:28:18 myhostname veyon-service[57904]: 2021-04-22T13:28:18.998: [DEBUG] PluginManager::loadPlugins(): discovered plugin "Config" at "/usr/lib/x86_64-linux-gnu/veyon/config.so" avril 22 13:28:19 myhostname veyon-service[57904]: 2021-04-22T13:28:19.030: [DEBUG] PluginManager::loadPlugins(): discovered plugin "Demonstration" at "/usr/lib/x86_64-linux-gnu/veyon/demo.so" avril 22 13:28:19 myhostname veyon-service[57904]: 2021-04-22T13:28:19.049: [DEBUG] PluginManager::loadPlugins(): discovered plugin "DesktopServices" at "/usr/lib/x86_64-linux-gnu/veyon/desktopservices.so" avril 22 13:28:19 myhostname veyon-service[57904]: 2021-04-22T13:28:19.089: [DEBUG] PluginManager::loadPlugins(): discovered plugin "ExternalVncServer" at "/usr/lib/x86_64-linux-gnu/veyon/external-vnc-server.so" avril 22 13:28:19 myhostname veyon-service[57904]: 2021-04-22T13:28:19.126: [DEBUG] PluginManager::loadPlugins(): discovered plugin "FileTransfer" at "/usr/lib/x86_64-linux-gnu/veyon/filetransfer.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.097: [DEBUG] PluginManager::loadPlugins(): discovered plugin "LDAP Basic" at "/usr/lib/x86_64-linux-gnu/veyon/ldap.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.112: [DEBUG] PluginManager::loadPlugins(): discovered plugin "PowerControl" at "/usr/lib/x86_64-linux-gnu/veyon/powercontrol.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.140: [DEBUG] PluginManager::loadPlugins(): discovered plugin "RemoteAccess" at "/usr/lib/x86_64-linux-gnu/veyon/remoteaccess.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.156: [DEBUG] PluginManager::loadPlugins(): discovered plugin "ScreenLock" at "/usr/lib/x86_64-linux-gnu/veyon/screenlock.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.176: [DEBUG] PluginManager::loadPlugins(): discovered plugin "Screenshot" at "/usr/lib/x86_64-linux-gnu/veyon/screenshot.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.178: [DEBUG] PluginManager::loadPlugins(): discovered plugin "ServiceControl" at "/usr/lib/x86_64-linux-gnu/veyon/servicecontrol.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.179: [DEBUG] PluginManager::loadPlugins(): discovered plugin "Shell" at "/usr/lib/x86_64-linux-gnu/veyon/shell.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.180: [DEBUG] PluginManager::loadPlugins(): discovered plugin "SystemUserGroups" at "/usr/lib/x86_64-linux-gnu/veyon/systemusergroups.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.182: [DEBUG] PluginManager::loadPlugins(): discovered plugin "TextMessage" at "/usr/lib/x86_64-linux-gnu/veyon/textmessage.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.184: [DEBUG] PluginManager::loadPlugins(): discovered plugin "UserSessionControl" at "/usr/lib/x86_64-linux-gnu/veyon/usersessioncontrol.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.277: [DEBUG] PluginManager::loadPlugins(): discovered plugin "WebAPI" at "/usr/lib/x86_64-linux-gnu/veyon/webapi.so" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.363: [DEBUG] VeyonCore::initSystemInfo(): "4.5.5" "myhostname.mydomain.mytld" "linux" "5.4.0-70-generic" "Ubuntu 20.04.2 LTS" "ubuntu" "20.04" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.374: [DEBUG] ServiceDataManager::ServiceDataManager(): avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.375: [DEBUG] PlatformSessionManager::PlatformSessionManager(): avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.376: [DEBUG] LinuxServiceCore::connectToLoginManager(): connected to login manager avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.397: [DEBUG] PlatformSessionManager::openSession(): Opening session 0 for platform session "/org/freedesktop/login1/session/c1" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.398: [INFO] LinuxServiceCore::startServer(): Starting server for new session "/org/freedesktop/login1/session/c1" with ID 0 at seat "/org/freedesktop/login1/seat/seat0" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.421: [DEBUG] PlatformSessionManager::closeSession(): Closing session 0 for platform session "/org/freedesktop/login1/session/c1" avril 22 13:28:20 myhostname veyon-service[57904]: 2021-04-22T13:28:20.422: [INFO] LinuxServiceCore::stopServer(): stopping server for removed session "/org/freedesktop/login1/session/c1" avril 22 13:28:24 myhostname veyon-service[57904]: 2021-04-22T13:28:24.449: [WARN] LinuxServiceCore::stopServer(): server for session "/org/freedesktop/login1/session/c1" still running - killing now avril 22 13:28:27 myhostname veyon-service[57904]: 2021-04-22T13:28:27.463: [DEBUG] PlatformSessionManager::openSession(): Opening session 0 for platform session "/org/freedesktop/login1/session/_32" avril 22 13:28:27 myhostname veyon-service[57904]: 2021-04-22T13:28:27.465: [INFO] LinuxServiceCore::startServer(): Starting server for new session "/org/freedesktop/login1/session/_32" with ID 0 at seat "/org/freedesktop/login1/seat/seat0" avril 22 13:28:27 myhostname veyon-service[57904]: 2021-04-22T13:28:27.467: [WARN] QProcess: Destroyed while process ("/usr/bin/catchsegv") is still running.Hope it'll help.
-
Jumping in here, I also have the same problem.
Ubuntu 20.04
Veyon 4.5.5 installed using ppa focal mainDebug turned on and no warnings showing at all in the logs or journalctl
Doing netstat shows none of 11100, 11200, or 11300 as there or listening or anything.
Systemctl shows Veyon is active.
Weird thing is I have an old Ubuntu 16.04 set up with veyon version 4.3.5 and from 20.04 I can see that computer but not the other way around.
Thinking it is a problem with port setup from veyon? As everything else appears to be working (ping and file sharing). Just no port 11100, 11200, or 11300.
-
Jumping in here, I also have the same problem.
Ubuntu 20.04
Veyon 4.5.5 installed using ppa focal mainDebug turned on and no warnings showing at all in the logs or journalctl
Doing netstat shows none of 11100, 11200, or 11300 as there or listening or anything.
Systemctl shows Veyon is active.
Weird thing is I have an old Ubuntu 16.04 set up with veyon version 4.3.5 and from 20.04 I can see that computer but not the other way around.
Thinking it is a problem with port setup from veyon? As everything else appears to be working (ping and file sharing). Just no port 11100, 11200, or 11300.
Hi.
Same here -- Ubuntu 20.04 with the same error.
Neither "telnet localhost 11100" nor "telnet <ip> 11100" worked. I also get the "connection refused" error!
Service is up and running.journalctl -xe Mai 04 19:58:17 raum1-vm x11vnc[560]: --- x11vnc loop: 117 --- Mai 04 19:58:18 raum1-vm x11vnc[560]: --- x11vnc loop: waiting for: 21520 Mai 04 19:58:18 raum1-vm x11vnc[560]: --- x11vnc loop: sleeping 2000 ms --- Mai 04 19:58:20 raum1-vm x11vnc[560]: --- x11vnc loop: 118 --- Mai 04 19:58:21 raum1-vm x11vnc[560]: --- x11vnc loop: waiting for: 21695 ps aux |grep veyon root 1225 0.2 0.3 326504 30192 ? SLsl 19:52 0:01 /usr/bin/veyon-service <user> 35233 13.7 1.0 2031728 84824 ? Sl 20:02 0:00 /usr/bin/veyon-worker {8e997d82-ebb9-430f-8f72-d42d9823961d} cat Veyon.conf |grep 11100 VeyonServerPort=11100 nmap -p11100 localhost Starting Nmap 7.80 ( https://nmap.org ) at 2021-05-04 20:10 CEST Nmap scan report for localhost (127.0.0.1) Host is up (0.00016s latency). PORT STATE SERVICE 11100/tcp closed unknown -
The problem in all these cases is that the
veyon-serverprocess is not running. It's launched by theveyon-serviceprogram (systemd unitveyon) to run inside the individual user sessions. However for some reasons it seems to be not started properly or crashes. A running systemd service "veyon" only indicates that the service itself is running, not the server which provides actual computer access (and listens at port 11100 etc.).According to @olivierk 's journalctl output for
veyon, the service first starts a server instance for the login screen. Once the user logs in, the login session goes away and the server is stopped and a new one is started for the user session. The message server still running - killing now indicates that the previous server instance did not terminate properly in time so the newly started server is not able to listen at port 11100, even if the previous server eventually dies a few seconds later. What you could try is to increase the Minimum session lifetime before server start setting (Veyon Configurator -> View -> Advanced, go to page "Linux" (requires Veyon 4.5.5 or newer)). The service should then wait a longer time until trying to start the server for the user session. -
The problem in all these cases is that the
veyon-serverprocess is not running. It's launched by theveyon-serviceprogram (systemd unitveyon) to run inside the individual user sessions. However for some reasons it seems to be not started properly or crashes. A running systemd service "veyon" only indicates that the service itself is running, not the server which provides actual computer access (and listens at port 11100 etc.).According to @olivierk 's journalctl output for
veyon, the service first starts a server instance for the login screen. Once the user logs in, the login session goes away and the server is stopped and a new one is started for the user session. The message server still running - killing now indicates that the previous server instance did not terminate properly in time so the newly started server is not able to listen at port 11100, even if the previous server eventually dies a few seconds later. What you could try is to increase the Minimum session lifetime before server start setting (Veyon Configurator -> View -> Advanced, go to page "Linux" (requires Veyon 4.5.5 or newer)). The service should then wait a longer time until trying to start the server for the user session.@tobydox said in Can't telnet localhost 11100:
According to @olivierk 's journalctl output for
veyon, the service first starts a server instance for the login screen. Once the user logs in, the login session goes away and the server is stopped and a new one is started for the user session. The message server still running - killing now indicates that the previous server instance did not terminate properly in time so the newly started server is not able to listen at port 11100, even if the previous server eventually dies a few seconds later. What you could try is to increase the Minimum session lifetime before server start setting (Veyon Configurator -> View -> Advanced, go to page "Linux" (requires Veyon 4.5.5 or newer)). The service should then wait a longer time until trying to start the server for the user session.Well... Even with a minimum session lifetime set to 60 s, it didn't resolve the issue.
$ journalctl -u veyon May 06 19:57:50 hostname systemd[1]: Started Veyon Service. May 06 19:57:51 hostname veyon-service[1058]: Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is created. May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.447: [DEBUG] PluginManager::loadPlugins(): discovered plugin "AuthKeys" at "/usr/lib/x86_64-linux-gnu/veyon/authkeys.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.579: [DEBUG] PluginManager::loadPlugins(): discovered plugin "BuiltinX11VncServer" at "/usr/lib/x86_64-linux-gnu/veyon/builtin-x11vnc-server.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.580: [DEBUG] PluginManager::loadPlugins(): discovered plugin "BuiltinDirectory" at "/usr/lib/x86_64-linux-gnu/veyon/builtindirectory.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.581: [DEBUG] PluginManager::loadPlugins(): discovered plugin "Config" at "/usr/lib/x86_64-linux-gnu/veyon/config.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.581: [DEBUG] PluginManager::loadPlugins(): discovered plugin "Demonstration" at "/usr/lib/x86_64-linux-gnu/veyon/demo.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.582: [DEBUG] PluginManager::loadPlugins(): discovered plugin "DesktopServices" at "/usr/lib/x86_64-linux-gnu/veyon/desktopservices.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.583: [DEBUG] PluginManager::loadPlugins(): discovered plugin "ExternalVncServer" at "/usr/lib/x86_64-linux-gnu/veyon/external-vnc-server.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.584: [DEBUG] PluginManager::loadPlugins(): discovered plugin "FileTransfer" at "/usr/lib/x86_64-linux-gnu/veyon/filetransfer.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.599: [DEBUG] PluginManager::loadPlugins(): discovered plugin "LDAP Basic" at "/usr/lib/x86_64-linux-gnu/veyon/ldap.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.600: [DEBUG] PluginManager::loadPlugins(): discovered plugin "PowerControl" at "/usr/lib/x86_64-linux-gnu/veyon/powercontrol.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.601: [DEBUG] PluginManager::loadPlugins(): discovered plugin "RemoteAccess" at "/usr/lib/x86_64-linux-gnu/veyon/remoteaccess.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.601: [DEBUG] PluginManager::loadPlugins(): discovered plugin "ScreenLock" at "/usr/lib/x86_64-linux-gnu/veyon/screenlock.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.602: [DEBUG] PluginManager::loadPlugins(): discovered plugin "Screenshot" at "/usr/lib/x86_64-linux-gnu/veyon/screenshot.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.605: [DEBUG] PluginManager::loadPlugins(): discovered plugin "ServiceControl" at "/usr/lib/x86_64-linux-gnu/veyon/servicecontrol.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.606: [DEBUG] PluginManager::loadPlugins(): discovered plugin "Shell" at "/usr/lib/x86_64-linux-gnu/veyon/shell.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.607: [DEBUG] PluginManager::loadPlugins(): discovered plugin "SystemUserGroups" at "/usr/lib/x86_64-linux-gnu/veyon/systemusergroups.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.608: [DEBUG] PluginManager::loadPlugins(): discovered plugin "TextMessage" at "/usr/lib/x86_64-linux-gnu/veyon/textmessage.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.608: [DEBUG] PluginManager::loadPlugins(): discovered plugin "UserSessionControl" at "/usr/lib/x86_64-linux-gnu/veyon/usersessioncontrol.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.609: [DEBUG] PluginManager::loadPlugins(): discovered plugin "WebAPI" at "/usr/lib/x86_64-linux-gnu/veyon/webapi.so" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.610: [DEBUG] VeyonCore::initSystemInfo(): "4.5.5" "hostname.poudlard.fr" "linux" "5.4.0-72-generic" "Ubuntu 20.04.2 LTS" "ubuntu" "20.04" May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.628: [DEBUG] ServiceDataManager::ServiceDataManager(): May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.629: [DEBUG] PlatformSessionManager::PlatformSessionManager(): May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.631: [DEBUG] LinuxServiceCore::connectToLoginManager(): connected to login manager May 06 19:57:51 hostname veyon-service[1058]: 2021-05-06T19:57:51.658: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:14 hostname veyon-service[1058]: 2021-05-06T19:58:14.285: [DEBUG] --- May 06 19:58:14 hostname veyon-service[1058]: 2021-05-06T19:58:14.285: [DEBUG] Last message repeated 22 times May 06 19:58:14 hostname veyon-service[1058]: 2021-05-06T19:58:14.285: [DEBUG] --- May 06 19:58:14 hostname veyon-service[1058]: 2021-05-06T19:58:14.285: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" still opening - retrying in 1000 msecs May 06 19:58:14 hostname veyon-service[1058]: 2021-05-06T19:58:14.979: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:15 hostname veyon-service[1058]: 2021-05-06T19:58:15.305: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:15 hostname veyon-service[1058]: 2021-05-06T19:58:15.999: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:16 hostname veyon-service[1058]: 2021-05-06T19:58:16.314: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:17 hostname veyon-service[1058]: 2021-05-06T19:58:17.016: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:17 hostname veyon-service[1058]: 2021-05-06T19:58:17.328: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:18 hostname veyon-service[1058]: 2021-05-06T19:58:18.030: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:18 hostname veyon-service[1058]: 2021-05-06T19:58:18.346: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:19 hostname veyon-service[1058]: 2021-05-06T19:58:19.053: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:19 hostname veyon-service[1058]: 2021-05-06T19:58:19.358: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:20 hostname veyon-service[1058]: 2021-05-06T19:58:20.071: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:20 hostname veyon-service[1058]: 2021-05-06T19:58:20.374: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:21 hostname veyon-service[1058]: 2021-05-06T19:58:21.088: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:21 hostname veyon-service[1058]: 2021-05-06T19:58:21.399: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:22 hostname veyon-service[1058]: 2021-05-06T19:58:22.105: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:22 hostname veyon-service[1058]: 2021-05-06T19:58:22.416: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:23 hostname veyon-service[1058]: 2021-05-06T19:58:23.142: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:23 hostname veyon-service[1058]: 2021-05-06T19:58:23.441: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:24 hostname veyon-service[1058]: 2021-05-06T19:58:24.175: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:24 hostname veyon-service[1058]: 2021-05-06T19:58:24.467: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:25 hostname veyon-service[1058]: 2021-05-06T19:58:25.223: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:25 hostname veyon-service[1058]: 2021-05-06T19:58:25.503: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:26 hostname veyon-service[1058]: 2021-05-06T19:58:26.263: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:26 hostname veyon-service[1058]: 2021-05-06T19:58:26.537: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:27 hostname veyon-service[1058]: 2021-05-06T19:58:27.281: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:27 hostname veyon-service[1058]: 2021-05-06T19:58:27.551: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:28 hostname veyon-service[1058]: 2021-05-06T19:58:28.294: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:28 hostname veyon-service[1058]: 2021-05-06T19:58:28.567: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:29 hostname veyon-service[1058]: 2021-05-06T19:58:29.309: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:29 hostname veyon-service[1058]: 2021-05-06T19:58:29.586: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:30 hostname veyon-service[1058]: 2021-05-06T19:58:30.325: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:30 hostname veyon-service[1058]: 2021-05-06T19:58:30.598: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:31 hostname veyon-service[1058]: 2021-05-06T19:58:31.343: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:31 hostname veyon-service[1058]: 2021-05-06T19:58:31.620: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:32 hostname veyon-service[1058]: 2021-05-06T19:58:32.360: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:32 hostname veyon-service[1058]: 2021-05-06T19:58:32.636: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:33 hostname veyon-service[1058]: 2021-05-06T19:58:33.376: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:33 hostname veyon-service[1058]: 2021-05-06T19:58:33.652: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:34 hostname veyon-service[1058]: 2021-05-06T19:58:34.392: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:34 hostname veyon-service[1058]: 2021-05-06T19:58:34.667: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:35 hostname veyon-service[1058]: 2021-05-06T19:58:35.408: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:35 hostname veyon-service[1058]: 2021-05-06T19:58:35.683: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:36 hostname veyon-service[1058]: 2021-05-06T19:58:36.425: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:36 hostname veyon-service[1058]: 2021-05-06T19:58:36.698: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:37 hostname veyon-service[1058]: 2021-05-06T19:58:37.440: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:37 hostname veyon-service[1058]: 2021-05-06T19:58:37.714: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:38 hostname veyon-service[1058]: 2021-05-06T19:58:38.456: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:38 hostname veyon-service[1058]: 2021-05-06T19:58:38.730: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:39 hostname veyon-service[1058]: 2021-05-06T19:58:39.472: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:39 hostname veyon-service[1058]: 2021-05-06T19:58:39.745: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:40 hostname veyon-service[1058]: 2021-05-06T19:58:40.486: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:40 hostname veyon-service[1058]: 2021-05-06T19:58:40.756: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:41 hostname veyon-service[1058]: 2021-05-06T19:58:41.502: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:41 hostname veyon-service[1058]: 2021-05-06T19:58:41.776: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:42 hostname veyon-service[1058]: 2021-05-06T19:58:42.517: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:42 hostname veyon-service[1058]: 2021-05-06T19:58:42.789: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:43 hostname veyon-service[1058]: 2021-05-06T19:58:43.533: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:43 hostname veyon-service[1058]: 2021-05-06T19:58:43.807: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:44 hostname veyon-service[1058]: 2021-05-06T19:58:44.549: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:44 hostname veyon-service[1058]: 2021-05-06T19:58:44.823: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:45 hostname veyon-service[1058]: 2021-05-06T19:58:45.567: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:45 hostname veyon-service[1058]: 2021-05-06T19:58:45.838: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:46 hostname veyon-service[1058]: 2021-05-06T19:58:46.583: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:46 hostname veyon-service[1058]: 2021-05-06T19:58:46.856: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:47 hostname veyon-service[1058]: 2021-05-06T19:58:47.601: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:47 hostname veyon-service[1058]: 2021-05-06T19:58:47.872: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:48 hostname veyon-service[1058]: 2021-05-06T19:58:48.619: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:48 hostname veyon-service[1058]: 2021-05-06T19:58:48.889: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:49 hostname veyon-service[1058]: 2021-05-06T19:58:49.637: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/c1" too young - retrying in 1000 msecs May 06 19:58:49 hostname veyon-service[1058]: 2021-05-06T19:58:49.904: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:58:50 hostname veyon-service[1058]: 2021-05-06T19:58:50.653: [DEBUG] PlatformSessionManager::openSession(): Opening session 0 for platform session "/org/freedesktop/login1/session/c1" May 06 19:58:50 hostname veyon-service[1058]: 2021-05-06T19:58:50.654: [INFO] LinuxServiceCore::startServer(): Starting server for new session "/org/freedesktop/login1/session/c1" with ID 0 at seat "/org/freedesktop/login1/seat/seat0" May 06 19:58:50 hostname veyon-service[1058]: 2021-05-06T19:58:50.916: [DEBUG] PlatformSessionManager::closeSession(): Closing session 0 for platform session "/org/freedesktop/login1/session/c1" May 06 19:58:50 hostname veyon-service[1058]: 2021-05-06T19:58:50.917: [INFO] LinuxServiceCore::stopServer(): stopping server for removed session "/org/freedesktop/login1/session/c1" May 06 19:58:50 hostname veyon-service[1058]: 2021-05-06T19:58:50.918: [DEBUG] LinuxServiceCore::startServer(): Session "/org/freedesktop/login1/session/_32" too young - retrying in 1000 msecs May 06 19:59:14 hostname veyon-service[1058]: 2021-05-06T19:59:14.287: [DEBUG] --- May 06 19:59:14 hostname veyon-service[1058]: 2021-05-06T19:59:14.288: [DEBUG] Last message repeated 22 times May 06 19:59:14 hostname veyon-service[1058]: 2021-05-06T19:59:14.288: [DEBUG] --- May 06 19:59:14 hostname veyon-service[1058]: 2021-05-06T19:59:14.288: [DEBUG] PlatformSessionManager::openSession(): Opening session 0 for platform session "/org/freedesktop/login1/session/_32" May 06 19:59:14 hostname veyon-service[1058]: 2021-05-06T19:59:14.289: [INFO] LinuxServiceCore::startServer(): Starting server for new session "/org/freedesktop/login1/session/_32" with ID 0 at seat "/org/freedesktop/login1/seat/seat0"I waited several minutes but nothing good happened.
Here is the result of
$ ps auxww | grep -i veyon root 1058 0.1 0.9 328756 30408 ? SLsl 19:57 0:01 /usr/bin/veyon-service gdm 2165 0.0 1.7 291328 56388 ? Sl 19:58 0:00 /usr/bin/veyon-worker {8e997d84-ebb9-430f-8f72-d45d9821963d} olivierk 2207 0.0 1.7 439036 57024 ? Sl 19:59 0:00 /usr/bin/veyon-worker {8e997d84-ebb9-430f-8f72-d45d9821963d} olivierk 2912 0.0 0.0 11468 732 pts/1 D+ 20:11 0:00 grep -i veyonYou can see veyon-service launched by root and two veyon-worker(s) run by gdm anf by me. They both have the same GUID. Don't know if it's okay. Anyway, there is no veyon-service running.
-
The problem in all these cases is that the
veyon-serverprocess is not running. It's launched by theveyon-serviceprogram (systemd unitveyon) to run inside the individual user sessions. However for some reasons it seems to be not started properly or crashes. A running systemd service "veyon" only indicates that the service itself is running, not the server which provides actual computer access (and listens at port 11100 etc.).According to @olivierk 's journalctl output for
veyon, the service first starts a server instance for the login screen. Once the user logs in, the login session goes away and the server is stopped and a new one is started for the user session. The message server still running - killing now indicates that the previous server instance did not terminate properly in time so the newly started server is not able to listen at port 11100, even if the previous server eventually dies a few seconds later. What you could try is to increase the Minimum session lifetime before server start setting (Veyon Configurator -> View -> Advanced, go to page "Linux" (requires Veyon 4.5.5 or newer)). The service should then wait a longer time until trying to start the server for the user session.This post is deleted! -
I started "veyon-server" as a USER directly and got these messages:
08/05/2021 17:42:33 Listening for VNC connections on TCP port 11200 08/05/2021 17:42:33 Listening for VNC connections on TCP6 port 11200 08/05/2021 17:42:33 08/05/2021 17:42:33 Xinerama is present and active (e.g. multi-head). 08/05/2021 17:42:33 Xinerama: number of sub-screens: 1 08/05/2021 17:42:33 Xinerama: no blackouts needed (only one sub-screen) 08/05/2021 17:42:33 08/05/2021 17:42:33 fb read rate: 305 MB/sec 08/05/2021 17:42:33 fast read: reset -wait ms to: 10 08/05/2021 17:42:33 fast read: reset -defer ms to: 10 08/05/2021 17:42:33 The X server says there are 10 mouse buttons. 08/05/2021 17:42:33 screen setup finished. 08/05/2021 17:42:33 The VNC desktop is: localhost:5300 08/05/2021 17:42:33 possible aliases: localhost:11200, localhost::11200 PORT=11200 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching 08/05/2021 17:42:33 Got connection from client 127.0.0.1 08/05/2021 17:42:33 0 other clients 08/05/2021 17:42:33 check_access: client 127.0.0.1 matches host 127.0.0.1 08/05/2021 17:42:33 incr accepted_client=1 for 127.0.0.1:40640 sock=24 08/05/2021 17:42:33 Client Protocol Version 3.8 08/05/2021 17:42:33 Protocol version sent 3.8, using 3.8 08/05/2021 17:42:33 rfbProcessClientSecurityType: executing handler for type 2 08/05/2021 17:42:33 copy_tiles: allocating first_line at size 33 08/05/2021 17:42:33 Pixel format for client 127.0.0.1: 08/05/2021 17:42:33 32 bpp, depth 24, little endian 08/05/2021 17:42:33 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 08/05/2021 17:42:33 no translation needed 08/05/2021 17:42:33 rfbProcessClientNormalMessage: ignoring unsupported encoding type ultraZip 08/05/2021 17:42:33 Using compression level 9 for client 127.0.0.1 08/05/2021 17:42:33 Enabling KeyboardLedState protocol extension for client 127.0.0.1 08/05/2021 17:42:33 Enabling NewFBSize protocol extension for client 127.0.0.1 08/05/2021 17:42:33 Enabling SupportedMessages protocol extension for client 127.0.0.1 ...Another Client was able to connect now!
So: it runs when the "veyon-server" was started again ... do you have an idea, why it crashes?First I tried it as root -- but the "veyon-server" didn't start!
... X11 MIT Shared Memory Attach failed: Is your DISPLAY=:0 on a remote machine? Suggestion, use: x11vnc -display :0 ... for local display :0 caught X11 error: 08/05/2021 17:12:29 deleted 32 tile_row polling images. X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 130 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 60 Current serial number in output stream: 94 -
I started "veyon-server" as a USER directly and got these messages:
08/05/2021 17:42:33 Listening for VNC connections on TCP port 11200 08/05/2021 17:42:33 Listening for VNC connections on TCP6 port 11200 08/05/2021 17:42:33 08/05/2021 17:42:33 Xinerama is present and active (e.g. multi-head). 08/05/2021 17:42:33 Xinerama: number of sub-screens: 1 08/05/2021 17:42:33 Xinerama: no blackouts needed (only one sub-screen) 08/05/2021 17:42:33 08/05/2021 17:42:33 fb read rate: 305 MB/sec 08/05/2021 17:42:33 fast read: reset -wait ms to: 10 08/05/2021 17:42:33 fast read: reset -defer ms to: 10 08/05/2021 17:42:33 The X server says there are 10 mouse buttons. 08/05/2021 17:42:33 screen setup finished. 08/05/2021 17:42:33 The VNC desktop is: localhost:5300 08/05/2021 17:42:33 possible aliases: localhost:11200, localhost::11200 PORT=11200 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching 08/05/2021 17:42:33 Got connection from client 127.0.0.1 08/05/2021 17:42:33 0 other clients 08/05/2021 17:42:33 check_access: client 127.0.0.1 matches host 127.0.0.1 08/05/2021 17:42:33 incr accepted_client=1 for 127.0.0.1:40640 sock=24 08/05/2021 17:42:33 Client Protocol Version 3.8 08/05/2021 17:42:33 Protocol version sent 3.8, using 3.8 08/05/2021 17:42:33 rfbProcessClientSecurityType: executing handler for type 2 08/05/2021 17:42:33 copy_tiles: allocating first_line at size 33 08/05/2021 17:42:33 Pixel format for client 127.0.0.1: 08/05/2021 17:42:33 32 bpp, depth 24, little endian 08/05/2021 17:42:33 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 08/05/2021 17:42:33 no translation needed 08/05/2021 17:42:33 rfbProcessClientNormalMessage: ignoring unsupported encoding type ultraZip 08/05/2021 17:42:33 Using compression level 9 for client 127.0.0.1 08/05/2021 17:42:33 Enabling KeyboardLedState protocol extension for client 127.0.0.1 08/05/2021 17:42:33 Enabling NewFBSize protocol extension for client 127.0.0.1 08/05/2021 17:42:33 Enabling SupportedMessages protocol extension for client 127.0.0.1 ...Another Client was able to connect now!
So: it runs when the "veyon-server" was started again ... do you have an idea, why it crashes?First I tried it as root -- but the "veyon-server" didn't start!
... X11 MIT Shared Memory Attach failed: Is your DISPLAY=:0 on a remote machine? Suggestion, use: x11vnc -display :0 ... for local display :0 caught X11 error: 08/05/2021 17:12:29 deleted 32 tile_row polling images. X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 130 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 60 Current serial number in output stream: 94I don't know if this helps ... but when I start "veyon-server" as a login-Script I get this message:
