Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1336940 - Disable squid systemd unit start/stop timeouts
Disable squid systemd unit start/stop timeouts
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: squid (Show other bugs)
7.2
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Luboš Uhliarik
Jan Houska
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-17 16:48 EDT by Robert Marcano
Modified: 2016-11-03 17:17 EDT (History)
2 users (show)

See Also:
Fixed In Version: squid-3.5.10-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 17:17:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2600 normal SHIPPED_LIVE Moderate: squid security, bug fix, and enhancement update 2016-11-03 08:12:25 EDT

  None (edit)
Description Robert Marcano 2016-05-17 16:48:21 EDT
There are problems with squid cache swap.state file when they are killed by systemd when the default timeout is reached. See Fedora Bug #855111.

It was fixed on that bug by disabling the timeout on the unit file adding

  [Service]
  ...
  TimeoutSec=0

The problem can make the system to fill all the disk, and when using XFS (the EL 7 default) it can fill the entire root partition. At least ext4 has reserved blocks for root to make the system bootable and remote manageable.

On one occasion I experienced a XFS corruption with this problem when the disk filled out in minutes. The system was unresponsive to shutdown commands. the next boot the disk was full, with no file using that space, an offline xfs_repair was needed to recover the disk space.
Comment 9 errata-xmlrpc 2016-11-03 17:17:56 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2600.html

Note You need to log in before you can comment on or make changes to this bug.