• 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 server
    

    The 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*.log here 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*.log here 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 refused
    

    Here 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 
    x11
    

    Anyway, what could be the next step in resolving this issue? Thank you for any help you could bring in.