Hello Alan,
Thanks for the answer. I'll have a look on TS-2564.
Regarding traffic.out, yes, I've got some more informations:
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x2b95c370e030]
/usr/bin/traffic_server(_Z12ink_aio_readP11AIOCallbacki+0x29)[0x2b95c15cefd9]
/usr/bin/traffic_server(_ZN3Vol10evac_rangeElli+0x225)[0x2b95c15bd235]
/usr/bin/traffic_server(_ZN3Vol8aggWriteEiPv+0x52e)[0x2b95c15bdade]
/usr/bin/traffic_server(_ZN7CacheVC12updateVectorEiP5Event+0x2cb)[0x2b95c15c098b]
/usr/bin/traffic_server(_ZN7CacheVC13openWriteMainEiP5Event+0x5a7)[0x2b95c15c3077]
/usr/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x9b)[0x2b95c1603e4b]
/usr/bin/traffic_server(_ZN7EThread7executeEv+0x53b)[0x2b95c160467b]
/usr/bin/traffic_server(+0x2b721a)[0x2b95c160321a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x2b95c3705b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b95c439c0ed]
I wonder why I did not think about looking in that file before :-/
Seems that AIO is somewhat involved. I've enable AIO support which might
not be the best idea on Debian Wheezy.
Since I didn't had this option with 4.0.2, I'll try without it on 4.2.
Regards,
Jean-Baptiste
On 09/04/2014 15:30, Alan M. Carroll wrote:
> Jean,
>
> Please look at TS-2564. Also, the traffic.out logfile should have more
> details
> on the crash.
>
> Wednesday, April 9, 2014, 2:25:57 AM, you wrote:
>
>> Hello,
>> I tried to upgrade a 2 server's cluster from ATS 4.0.2 to 4.2.0.
>> Everything is fine on one server when to other one keeps crashing with
>> either with segfault:
>
>> Manager {0x7ff6e0fe5720} ERROR: [LocalManager::pollMgmtProcessServer]
>> Server Process terminated due to Sig 11: Segmentation fault
>
>> or read errors:
>
>> FATAL: [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
>
>> I have 2 plugins enabled: stats_over_http.so and gzip.so
>
>> Disabling plugins does not improve situation.
>
>> Is there a way to get more details in logs ?
>> Could this be caused by somewhat corrupted data on disk ?
>
>> Any help appreciated,
>> Regards,
>> Jean-Baptiste
>
>
>
> !DSPAM:53454bb718302164719579!
>
>
