ich stehe gerade vor dem Problem das ich auf einer cleanen UCS4.4.1 Err196-Installation kein UCS@school zu Testzwecken installiert bekomme. Egal wie ich UCS installiere, ob in einer älteren Version oder aktuell, ich bekomme ständig den selben Fehler:
ucs-school-umc-installer kann nicht gefunden werden
root@ucsmaster:~# ucr search repository/online/component
repository/online/component/.*/clean: <empty>
If a local repository is used (see 'local/repository') and if the option 'online/repository/clean' is activated, a shell script with the filename '/var/lib/univention-repository/var/clean.sh' is generating. Executing this shell script removes mirrored repository content, which is no longer used. If this option is activated, packages from the component which are no longer needed are integrated in the script.
repository/online/component/.*/description: <empty>
The description of a repository component.
repository/online/component/.*/localmirror: <empty>
If this option is activated, the component is mirrored to a local repository (if one exists).
repository/online/component/.*/password: <empty>
Some repository components require authentication for accessing the repository. The password can be configured with this variable. See also 'repository/online/component/.*/username'.
repository/online/component/.*/port: <empty>
This variable configures the TCP port under which the server of the repository component is reachable. If the variable is unset, '80' is used.
repository/online/component/.*/prefix: <empty>
Some repositories use several update subdirectories. This variable allows to configure such a path for the component. If the variable is unset, no prefix is used.
repository/online/component/.*/server: <empty>
The repository server from which packages of the component are retrieved. If the variable is unset, the value from 'repository/online/server' is used. If an URI is given instead on a hostname, this also overwrites '.../port' and '.../prefix'.
repository/online/component/.*/unmaintained: <empty>
Repository components also differentiate between 'maintained' and 'unmaintained' (see 'repository/online/unmaintained'). Components which are included through the Univention App Center usually only use 'maintained'. If this option is activated, packages of the component from 'unmaintained' are included. If the variable is unset, the global setting is used.
repository/online/component/.*/username: <empty>
Some repository components require authentication for accessing the repository. The username can be configured with this variable. See also 'repository/online/component/.*/password'.
repository/online/component/.*/version: <empty>
Components can be versioned. This ensures that only components are installed that are compatible with a UCS version. If the variable is empty or unset, all versions of the same major number will be used. If for example UCS 3.2 is installed, all repositories of the component with version numbers 3.0, 3.1 and 3.2 will be used if available. If the variable is set to 'current' all versions of the same major version will be included. Additionally it will block all minor and major upgrades of the installed UCS system until the respective component is also available for the new release. Patch level and errata updates are not affected.
repository/online/component/.*: <empty>
In addition to the standard repository additional components can be included. While such components are usually included through the Univention App Center, they can also be configured manually in Univention Configuration Registry. To include a component the option 'repository/online/component/COMPONENTNAME' must be activated. Additional parameters can be set following the scheme 'repository/online/component/COMPONENTNAME/OPTION=VALUE'.
repository/online/component/4.4-0-errata/description: Errata updates for UCS 4.4-0
The description of a repository component.
repository/online/component/4.4-0-errata/localmirror: true
If this option is activated, the component is mirrored to a local repository (if one exists).
repository/online/component/4.4-0-errata/version: 4.4
Components can be versioned. This ensures that only components are installed that are compatible with a UCS version. If the variable is empty or unset, all versions of the same major number will be used. If for example UCS 3.2 is installed, all repositories of the component with version numbers 3.0, 3.1 and 3.2 will be used if available. If the variable is set to 'current' all versions of the same major version will be included. Additionally it will block all minor and major upgrades of the installed UCS system until the respective component is also available for the new release. Patch level and errata updates are not affected.
repository/online/component/4.4-0-errata: false
In addition to the standard repository additional components can be included. While such components are usually included through the Univention App Center, they can also be configured manually in Univention Configuration Registry. To include a component the option 'repository/online/component/COMPONENTNAME' must be activated. Additional parameters can be set following the scheme 'repository/online/component/COMPONENTNAME/OPTION=VALUE'.
repository/online/component/4.4-1-errata/description: Errata updates for UCS 4.4-1
The description of a repository component.
repository/online/component/4.4-1-errata/version: 4.4
Components can be versioned. This ensures that only components are installed that are compatible with a UCS version. If the variable is empty or unset, all versions of the same major number will be used. If for example UCS 3.2 is installed, all repositories of the component with version numbers 3.0, 3.1 and 3.2 will be used if available. If the variable is set to 'current' all versions of the same major version will be included. Additionally it will block all minor and major upgrades of the installed UCS system until the respective component is also available for the new release. Patch level and errata updates are not affected.
repository/online/component/4.4-1-errata: enabled
In addition to the standard repository additional components can be included. While such components are usually included through the Univention App Center, they can also be configured manually in Univention Configuration Registry. To include a component the option 'repository/online/component/COMPONENTNAME' must be activated. Additional parameters can be set following the scheme 'repository/online/component/COMPONENTNAME/OPTION=VALUE'.
root@ucsmaster:~# ucr search appcenter
appcenter/apps/pkgdb/status: installed
appcenter/apps/pkgdb/ucs: 4.4
appcenter/apps/pkgdb/version: 11.0
appcenter/docker/container/proxy/settings: <empty>
This variable controls whether containers are started with the proxy settings (proxy/http, proxy/https, proxy/no_proxy, /etc/apt/apt.conf.d/80proxy) of the host.
appcenter/docker: enabled
This variable controls whether the App Center supports so-called Docker Apps. Docker Apps run in a container and need a running "docker" service.
appcenter/index/verify: <empty>
This variable allows deactivation of the signature verification for the Appcenter index. Default value is "true".
appcenter/installed: PK
appcenter/prudence/docker/pkgdb: yes
root@ucsmaster:~# ucr search app_center
repository/app_center/blacklist: <empty>
This variable configures a blacklist for the apps of the Univention App Center. If the app's ID, its name or any of its categories shows up in this list, the app will not be shown in the App Center, unless the app can be found in repository/app_center/whitelist, too. The elements of the list are comma separated.
repository/app_center/installed: PK
repository/app_center/server: appcenter.software-univention.de
repository/app_center/whitelist: <empty>
This variable configures a whitelist for the apps of the Univention App Center. If the app's ID, its name or any of its categories shows up in this list, the app will be shown even if it would have been filtered by repository/app_center/blacklist. The elements of the list are comma separated.
root@ucsmaster:~# apt-cache policy ucs-school-umc-installer
N: Paket ucs-school-umc-installer kann nicht gefunden werden.
und
root@ucsmaster:~# apt-get -s install ucs-school-umc-installer
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen… Fertig
E: Paket ucs-school-umc-installer kann nicht gefunden werden.
In einer vorherigen Installation hatte ich unmaintained Paketquellen aktiviert und die Fehlermeldung wurde ergänzt durch einen Hinweis, dass fehlende Paketabhängikeiten die Ursache wären. Python-ucs-school und ucs-school-umc-installer haben fehlende Abhänigkeiten. Es ist sehr verwirrend mit diesen Paketquellen.
Vor einer halben Std. wurde mir ein Update angeboten. Err207. Danach habe ich die letzten von dir beschriebenen Schritte erneut ausgeführt und bekomme nun andere Ausgaben:
Im vorletzten Posting fehlte in den Paketquellen https://appcenter.software-univention.de/univention-repository/4.4/maintained/component ucsschool_20190723074557.
Wenn so etwas passiert in die Dateien /etc/apt/sources.list.d/15_ucs-online-version.list und /etc/apt/sources.list.d/20_ucs-online-component.list
schauen. Dort ist dann ein Kommentar, wenn die Komponente nicht eingebunden werden konnte.
Meistens handelt es sich dabei um Netzwerk- / Firewall- / Proxy- / DNS-Fehler.
geben jetzt wieder aus: kann nicht gefunden werden
Da is doch irgend was faul. Netzwerkfehler/DNS/Proxy/etc. habe ich schon vor mehreren Installationen ausgemerzt.Kann alles pingen und auflösen. Die Dateien: /etc/apt/sources.list.d/15_ucs-online-version.list und /etc/apt/sources.list.d/20_ucs-online-component.list
zeigen auch nichts außer verweise auf Templates. Der Inhalt der beiden Dateien in den Templates ist gleich
repository/online steht auf yes.Den Rest der Ausgabe verstehe ich nicht.
Nachdem ich mich ein wenig bwegt habe auf der Weboberfläche wird mir @school auch nicht mehr als installierte Anwendung angezeigt. Führe ich dir registrierung erneut durch steht sie wieder im Feld installierte Software. Es ist zum Haare raufen.
das univention-app register --do-it ucsschool fügt nur die Paketquellen hinzu und tut so, als ob die App installiert wäre - sie wird dabei aber nicht installiert. Dies war nur zur Prüfung, ob das System überhaupt die Paketquellen lesen kann. Eine richtige Installation benötigt univention-app install ucsschool (oder graphisch über die UMC).
Offenbar kann System die Paketquellen lesen - aber nur ab und zu.
Der Inhalt von /etc/apt/sources.list.d/15_… bzw …/20_… füllt sich nur, wenn die Update-Server gefunden werden können. Beim Verbinden mit diesen scheint es ein Problem zu geben.
