Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1361626

Summary: squid crashes with clients trying to ftp PUT a 0 bytes file
Product: Red Hat Enterprise Linux 7 Reporter: Felipe Zipitría <fzipi>
Component: squidAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Jan Houska <jhouska>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.4CC: jhouska, jkejda, mfrodl, thozza
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: squid-3.5.20-6.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 21:35:36 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:
Attachments:
Description Flags
Patch from upstream. none

Description Felipe Zipitría 2016-07-29 14:55:10 UTC
Description of problem:

In version from upstream, squid 3.3.8 has a bug which keeps crashing the proxy server.

2016/07/25 11:56:36| assertion failed: Server.cc:246: "r->body_pipe != NULL" 2016/07/25 11:56:40| Starting Squid Cache version 3.3.8 for x86_64-redhat-linux-gnu...

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

3.3.8

How reproducible: Always

Steps to Reproduce:
1. generate empty file ( e.g. : > empty.txt)
2. export ftp_proxy=http://<yourproxy>:3128
3. lftp -c 'open <yourftphost>; put empty.txt'

Actual results: Squid server crashes and restart. Your lftp client willl try to do the same in 30 seconds... so it will keep crashing your server until yo do something.


Expected results: Create an empty file in the ftp server, and the squid server keeps working.


Additional info: upstream already have corrected this bug: http://bugs.squid-cache.org/show_bug.cgi?id=3498

Comment 1 Felipe Zipitría 2016-07-29 15:03:07 UTC
Created attachment 1185590 [details]
Patch from upstream.

Attachment applied to CentOS version of the package, and tested ok there.

Comment 4 Felipe Zipitría 2016-08-01 14:42:59 UTC
BTW, this problem happens also in squid 3.1.23 in RHEL 6. We ended updating our servers to 7 hoping the new version will address this problem, without success.

Comment 9 errata-xmlrpc 2017-08-01 21:35:36 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://access.redhat.com/errata/RHBA-2017:2174