Trunk compiles, but cannot start on VPS
---------------------------------------
Key: TS-296
URL: https://issues.apache.org/jira/browse/TS-296
Project: Traffic Server
Issue Type: Bug
Environment: Virtuozzo VPS, Debian 4 Linux 2.6.18 kernel
Reporter: Marcus Clyne
Priority: Blocker
Fix For: 2.1.0
Trunk compiles and starts (with TC and TM - but not TS - processes) but gives
the following errors :
Apr 16 01:49:25 tagmata traffic_cop[3500]: --- Cop Starting [Version: Apache
Traffic Server - traffic_cop - 2.1.0 - (build # 3161 on Apr 16 2010 at
01:19:23)] ---
Apr 16 01:49:25 tagmata traffic_cop[3500]: traffic_manager not running, making
sure traffic_server is dead
Apr 16 01:49:25 tagmata traffic_cop[3500]: spawning traffic_manager
Apr 16 01:49:25 tagmata traffic_manager[3501]: NOTE: --- Manager Starting ---
Apr 16 01:49:25 tagmata traffic_manager[3501]: NOTE: Manager Version: Apache
Traffic Server - traffic_manager - 2.1.0 - (build # 3161 on Apr 16 2010 at
01:21:36)
Apr 16 01:49:25 tagmata traffic_manager[3501]: NOTE:
RLIMIT_NOFILE(7):cur(10000),max(10000)
Apr 16 01:49:25 tagmata traffic_manager[3501]: {3080558272} STATUS: opened
var/log/trafficserver/manager.log
Apr 16 01:49:25 tagmata traffic_manager[3501]: {3080558272} NOTE: updated diags
config
Apr 16 01:49:25 tagmata traffic_manager[3501]: {3080558272} NOTE:
[ClusterCom::ClusterCom] Node running on OS: 'Linux' Release:
'2.6.18-028stab067.4-PAE'
Apr 16 01:49:25 tagmata traffic_manager[3501]: {3080558272} NOTE:
[LocalManager::listenForProxy] Listening on port: 8000
Apr 16 01:49:25 tagmata traffic_manager[3501]: {3080558272} NOTE:
[TrafficManager] Setup complete
Apr 16 01:49:26 tagmata traffic_manager[3501]: {3080558272} NOTE:
[LocalManager::startProxy] Launching ts process
Apr 16 01:49:26 tagmata traffic_manager[3501]: {3080558272} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '14'
Apr 16 01:49:26 tagmata traffic_manager[3501]: {3080558272} NOTE:
[Alarms::signalAlarm] Server Process born
Apr 16 01:49:27 tagmata traffic_server[3511]: NOTE: --- Server Starting ---
Apr 16 01:49:27 tagmata traffic_server[3511]: NOTE: Server Version: Apache
Traffic Server - traffic_server - 2.1.0 - (build # 3161 on Apr 16 2010 at
01:22:47)
Apr 16 01:49:27 tagmata traffic_server[3511]: {1079967904} STATUS: opened
var/log/trafficserver/diags.log
Apr 16 01:49:27 tagmata traffic_server[3511]: {1079967904} NOTE: updated diags
config
Apr 16 01:49:27 tagmata traffic_server[3511]: {1079967904} NOTE: cache
clustering disabled
Apr 16 01:49:28 tagmata traffic_server[3511]: {1079967904} FATAL:
EThread::EThread: -1=eventfd(0,0),errno(38)
Apr 16 01:49:28 tagmata traffic_server[3511]: FATAL: EThread::EThread:
-1=eventfd(0,0),errno(38)
Apr 16 01:49:28 tagmata traffic_manager[3501]: {3080558272} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
Apr 16 01:49:28 tagmata traffic_manager[3501]: {3080558272} ERROR: (last
system error 2: No such file or directory)
Apr 16 01:49:28 tagmata traffic_manager[3501]: {3080558272} ERROR:
[Alarms::signalAlarm] Server Process was reset
Apr 16 01:49:28 tagmata traffic_manager[3501]: {3080558272} ERROR: (last
system error 2: No such file or directory)
Apr 16 01:49:29 tagmata traffic_manager[3501]: {3080558272} NOTE:
[LocalManager::startProxy] Launching ts process
Apr 16 01:49:29 tagmata traffic_manager[3501]: {3080558272} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '14'
Apr 16 01:49:29 tagmata traffic_manager[3501]: {3080558272} NOTE:
[Alarms::signalAlarm] Server Process born
Proxying does not work.
The latest version 2.0.x works with the same setup.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
