You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/05/29 05:22:37 UTC
[jira] Updated: (TS-300) Binding to outgoing IP does not work
[ https://issues.apache.org/jira/browse/TS-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-300:
-----------------------------
Fix Version/s: 2.1.2
(was: 2.1.1)
> Binding to outgoing IP does not work
> ------------------------------------
>
> Key: TS-300
> URL: https://issues.apache.org/jira/browse/TS-300
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.1.0
> Environment: Virtuozzo VPS Debian Linux 2.6.18 32-bit and Debian Linux 2.6.31 64-bit
> Reporter: Marcus Clyne
> Priority: Minor
> Fix For: 2.1.2
>
>
> When setting the outgoing IP binding in the config file (MY_IP is a bindable IP other than 0.0.0.0):
> LOCAL proxy.local.outgoing_ip_to_bind STRING [MY_IP]
> I get 502 errors in the response
> Tested versions :
> 2.0.x (not affected)
> trunk (affected)
> for both platforms mentioned.
> Compiled using :
> ./configure --disable-eventfd
> (I will try without --disable-eventfd on the newer machine and add an additional edit later.)
> The syslog entries include many repetitions of :
> Apr 17 03:33:41 tagmata traffic_server[28204]: NOTE: --- Server Starting ---
> Apr 17 03:33:41 tagmata traffic_server[28204]: NOTE: Server Version: Apache Traffic Server - traffic_server - 2.1.0 - (build # 3172 on Apr 17 2010 at 02:17:08)
> Apr 17 03:33:41 tagmata traffic_server[28204]: {1079967664} STATUS: opened var/log/trafficserver/diags.log
> Apr 17 03:33:41 tagmata traffic_server[28204]: {1079967664} NOTE: updated diags config
> Apr 17 03:33:41 tagmata traffic_server[28204]: {1079967664} NOTE: cache clustering disabled
> Apr 17 03:33:41 tagmata traffic_server[28204]: {1079967664} NOTE: cache clustering disabled
> Apr 17 03:33:42 tagmata traffic_server[28204]: {1105550224} NOTE: cache enabled
> Apr 17 03:33:42 tagmata traffic_server[28204]: {1079967664} NOTE: logging initialized[7], logging_mode = 3
> Apr 17 03:33:42 tagmata traffic_server[28204]: {1079967664} NOTE: traffic server running
> Apr 17 03:33:52 tagmata traffic_cop[22344]: (http test) received non-200 status(502)
> Apr 17 03:33:52 tagmata traffic_cop[22344]: server heartbeat failed [1]
> Apr 17 03:34:02 tagmata traffic_cop[22344]: (http test) received non-200 status(502)
> Apr 17 03:34:02 tagmata traffic_cop[22344]: server heartbeat failed [2]
> Apr 17 03:34:02 tagmata traffic_cop[22344]: killing server
> Apr 17 03:34:02 tagmata traffic_manager[23915]: {3080586944} ERROR: [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 9: Killed
> Apr 17 03:34:02 tagmata traffic_manager[23915]: {3080586944} ERROR: (last system error 2: No such file or directory)
> Apr 17 03:34:02 tagmata traffic_manager[23915]: {3080586944} ERROR: [Alarms::signalAlarm] Server Process was reset
> Apr 17 03:34:02 tagmata traffic_manager[23915]: {3080586944} ERROR: (last system error 2: No such file or directory)
> Apr 17 03:34:03 tagmata traffic_manager[23915]: {3080586944} NOTE: [LocalManager::startProxy] Launching ts process
> Apr 17 03:34:03 tagmata traffic_manager[23915]: {3080586944} NOTE: [LocalManager::pollMgmtProcessServer] New process connecting fd '15'
> Apr 17 03:34:03 tagmata traffic_manager[23915]: {3080586944} NOTE: [Alarms::signalAlarm] Server Process born
> And traffic.out give :
> [Apr 17 03:32:32.676] {1079967664} STATUS: opened var/log/trafficserver/diags.log
> [Apr 17 03:32:53.659] Manager {3080586944} ERROR: [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 9: Killed
> [Apr 17 03:32:53.659] Manager {3080586944} ERROR: (last system error 2: No such file or directory)
> [Apr 17 03:32:53.659] Manager {3080586944} ERROR: [Alarms::signalAlarm] Server Process was reset
> [Apr 17 03:32:53.659] Manager {3080586944} ERROR: (last system error 2: No such file or directory)
> which I'm presuming comes from heartbeat monitoring of the traffic_cop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.