[jira] [Commented] (TS-1528) ats_memalign: couldn't allocate -548249600 bytes in Vol::init()

["Jack Bates (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490154#comment-13490154 ] 

Jack Bates commented on TS-1528:
--------------------------------

Thank you very much for your support James Peach, and for the support I received in IRC. Traffic Server is running on a dedicated EeeBox B202 machine, with an Intel Atom N270 processor (32-bit) and 1 GB of RAM

Thanks a lot for these improved log messages. I haven't yet had a chance to re-test master, but expect they will make it much easier to understand problems like this in future. I will re-test and post the output

With help on IRC, I was able to avoid this integer overflow by increasing proxy.config.cache.min_average_object_size to 16K, but when I started Traffic Server, the system load average would climb because Traffic Server used all available memory, and eventually segfaulted. I set proxy.config.cache.ram_cache.size to zero and increased proxy.config.cache.min_average_object_size until it used less than all available memory. It's been running okay for about a week now, with proxy.config.cache.ram_cache.size zero and proxy.config.cache.min_average_object_size 64K

I'm now experimenting with re-enabling a 256M RAM cache
                
> ats_memalign: couldn't allocate -548249600 bytes in Vol::init()
> ---------------------------------------------------------------
>
>                 Key: TS-1528
>                 URL: https://issues.apache.org/jira/browse/TS-1528
>             Project: Traffic Server
>          Issue Type: Bug
>    Affects Versions: 3.2.0
>         Environment: Debian testing (wheezy) on i686
>            Reporter: Jack Bates
>            Assignee: James Peach
>
> I consistently get the following error whenever I try to start Traffic Server (release 3.2.0). Yesterday I built Traffic Server from Git HEAD (34a2ba) to check if it behaves any differently, but I consistently reproduce this same error whenever I try to start it, too
> Here's my configuration, which is pretty minimal: http://nottheoilrig.com/trafficserver/201210120/
> What details can I provide to help debug this? James Peach suggested attaching some kind of dump of the volume header: http://mail-archives.apache.org/mod_mbox/trafficserver-users/201210.mbox/%3C9ED91AE2-2F52-4BDB-9088-E14D40642C34%40apache.org%3E
> {code}
> administrator@debian$ TS_ROOT=/home/administrator/trafficserver trafficserver/traffic_server
> [TrafficServer] using root directory '/home/administrator/trafficserver'
> FATAL: ats_memalign: couldn't allocate -548249600 bytes at alignment 4096 - insufficient memory
> trafficserver/traffic_server - STACK TRACE:
> trafficserver/libtsutil.so.3(+0x1075b)[0xb76d075b]
> trafficserver/libtsutil.so.3(ats_memalign+0xa1)[0xb76d34c1]
> trafficserver/traffic_server(_ZN3Vol4initEPcxxb+0x282)[0x827bd52]
> trafficserver/traffic_server(_ZN5Cache4openEbb+0x5d8)[0x827dc48]
> trafficserver/traffic_server(_ZN14CacheProcessor15diskInitializedEv+0x323)[0x827e0d3]
> trafficserver/traffic_server(_ZN9CacheDisk9openStartEiPv+0x483)[0x828c9c3]
> trafficserver/traffic_server(_ZN19AIOCallbackInternal11io_completeEiPv+0x25)[0x8280a75]
> trafficserver/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8b)[0x830343b]
> trafficserver/traffic_server(_ZN7EThread7executeEv+0x723)[0x8304003]
> trafficserver/traffic_server(main+0x178d)[0x80c572d]
> /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xb7039e46]
> trafficserver/traffic_server[0x80cabdd]
> administrator@debian:~$ 
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira