Basic Fedora Core 8 (AMI Id: ami-84db39ed) Minimal Fedora Core 8, 32-bit architecture, and Amazon EC2 AMI Tools.
I placed it in the JIRA as well, Best, Moshe On Tue, Mar 23, 2010 at 1:41 AM, Jason <[email protected]> wrote: > Can you provide me with > - AMI/AKI are you using? > -Arch type? (i386/x64)? > > Thanks, > Jason > > > On Mon, Mar 22, 2010 at 6:51 PM, Moshe Kaplan <[email protected]> wrote: > >> Hi, >> >> 10x for the quick response, I indeed changed the wrong files. >> After updating the right files under /usr/local/etc/trafficserver/ the >> daemon started listening on port 80. However, I still did not had response >> from the mapped server. >> >> When I tailed /var/log/messages, I receive the following error that is >> mentioned in >> http://mail-archives.apache.org/mod_mbox/incubator-trafficserver-dev/201003.mbox/%[email protected]%3e(I >> really use 2.6.21.7-2.ec2.v1.2.fc8xen) >> >> Mar 22 18:30:41 domU-12-31-39-09-25-24 traffic_server[31067]: {1082005552} >> NOTE: cache clustering disabled >> Mar 22 18:30:41 domU-12-31-39-09-25-24 traffic_server[31067]: {1082005552} >> NOTE: clearing statistics >> *Mar 22 18:30:41 domU-12-31-39-09-25-24 traffic_server[31067]: FATAL: >> UnixEThread.cc:70: failed assert `(evfd = eventfd(0,0)) >= 0` >> *Mar 22 18:30:41 domU-12-31-39-09-25-24 traffic_manager[27640]: >> {3086059840} ERROR: [LocalManager::pollMgmtProcessServer] Server Process >> terminated due to Sig 6: Aborted >> Mar 22 18:30:41 domU-12-31-39-09-25-24 traffic_manager[27640]: >> {3086059840} ERROR: (last system error 2: No such file or directory) >> Mar 22 18:30:41 domU-12-31-39-09-25-24 traffic_manager[27640]: >> {3086059840} ERROR: [Alarms::signalAlarm] Server Process was reset >> Mar 22 18:30:41 domU-12-31-39-09-25-24 traffic_manager[27640]: >> {3086059840} ERROR: (last system error 2: No such file or directory) >> Mar 22 18:30:42 domU-12-31-39-09-25-24 traffic_manager[27640]: >> {3086059840} NOTE: [LocalManager::startProxy] Launching ts process >> Mar 22 18:30:42 domU-12-31-39-09-25-24 traffic_manager[27640]: >> {3086059840} NOTE: [LocalManager::pollMgmtProcessServer] New process >> connecting fd '9' >> Mar 22 18:30:42 domU-12-31-39-09-25-24 traffic_manager[27640]: >> {3086059840} NOTE: [Alarms::signalAlarm] Server Process born >> >> Please notice, that after I changed line 67 to the following code and >> remaked the code >> /* evfd = eventfd(0, O_NONBLOCK | FD_CLOEXEC);*/ >> evfd = eventfd(0, 0); >> >> I received the error: >> FATAL: UnixEThread.cc:*71*: failed assert `(evfd = eventfd(0,0)) >= 0` >> (The error moved from line 70 to 71 due to the commented line, which means >> that server really runs the updated code) >> >> Do you have any recommendation how to handle the situation? >> >> Thanks in advance, >> Moshe Kaplan >> >> >> On Mon, Mar 22, 2010 at 2:35 AM, Leif Hedstrom <[email protected]> wrote: >> >>> On 03/21/2010 04:55 PM, Moshe Kaplan wrote: >>> >>>> Hi, >>>> >>>> I tried to configure Apache Traffic Server (ATS) as a reverse proxy on >>>> port 80. >>>> The server but built from scratch from the SVN. I did not implement any >>>> plug-ins. >>>> >>>> 1. I set a reverse proxy rule in >>>> /usr/local/src/ats/proxy/config/remap.config: >>>> map http://127.0.0.1/ http://www.globes.co.il/ >>>> Note: I created either a rule for port 8080 and using the server DNS >>>> name. >>>> >>>> 2. I verified that the proxy.config.reverse_proxy.enabled parameter was >>>> set to 1 in /usr/local/src/ats/proxy/config/records.config >>>> >>>> 3. I changed the listening port from 8080 to 80 in >>>> /usr/local/src/ats/proxy/config/records.config >>>> >>> >>> This is where you installed trafficserver? By default, it would be >>> /usr/local/etc/trafficserver/records.config. >>> >>> >>> Assuming you are editing the correct files, is there anything showing up >>> in /var/log/messages, indicating a problem? >>> >>> -- Leif >>> >>> >> >
