After enabling the debug mode I got seg fault in
/usr/local/var/log/trafficserver/traffic.out

 

 

NOTE: Traffic Server received Sig 11: Segmentation fault

/usr/local/bin/traffic_server - STACK TRACE:

/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b30fc503cb0]

/usr/local/bin/traffic_server(_ZN23RamCacheCLFUSCompressor9mainEventEiP5Even
t+0xa4)[0x65d104]

/usr/local/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x86)[0x6a
45c6]

/usr/local/bin/traffic_server(_ZN7EThread7executeEv+0x31b)[0x6a4ebb]

/usr/local/bin/traffic_server[0x6a33b2]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b30fc4fbe9a]

/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b30fe3f5cbd]

[E. Mgmt] log ==> [TrafficManager] using root directory '/usr/local'

 

From: Leif Hedstrom [mailto:[email protected]] 
Sent: maandag 3 december 2012 17:23
To: [email protected]
Cc: Aleksandrs Andrijekno
Subject: Re: ATS raw disk problem

 

On 12/3/12 8:42 AM, Aleksandrs Andrijekno wrote:

Hi,

 

I got ATS 3.3.1 configured with raw disks of 3TB.

 

OS: Ubuntu 12 (Linux edge002 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15
10:48:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux)

 

I'm facing the problem of ATS not being able to handle more than 1 HDD of
3TB.

 

If I add more than 1 HDD ATS is reserving memory and it is killing itself in
~20GB of RAM and restarting again and again.


Go check the archives for an explanation on how disk cache size correlates
to RAM consumption.




 

No errors in diags.log only in manage.log:

 

[Dec  3 16:30:25.473] {0x7f301e55d740} STATUS: opened
/usr/local/var/log/trafficserver/manager.log

[Dec  3 16:30:25.473] {0x7f301e55d740} NOTE: updated diags config

[Dec  3 16:30:25.475] Manager {0x7f301e55d740} NOTE:
[ClusterCom::ClusterCom] Node running on OS: 'Linux' Release:
'3.2.0-34-generic'


Now, it sounds like you have enough memory to support these large drives.
So, I can't tell from the information given why you are seeing server
restarts. ATS typically would kill / restart itself only if the
traffic_server process is not responding to the synthetic health checks that
the system uses. 

-- Leif

Reply via email to