Univention Bugzilla – Bug 43581
UCS4.2: squidguard update fails
Last modified: 2017-04-04 18:28:55 CEST
+++ This bug was initially created as a clone of Bug #43580 +++ #### It is possible this bug get automatically fixed, by fixing Bug #43580. #### During an Upgrade from UCS 4.1 with UCS@school 4.1R2 v10 installed to UCS 4.2: squidguard (1.5-4) wird eingerichtet ... Neue Version der Konfigurationsdatei /etc/squidguard/squidGuard.conf.default wird installiert ... Rebuild SquidGuard database - this can take a while. ######################################################################## Welcome to Univention Corporate Server (UCS)! This system is not completely configured yet. To finalise the configuration of this system you need to login to the web-based Univention Management Console which can be reached with a web browser under the following URL https://10.20.30.5/ The login at the Univention Management Console needs to be done with the user "root" and the password you entered during installation. UMC uses numerous Javascript and CSS functions to display the web interface. Some of these features are unavailable in older browsers. The following web browsers are supported: - Chrome as of version 37 or later - Firefox as of version 38 or later - Internet Explorer as of version 11 or later - Safari and Safari Mobile as of version 9 ######################################################################## This account is currently not available. dpkg: Fehler beim Bearbeiten des Paketes squidguard (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
When patching squidguard don't forget the 001-added_dbtemp_option patch.
r17251: failed patch r17252: success migrating 001-added_dbtemp_option.patch to UCS 4.2 r17255: failed patch r17257: success backporting update-squidguard from 1.5-5 to fix this bug r77223: changelog entry Having fixed this and Bug #43580, an upgrade from UCS 4.1-4 with UCS@school 4.1 R2 v9 to UCS 4.2 with UCS@school 4.2 succeeded on a singleserver. (Starting Jenkins 4.1 to 4.2 update jobs now.) Package: squidguard Version: 1.5-4A~4.2.0.201703021035 Branch: ucs_4.2-0
The problem was, that the rebuild of the SquidGuard database was done using a login shell - which is disabled since Jessie. The fix from upstreams 1.5-5 release has been backported to patch squidguard/4.2-0-0-ucs/1.5-4/002-proxy-user-nologin.patch.
(In reply to Daniel Tröder from comment #2) > r17251: failed patch → squidguard-1.5/debian/patches/series changed, that's why r17251 failed > r17252: success migrating 001-added_dbtemp_option.patch to UCS 4.2 → this change removed the comment to the patch → readded the comment via r17426 > r17255: failed patch > r17257: success backporting update-squidguard from 1.5-5 to fix this bug → OK > r77223: changelog entry → OK > Package: squidguard > Version: 1.5-4A~4.2.0.201703021035 > Branch: ucs_4.2-0 → Patches applied > Applying patch 001-added_dbtemp_option.patch using -p1 > Output of the patch process: > patching file debian/patches/15_add_option_dbtemp.patch > patching file debian/patches/series > > OK > Applying patch 002-proxy-user-nologin.patch using -p1 > Output of the patch process: > patching file debian/update-squidguard > > OK → Package has been built. ??: functional test
root@master:~# strings /usr/bin/squidGuard | grep dbhome dbhome root@master:~# strings /usr/bin/squidGuard | grep dbtemp dbtemp root@master:~# /usr/sbin/update-squidguard Rebuild SquidGuard database - this can take a while. root@master:~#
UCS 4.2 has been released: https://docs.software-univention.de/release-notes-4.2-0-en.html https://docs.software-univention.de/release-notes-4.2-0-de.html If this error occurs again, please use "Clone This Bug".