Bug 1336940

Summary:	Disable squid systemd unit start/stop timeouts
Product:	Red Hat Enterprise Linux 7	Reporter:	Robert Marcano <robert>
Component:	squid	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	Jan Houska <jhouska>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	isenfeld, thozza
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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 21:17:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Robert Marcano 2016-05-17 20:48:21 UTC

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 21:17:56 UTC

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