[jira] [Commented] (TS-968) During/after daily logfile roll, trafficserver seg faults (Sig 11)

2012-03-01 Thread Zhao Yongming (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13220136#comment-13220136
 ] 

Zhao Yongming commented on TS-968:
--

is this issue still valid for now? can you test if it still valid with current 
stable release and the current git master tree?

 During/after daily logfile roll, trafficserver seg faults (Sig 11)
 --

 Key: TS-968
 URL: https://issues.apache.org/jira/browse/TS-968
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Affects Versions: 3.0.1
 Environment: Ubuntu 10.10, 2.6.35-24-virtual
Reporter: Drew Rothstein
 Fix For: 3.1.4


 Every day at 00:00:00 after/during the log file roll, I see a segfault.  Here 
 are the past couple days:
 [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile 
 /usr/local/var/log/trafficserver/error.log was rolled to 
 /usr/local/var/log/trafficserver/error.log_trafficserver02.20110921.00h00m06s-20110922.00h00m00s.old.
 [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile 
 /usr/local/var/log/trafficserver/squid.log was rolled to 
 /usr/local/var/log/trafficserver/squid.log_trafficserver02.20110921.00h00m01s-20110922.00h00m00s.old.
 [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile 
 /usr/local/var/log/trafficserver/extended2.log was rolled to 
 /usr/local/var/log/trafficserver/extended2.log_trafficserver02.20110921.00h00m01s-20110922.00h00m00s.old.
 NOTE: Traffic Server received Sig 11: Segmentation fault
 /usr/local/bin/traffic_server - STACK TRACE: 
 [Sep 22 00:00:17.729] Manager {140722071643936} FATAL: 
 [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
 [Sep 22 00:00:17.729] Manager {140722071643936} FATAL:  (last system error 
 104: Connection reset by peer)
 [Sep 22 00:00:17.730] Manager {140722071643936} NOTE: 
 [LocalManager::mgmtShutdown] Executing shutdown request.
 [Sep 22 00:00:17.730] Manager {140722071643936} NOTE: 
 [LocalManager::processShutdown] Executing process shutdown request.
 [Sep 22 00:00:17.730] Manager {140722071643936} ERROR: 
 [LocalManager::sendMgmtMsgToProcesses] Error writing message
 [Sep 22 00:00:17.730] Manager {140722071643936} ERROR:  (last system error 
 32: Broken pipe)
 [E. Mgmt] log == [TrafficManager] using root directory '/usr/local'
 [Sep 22 00:00:17.786] {140131209512736} STATUS: opened 
 /usr/local/var/log/trafficserver/manager.log
 [Sep 22 00:00:17.786] {140131209512736} NOTE: updated diags config
 [Sep 22 00:00:17.805] Manager {140131209512736} NOTE: 
 [ClusterCom::ClusterCom] Node running on OS: 'Linux' Release: 
 '2.6.35-24-virtual'
 [Sep 22 00:00:17.805] Manager {140131209512736} NOTE: 
 [LocalManager::listenForProxy] Listening on port: 80
 [Sep 22 00:00:17.805] Manager {140131209512736} NOTE: [TrafficManager] Setup 
 complete
 [Sep 22 00:00:18.827] Manager {140131209512736} NOTE: 
 [LocalManager::startProxy] Launching ts process
 [TrafficServer] using root directory '/usr/local'
 [Sep 22 00:00:18.849] Manager {140131209512736} NOTE: 
 [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
 [Sep 22 00:00:18.849] Manager {140131209512736} NOTE: [Alarms::signalAlarm] 
 Server Process born
 [Sep 22 00:00:19.874] {47510015031936} STATUS: opened 
 /usr/local/var/log/trafficserver/diags.log
 [Sep 22 00:00:19.874] {47510015031936} NOTE: updated diags config
 [Sep 22 00:00:19.879] Server {47510015031936} NOTE: cache clustering disabled
 [Sep 22 00:00:19.908] Server {47510015031936} NOTE: cache clustering disabled
 [Sep 22 00:00:20.019] Server {47510015031936} NOTE: logging initialized[7], 
 logging_mode = 3
 [Sep 22 00:00:20.032] Server {47510015031936} NOTE: traffic server running
 [Sep 22 00:00:20.045] Server {47510028859136} NOTE: cache enabled
 [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile 
 /usr/local/var/log/trafficserver/error.log was rolled to 
 /usr/local/var/log/trafficserver/error.log_trafficserver02.20110922.00h00m11s-20110923.00h00m00s.old.
 [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile 
 /usr/local/var/log/trafficserver/squid.log was rolled to 
 /usr/local/var/log/trafficserver/squid.log_trafficserver02.20110922.00h00m06s-20110923.00h00m00s.old.
 [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile 
 /usr/local/var/log/trafficserver/extended2.log was rolled to 
 /usr/local/var/log/trafficserver/extended2.log_trafficserver02.20110922.00h00m06s-20110923.00h00m00s.old.
 NOTE: Traffic Server received Sig 11: Segmentation fault
 /usr/local/bin/traffic_server - STACK TRACE: 
 [Sep 23 00:00:14.668] Manager {140131209512736} FATAL: 
 [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
 [Sep 23 00:00:14.668] Manager {140131209512736} FATAL:  (last system error 
 104: 

[jira] [Commented] (TS-968) During/after daily logfile roll, trafficserver seg faults (Sig 11)

2011-10-11 Thread Leif Hedstrom (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13125451#comment-13125451
 ] 

Leif Hedstrom commented on TS-968:
--

Hmmm, I use log rotation all the time, and never see this. Can you give us a 
stack trace from this crash?

 During/after daily logfile roll, trafficserver seg faults (Sig 11)
 --

 Key: TS-968
 URL: https://issues.apache.org/jira/browse/TS-968
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Affects Versions: 3.0.1
 Environment: Ubuntu 10.10, 2.6.35-24-virtual
Reporter: Drew Rothstein
 Fix For: 3.1.1


 Every day at 00:00:00 after/during the log file roll, I see a segfault.  Here 
 are the past couple days:
 [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile 
 /usr/local/var/log/trafficserver/error.log was rolled to 
 /usr/local/var/log/trafficserver/error.log_trafficserver02.20110921.00h00m06s-20110922.00h00m00s.old.
 [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile 
 /usr/local/var/log/trafficserver/squid.log was rolled to 
 /usr/local/var/log/trafficserver/squid.log_trafficserver02.20110921.00h00m01s-20110922.00h00m00s.old.
 [Sep 22 00:00:00.000] Server {47590596851456} STATUS: The logfile 
 /usr/local/var/log/trafficserver/extended2.log was rolled to 
 /usr/local/var/log/trafficserver/extended2.log_trafficserver02.20110921.00h00m01s-20110922.00h00m00s.old.
 NOTE: Traffic Server received Sig 11: Segmentation fault
 /usr/local/bin/traffic_server - STACK TRACE: 
 [Sep 22 00:00:17.729] Manager {140722071643936} FATAL: 
 [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
 [Sep 22 00:00:17.729] Manager {140722071643936} FATAL:  (last system error 
 104: Connection reset by peer)
 [Sep 22 00:00:17.730] Manager {140722071643936} NOTE: 
 [LocalManager::mgmtShutdown] Executing shutdown request.
 [Sep 22 00:00:17.730] Manager {140722071643936} NOTE: 
 [LocalManager::processShutdown] Executing process shutdown request.
 [Sep 22 00:00:17.730] Manager {140722071643936} ERROR: 
 [LocalManager::sendMgmtMsgToProcesses] Error writing message
 [Sep 22 00:00:17.730] Manager {140722071643936} ERROR:  (last system error 
 32: Broken pipe)
 [E. Mgmt] log == [TrafficManager] using root directory '/usr/local'
 [Sep 22 00:00:17.786] {140131209512736} STATUS: opened 
 /usr/local/var/log/trafficserver/manager.log
 [Sep 22 00:00:17.786] {140131209512736} NOTE: updated diags config
 [Sep 22 00:00:17.805] Manager {140131209512736} NOTE: 
 [ClusterCom::ClusterCom] Node running on OS: 'Linux' Release: 
 '2.6.35-24-virtual'
 [Sep 22 00:00:17.805] Manager {140131209512736} NOTE: 
 [LocalManager::listenForProxy] Listening on port: 80
 [Sep 22 00:00:17.805] Manager {140131209512736} NOTE: [TrafficManager] Setup 
 complete
 [Sep 22 00:00:18.827] Manager {140131209512736} NOTE: 
 [LocalManager::startProxy] Launching ts process
 [TrafficServer] using root directory '/usr/local'
 [Sep 22 00:00:18.849] Manager {140131209512736} NOTE: 
 [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
 [Sep 22 00:00:18.849] Manager {140131209512736} NOTE: [Alarms::signalAlarm] 
 Server Process born
 [Sep 22 00:00:19.874] {47510015031936} STATUS: opened 
 /usr/local/var/log/trafficserver/diags.log
 [Sep 22 00:00:19.874] {47510015031936} NOTE: updated diags config
 [Sep 22 00:00:19.879] Server {47510015031936} NOTE: cache clustering disabled
 [Sep 22 00:00:19.908] Server {47510015031936} NOTE: cache clustering disabled
 [Sep 22 00:00:20.019] Server {47510015031936} NOTE: logging initialized[7], 
 logging_mode = 3
 [Sep 22 00:00:20.032] Server {47510015031936} NOTE: traffic server running
 [Sep 22 00:00:20.045] Server {47510028859136} NOTE: cache enabled
 [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile 
 /usr/local/var/log/trafficserver/error.log was rolled to 
 /usr/local/var/log/trafficserver/error.log_trafficserver02.20110922.00h00m11s-20110923.00h00m00s.old.
 [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile 
 /usr/local/var/log/trafficserver/squid.log was rolled to 
 /usr/local/var/log/trafficserver/squid.log_trafficserver02.20110922.00h00m06s-20110923.00h00m00s.old.
 [Sep 23 00:00:00.000] Server {47409990321920} STATUS: The logfile 
 /usr/local/var/log/trafficserver/extended2.log was rolled to 
 /usr/local/var/log/trafficserver/extended2.log_trafficserver02.20110922.00h00m06s-20110923.00h00m00s.old.
 NOTE: Traffic Server received Sig 11: Segmentation fault
 /usr/local/bin/traffic_server - STACK TRACE: 
 [Sep 23 00:00:14.668] Manager {140131209512736} FATAL: 
 [LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
 [Sep 23 00:00:14.668] Manager {140131209512736} FATAL:  (last system error 
 104: Connection reset by peer)