The signature changed into: Version: 4.2-2 errata189 (Lesum) Remark: Standard Installation,....Option Member Server in AD. Traceback(d41d8cd98f00b204e9800998ecf8427e): Domain setup (this might take a while): The ssh-login to Administrator@**** failed with "ssh: connect to host ucs-server.homelab.loc port 22: Connection refused ". Please make sure the account Administrator exists and is a member of the Domain Admins group! +++ This bug was initially created as a clone of Bug #42425 +++ Version: 4.1-3 errata268 (Vahr) We received the following feedback: Domäneneinrichtung (Dies kann einige Zeit dauern): ssh-login for Administrator@ac001c01.deac.****** failed. Maybe you entered a wrong password. We should check this prior to starting the setup wizard.
Version: 4.2-2 errata157 (Lesum) Remark: it only worked once, never aftewards (due to necesserry reinstallation). Although cleaneing up the ADS (based on Samba4)
Version: 4.2-2 errata184 (Lesum)
Version: 4.2-2 errata159 (Lesum)
Reported again, 4.2-2 errata204 (Lesum)
Reported again: Version: 4.3-0 errata0 (Neustadt) Domain setup (this might take a while): The ssh-login to Administrator@intra.yaka.fr.cr failed with "bash: /home/Administrator/.bashrc: Permission non accordée ls: impossible d'ouvrir le répertoire '.': Permission non accordée ". Please make sure the account Administrator exists and is a member of the Domain Admins group! Role: domaincontroller_backup
*** Bug 45520 has been marked as a duplicate of this bug. ***
idea: add a link to a knowledge base article about join problems to the standard join fail message kbd: https://help.univention.com/t/8842 univention-join b97c09b6dd7acfe368d7de3171f2d2d952efd089 yaml: 32c10260090849ecb771d43c66ae0c39f08f2062 qa: * Is that even helpful? * article: wording, spelling, informations * is the fail message ok (command line, UMC, setup?)
(In reply to Felix Botner from comment #7) > * Is that even helpful? We will see if the feedback tickets with error messages regarding these problems will go down in volume. I think its a good start. We also added checks to system setup a while ago to catch these errors early. > * article: wording, spelling, informations I made some small adjustments to the article. > * is the fail message ok (command line, UMC, setup?) Please adjust the code so that the hint to the SDB article is on a separate line from the error message. Also, please comply with the line length of the surrounding statements. -> reopen
(In reply to Erik Damrose from comment #8) > > > * is the fail message ok (command line, UMC, setup?) > > Please adjust the code so that the hint to the SDB article is on a separate > line from the error message. Also, please comply with the line length of the > surrounding statements. -> reopen the umc setup looks for the "* Message:" line and prints only this line in the dialog, so at the moment we can only have a on liner error message
Thanks for the clarification. I agree that the current solution is okay for now OK: univention-join OK: yaml Verified
<http://errata.software-univention.de/ucs/4.3/95.html>