Run join script - SEP Sesam CLI 4.4.2.87 - UCS 4.1-3

appcenter
join
sep-sesam

#1

Hallo liebes Forum,

ich habe gerade auf einem Backup DC den Sesam Client 4.4.2.87 über das AppCenter installiert,
und wollte das fehlende Join Script ausführen.

Leider kommt folgender Fehler:

univention-run-join-scripts: runs all join scripts existing on local computer.
copyright (c) 2001-2016 Univention GmbH, Germany

Enter DC Master Account : Administrator
Enter DC Master Password: 

Search LDAP binddn                                         done
Running 00zarafa4ucs-safemode-on.inst                      skipped (already executed)
Running 01univention-ldap-server-init.inst                 skipped (already executed)
Running 02univention-directory-notifier.inst               skipped (already executed)
Running 03univention-directory-listener.inst               skipped (already executed)
Running 04univention-ldap-client.inst                      skipped (already executed)
Running 05univention-bind.inst                             skipped (already executed)
Running 08univention-apache.inst                           skipped (already executed)
Running 10univention-ldap-server.inst                      skipped (already executed)
Running 11univention-heimdal-init.inst                     skipped (already executed)
Running 11univention-pam.inst                              skipped (already executed)
Running 15univention-directory-notifier-post.inst          skipped (already executed)
Running 15univention-heimdal-kdc.inst                      skipped (already executed)
Running 18python-univention-directory-manager.inst         skipped (already executed)
Running 20univention-directory-policy.inst                 skipped (already executed)
Running 20univention-join.inst                             skipped (already executed)
Running 25univention-dhcp.inst                             skipped (already executed)
Running 26univention-nagios-common.inst                    skipped (already executed)
Running 30univention-appcenter.inst                        skipped (already executed)
Running 30univention-nagios-client.inst                    skipped (already executed)
Running 31univention-nagios-s4-connector.inst              skipped (already executed)
Running 31univention-nagios-samba.inst                     skipped (already executed)
Running 34univention-management-console-server.inst        skipped (already executed)
Running 35univention-appcenter-docker.inst                 skipped (already executed)
Running 35univention-management-console-module-appcenter.inskipped (already executed)
Running 35univention-management-console-module-diagnostic.iskipped (already executed)
Running 35univention-management-console-module-ipchange.insskipped (already executed)
Running 35univention-management-console-module-join.inst   skipped (already executed)
Running 35univention-management-console-module-lib.inst    skipped (already executed)
Running 35univention-management-console-module-mrtg.inst   skipped (already executed)
Running 35univention-management-console-module-passwordchanskipped (already executed)
Running 35univention-management-console-module-quota.inst  skipped (already executed)
Running 35univention-management-console-module-reboot.inst skipped (already executed)
Running 35univention-management-console-module-services.insskipped (already executed)
Running 35univention-management-console-module-setup.inst  skipped (already executed)
Running 35univention-management-console-module-sysinfo.instskipped (already executed)
Running 35univention-management-console-module-top.inst    skipped (already executed)
Running 35univention-management-console-module-ucr.inst    skipped (already executed)
Running 35univention-management-console-module-udm.inst    skipped (already executed)
Running 35univention-management-console-module-updater.instskipped (already executed)
Running 36univention-management-console-module-apps.inst   skipped (already executed)
Running 40univention-virtual-machine-manager-schema.inst   skipped (already executed)
Running 70zarafa4ucs-udm.inst                              skipped (already executed)
Running 70zarafa4ucs-webapp-update.inst                    skipped (already executed)
Running 70zarafa4ucs.inst                                  skipped (already executed)
Running 71zarafa4ucs-webapp.inst                           skipped (already executed)
Running 78univention-kde.inst                              skipped (already executed)
Running 81univention-nfs-server.inst                       skipped (already executed)
**Running 90sep-sesam-cli.inst                               failed (exitcode: 1)**
Running 90univention-bind-post.inst                        skipped (already executed)
Running 91univention-saml.inst                             skipped (already executed)
Running 92univention-management-console-web-server.inst    skipped (already executed)
Running 96univention-samba4.inst                           skipped (already executed)
Running 97univention-s4-connector.inst                     skipped (already executed)
Running 98univention-pkgdb-tools.inst                      skipped (already executed)
Running 98univention-samba4-dns.inst                       skipped (already executed)
Running 99zarafa4ucs-safemode-off.inst                     skipped (already executed)

Im join.log finde ich folgenden Fehler:

2018-04-04 10:43:08.604894440+02:00 (in joinscript_init)
ERROR: Did not find any SEP Sesam server installation in your domain.
       Please install one SEP Sesam server in your domain, and
       re-run this join script.

Auf dem Masterserver ist aber sehr wohl ein SEP Sesam Server über das AppCenter installiert worden.

Das sehe ich mit univention-app info:

UCS: 4.1-3 errata318
App Center compatibility: 4
Installed: kde=4 kvm=1.1.2 samba4=4.5 **sep-sesam=4.4.2-87** uvmm=5
Upgradable: 

Danke für eure Hilfe im Voraus!


#2

Moin,

lief das Join-Script des SEP Sesam Servers auf dem Master problemlos durch?

Viele Grüße von der bytemine GmbH


#3

Hy,

ja, denn den Sesam Server gibt es schon länger - Siehe Join Datum.

RUNNING 78univention-kde.inst
EXITCODE=already_executed
RUNNING 81univention-nfs-server.inst
EXITCODE=already_executed
RUNNING 90sep-sesam.inst
EXITCODE=already_executed
RUNNING 90univention-bind-post.inst
EXITCODE=already_executed
RUNNING 96univention-samba4.inst
EXITCODE=already_executed
RUNNING 97univention-s4-connector.inst
EXITCODE=already_executed
RUNNING 98univention-pkgdb-tools.inst
EXITCODE=already_executed
RUNNING 98univention-samba4-dns.inst
EXITCODE=already_executed

Fr 28. Okt 11:59:12 CEST 2016
univention-run-join-scripts finished
univention-check-join-status
Joined successfully

LG und danke für die Hilfe!


#4

Moin,

bitte einmal auf dem Master univention-ldapsearch cn=SESAM-SRV ausführen. Wenn dabei nichts zurückgeliefert wird, hat das Join-Script des Backup-Servers den Service nicht richtig registriert.

Viele Grüße von der Bytemine GmbH


#5

Moin,

sorry für die verspätete Antwort:

root@mastersrv:~# univention-ldapsearch cn=SESAM-SRV

extended LDIF

 LDAPv3
 base <dc=xxxx,dc=local> (default) with scope subtree
 filter: cn=SESAM-SRV
 requesting: ALL


 search result
search: 3
result: 0 Success

 numResponses: 1

#6

Führen Sie bitte einmal univention-run-join-scripts --force --run-scripts 90sep-sesam aus, danach sollte der SEP-Sesam-Server ordnungsgemässig registriert sein.

Viele Grüße von der bytemine GmbH


#7

Hat funtioniert - Danke vielmals!