From: Scott W. <swe...@sa...> - 2011-01-20 13:31:14
|
I appreciate your help on this. It turns out iptables was enabled and blocking any port I tried. I'm very sorry for the inconvenience. It works fine now. Scott ________________________________________ From: S, Sajeesh [saj...@hp...] Sent: 20 January, 2011 1:09 PM To: Scott Weisman Subject: RE: seagull question on remote control Hi, Can you please send me the log file also? Log file will have the HTTP trace in case seagull is receiving the HTTP request from the web client. Have you tried using another listening port other than 8080 ? Regards, Sajeesh -----Original Message----- From: Scott Weisman [mailto:swe...@sa...] Sent: Thursday, January 20, 2011 4:28 PM To: S, Sajeesh Subject: RE: seagull question on remote control Linux host-172-16-3-164.lab-il.sandvine.com 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Name : glibc Relocations: (not relocatable) Version : 2.5 Vendor: Red Hat, Inc. Release : 42 Build Date: Fri 17 Jul 2009 11:33:41 AM EDT ________________________________________ From: S, Sajeesh [saj...@hp...] Sent: 20 January, 2011 12:49 PM To: Scott Weisman Subject: RE: seagull question on remote control Hi, You can ignore the warning. Please let me know the platform and libc version and seagull version. Regards, Sajeesh -----Original Message----- From: Srivastava, Anuj Kumar (CMS) Sent: Thursday, January 20, 2011 2:24 PM To: S, Sajeesh Cc: Sulpis, Michel; Scott Weisman Subject: RE: seagull question on remote control Forwarding to tool support.. Regards Anuj -----Original Message----- From: Scott Weisman [mailto:swe...@sa...] Sent: Thursday, January 20, 2011 2:23 PM To: Sulpis, Michel; Srivastava, Anuj Kumar (CMS) Subject: seagull question on remote control I sent this to the list but it doesn't seem to have posted. Can you help? ________________________________ From: Scott Weisman Sent: 20 January, 2011 10:49 AM To: gul...@li... Subject: question on remote control My company uses Seagull for testing our software. I would like to improve the way we use it by taking advantage of the remote control feature it has, but am having a problem with it. When I start Seagull, like so: [root@host-172-16-3-164 seagull-ldap-test]# seagull -conf conf.client2.xml -dico ./seagull_client_dictionary.xml -scen ccr-init_update_terminate.xml -log ccr-cca.client1.log -llevel A -bg -ctrl 127.0.0.1:8080 I get the following response: |W|No definition found for configuration parameters definition for protocol [cmd-seagull-protocol] Background mode - PID [16348] Then, Seagull runs the simulation and does open port 8080 for listening, but doesn't respond to any HTTP requests. Can someone explain what I am doing wrong here? Why the "no definition found" warning? Thanks, Scott |