You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "George Paul (JIRA)" <ji...@apache.org> on 2010/02/03 20:05:27 UTC
[jira] Resolved: (TS-88) traffic_server not able to setrlimit >
1024 on FDs
[ https://issues.apache.org/jira/browse/TS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Paul resolved TS-88.
---------------------------
Resolution: Fixed
This patch 'TS88_patch2.diff' has been committed to trunk.
-George
> traffic_server not able to setrlimit > 1024 on FDs
> --------------------------------------------------
>
> Key: TS-88
> URL: https://issues.apache.org/jira/browse/TS-88
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0a
> Reporter: Leif Hedstrom
> Assignee: George Paul
> Fix For: 2.0.0a
>
> Attachments: TS88_patch1.diff, TS88_patch2.diff
>
>
> When starting TS, i get a warning / error like this:
> [example_alarm_bin.sh] sent alarm: loki.ogre.com [Tue Dec 15 20:33:55 2009] connection throttle too high, 10000 (throttle) + 192 (internal use) > 8192 (file descriptor limit), using throttle of 8000
> stracing traffic_manager, I see:
> root@loki 332/1 # strace -f -e trace=setrlimit ./bin/traffic_manager 2>&1 | grep setrlimit
> [pid 24114] setrlimit(RLIMIT_CPU, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0
> [pid 24114] setrlimit(RLIMIT_FSIZE, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0
> [pid 24114] setrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
> [pid 24126] setrlimit(RLIMIT_CORE, {rlim_cur=0, rlim_max=0}) = 0
> [pid 24126] setrlimit(RLIMIT_NOFILE, {rlim_cur=10000, rlim_max=10000}) = -1 EPERM (Operation not permitted)
> The last call is from traffic_server, indicating that it's not able to setrlimit() to 10000. This would only happen (I think) if at this point it's running as a non-root user. If I run traffic_server as root directly, I don't have this problem (i.e. when it calls setrlimit() as root, it works fine).
> This is using a standard installation in /usr/local.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.