Re: 3.2.0 segfaulting

2012-09-17 Thread Jan-Frode Myklebust
Ok, I see.. Thanks! I'm now building 3.2.0 with 8586b8ec6d6e934233fc195a4f35944cea1d85a4 and will install that on our traffic servers to see if the problem goes away. Will report back if it fixes it or not. -jf

Re: 3.2.0 segfaulting

2012-09-17 Thread Igor Galić
- Original Message - > My stack trace looks *very* similar to the one in TS-1276. Your stack trace (ran through c++filt): NOTE: Traffic Server received Sig 11: Segmentation fault /usr/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0xf500)[0x2b0bc33aa500] /usr/lib64/lib

Re: 3.2.0 segfaulting

2012-09-17 Thread Jan-Frode Myklebust
My stack trace looks *very* similar to the one in TS-1276. -jf

Re: 3.2.0 segfaulting

2012-09-17 Thread Jan-Frode Myklebust
BTW, I do also have these in my records.config: CONFIG proxy.config.http.server_ports STRING 80:ipv4 80:ipv6 443:ipv4:ssl 443:ipv6:ssl CONFIG proxy.config.ssl.number.threads INT 0 CONFIG proxy.config.ssl.SSLv2 INT 0 CONFIG proxy.config.ssl.SSLv3 INT 1 CONFIG proxy.config.ssl.TLSv1 INT 1 CONFIG pro

Re: 3.2.0 segfaulting

2012-09-17 Thread Jan-Frode Myklebust
> This looks a bit like https://issues.apache.org/jira/browse/TS-1198. I saw TS-1198, but believe my certificates are *not* missing.. % grep ^dest_ip /etc/trafficserver/ssl_multicert.config dest_ip=109.247.114.202 ssl_cert_name=/etc/pki/tls/certs/STAR_services_EXAMPLE_net.crt ssl_key_name=/etc/pk

Re: Log.cc and Free-/Open-BSD

2012-09-17 Thread Phil Sorber
On Mon, Sep 17, 2012 at 5:52 AM, Daniel Gruno wrote: > Hello, happy people, > > Lately, I've been wrapping my head around Traffic Server 3.2/3.3 not > running well on FreeBSD. The exact issue is described in TS-993 as well: > 1) When starting TS, it runs up a hefty CPU bill (100% cpu used at all >

Log.cc and Free-/Open-BSD

2012-09-17 Thread Daniel Gruno
Hello, happy people, Lately, I've been wrapping my head around Traffic Server 3.2/3.3 not running well on FreeBSD. The exact issue is described in TS-993 as well: 1) When starting TS, it runs up a hefty CPU bill (100% cpu used at all times), even when idling. 2) It crashes and burns when compiled