Hi - not sure if i have to use English or if German is also OK - please let me know.
Second - I’m just a web interface hero - not command line - so please keep the explanation simple
Background:
Since about 15 months I’m using UCS - and it is great platform for people like me.
I started with the core system - added samba for integrate my windows systems - and enabled mail based on Dovecot (UCS packet) - finally I added OX App Suit with OX Documents. All great and simple.
To “backup” the core system, I installed a DC backup. Still all fine.
Than 4.2 was offered - and my trouble started.
The upgrade to 4.2 itself on both systems looked good - just web-interface timed out or was coming up with some error messages. I could still work - and my hope was that an upgrade would fix this soonest.
At one point in time, I found out, that I was unable to download the OX mail-client for windows “emclientforox/emclient_appsuite_v6.0.26257.msi”. The file is not where it should be - and even a full search couldn’t find the file on the core system. The OX-drive file is where it should be and can be downloaded. Second issues on OX is - if I share files with someone, the shared link is a http link - but all my communication is based on https - and I was unable to find in the UCS registry something to change this from http to https.
Now - even after following the UCS update process - the web-interface is coming with error messages. And finally now, UCS is unable to offer the latest update packet on the core system (on the DC backup it worked).
Where I need your help:
I’m currently at the point, where I’m not sure if it would not be better to install a new core system (and a DC backup) directly based on 4.2 - or to work on fixing the issues.
Option 1 --> building a new UCS core - plus a new DC backup all based on 4.2:
Building the two systems is a quick and simple task. The challenge for me is just on how to keep all the user/computer accounts, the samba AD integration and maybe most important - how to keep all emails (incl the accounts).
Option 2 --> fixing issue by issue by keeping the existing systems:
In general a good good thing - but option 1 would give me some advantages --> fresh system - and I would know also for future on how to migrate services from one system to an other.
Below as an example the message from the UCS core after opening the “Software update” page.
PS: Now after about 8 to 10 try over some days and some reboots, I’m getting the option to install the latest update packet (errata 26). Let’s see how it goes - system finished with no errors - but after reboot, the “Software update” pages has the same issue (timeout - but showing errata 26 is installed).
Any feedback is more than welcome - maybe we focus on option 1 (I hope that is the long term better one).
FYI: As a new user I’, just allowed to add max two links - what doesn’t worked here. So to be able to publish the answer - I have added a SPACE after each https:// - so the link itself will not work (and not seen as a link). The two http:// links are untouched.
Some more lines :
root@vmucs41-rd1:~# cat /etc/apt/sources.list.d/*
Warning: This file is auto-generated and might be overwritten by
univention-config-registry.
Please edit the following file(s) instead:
Warnung: Diese Datei wurde automatisch generiert und kann durch
univention-config-registry überschrieben werden.
Bitte bearbeiten Sie an Stelle dessen die folgende(n) Datei(en):
/etc/univention/templates/files/etc/apt/sources.list.d/15_ucs-online-version.list
Hi - I did two commands - the one from yesterday (you assumed the server is temporary down) and the new command.
repeat command from yesterday
root@vmucs41-rd1:~# cat /etc/apt/sources.list.d/*
#Warning: This file is auto-generated and might be overwritten by
# univention-config-registry.
# Please edit the following file(s) instead:
#Warnung: Diese Datei wurde automatisch generiert und kann durch
# univention-config-registry überschrieben werden.
# Bitte bearbeiten Sie an Stelle dessen die folgende(n) Datei(en):
#
# /etc/univention/templates/files/etc/apt/sources.list.d/15_ucs-online-version.list
#
deb https://updates.software-univention.de/4.0/maintained/ 4.0-0/all/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-0/amd64/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-1/all/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-1/amd64/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-2/all/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-2/amd64/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-3/all/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-3/amd64/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-4/all/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-4/amd64/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-5/all/
deb https://updates.software-univention.de/4.0/maintained/ 4.0-5/amd64/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-0/all/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-0/amd64/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-1/all/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-1/amd64/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-2/all/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-2/amd64/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-3/all/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-3/amd64/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-4/all/
deb https://updates.software-univention.de/4.1/maintained/ 4.1-4/amd64/
deb https://updates.software-univention.de/4.2/maintained/ 4.2-0/all/
deb https://updates.software-univention.de/4.2/maintained/ 4.2-0/amd64/
#Warning: This file is auto-generated and might be overwritten by
# univention-config-registry.
# Please edit the following file(s) instead:
#Warnung: Diese Datei wurde automatisch generiert und kann durch
# univention-config-registry überschrieben werden.
# Bitte bearbeiten Sie an Stelle dessen die folgende(n) Datei(en):
#
# /etc/univention/templates/files/etc/apt/sources.list.d/20_ucs-online-component.list
#
deb https://appcenter.software-univention.de/univention-repository/4.2/maintained/component/ oxseforucs_20170123162817/all/
deb https://appcenter.software-univention.de/univention-repository/4.2/maintained/component/ oxseforucs_20170123162817/amd64/
deb https://appcenter.software-univention.de/univention-repository/4.1/maintained/component/ oxseforucs_20170123162817/all/
deb https://appcenter.software-univention.de/univention-repository/4.1/maintained/component/ oxseforucs_20170123162817/amd64/
# Configuration error: component not found: oxoutlook783
# Configuration error: component not found: oxdrive783
deb https://appcenter.software-univention.de/univention-repository/4.2/maintained/component/ open-xchange-text_20160901105322/all/
deb https://appcenter.software-univention.de/univention-repository/4.2/maintained/component/ open-xchange-text_20160901105322/amd64/
deb https://appcenter.software-univention.de/univention-repository/4.1/maintained/component/ open-xchange-text_20160901105322/all/
deb https://appcenter.software-univention.de/univention-repository/4.1/maintained/component/ open-xchange-text_20160901105322/amd64/
deb https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/
deb https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/amd64/
# Configuration error: component not found: oxdrivehelp200
# Configuration error: component not found: oxmobility783
# Configuration error: component not found: oxofficeweb783
# Configuration error: component not found: oxusm783
deb https://updates.software-univention.de/4.2/maintained/component/ 4.2-0-errata/all/
deb https://updates.software-univention.de/4.2/maintained/component/ 4.2-0-errata/amd64/
# Configuration error: component not found: oxdocconvapi783
# Configuration error: component not found: oxdocconv783
# Configuration error: component not found: backend783
# Configuration error: component not found: oxreaderengine783
# Configuration error: component not found: oxoffice783
# Configuration error: component not found: frontend783
# Configuration error: component not found: frontend62213
I can repeat the command again and again - but I’m getting all time the same information back - even if I’m using this command on the DC backup one.
The only difference between the two is, that it takes longer on the core system before I’m getting information back - specially for the second line I have to wait about 1,5 secs and than about 8 to 10 sec before the command prompt comes back.
You mentioned “Unluckily I can’t check it because the folders are password protected. Maybe you try the commands again.” - so what can we do? Is ROOT not GOD on the system?
I think, what SirTux meant was, that the repository is password protected, since you need a subscription of some sort to access it. In the UMC under OX-Licence management you should be able to access the repositories too.
Sorry - as mentioned - I’m just a web-interface hero
I looked in UMC under “System” --> “OX License Management”. But there I can just add an “Customer ID” by following the “Password”.
I don’t have a personal OX license - I’m just using the parts that are shared for free and developed with UCS.
I had to recreate this in my testenvironment: as long as I did not configure OX via the ox license management, the repositories were not available. I had the same problem as you.
Sorry! That’s a spam preventing limit. However, you should be able to use the preformatted layout for console outputs and file contents - this way it’s more readable and the repository URLs will not be converted to clickable hyperlinks and therefore not count against the anti-spam limit.
Have a look at this article for details:
Uh, what I meant was, that the repositories are not available if you do not have a OX license. OpenXchange is not free, there is only free testversion available.
I did some investigation if OX is free or not - and it look like it is not easy to answer.
I just had a phone call with someone from IKU “http://www.iku-systems.de/”. He confirmed that there is a free version but war not able to explain on the phone what is part of this free version. He will now investigate and come back to me via eMail. So let’s see what is part of the free deal.
Back to the general issues (e.g. having problems to update the system). This part is now much better - after installing all the UCS patches. But still the web interfaces come with some error messages (see above status code 502).
: