Univention Bugzilla – Bug 55471
Could not modify the autostart property for the Veyon Service in a docker instance
Last modified: 2023-07-12 16:36:47 CEST
Currently it seams that the current Veyon docker instance installed through univention app center immediately fails with the errors: [ERROR] Could not modify the autostart property for the Veyon Service. [FAIL] [INFO] WebAPI server running at port 11080 [ERROR] Could not modify the autostart property for the Veyon Service. [FAIL] [INFO] WebAPI server running at port 11080 If I try to modify the Autostart value in the docker instance with: # veyon-cli config set Service/Autostart true It will fail with the aforementioned error: [ERROR] Could not modify the autostart property for the Veyon Service. [FAIL] The version installed is 4.4/ucsschool-veyon-proxy=4.7.4.14-0. It is apparantly not even clear to me wether this veyon instance is now running or not.
What is the exact problem you or a customer is facing? Mybe the error message in the logs are confusing? The last line informs that the veyon service has been started. On a testmachine, "docker ps" shows that the container is running. With ps i can see that the veyon-cli binary is running inside the container.
I now have a customer with the same messages in Log. The Problem is, that the computer room control which veyon use is not working at all. The "circle" in front of the client remains light gray, Watch does not work Locking, logging off, switching off does not work An other log, I guess from the Windows Client shows: 05.07.23 10:41:04.646 MODULE ( WARN ) : Veyon error on WIN- TESTCLIENT1: Authentication failed 05.07.23 10:41:04.646 MODULE ( WARN ) : WIN-TESTCLIENT1: Updating information was not successful. I will try the ps and check if veyon-cli is running. Any other hints how to debug?
looks like a problem with the certificates or permissions issue: 2023-07-05T10:17:43.728: [DEBUG] ServerAuthenticationManager::performKeyAuthentication(): SUCCESS 2023-07-05T10:17:43.728: [DEBUG] AccessControlProvider::checkAccess(): no access control method configured, allowing access. 2023-07-05T10:17:43.728: [INFO] ComputerControlServer::showAccessControlMessage(): Access control successful for "::ffff:10.112.40.50" "root" Ein paar Minuten später konnte der Key wieder nicht geladen werden: 2023-07-05T10:19:25.607: [WARN] ServerAuthenticationManager::performKeyAuthentication(): failed to load public key from "C:\\ProgramData\\Veyon\\keys\\public\\teacher\\key" Solution was to delete the certificates, re execute the joinscripts, and reinitialize the veyon container.
To me it looks like we have at least a workaround then? If the problem occurred without a good reason it still feels buggy to me, but if the servers configuration or certificates changed I would like to close this bug.