[jira] [Closed] (TS-726) Crash Report: DNSEntry::post in 2.1.7
[
https://issues.apache.org/jira/browse/TS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-726.
---
Resolution: Fixed
Never reproduce this problem, close and wait for another issue.
Crash Report: DNSEntry::post in 2.1.7
-
Key: TS-726
URL: https://issues.apache.org/jira/browse/TS-726
Project: Traffic Server
Issue Type: Bug
Components: DNS
Affects Versions: 2.1.7
Environment: 2.1.7
Reporter: Zhao Yongming
Labels: crash
Fix For: 3.1.0
reported from user, for tracking.
{code:none}
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/local/ts/bin/traffic_server - STACK TRACE:
[0x4001c420]
/usr/local/ts/bin/traffic_server(DNSEntry::post(DNSHandler*, HostEnt*,
bool)+0x5d5)[0x82503e5]
[0x0]
/usr/local/ts/bin/traffic_server(EThread::process_event(Event*,
int)+0x1ff)[0x8320e9f]
/usr/local/ts/bin/traffic_server(EThread::execute()+0x4be)[0x83216be]
/usr/local/ts/bin/traffic_server(main+0x1245)[0x8104505]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0x4050]
/usr/local/ts/bin/traffic_server[0x80bdec1]
/usr/local/ts/bin/traffic_server[0x80bdec1]
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-801) Crash Report: enable update will triger Segmentation fault
[
https://issues.apache.org/jira/browse/TS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-801:
Fix Version/s: (was: 3.1.0)
3.1.1
Crash Report: enable update will triger Segmentation fault
--
Key: TS-801
URL: https://issues.apache.org/jira/browse/TS-801
Project: Traffic Server
Issue Type: Bug
Components: HTTP
Affects Versions: 2.1.8
Environment: v2.1.8 and update function enabled.
Reporter: Zhao Yongming
Labels: update
Fix For: 3.1.1
{code}
b13621367...@hotmail.com: NOTE: Traffic Server received Sig 11: Segmentation
fault
/usr/local/ts/bin/traffic_server - STACK TRACE:
b13621367...@hotmail.com:
/usr/local/ts/bin/traffic_server[0x5260c9]
/lib64/libpthread.so.0[0x3088e0f4c0]
[0x6e]
/usr/local/ts/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
(*)(HttpTransact::State*))+0x6e)[0x57e0e2]
/usr/local/ts/bin/traffic_server(HttpSM::set_next_state()+0x18b)[0x57e369]
/usr/local/ts/bin/traffic_server(HttpUpdateSM::set_next_state()+0xad)[0x5b604b]
/usr/local/ts/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
(*)(HttpTransact::State*))+0x15e)[0x57e1d2]
/usr/local/ts/bin/traffic_server(HttpSM::handle_api_return()+0x138)[0x56d9aa]
/usr/local/ts/bin/traffic_server(HttpUpdateSM::handle_api_return()+0x47)[0x5b5cc1]
/usr/local/ts/bin/traffic_server(HttpSM::do_api_callout()+0x3f)[0x582cc3]
/usr/local/ts/bin/traffic_server(HttpSM::set_next_state()+0x64)[0x57e242]
/usr/local/ts/bin/traffic_server(HttpUpdateSM::set_next_state()+0xad)[0x5b604b]
/usr/local/ts/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
(*)(HttpTransact::State*))+0x15e)[0x57e1d2]
/usr/local/ts/bin/traffic_server(HttpSM::handle_api_return()+0x13b13621367...@hotmail.com:
8)[0x56d9aa]
/usr/local/ts/bin/traffic_server(HttpUpdateSM::handle_api_return()+0x47)[0x5b5cc1]
/usr/local/ts/bin/traffic_server(HttpSM::do_api_callout()+0x3f)[0x582cc3]
/usr/local/ts/bin/traffic_server(HttpSM::set_next_state()+0x64)[0x57e242]
/usr/local/ts/bin/traffic_server(HttpUpdateSM::set_next_state()+0xad)[0x5b604b]
/usr/local/ts/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
(*)(HttpTransact::State*))+0x15e)[0x57e1d2]
/usr/local/ts/bin/traffic_server(HttpUpdateSM::handle_api_return()+0x36)[0x5b5cb0]
/usr/local/ts/bin/traffic_server(HttpSM::do_api_callout()+0x3f)[0x582cc3]
/usr/local/ts/bin/traffic_server(HttpSM::state_add_to_list(int,
void*)+0x2aa)[0x56a51c]
/usr/local/ts/bin/traffic_server(HttpSM::main_handler(int,
void*)+0x2cb)[0x570c13]
/usr/local/ts/bin/traffic_server(Continuation::handleEvent(int,
void*)+0x6c)[0x4e0486]
/usr/local/ts/bin/traffic_server(HttpUpdateSM::start_scheduled_update(Continuation*,
HTTPHdr*)+0x168)[0x5b5c1c]
/usr/local/ts/bin/traffic_server(UpdateSM::http_scheme(UpdateSM*)+0x335)[0x53599f]
/usr/local/ts/bin/traffic_server(UpdateSM::HandleSMEvent(int,
Event*)+0x1ab)[0x535437]
/usr/local/ts/bin/traffic_server(Continuation::handleEvent(int,
void*)+0x6c)[0x4e0486]
/usr/local/ts/bin/traffic_server(EThread::process_event(Event*,
int)+0x12c)[0x6fa9dc]
/usr/local/ts/bin/traffic_server(EThread::execute()+0x9b)[0x6fabef]
/usr/local/ts/bin/traffic_server[0x6f9b4c]
/lib64/libpthread.so.0[0x3088e077e1]
/lib64/libc.so.6(clone+0x6d)[0x38584e18ed]
/lib64/libc.so.6(clone+0x6d)[0x38584e18ed]
/lib64/libc.so.6(clone+0x6d)[0x38584e18ed]
[May 26 16:25:14.569] Manager {140030245394400} ERROR:
[LocalManager::-PollMgmtProcessServer] Server Process terminated due to Sig
11: Segmentation fault
[May 26 16:25:14.569] Manager {140030245394400} ERROR: (last system error
32: Broken pipe)
[[May 26 16:25:14.569] Manager {140030245394400} ERROR:
[Alarms::-SignalAlarm] Server Process was reset
[May 26 16:25:14.569] Manager {140030245394400} ERROR: (last system error
32: Broken pipe)
[May 26 16:25:15.577] Manager {140030245394400} NOTE:
[LocalManager::-StartProxy] Launching ts process
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TS-835) Crash Report: heartbeat_manager - test_mgmt_cli_port in traffic_cop
[
https://issues.apache.org/jira/browse/TS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-835.
---
Resolution: Fixed
Not reproduce this problem again, now first close it and wait for another
report.
Crash Report: heartbeat_manager - test_mgmt_cli_port in traffic_cop
Key: TS-835
URL: https://issues.apache.org/jira/browse/TS-835
Project: Traffic Server
Issue Type: Bug
Components: Management
Affects Versions: 3.1.0
Environment: current trunk, v3.0 stable time
Reporter: Zhao Yongming
Labels: cop
Fix For: 3.1.0
bt #1
{code}
Reading symbols from /lib64/libnss_files.so.2...done.
Loaded symbols for /lib64/libnss_files.so.2
warning: Can't read pathname for load map: Input/output error.
warning: Can't read pathname for load map: Input/output error.
Core was generated by `/usr/bin/traffic_cop'.
Program terminated with signal 6, Aborted.
[New process 27092]
#0 0x003c33030265 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x003c33030265 in raise () from /lib64/libc.so.6
#1 0x003c33031d10 in abort () from /lib64/libc.so.6
#2 0x003c3306a84b in __libc_message () from /lib64/libc.so.6
#3 0x003c330722ef in _int_free () from /lib64/libc.so.6
#4 0x003c3307273b in free () from /lib64/libc.so.6
#5 0x2b95bf2a2da7 in ink_free (ptr=Could not find the frame base for
ink_free.
) at ink_memory.cc:175
#6 0x2b95bf2a7251 in _xfree (mem=Could not find the frame base for
_xfree(void*).
) at ink_resource.cc:710
#7 0x2b95bf07b42b in _TSfree (ptr=Could not find the frame base for
_TSfree.
) at ../INKMgmtAPI.cc:88
#8 0x00403b17 in test_mgmt_cli_port () at TrafficCop.cc:1180
#9 0x00404fa7 in heartbeat_manager () at TrafficCop.cc:1265
#10 0x004052fb in check_programs () at TrafficCop.cc:1500
#11 0x00405879 in check (arg=0x0) at TrafficCop.cc:1670
#12 0x00405a87 in main (argc=1, argv=0x7fff8c071c88) at
TrafficCop.cc:1942
(gdb) info f
Stack level 0, frame at 0x7fff8c06ef00:
rip = 0x3c33030265 in raise; saved rip 0x3c33031d10
called by frame at 0x7fff8c06f040
Arglist at 0x7fff8c06eef0, args:
Locals at 0x7fff8c06eef0, Previous frame's sp is 0x7fff8c06ef00
Saved registers:
rip at 0x7fff8c06eef8
{code}
bt #2
{code}
Loaded symbols for /lib64/libselinux.so.1
Reading symbols from /lib64/libsepol.so.1...done.
Loaded symbols for /lib64/libsepol.so.1
Reading symbols from /lib64/libnss_files.so.2...done.
Loaded symbols for /lib64/libnss_files.so.2
warning: Can't read pathname for load map: Input/output error.
warning: Can't read pathname for load map: Input/output error.
Core was generated by `/usr/bin/traffic_cop'.
Program terminated with signal 6, Aborted.
[New process 26537]
#0 0x003f57e30265 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x003f57e30265 in raise () from /lib64/libc.so.6
#1 0x003f57e31d10 in abort () from /lib64/libc.so.6
#2 0x003f57e6a84b in __libc_message () from /lib64/libc.so.6
#3 0x003f57e722ef in _int_free () from /lib64/libc.so.6
#4 0x003f57e7273b in free () from /lib64/libc.so.6
#5 0x2b682f2f8da7 in ink_free (ptr=Could not find the frame base for
ink_free.
) at ink_memory.cc:175
#6 0x2b682f2fd251 in _xfree (mem=Could not find the frame base for
_xfree(void*).
) at ink_resource.cc:710
#7 0x2b682f0d142b in _TSfree (ptr=Could not find the frame base for
_TSfree.
) at ../INKMgmtAPI.cc:88
#8 0x00403b17 in test_mgmt_cli_port () at TrafficCop.cc:1180
#9 0x00404fa7 in heartbeat_manager () at TrafficCop.cc:1265
#10 0x004052fb in check_programs () at TrafficCop.cc:1500
#11 0x00405879 in check (arg=0x0) at TrafficCop.cc:1670
#12 0x00405a87 in main (argc=1, argv=0x7fff396dede8) at
TrafficCop.cc:1942
(gdb) info f
Stack level 0, frame at 0x7fff396dc060:
rip = 0x3f57e30265 in raise; saved rip 0x3f57e31d10
called by frame at 0x7fff396dc1a0
Arglist at 0x7fff396dc050, args:
Locals at 0x7fff396dc050, Previous frame's sp is 0x7fff396dc060
Saved registers:
rip at 0x7fff396dc058
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TS-851) unable to run TS without a real interface
[
https://issues.apache.org/jira/browse/TS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-851.
---
Resolution: Fixed
unable to run TS without a real interface
-
Key: TS-851
URL: https://issues.apache.org/jira/browse/TS-851
Project: Traffic Server
Issue Type: Bug
Components: Management
Affects Versions: 3.1.0
Environment: trunk after TS-845
Reporter: Zhao Yongming
Assignee: Zhao Yongming
Fix For: 3.1.0
Attachments: TS-851.patch
it seems like that start_HttpProxyServerBackDoor with port
8084(proxy.config.process_manager.mgmt_port) does some dirty job, we need to
track it down.
{code}
[Jun 21 22:51:02.915] Server {47475602368256} NOTE: cache clustering disabled
[Jun 21 22:51:02.915] Server {47475602368256} NOTE: clearing statistics
[Jun 21 22:51:02.916] Server {47475602368256} DEBUG: (dns) ink_dns_init:
called with init_called = 0
[Jun 21 22:51:02.926] Server {47475602368256} DEBUG: (dns) localhost=zym6400
[Jun 21 22:51:02.927] Server {47475602368256} DEBUG: (dns) Round-robin
nameservers = 0
[Jun 21 22:51:02.932] Server {47475602368256} NOTE: cache clustering disabled
[Jun 21 22:51:02.984] Server {47475602368256} NOTE: logging initialized[7],
logging_mode = 3
[Jun 21 22:51:02.989] Server {47475602368256} DEBUG: (http_init)
proxy.config.http.redirection_enabled = 0
[Jun 21 22:51:02.989] Server {47475602368256} DEBUG: (http_init)
proxy.config.http.number_of_redirections = 1
[Jun 21 22:51:02.989] Server {47475602368256} DEBUG: (http_init)
proxy.config.http.post_copy_size = 2048
[Jun 21 22:51:02.989] Server {47475602368256} DEBUG: (http_tproxy) Primary
listen socket transparency is off
[Jun 21 22:51:02.992] Server {47475602368256} ERROR: getaddrinfo error -2:
Name or service not known
[Jun 21 22:51:02.992] Server {47475602368256} WARNING: unable to listen on
port 8084: -1 2, No such file or directory
[Jun 21 22:51:02.993] Server {47475602368256} NOTE: traffic server running
[Jun 21 22:51:02.993] Server {47475602368256} DEBUG: (dns)
DNSHandler::startEvent: on thread 0
[Jun 21 22:51:02.993] Server {47475602368256} DEBUG: (dns) open_con: opening
connection 127.0.0.1:53
[Jun 21 22:51:02.993] Server {47475602368256} DEBUG: (dns) random port = 28547
[Jun 21 22:51:02.993] Server {47475602368256} DEBUG: (dns) opening connection
127.0.0.1:53 SUCCEEDED for 0
[Jun 21 22:51:03.308] Server {47475617863424} NOTE: cache enabled
[Jun 21 22:51:21.870] Manager {140119188903712} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Jun 21 22:51:21.870] Manager {140119188903712} FATAL: (last system error
104: Connection reset by peer)
[Jun 21 22:51:21.870] Manager {140119188903712} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Jun 21 22:51:21.870] Manager {140119188903712} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Jun 21 22:51:21.870] Manager {140119188903712} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Jun 21 22:51:21.870] Manager {140119188903712} ERROR: (last system error
32: Broken pipe)
[E. Mgmt] log == [TrafficManager] using root directory '/usr'
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-857) Crash Report: HttpTunnel::chain_abort_all - HttpServerSession::do_io_close - UnixNetVConnection::do_io_close
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-857:
Fix Version/s: (was: 3.1.0)
3.1.1
Crash Report: HttpTunnel::chain_abort_all - HttpServerSession::do_io_close
- UnixNetVConnection::do_io_close
--
Key: TS-857
URL: https://issues.apache.org/jira/browse/TS-857
Project: Traffic Server
Issue Type: Bug
Components: HTTP, Network
Affects Versions: 3.1.0
Environment: in my branch that is something same as 3.0.x
Reporter: Zhao Yongming
Fix For: 3.1.1
here is the bt from the crash, some of the information is missing due to we
have not enable the --enable-debug configure options.
{code}
[New process 7532]
#0 ink_stack_trace_get (stack=value optimized out, len=value optimized
out, signalhandler_frame=value optimized out)
at ink_stack_trace.cc:68
68fp = (void **) (*fp);
(gdb) bt
#0 ink_stack_trace_get (stack=value optimized out, len=value optimized
out, signalhandler_frame=value optimized out)
at ink_stack_trace.cc:68
#1 0x2ba641dccef1 in ink_stack_trace_dump (sighandler_frame=value
optimized out) at ink_stack_trace.cc:114
#2 0x004df020 in signal_handler (sig=value optimized out) at
signals.cc:225
#3 signal handler called
#4 0x006a1ea9 in UnixNetVConnection::do_io_close (this=0x1cc9bd20,
alerrno=value optimized out)
at ../../iocore/eventsystem/I_Lock.h:297
#5 0x0051f1d0 in HttpServerSession::do_io_close
(this=0x2aaab0042c80, alerrno=20600) at HttpServerSession.cc:127
#6 0x0056d1e9 in HttpTunnel::chain_abort_all (this=0x2aabeeffdd70,
p=0x2aabeeffdf68) at HttpTunnel.cc:1300
#7 0x005269ca in HttpSM::tunnel_handler_ua (this=0x2aabeeffc070,
event=104, c=0x2aabeeffdda8) at HttpSM.cc:2987
#8 0x00571dfc in HttpTunnel::consumer_handler (this=0x2aabeeffdd70,
event=104, c=0x2aabeeffdda8) at HttpTunnel.cc:1232
#9 0x00572032 in HttpTunnel::main_handler (this=0x2aabeeffdd70,
event=1088608784, data=value optimized out)
at HttpTunnel.cc:1456
#10 0x006a6307 in write_to_net_io (nh=0x2b12d688, vc=0x1cc876e0,
thread=value optimized out)
at ../../iocore/eventsystem/I_Continuation.h:146
#11 0x0069ce97 in NetHandler::mainNetEvent (this=0x2b12d688,
event=value optimized out, e=0x171c1ed0) at UnixNet.cc:405
#12 0x006cddaf in EThread::process_event (this=0x2b12c010,
e=0x171c1ed0, calling_code=5) at I_Continuation.h:146
#13 0x006ce6bc in EThread::execute (this=0x2b12c010) at
UnixEThread.cc:262
#14 0x006cd0ee in spawn_thread_internal (a=0x171b58f0) at Thread.cc:88
#15 0x003c33c064a7 in start_thread () from /lib64/libpthread.so.0
#16 0x003c330d3c2d in clone () from /lib64/libc.so.6
(gdb) info f
Stack level 0, frame at 0x40e2b790:
rip = 0x2ba641dccdf3 in ink_stack_trace_get(void**, int, int)
(ink_stack_trace.cc:68); saved rip 0x2ba641dccef1
called by frame at 0x40e2bbe0
source language c++.
Arglist at 0x40e2b770, args: stack=value optimized out, len=value
optimized out, signalhandler_frame=value optimized out
Locals at 0x40e2b770, Previous frame's sp is 0x40e2b790
Saved registers:
rbx at 0x40e2b778, rbp at 0x40e2b780, rip at 0x40e2b788
(gdb)
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-730) [gsoc2011] SSL needs CipherSuite control in negotiation
[ https://issues.apache.org/jira/browse/TS-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Galić reassigned TS-730: - Assignee: Igor Galić [gsoc2011] SSL needs CipherSuite control in negotiation Key: TS-730 URL: https://issues.apache.org/jira/browse/TS-730 Project: Traffic Server Issue Type: Improvement Components: SSL Affects Versions: 2.1.7 Environment: ATS trunk + SSL Reporter: Zhao Yongming Assignee: Igor Galić Labels: gsoc2011, ssl Fix For: 3.1.1 when TS does negotiation, the CipherSuite is not configurable, for this time being, ciphers short than 128bits it not consider a good protect for secure connection. we should give CipherSuite more control. for example we can specify those preferred ciphers we want to use, as Apache httpd. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-882) traffic_logstats dies when printing log
[
https://issues.apache.org/jira/browse/TS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067342#comment-13067342
]
Alan M. Carroll commented on TS-882:
I would recommend starting with having the setrlimit call provide a bit more
information about its failure.
traffic_logstats dies when printing log
---
Key: TS-882
URL: https://issues.apache.org/jira/browse/TS-882
Project: Traffic Server
Issue Type: Bug
Components: Logging
Affects Versions: 3.0.0
Environment: Mac OSX 10.6.8
Reporter: Alan Cabrera
Priority: Critical
Labels: crash
Fix For: 3.1.0
{code}
[daruma:trafficserver 598]$ ./bin/traffic_logstats -l
var/log/trafficserver/squid.blog
FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST)
which, rl) = 0`
./bin/traffic_logstats - STACK TRACE:
0 libtsutil.3.dylib 0x0001000cbb6b ink_fatal + 123
1 libtsutil.3.dylib 0x0001000ca571 _ink_assert + 145
2 traffic_logstats0x000152f4 _Z11init_systemv +
100
3 traffic_logstats0x0001538b
_Z25init_log_standalone_basicPKc + 27
4 traffic_logstats0x000155ab main + 411
5 traffic_logstats0x00011484 start + 52
6 ??? 0x0003 0x0 + 3
Abort trap
[daruma:trafficserver 599]$ ./bin/traffic_logstats -f
var/log/trafficserver/squid.blog
FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST)
which, rl) = 0`
./bin/traffic_logstats - STACK TRACE:
0 libtsutil.3.dylib 0x0001000cbb6b ink_fatal + 123
1 libtsutil.3.dylib 0x0001000ca571 _ink_assert + 145
2 traffic_logstats0x000152f4 _Z11init_systemv +
100
3 traffic_logstats0x0001538b
_Z25init_log_standalone_basicPKc + 27
4 traffic_logstats0x000155ab main + 411
5 traffic_logstats0x00011484 start + 52
6 ??? 0x0003 0x0 + 3
Abort trap
[daruma:trafficserver 600]$ ./bin/traffic_logstats
FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST)
which, rl) = 0`
./bin/traffic_logstats - STACK TRACE:
0 libtsutil.3.dylib 0x0001000cbb6b ink_fatal + 123
1 libtsutil.3.dylib 0x0001000ca571 _ink_assert + 145
2 traffic_logstats0x000152f4 _Z11init_systemv +
100
3 traffic_logstats0x0001538b
_Z25init_log_standalone_basicPKc + 27
4 traffic_logstats0x000155ab main + 411
5 traffic_logstats0x00011484 start + 52
6 ??? 0x0001 0x0 + 1
Abort trap
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-804) Without Posix Capabilities, traffic_server is not able to bind restricted ports
[ https://issues.apache.org/jira/browse/TS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll reassigned TS-804: -- Assignee: Alan M. Carroll Without Posix Capabilities, traffic_server is not able to bind restricted ports --- Key: TS-804 URL: https://issues.apache.org/jira/browse/TS-804 Project: Traffic Server Issue Type: Bug Reporter: Leif Hedstrom Assignee: Alan M. Carroll Fix For: 3.1.0 As of some recent changes with transparent proxy, when running traffic_server standalone (not with traffic_manager), it is unable to bind restricted ports unless it's compiled with Posix capabilities support. For RPM style distributions, make sure to install: libcap libcap-devel For Debian style distributions: libcap2 libcap-dev Also note that when running normally (e.g. using the trafficserver startup script, or traffic_manager), this is not a problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-804) Without Posix Capabilities, traffic_server is not able to bind restricted ports
[ https://issues.apache.org/jira/browse/TS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll resolved TS-804. Resolution: Fixed Added back the old path in the standalone case, conditionally compiled based on TS_USE_POSIX_CAP. Tested it both ways and it seems to work. It should be noted that server transparency won't work in this case as it requires POSIX capabilities to retain the ability to set the outgoing socket transparent. Without Posix Capabilities, traffic_server is not able to bind restricted ports --- Key: TS-804 URL: https://issues.apache.org/jira/browse/TS-804 Project: Traffic Server Issue Type: Bug Reporter: Leif Hedstrom Assignee: Alan M. Carroll Fix For: 3.1.0 As of some recent changes with transparent proxy, when running traffic_server standalone (not with traffic_manager), it is unable to bind restricted ports unless it's compiled with Posix capabilities support. For RPM style distributions, make sure to install: libcap libcap-devel For Debian style distributions: libcap2 libcap-dev Also note that when running normally (e.g. using the trafficserver startup script, or traffic_manager), this is not a problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
