Univention Bugzilla – Bug 35421
Squid3 without cache, squid restart failed
Last modified: 2017-08-08 07:11:02 CEST
+++ This bug was initially created as a clone of Bug #33332 +++ Hallo zusammen Wir würden gerne Squid3 ohne Cache verwenden. Das funktioniert gemäss UCR Variable folgendermassen: ucr set squid/cache="false" Danach werden folgende Einträge gemacht in /etc/squid3/squid.conf: cache deny all cache_dir null /tmp Ein Reload funktioniert: /etc/init.d/squid3 reload Reloading Squid HTTP Proxy 3.x configuration files. done. Ein restart leider nicht: /etc/init.d/squid3 restart Restarting Squid HTTP Proxy 3.x: squid3FATAL: Bungled squid.conf line 40: cache_dir null /tmp Squid Cache (Version 3.1.6): Terminated abnormally. CPU Usage: 0.004 seconds = 0.000 user + 0.004 sys Maximum Resident Size: 20672 KB Page faults with physical i/o: 0 failed! Squid verweist ebenfalls auch auf diese Einstellung: http://wiki.squid-cache.org/SquidFaq/CompleteFaq#SquidFaq.2BAC8-ConfiguringSquid.Can_I_make_Squid_proxy_only.2C_without_caching_anything.3F Wenn man im die UCR Variable wieder korrigiert (ucr set squid/cache="yes") und danach die Datei /etc/squid3/local.conf mit folgendem Eintrag erweitert, dann geht es: # add local config here cache deny all Vielen Dank für Eure Hilfe. Grüsse, RolandB
The problem still seems to appear: From bug 33332#c5: > Hallo zusammen > > Wir haben ein frisch installierte UCS3.2-2 mit ucs@school R3.2. > root@sr-server-01:~# ucr set squid/cache="false" > Setting squid/cache > File: /etc/squid3/squid.conf > root@sr-server-01:~# /etc/init.d/squid3 restart > Restarting Squid HTTP Proxy 3.x: squid3FATAL: Bungled squid.conf line 35: cache_dir null /tmp > Squid Cache (Version 3.1.6): Terminated abnormally. > CPU Usage: 0.008 seconds = 0.008 user + 0.000 sys > Maximum Resident Size: 20608 KB > Page faults with physical i/o: 0 > failed! > > Das selbe Problem besteht immer noch. > > Grüsse, RolandB
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
There is a Customer ID set so I set the flag "Enterprise Customer affected".
This issue has been filed against UCS 3.2. UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.