Project

General

Profile

Actions

Bug #9185

closed

incorrect Centos 6.5 fastcgi package

Added by Yehuda Sadeh over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The fastcgi package that is being installed is, or either based off: fcgi-2.4.0-10.el6.x86_64. Not 100% sure that it even has our modifications to it, but in any case, it's based on 2.4.0 and missing the -idle-timeout option. We need to build a newer one that is based of 2.4.7.


Related issues 1 (0 open1 closed)

Related to devops - Bug #9190: idle times out do not work on ubuntu preciseResolved08/21/2014

Actions
Actions #1

Updated by Yuri Weinstein over 9 years ago

This should fix #9169

Actions #2

Updated by Sage Weil over 9 years ago

  • Priority changed from Normal to Urgent
Actions #3

Updated by Sandon Van Ness over 9 years ago

So this problem is with the fcgi package not mod_fastcgi?

Actions #4

Updated by Dan Mick over 9 years ago

fcgi? how does that even enter into it? I thought our work was only with fastcgi?

Is this on teuthology, or customer systems?

Actions #5

Updated by Sage Weil over 9 years ago

(09:51:57 AM) /montreal: mod_fastcgi-2.4.7-1.ceph.el6.x86_64
(09:52:15 AM) /montreal: fcgi-2.4.0-10.el6.x86_64

both of these were installed... they are probably misnamed or something

i will reproduce the environment

Actions #6

Updated by Sage Weil over 9 years ago

  • Assignee set to Sage Weil
Actions #7

Updated by Sage Weil over 9 years ago

  • Status changed from New to In Progress
Actions #8

Updated by Sage Weil over 9 years ago

ok, the idle timeout is working fine.. i can pause the radosgw process (kill -STOP) and curl will block for well over 30s. conversely, if i change idle timeout to 10s, it returns with a 500 after exactly 10s.

but s3tests are still erroring out. there must be a client-side boto timeout?

Actions #9

Updated by Sage Weil over 9 years ago

  • Status changed from In Progress to Rejected

this isn't the package, it's boto timeouts.

we can now adjust them up some, but there seems to be a limit of ~3-4 minutes before we get a 'timed out' error anyway.

Actions

Also available in: Atom PDF