[ 
https://issues.apache.org/jira/browse/TS-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-1375:
------------------------------

    Fix Version/s: 3.3.1

Kuotai: Is there another bug related this?  If so, make sure we only have one.

Also, I assume this is the same issue you showed me in Hangzhou?  The warnings 
themselves are expected, what's not expected is to run out of sockets / FDs 
unless you truly have a large amount of connections (i.e. what you showed me 
looks like a "leak").
                
> too many connections, throttling
> --------------------------------
>
>                 Key: TS-1375
>                 URL: https://issues.apache.org/jira/browse/TS-1375
>             Project: Traffic Server
>          Issue Type: Bug
>         Environment: centos 6.2 x86_64  ats from git(3.3.0)
>            Reporter: bettydramit
>            Assignee: kuotai
>             Fix For: 3.3.1
>
>
> [Jul 20 09:09:19.787] Server {0x2ad5ddd00060} WARNING: too many open file 
> descriptors, emergency throttling
> [Jul 20 09:09:19.788] Server {0x2ad5ded28700} WARNING: too many connections, 
> throttling
> [Jul 20 09:19:19.823] Server {0x2ad5eb6d2700} WARNING: too many connections, 
> throttling
> [Jul 20 09:19:22.634] Manager {0x7f10bc4327e0} NOTE: [Alarms::signalAlarm] 
> Skipping Alarm: 'too many connections, throttling'
> [TrafficManager] ==> Cleaning up and reissuing signal #15
> [Jul 20 09:21:50.819] Manager {0x7f10bc4327e0} ERROR: [TrafficManager] ==> 
> Cleaning up and reissuing signal #15
> [Jul 20 09:21:50.819] Manager {0x7f10bc4327e0} ERROR:  (last system error 2: 
> No such file or directory)
> NOTE: Traffic Server received Sig 15: Terminated
> [TrafficManager] ==> signal #15

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to