Bug 747110

Summary: squid does not start if adding "memory_pools off" to the squid.conf
Product: [Fedora] Fedora Reporter: Michael Weidner <micha>
Component: squidAssignee: Jiri Skala <jskala>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: aglotov, henrik, jonathansteffan, jskala
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: squid-3.2.0.13-4.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-14 22:24:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Weidner 2011-10-18 20:24:25 UTC 
Description of problem:

When adding "memory_pools off" to the default squid.conf (installed with squid-3.2.0.13-1.fc16.i686), squid does not start anymore.

Output in the cache.log:

2011/10/18 22:13:00 kid1| Starting Squid Cache version 3.2.0.12 for i386-redhat-linux-gnu...
2011/10/18 22:13:00 kid1| Process ID 7493
2011/10/18 22:13:00 kid1| With 1024 file descriptors available
2011/10/18 22:13:00 kid1| Initializing IP Cache...
2011/10/18 22:13:00 kid1| DNS Socket created at [::], FD 7
2011/10/18 22:13:00 kid1| DNS Socket created at 0.0.0.0, FD 8
2011/10/18 22:13:00 kid1| Adding domain at.home from /etc/resolv.conf
2011/10/18 22:13:00 kid1| Adding domain at.home from /etc/resolv.conf
2011/10/18 22:13:00 kid1| Adding nameserver 127.0.0.1 from /etc/resolv.conf
2011/10/18 22:13:00 kid1| ErrorDetailManager.cc(222) parse: WARNING! invalid error detail name: ?X" ?"09_V_ERR_DOMAIN_MISMATCH
2011/10/18 22:13:00 kid1| errorpage.cc(352) loadFromFile:  parse error while reading template file: /usr/share/squid/errors/templates/error-details.txt
2011/10/18 22:13:00 kid1| storeDirWriteCleanLogs: Starting...
2011/10/18 22:13:00 kid1|   Finished.  Wrote 0 entries.
2011/10/18 22:13:00 kid1|   Took 0.00 seconds (  0.00 entries/sec).
FATAL: failed to find or read error text file.
Squid Cache (Version 3.2.0.12): Terminated abnormally.
Version-Release number of selected component (if applicable):

Output in the /var/log/messages:

Oct 18 22:12:47 han squid[7422]: Squid Parent: child process 7424 started
Oct 18 22:12:47 han (squid-1): failed to find or read error text file.
Oct 18 22:12:47 han squid[7422]: Squid Parent: child process 7424 exited with status 1
Oct 18 22:12:50 han squid[7422]: Squid Parent: child process 7427 started
Oct 18 22:12:50 han (squid-1): failed to find or read error text file.
Oct 18 22:12:50 han squid[7422]: Squid Parent: child process 7427 exited with status 1
Oct 18 22:12:53 han squid[7422]: Squid Parent: child process 7432 started
Oct 18 22:12:53 han (squid-1): failed to find or read error text file.
Oct 18 22:12:53 han squid[7422]: Squid Parent: child process 7432 exited with status 1
Oct 18 22:12:56 han squid[7422]: Squid Parent: child process 7445 started
Oct 18 22:12:56 han (squid-1): failed to find or read error text file.
Oct 18 22:12:56 han squid[7422]: Squid Parent: child process 7445 exited with status 1
Oct 18 22:12:59 han squid[7422]: Squid Parent: child process 7493 started
Oct 18 22:13:00 han (squid-1): failed to find or read error text file.
Oct 18 22:13:00 han squid[7422]: Squid Parent: child process 7493 exited with status 1
Oct 18 22:13:00 han squid[7422]: Squid Parent: child process 7493 will not be restarted due to repeated, frequent failures
Oct 18 22:13:00 han squid[7422]: Exiting due to repeated, frequent failures


Version-Release number of selected component (if applicable):

squid-3.2.0.13-1.fc16.i686

How reproducible:

Always

Steps to Reproduce:
1. Add "memory_pools off" to the squid.conf
2. Start squid with "systemctl start squid.service"

  
Actual results:

Squid does not start, see above

Expected results:

Squid should start
Comment 1 Jiri Skala 2011-10-20 18:52:04 UTC 
I've found a buffer overflow but the troubles persist - needs more investigation.
Comment 2 Fedora Update System 2011-10-26 08:42:10 UTC 
squid-3.2.0.13-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/squid-3.2.0.13-2.fc16
Comment 3 Michael Weidner 2011-10-26 10:49:18 UTC 
I can confirm the bug is fixed with squid-3.2.0.13-3.fc16
Comment 4 Fedora Update System 2011-10-26 19:04:52 UTC 
Package squid-3.2.0.13-3.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing squid-3.2.0.13-3.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-14951
then log in and leave karma (feedback).
Comment 5 Fedora Update System 2011-11-04 21:49:07 UTC 
Package squid-3.2.0.13-4.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing squid-3.2.0.13-4.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-14951
then log in and leave karma (feedback).
Comment 6 Fedora Update System 2011-11-14 22:24:09 UTC 
squid-3.2.0.13-4.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.