curl-loader-devel Mailing List for curl-loader - web application testing (Page 8)
Status: Alpha
Brought to you by:
coroberti
Menu
▾
▴
curl-loader-devel — curl-loader usage and development issues
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
(1) |
Mar
(7) |
Apr
(19) |
May
(25) |
Jun
(16) |
Jul
(59) |
Aug
(29) |
Sep
(18) |
Oct
(19) |
Nov
(7) |
Dec
(29) |
| 2008 |
Jan
(6) |
Feb
(18) |
Mar
(8) |
Apr
(27) |
May
(26) |
Jun
(5) |
Jul
(6) |
Aug
|
Sep
(9) |
Oct
(37) |
Nov
(61) |
Dec
(17) |
| 2009 |
Jan
(21) |
Feb
(25) |
Mar
(4) |
Apr
(2) |
May
(8) |
Jun
(15) |
Jul
(18) |
Aug
(23) |
Sep
(10) |
Oct
(16) |
Nov
(14) |
Dec
(22) |
| 2010 |
Jan
(23) |
Feb
(8) |
Mar
(18) |
Apr
(1) |
May
(34) |
Jun
(23) |
Jul
(11) |
Aug
(1) |
Sep
(13) |
Oct
(10) |
Nov
(2) |
Dec
(8) |
| 2011 |
Jan
|
Feb
(7) |
Mar
(24) |
Apr
(12) |
May
(3) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(20) |
Nov
(7) |
Dec
(11) |
| 2012 |
Jan
(12) |
Feb
(5) |
Mar
(16) |
Apr
(3) |
May
|
Jun
(5) |
Jul
(12) |
Aug
(6) |
Sep
|
Oct
|
Nov
(8) |
Dec
|
| 2013 |
Jan
(1) |
Feb
(3) |
Mar
(5) |
Apr
(3) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(9) |
Oct
|
Nov
(8) |
Dec
(4) |
| 2014 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
(11) |
Dec
(5) |
| 2015 |
Jan
(1) |
Feb
|
Mar
(11) |
Apr
(3) |
May
(1) |
Jun
(1) |
Jul
(4) |
Aug
(1) |
Sep
(7) |
Oct
(4) |
Nov
(2) |
Dec
|
| 2016 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: LELAURE, L. (LUC) <luc...@al...> - 2011-12-12 12:51:27
|
Hello curl-loader users and developers, Is there a way to set the name of an "UPLOAD_FILE" in connection with the user name used in an URL_TEMPLATE (like %s)? More generally, is there a way to use a global variable in a configuration file indexed by a list? I need to index the user name in a URL, and the associated upload file for this user, and that, for each user? Thanks in advance for your help. Best Regards. Luc. |
|
From: LELAURE, L. (LUC) <luc...@al...> - 2011-12-12 10:05:28
|
Thank you very much. I try it as soon as possible. For information, I am a beginner in C, I used the "patch -p1 -i head-delete-method.patch" command to apply the patch and it seems to be ok. Best Regards, Luc. ________________________________ De : wei guo [mailto:wei...@gm...] Envoyé : lundi 12 décembre 2011 10:28 À : curl-loader-devel Objet : Re: DELETE method? I have a delete method patch for curl-loader-0.53, I developed it myself and make som simple test. I used it in my project. you can try it. the attachment contain the patch file and a demo. Hope it is helpful. :) 2011/12/12 LELAURE, LUC (LUC) <luc...@al...<mailto:luc...@al...>> Hello curl-loader users and developers, Curl supports the DELETE method in "-X, --request" parameter but not curl-loader! Do you know a way to use this method anyway? Otherwise, are there plans to do something about this issue? Thanks for your help. Best Regards, Luc. ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ curl-loader-devel mailing list cur...@li...<mailto:cur...@li...> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel |
|
From: wei g. <wei...@gm...> - 2011-12-12 09:27:40
|
I have a delete method patch for curl-loader-0.53, I developed it myself and make som simple test. I used it in my project. you can try it. the attachment contain the patch file and a demo. Hope it is helpful. :) 2011/12/12 LELAURE, LUC (LUC) <luc...@al...> > Hello curl-loader users and developers, > > Curl supports the DELETE method in “-X, --request” parameter but not > curl-loader! > > Do you know a way to use this method anyway? > > Otherwise, are there plans to do something about this issue? > > Thanks for your help. > > Best Regards, Luc. > > > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > |
|
From: LELAURE, L. (LUC) <luc...@al...> - 2011-12-12 09:14:57
|
Hello curl-loader users and developers, Curl supports the DELETE method in "-X, --request" parameter but not curl-loader! Do you know a way to use this method anyway? Otherwise, are there plans to do something about this issue? Thanks for your help. Best Regards, Luc. |
|
From: Humair M. <hu...@ho...> - 2011-12-09 05:56:38
|
There are a couple of observations I have made with curl-loader that may need remediation: 1) The loader object does not allow more than 2 tokens when using the RECORDS_FROM_FILE variable even though the documentation indicates you can use up to 16 tokens - I believe by modifying the snprintf call in the client buffer initialization the number of tokens can be increased 2) The application crashes with a segmentation fault at the snprintf call in the client buffer initialization if the post data contains form-encoded values with percent (%) signs. So for example $ is represented as %24 in a form-encoded format and a few of these percent signs will cause the segmentation fault - Not sure what the best way is to handle this will be since % is also the token format character for string replacements Humair |
|
From: Feighery, P. D. <fei...@mi...> - 2011-12-08 16:29:21
|
I'm trying to determine how many HTTP transactions per second a particular device can support given one http transaction per each tcp connection. Ideally I would like to generate 100 HTTP TPS every second for X seconds, then increase the load to 200 HTTP TPS every second for X seconds, etc., until I find the threshold.
Initially I took the brute force method and wrote a bunch of bash scripts around curl, and was able to successfully generate about 900 TPS. Given my test setup, I believe my bottleneck was forking curl 900 times per second in a bash script.
So I found and downloaded and installed curl-load 0.52 and have been trying to understand how I can use it to replace my scripts. Currently I'm using the lo interface to better understand how it works
I can't seem to configure curl-loader to match the above configuration
When I try the following
---
########### GENERAL SECTION ################################
BATCH_NAME= http
CLIENTS_NUM_MAX=12
CLIENTS_NUM_START=6
CLIENTS_RAMPUP_INC=2
INTERFACE =lo
NETMASK=29
IP_ADDR_MIN= 10.200.001.1
IP_ADDR_MAX= 10.200.200.255 #Actually - this is for self-control
CYCLES_NUM=1
URLS_NUM=1
########### URL SECTION ####################################
URL=http://localhost/index.html
URL_SHORT_NAME="BB"
REQUEST_TYPE=GET
TIMER_URL_COMPLETION = 5000
---
According to the logs
During the 0th second it generated 6 HTTP GET transactions
During the 1th second it generated 2 HTTP GET transactions
During the 2nd second it generated 2 HTTP GET transactions
During the 3rd second it generated 2 HTTP GET transactions
Is there a way for it to generated 6,8,10,12 transactions per second?
Also I want to repeat each loading for X seconds, which I thought I could do with CYCLES_NUM, however when I add CYCLES_NUM=2 I get the following
During the 0th second it generated 12 HTTP GET transactions
During the 1th second it generated 2 HTTP GET transactions
During the 2nd second it generated 2 HTTP GET transactions
During the 3rd second it generated 2 HTTP GET transactions
Where I would have preferred the following
During the 0th second I want it to generate 6 HTTP GET transactions
During the 1th second I want it to generate 6 HTTP GET transactions
During the 2nd second I want it to generate 8 HTTP GET transactions
During the 3rd second I want it to generate 8 HTTP GET transactions
During the 4th second I want it to generate 10 HTTP GET transactions
During the 5th second I want it to generate 10 HTTP GET transactions
During the 6th second I want it to generate 12 HTTP GET transactions
During the 7th second I want it to generate 12 HTTP GET transactions
>From reading the description of curl-loader it appears that this is possible, can anyone help me with a correct config file.
Thanks
Pat
|
|
From: Brendan M. <Bre...@mo...> - 2011-11-30 21:27:42
|
Does curl-loader allow for recursive downloading? i.e. go to a site like yahoo.com and get all of the embedded objects within the index.html? |
|
From: Humair M. <hu...@ho...> - 2011-11-29 13:37:23
|
Hello Robert - Thanks for confirming. I will double this to 16kb for my needs. Hopefully that wont cause any buffer overflow issues. Humair Date: Tue, 29 Nov 2011 08:35:30 +0200 Subject: Re: Size Limit on FORM_STRING variable From: cor...@gm... To: cur...@li... Yes. On Tue, Nov 29, 2011 at 5:28 AM, Humair Mohammed <hu...@ho...> wrote: It appears the following line # 2815 in parse_conf.c (v0.52) reads the 8192 characters from each line of the config file and I believe that explains the 8kb truncation. char fgets_buff[1024*8]; From: hu...@ho... To: cur...@li... Subject: Size Limit on FORM_STRING variable Date: Mon, 28 Nov 2011 12:04:25 -0600 Hello - It appears that there is a 8kb size limit on the the FORM_STRING variable value in the curl-loader configuration file. I am testing an application with a large size post data and curl-loader fails to start with the following message: ******************************found form_str XXXadd_param_to_batch - error: unknown tag n. ATTENTION: If the tag not misspelled, read README.Migration file. parse_config_file - error: add_param_to_batch () failed processing buffer "n" main - error: parse_config_file () failed.****************************** It appears that if the FORM_STRING has a value that exceeds 8kb length the error message traps this and anything past the 8kb limit (in this case 'n' which is reported as unknown tag n) and reports the error above. If I remove anything past the 8kb string then the post works just fine. Is there a setting that will allow me to post large amounts of form data? I haven't tried the MULTIPART_FORM_DATA since it does not allow token replacements and I need token replacement functionality using the FORM_STRING and template file. If this need code recompilation to adjust for my case I would request any pointers in terms of which source file needs to be changed to increase the limits. I understand libcurl does not have any limits imposed on the size of the data that can be posted so I am hoping there is some setting in the curl-loader code that is adding this limitation that can be resolved. Thanks! Humair ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ curl-loader-devel mailing list cur...@li... https://lists.sourceforge.net/lists/listinfo/curl-loader-devel ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ curl-loader-devel mailing list cur...@li... https://lists.sourceforge.net/lists/listinfo/curl-loader-devel -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit...................................................................... Ghotit DyslexiaAssistive technology that understands you ...................................................................... ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ curl-loader-devel mailing list cur...@li... https://lists.sourceforge.net/lists/listinfo/curl-loader-devel |
|
From: Robert I. <cor...@gm...> - 2011-11-29 06:35:39
|
Yes. On Tue, Nov 29, 2011 at 5:28 AM, Humair Mohammed <hu...@ho...>wrote: > It appears the following line # 2815 in parse_conf.c (v0.52) reads the > 8192 characters from each line of the config file and I believe that > explains the 8kb truncation. > > char fgets_buff[1024*8]; > > > ------------------------------ > From: hu...@ho... > To: cur...@li... > Subject: Size Limit on FORM_STRING variable > Date: Mon, 28 Nov 2011 12:04:25 -0600 > > > Hello - It appears that there is a 8kb size limit on the the FORM_STRING > variable value in the curl-loader configuration file. I am testing an > application with a large size post data and curl-loader fails to start with > the following message: > > ****************************** > found form_str XXX > add_param_to_batch - error: unknown tag n. > > ATTENTION: If the tag not misspelled, read README.Migration file. > > parse_config_file - error: add_param_to_batch () failed processing buffer > "n" > main - error: parse_config_file () failed. > ****************************** > > It appears that if the FORM_STRING has a value that exceeds 8kb length the > error message traps this and anything past the 8kb limit (in this case 'n' > which is reported as unknown tag n) and reports the error above. If I > remove anything past the 8kb string then the post works just fine. Is there > a setting that will allow me to post large amounts of form data? I haven't > tried the MULTIPART_FORM_DATA since it does not allow token replacements > and I need token replacement functionality using the FORM_STRING and > template file. > > If this need code recompilation to adjust for my case I would request any > pointers in terms of which source file needs to be changed to increase the > limits. I understand libcurl does not have any limits imposed on the size > of the data that can be posted so I am hoping there is some setting in the > curl-loader code that is adding this limitation that can be resolved. > > Thanks! > > Humair > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security threats, > fraudulent activity, and more. Splunk takes this data and makes sense of > it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ curl-loader-devel mailing > list cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... |
|
From: Humair M. <hu...@ho...> - 2011-11-29 03:28:20
|
It appears the following line # 2815 in parse_conf.c (v0.52) reads the 8192 characters from each line of the config file and I believe that explains the 8kb truncation. char fgets_buff[1024*8]; From: hu...@ho... To: cur...@li... Subject: Size Limit on FORM_STRING variable Date: Mon, 28 Nov 2011 12:04:25 -0600 Hello - It appears that there is a 8kb size limit on the the FORM_STRING variable value in the curl-loader configuration file. I am testing an application with a large size post data and curl-loader fails to start with the following message: ******************************found form_str XXXadd_param_to_batch - error: unknown tag n. ATTENTION: If the tag not misspelled, read README.Migration file. parse_config_file - error: add_param_to_batch () failed processing buffer "n"main - error: parse_config_file () failed.****************************** It appears that if the FORM_STRING has a value that exceeds 8kb length the error message traps this and anything past the 8kb limit (in this case 'n' which is reported as unknown tag n) and reports the error above. If I remove anything past the 8kb string then the post works just fine. Is there a setting that will allow me to post large amounts of form data? I haven't tried the MULTIPART_FORM_DATA since it does not allow token replacements and I need token replacement functionality using the FORM_STRING and template file. If this need code recompilation to adjust for my case I would request any pointers in terms of which source file needs to be changed to increase the limits. I understand libcurl does not have any limits imposed on the size of the data that can be posted so I am hoping there is some setting in the curl-loader code that is adding this limitation that can be resolved. Thanks! Humair ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ curl-loader-devel mailing list cur...@li... https://lists.sourceforge.net/lists/listinfo/curl-loader-devel |
|
From: Humair M. <hu...@ho...> - 2011-11-28 18:04:32
|
Hello - It appears that there is a 8kb size limit on the the FORM_STRING variable value in the curl-loader configuration file. I am testing an application with a large size post data and curl-loader fails to start with the following message: ******************************found form_str XXXadd_param_to_batch - error: unknown tag n. ATTENTION: If the tag not misspelled, read README.Migration file. parse_config_file - error: add_param_to_batch () failed processing buffer "n"main - error: parse_config_file () failed.****************************** It appears that if the FORM_STRING has a value that exceeds 8kb length the error message traps this and anything past the 8kb limit (in this case 'n' which is reported as unknown tag n) and reports the error above. If I remove anything past the 8kb string then the post works just fine. Is there a setting that will allow me to post large amounts of form data? I haven't tried the MULTIPART_FORM_DATA since it does not allow token replacements and I need token replacement functionality using the FORM_STRING and template file. If this need code recompilation to adjust for my case I would request any pointers in terms of which source file needs to be changed to increase the limits. I understand libcurl does not have any limits imposed on the size of the data that can be posted so I am hoping there is some setting in the curl-loader code that is adding this limitation that can be resolved. Thanks! Humair |
|
From: Robert I. <cor...@gm...> - 2011-11-20 05:17:01
|
Dear Shao Shuchao, Thanks, good catch. I see that the area is buggy and will correct it. Sincerely. Robert On Fri, Nov 18, 2011 at 11:38 AM, Shao, Shuchao <ss...@we...> wrote: > Hi all, > > When curl-loader(0.53) runs with -t option and reads URLs from a file with > token and template, it will crash immediately. I create a patch file to fix > this issue, please review it and let me know if has any questions. > > Thanks, > Simon > > > Protected by Websense Hosted Email Security -- www.websense.com > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... |
|
From: Shao, S. <ss...@we...> - 2011-11-18 09:39:07
|
Hi all, When curl-loader(0.53) runs with -t option and reads URLs from a file with token and template, it will crash immediately. I create a patch file to fix this issue, please review it and let me know if has any questions. Thanks, Simon Protected by Websense Hosted Email Security -- www.websense.com |
|
From: Tomy a. <i_r...@ho...> - 2011-10-30 23:30:46
|
http://nrol8kgvi.blog.com/ed/ |
|
From: Brendan M. <Bre...@mo...> - 2011-10-25 01:25:07
|
Thanks Robert, setting the LD_LIBRARY_PATH sorted it. -----Original Message----- From: Robert Iakobashvili [mailto:cor...@gm...] Sent: Sunday, 23 October 2011 5:48 a.m. To: curl-loader-devel Subject: Re: curl-loader: undefined symbol: ares_library_init Hi Brendan McGoldrick, Alternatively, you can take the version from the svn since this issue has been fixed. Regards, Robert On Sat, Oct 22, 2011 at 6:46 PM, Robert Iakobashvili <cor...@gm...> wrote: > Hi Brendan McGoldrick, > > curl-loader builds libcares by itself. > > It should be libcares.so as well as libcurl.so built within > curl-loader distribution. > You can add that dir as the first one in your LD_LIBRARY_PATH > > E..g. > > export LD_LIBRARY_PATH=FULL_PATH_TO_THAT_DIR:$LD_LIBRARY_PATH > > Take care, > > Regards, > Robert Iakobashvili, Ph.D. > > Home: http://www.ghotit.com > Blog: http://dyslexia-blog.ghotit.com > Twitter: http://twitter.com/ghotit > Facebook: http://facebook.com/ghotit > ...................................................................... > Ghotit Dyslexia > Assistive technology that understands you > ...................................................................... > > On Fri, Oct 21, 2011 at 2:34 AM, Brendan McGoldrick > <Bre...@mo...> wrote: >> Hi Folks, >> >> >> >> I'm trying to use curl-loader for the first time. I've successfully >> downloaded and built it on my Redhat5.6 x64 OS by following the Fast Start >> instructions. The open additional item that I did was to edit the MakeFile >> to change >> >> >> >> OPENSSLDIR=$(shell $(CURDIR)/openssldir.sh) >> to >> OPENSSLDIR=/usr/lib64/openssl >> >> >> >> I didn't appear to have any make errors. >> >> >> >> Now when I try to run curl-loader for the first time with the >> conf-examples/bulk.conf as the conf file, I keep getting the below error. >> (full output and configuration file are below). >> >> >> >> curl-loader: symbol lookup error: curl-loader: undefined symbol: >> ares_library_init >> >> >> >> My installed c-ares rpm's are below. >> >> >> >> [root@iamsp09mte lib64]# rpm -qa | grep ares >> >> c-ares-1.6.0-5.el5 >> >> c-ares-devel-1.6.0-5.el5 >> >> >> >> Any ideas on what is causing this error and what I can do to resolve it? >> >> >> >> Cheers >> >> Brendan >> >> >> >> ########### GENERAL SECTION ################################ >> >> >> >> BATCH_NAME= bulk >> >> CLIENTS_NUM_MAX=200 # Same as CLIENTS_NUM >> >> #CLIENTS_NUM_START=10 >> >> CLIENTS_RAMPUP_INC=5 >> >> INTERFACE =eth0 >> >> NETMASK=16 >> >> IP_ADDR_MIN= 192.168.1.1 >> >> IP_ADDR_MAX= 192.168.1.3 >> >> IP_SHARED_NUM=3 >> >> CYCLES_NUM= -1 >> >> URLS_NUM= 1 >> >> >> >> ########### URL SECTION #################################### >> >> >> >> URL=http://localhost/index.html >> >> #URL=http://localhost/apache2-default/ACE-INSTALL.html >> >> #URL=http://localhost/ACE-INSTALL.html >> >> URL_SHORT_NAME="local-apache" >> >> REQUEST_TYPE=GET >> >> TIMER_URL_COMPLETION = 5000 >> >> TIMER_AFTER_URL_SLEEP = 500 >> >> >> >> [root@iamsp09mte conf-examples]# curl-loader -f bulk.conf >> >> parse_config_file - loaded 1 batches >> >> >> >> The configuration has been post-validated successfully. >> >> >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> add_secondary_ip_addrs - successfully added 192.168.1.1/16 IP-address. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> add_secondary_ip_addrs - successfully added 192.168.1.2/16 IP-address. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> add_secondary_ip_addrs - successfully added 192.168.1.3/16 IP-address. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> main - added IP-addresses to the loading network interface. >> >> >> >> RUNNING LOAD >> >> >> >> curl-loader: symbol lookup error: curl-loader: undefined symbol: >> ares_library_init >> >> ------------------------------------------------------------------------------ >> The demand for IT networking professionals continues to grow, and the >> demand for specialized networking skills is growing even more rapidly. >> Take a complimentary Learning@Cisco Self-Assessment and learn >> about Cisco certifications, training, and career opportunities. >> http://p.sf.net/sfu/cisco-dev2dev >> _______________________________________________ >> curl-loader-devel mailing list >> cur...@li... >> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >> >> > -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ curl-loader-devel mailing list cur...@li... https://lists.sourceforge.net/lists/listinfo/curl-loader-devel |
|
From: Shao, S. <ss...@we...> - 2011-10-24 03:19:49
|
Thanks for your reply Robert. Yes the proxy authentication using passwords from file is not supported for all other methods neither. But my patch is only for NTLM until now. I think it is very easy to make extension to supporting the other methods. I think NTLM is supported by libcurl for a long time, while Negotiation Authentication is supported from libcurl 7.21.0. I've tried with 1000 users (1000 IP and 1000 usernames) to authenticate against the proxy, and it works well. Thanks, Simon -----Original Message----- From: Robert Iakobashvili [mailto:cor...@gm...] Sent: Sunday, October 23, 2011 00:58 To: curl-loader-devel Subject: Re: Questions with curl-loader 0.53 Dear Sha, Shuchao. On Thu, Oct 20, 2011 at 5:17 AM, Shao, Shuchao <ss...@we...> wrote: > 1. I noticed there are two new params ( URL_RANDOM_RANGE and > URL_RANDOM_TOKEN ) which introduced by 0.5.3, but seems there is no > document/help sys to mention how to use them? Could you give an > example how to use them? They are explained in man page as well as in README.There is a sample configuration file as well. > > 2. When I launch curl-loader with -t option (e.g. -t 10), I always > get "segmentation fault", while all the things will go to OK if get > rid if this option. Does any of you have tested if this option works? > If yes, could you give me some suggestions how to use it? You can compile it it with -g (make debug=1 optimize=1) option, allow core in your shell by: #ulimit -c unlimited get the core, inspect it and, hopefully, to find the bug. I was using this option with -t 2 and -t 4. I'd recommend to try it equal to the number of effective CPU cores. > > 3. As I know, the current version supports to read the usernames and > passwords from file when login to a webserver, while does NOT support > to read credentials from a file when authenticate against a proxy > server using NTLM method. I have written some code to support it, > please find the patch file from attachment if you have interest. Thank you for your patch very much! I'll look at it at my free timeslot. My understanding is that proxy authentication using passwords from file is not supported for all other methods as well (Digest, Basic, etc) >From what I mem, NTML is only recently started to be supported in >libcurl that curl-loader is using for multiple connections. What is the number of connections it works for you? -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... > Thanks, > > Simon > > > > Protected by Websense Hosted Email Security - www.websense.com > > ---------------------------------------------------------------------- > -------- The demand for IT networking professionals continues to grow, > and the demand for specialized networking skills is growing even more > rapidly. > Take a complimentary Learning@Ciosco Self-Assessment and learn about > Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ curl-loader-devel mailing list cur...@li... https://lists.sourceforge.net/lists/listinfo/curl-loader-devel To report this as spam, please forward to sp...@we.... Thank you. --- Scanned by ESG 7.6 --- |
|
From: Robert I. <cor...@gm...> - 2011-10-22 16:57:41
|
Dear Sha, Shuchao. On Thu, Oct 20, 2011 at 5:17 AM, Shao, Shuchao <ss...@we...> wrote: > 1. I noticed there are two new params ( URL_RANDOM_RANGE and > URL_RANDOM_TOKEN ) which introduced by 0.5.3, but seems there is no > document/help sys to mention how to use them? Could you give an example how > to use them? They are explained in man page as well as in README. There is a sample configuration file as well. > > 2. When I launch curl-loader with –t option (e.g. –t 10), I always get > “segmentation fault”, while all the things will go to OK if get rid if this > option. Does any of you have tested if this option works? If yes, could you > give me some suggestions how to use it? You can compile it it with -g (make debug=1 optimize=1) option, allow core in your shell by: #ulimit -c unlimited get the core, inspect it and, hopefully, to find the bug. I was using this option with -t 2 and -t 4. I'd recommend to try it equal to the number of effective CPU cores. > > 3. As I know, the current version supports to read the usernames and > passwords from file when login to a webserver, while does NOT support to > read credentials from a file when authenticate against a proxy server using > NTLM method. I have written some code to support it, please find the patch > file from attachment if you have interest. Thank you for your patch very much! I'll look at it at my free timeslot. My understanding is that proxy authentication using passwords from file is not supported for all other methods as well (Digest, Basic, etc) >From what I mem, NTML is only recently started to be supported in libcurl that curl-loader is using for multiple connections. What is the number of connections it works for you? -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... > Thanks, > > Simon > > > > Protected by Websense Hosted Email Security — www.websense.com > > ------------------------------------------------------------------------------ > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Ciosco Self-Assessment and learn > about Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > |
|
From: Robert I. <cor...@gm...> - 2011-10-22 16:48:10
|
Hi Brendan McGoldrick, Alternatively, you can take the version from the svn since this issue has been fixed. Regards, Robert On Sat, Oct 22, 2011 at 6:46 PM, Robert Iakobashvili <cor...@gm...> wrote: > Hi Brendan McGoldrick, > > curl-loader builds libcares by itself. > > It should be libcares.so as well as libcurl.so built within > curl-loader distribution. > You can add that dir as the first one in your LD_LIBRARY_PATH > > E..g. > > export LD_LIBRARY_PATH=FULL_PATH_TO_THAT_DIR:$LD_LIBRARY_PATH > > Take care, > > Regards, > Robert Iakobashvili, Ph.D. > > Home: http://www.ghotit.com > Blog: http://dyslexia-blog.ghotit.com > Twitter: http://twitter.com/ghotit > Facebook: http://facebook.com/ghotit > ...................................................................... > Ghotit Dyslexia > Assistive technology that understands you > ...................................................................... > > On Fri, Oct 21, 2011 at 2:34 AM, Brendan McGoldrick > <Bre...@mo...> wrote: >> Hi Folks, >> >> >> >> I’m trying to use curl-loader for the first time. I’ve successfully >> downloaded and built it on my Redhat5.6 x64 OS by following the Fast Start >> instructions. The open additional item that I did was to edit the MakeFile >> to change >> >> >> >> OPENSSLDIR=$(shell $(CURDIR)/openssldir.sh) >> to >> OPENSSLDIR=/usr/lib64/openssl >> >> >> >> I didn’t appear to have any make errors. >> >> >> >> Now when I try to run curl-loader for the first time with the >> conf-examples/bulk.conf as the conf file, I keep getting the below error. >> (full output and configuration file are below). >> >> >> >> curl-loader: symbol lookup error: curl-loader: undefined symbol: >> ares_library_init >> >> >> >> My installed c-ares rpm’s are below. >> >> >> >> [root@iamsp09mte lib64]# rpm -qa | grep ares >> >> c-ares-1.6.0-5.el5 >> >> c-ares-devel-1.6.0-5.el5 >> >> >> >> Any ideas on what is causing this error and what I can do to resolve it? >> >> >> >> Cheers >> >> Brendan >> >> >> >> ########### GENERAL SECTION ################################ >> >> >> >> BATCH_NAME= bulk >> >> CLIENTS_NUM_MAX=200 # Same as CLIENTS_NUM >> >> #CLIENTS_NUM_START=10 >> >> CLIENTS_RAMPUP_INC=5 >> >> INTERFACE =eth0 >> >> NETMASK=16 >> >> IP_ADDR_MIN= 192.168.1.1 >> >> IP_ADDR_MAX= 192.168.1.3 >> >> IP_SHARED_NUM=3 >> >> CYCLES_NUM= -1 >> >> URLS_NUM= 1 >> >> >> >> ########### URL SECTION #################################### >> >> >> >> URL=http://localhost/index.html >> >> #URL=http://localhost/apache2-default/ACE-INSTALL.html >> >> #URL=http://localhost/ACE-INSTALL.html >> >> URL_SHORT_NAME="local-apache" >> >> REQUEST_TYPE=GET >> >> TIMER_URL_COMPLETION = 5000 >> >> TIMER_AFTER_URL_SLEEP = 500 >> >> >> >> [root@iamsp09mte conf-examples]# curl-loader -f bulk.conf >> >> parse_config_file - loaded 1 batches >> >> >> >> The configuration has been post-validated successfully. >> >> >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> add_secondary_ip_addrs - successfully added 192.168.1.1/16 IP-address. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> add_secondary_ip_addrs - successfully added 192.168.1.2/16 IP-address. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> add_secondary_ip_addrs - successfully added 192.168.1.3/16 IP-address. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.3 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.1 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" >> already exists. >> >> add_secondary_ip_addrs - setting secondary IP 192.168.1.2 >> >> rtnl_talk(): RTNETLINK answers: File exists >> >> add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" >> already exists. >> >> main - added IP-addresses to the loading network interface. >> >> >> >> RUNNING LOAD >> >> >> >> curl-loader: symbol lookup error: curl-loader: undefined symbol: >> ares_library_init >> >> ------------------------------------------------------------------------------ >> The demand for IT networking professionals continues to grow, and the >> demand for specialized networking skills is growing even more rapidly. >> Take a complimentary Learning@Cisco Self-Assessment and learn >> about Cisco certifications, training, and career opportunities. >> http://p.sf.net/sfu/cisco-dev2dev >> _______________________________________________ >> curl-loader-devel mailing list >> cur...@li... >> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >> >> > -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... |
|
From: Robert I. <cor...@gm...> - 2011-10-22 16:47:05
|
Hi Brendan McGoldrick, curl-loader builds libcares by itself. It should be libcares.so as well as libcurl.so built within curl-loader distribution. You can add that dir as the first one in your LD_LIBRARY_PATH E..g. export LD_LIBRARY_PATH=FULL_PATH_TO_THAT_DIR:$LD_LIBRARY_PATH Take care, Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... On Fri, Oct 21, 2011 at 2:34 AM, Brendan McGoldrick <Bre...@mo...> wrote: > Hi Folks, > > > > I’m trying to use curl-loader for the first time. I’ve successfully > downloaded and built it on my Redhat5.6 x64 OS by following the Fast Start > instructions. The open additional item that I did was to edit the MakeFile > to change > > > > OPENSSLDIR=$(shell $(CURDIR)/openssldir.sh) > to > OPENSSLDIR=/usr/lib64/openssl > > > > I didn’t appear to have any make errors. > > > > Now when I try to run curl-loader for the first time with the > conf-examples/bulk.conf as the conf file, I keep getting the below error. > (full output and configuration file are below). > > > > curl-loader: symbol lookup error: curl-loader: undefined symbol: > ares_library_init > > > > My installed c-ares rpm’s are below. > > > > [root@iamsp09mte lib64]# rpm -qa | grep ares > > c-ares-1.6.0-5.el5 > > c-ares-devel-1.6.0-5.el5 > > > > Any ideas on what is causing this error and what I can do to resolve it? > > > > Cheers > > Brendan > > > > ########### GENERAL SECTION ################################ > > > > BATCH_NAME= bulk > > CLIENTS_NUM_MAX=200 # Same as CLIENTS_NUM > > #CLIENTS_NUM_START=10 > > CLIENTS_RAMPUP_INC=5 > > INTERFACE =eth0 > > NETMASK=16 > > IP_ADDR_MIN= 192.168.1.1 > > IP_ADDR_MAX= 192.168.1.3 > > IP_SHARED_NUM=3 > > CYCLES_NUM= -1 > > URLS_NUM= 1 > > > > ########### URL SECTION #################################### > > > > URL=http://localhost/index.html > > #URL=http://localhost/apache2-default/ACE-INSTALL.html > > #URL=http://localhost/ACE-INSTALL.html > > URL_SHORT_NAME="local-apache" > > REQUEST_TYPE=GET > > TIMER_URL_COMPLETION = 5000 > > TIMER_AFTER_URL_SLEEP = 500 > > > > [root@iamsp09mte conf-examples]# curl-loader -f bulk.conf > > parse_config_file - loaded 1 batches > > > > The configuration has been post-validated successfully. > > > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > add_secondary_ip_addrs - successfully added 192.168.1.1/16 IP-address. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > add_secondary_ip_addrs - successfully added 192.168.1.2/16 IP-address. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > add_secondary_ip_addrs - successfully added 192.168.1.3/16 IP-address. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.3 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.1 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" > already exists. > > add_secondary_ip_addrs - setting secondary IP 192.168.1.2 > > rtnl_talk(): RTNETLINK answers: File exists > > add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" > already exists. > > main - added IP-addresses to the loading network interface. > > > > RUNNING LOAD > > > > curl-loader: symbol lookup error: curl-loader: undefined symbol: > ares_library_init > > ------------------------------------------------------------------------------ > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Cisco Self-Assessment and learn > about Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > |
|
From: Brendan M. <Bre...@mo...> - 2011-10-21 00:35:18
|
Hi Folks, I'm trying to use curl-loader for the first time. I've successfully downloaded and built it on my Redhat5.6 x64 OS by following the Fast Start instructions. The open additional item that I did was to edit the MakeFile to change OPENSSLDIR=$(shell $(CURDIR)/openssldir.sh) to OPENSSLDIR=/usr/lib64/openssl I didn't appear to have any make errors. Now when I try to run curl-loader for the first time with the conf-examples/bulk.conf as the conf file, I keep getting the below error. (full output and configuration file are below). curl-loader: symbol lookup error: curl-loader: undefined symbol: ares_library_init My installed c-ares rpm's are below. [root@iamsp09mte lib64]# rpm -qa | grep ares c-ares-1.6.0-5.el5 c-ares-devel-1.6.0-5.el5 Any ideas on what is causing this error and what I can do to resolve it? Cheers Brendan ########### GENERAL SECTION ################################ BATCH_NAME= bulk CLIENTS_NUM_MAX=200 # Same as CLIENTS_NUM #CLIENTS_NUM_START=10 CLIENTS_RAMPUP_INC=5 INTERFACE =eth0 NETMASK=16 IP_ADDR_MIN= 192.168.1.1 IP_ADDR_MAX= 192.168.1.3 IP_SHARED_NUM=3 CYCLES_NUM= -1 URLS_NUM= 1 ########### URL SECTION #################################### URL=http://localhost/index.html #URL=http://localhost/apache2-default/ACE-INSTALL.html #URL=http://localhost/ACE-INSTALL.html URL_SHORT_NAME="local-apache" REQUEST_TYPE=GET TIMER_URL_COMPLETION = 5000 TIMER_AFTER_URL_SLEEP = 500 [root@iamsp09mte conf-examples]# curl-loader -f bulk.conf parse_config_file - loaded 1 batches The configuration has been post-validated successfully. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 add_secondary_ip_addrs - successfully added 192.168.1.1/16 IP-address. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 add_secondary_ip_addrs - successfully added 192.168.1.2/16 IP-address. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 add_secondary_ip_addrs - successfully added 192.168.1.3/16 IP-address. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.3 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.3/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.1 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.1/16" already exists. add_secondary_ip_addrs - setting secondary IP 192.168.1.2 rtnl_talk(): RTNETLINK answers: File exists add_secondary_ip_addrs - note: probably, the IP-address "192.168.1.2/16" already exists. main - added IP-addresses to the loading network interface. RUNNING LOAD curl-loader: symbol lookup error: curl-loader: undefined symbol: ares_library_init |
|
From: Graham B. <bi...@gm...> - 2011-10-12 21:54:05
|
Hello, I am using curl-loader 1.53. When I attempt to configure a POST request to login using the included examples as templates, I get a segmentation fault: curl-loader -c5 -m1 -r -v -u -f load-after-login.conf found form_str username=%s&password=%s Segmentation fault The URL configuration is: #Get the login page. URL=http://testing.foo.bar/signin URL_SHORT_NAME="signin1" URL_DONT_CYCLE=1 REQUEST_TYPE=GET TIMER_URL_COMPLETION=1000 TIMER_AFTER_URL_SLEEP=0 #Post it to login URL="" URL_USE_CURRENT=1 URL_SHORT_NAME="signin2" URL_DONT_CYCLE=1 USERNAME=tester PASSWORD=testing REQUEST_TYPE=POST FORM_USAGE_TYPE=SINGLE_USER #FORM_STRING= username_login=%s&password_login=%s #That might not work like it seems, from login-uas-cycling.conf: FORM_STRING= username=%s&password=%s TIMER_URL_COMPLETION=1000 TIMER_AFTER_URL_SLEEP=500 #Request something URL=http://testing.foo.bar/search URL_SHORT_NAME="latestkeeks" URL_DONT_CYCLE=1 REQUEST_TYPE=GET TIMER_URL_COMPLETION=1000 TIMER_AFTER_URL_SLEEP=500 Which is based off of login-uas-cycling.conf in the examples. Can you point out my error or suggest a remedy? \\//, Lorax |
|
From: CK Z. <ck...@fo...> - 2011-10-12 09:49:46
|
Thanks a lot for your help!! Best Regards, CK #8042 -----Original Message----- From: Robert Iakobashvili [mailto:cor...@gm...] Sent: Wednesday, October 12, 2011 4:52 PM To: curl-loader-devel Subject: Re: HTTPS throughput too low Hi CK Zhang, Now it clear what happens. curl-loader: - establishes TCP connections; - makes expensive TLS/SSL handshake - fetches the file. After fetching file, curl-loader closes the TCP-connection. Next cycle it establishes the TCP-connection and makes the expensive TLS/SSL handshake again, and fetches the file. To achieve high throughput libcurl needs to be configured to re-use the established TCP connection and TLS/SSL for the next file transfer and not to re-establish it every cycle. I suggest you to look in curl (libcurl) options and I will also be doing that. Thanks for your reporting. On Wed, Oct 12, 2011 at 2:59 AM, CK Zhang <ck...@fo...> wrote: > > Attached logs, and output from console > > ============ loading batch is: Apach > ====================================== > ---------------------------------------------------------------------------- > ---- > Interval stats (latest:3 sec, clients:100, CAPS-curr:60): > H/F > Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To > :0B/s > H/F/S > Req:200,1xx:0,2xx:201,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:553ms,D-2xx:553ms,Ti > :6854220B/s,To:18800B/s > ---------------------------------------------------------------------------- > ---- > Summary stats (runs:48 secs, CAPS-average:60): > H/F > Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To > :0B/s > H/F/S > Req:2878,1xx:0,2xx:2873,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:614ms,D-2xx:614ms, > Ti:6087722B/s,To:17182B/s > ============================================================================ > ===== > Manual: clients:max[100],curr[100]. Inc num: [+|*]. > ============================================================================ > ===== > > Best Regards, > CK > #8042 > > > -----Original Message----- > From: Robert Iakobashvili [mailto:cor...@gm...] > Sent: Tuesday, October 11, 2011 5:49 PM > To: curl-loader-devel > Subject: Re: HTTPS throughput too low > > Please, try > > CLIENTS_NUM_MAX=100 > CLIENTS_NUM_START=100 > > and comment out > #CLIENTS_RAMPUP_INC=10 > > Say, what happens with traffic and send me the log. > > On Tue, Oct 11, 2011 at 11:36 AM, CK Zhang <ck...@fo...> wrote: >> Attached :) thanks! >> >> Best Regards, >> CK >> #8042 >> >> >> -----Original Message----- >> From: Robert Iakobashvili [mailto:cor...@gm...] >> Sent: Tuesday, October 11, 2011 5:33 PM >> To: curl-loader-devel >> Subject: Re: HTTPS throughput too low >> >> Could you send me it zipped not rarred? >> Thanks! >> >> On Tue, Oct 11, 2011 at 11:30 AM, CK Zhang <ck...@fo...> wrote: >>> Dear Robert >>> >>> Attached test log by command "./curl-loader -f https.conf -v" >>> >>> Best Regards, >>> CK >>> #8042 >>> >>> -----Original Message----- >>> From: Robert Iakobashvili [mailto:cor...@gm...] >>> Sent: Tuesday, October 11, 2011 5:19 PM >>> To: curl-loader-devel >>> Subject: Re: HTTPS throughput too low >>> >>> Dear CK Zhang, >>> >>> Can you run HTTPS sessions with -v detailed logging and say if >>> you seen in logs something interesting. >>> Thanks, >>> Robert >>> >>> >>> >>> On Tue, Oct 11, 2011 at 11:14 AM, CK Zhang <ck...@fo...> wrote: >>>> Dear Robert >>>> >>>> >>>> >>>> Thanks a lot for your replay, >>>> >>>> >>>> >>>> Here are some answer about your questions >>>> >>>> >>>> >>>> >>>> >>>> What happens if you try HTTP? Does it impact throughput? >>>> >>>> It is normal and perfect if I test with HTTP, The throughput can reach >> to >>>> 950Mbps. >>>> >>>> >>>> >>>> Which tools you are using to measure throughput? >>>> >>>> There are 2 ways I used, >>>> >>>> 1 check the log summary form cur-loader like this >>>> Ti:5261372B/s,To:18375B/s >>>> >>>> 2 check real time traffic speed on switch with connected test PC and > HTTP >>>> server >>>> >>>> >>>> >>>> What happens, if you try just to ftp some large file between the >> machines? >>>> >>>> NO test >>>> >>>> What about CPU usage at both client and server? >>>> >>>> Both they are busy, about 80% >>>> >>>> Which HTTP server is in use? >>>> >>>> Apache/2.2.21 >>>> >>>> Have you looked into logs of curl-loader and your web-server? >>>> >>>> Checked log, not find abnormal issue. >>>> >>>> >>>> >>>> >>>> >>>> Today, I used Loadrunner11 to simulate https traffic with same >>> environments >>>> (same apache server) , it can reach to 110Mpbs. But still only get >>> 800kbps >>>> with cur-loader. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Best Regards, >>>> >>>> CK >>>> >>>> #8042 >>>> >>>> >>>> >>>> From: Robert Iakobashvili [mailto:cor...@gm...] >>>> Sent: Tuesday, September 27, 2011 1:19 PM >>>> To: curl-loader-devel >>>> Subject: Re: HTTPS throughput too low >>>> >>>> >>>> >>>> Dear CK Zhang, >>>> >>>> On Mon, Sep 26, 2011 at 5:01 AM, CK Zhang <ck...@fo...> wrote: >>>> >>>> >>>> >>>> I want to get high https stream with curl loader, but the Https >> throughput >>>> is about 800kbps between two PC, Http throughput can reach 950Mbps in >> that >>> 2 >>>> pcs, I do know if some have experience like this, and get a high https >>>> throughput with curl-loader, Thanks for any supports and help!! >>>> >>>> >>>> >>>> >>>> >>>> Here is my configuration: >>>> >>>> >>>> >>>> PC1:CPU Inter E2200, Mem 2G, 1000M NIC >>>> >>>> OpenSSL: >>>> >>>> openssl-devel-1.0.0-4.el6_0.2.x86_64 >>>> >>>> openssl-1.0.0-4.el6_0.2.x86_64 >>>> >>>> openssl-perl-1.0.0-4.el6_0.2.x86_64 >>>> >>>> >>>> >>>> curl-loader-0.53 >>>> >>>> ########### GENERAL SECTION >>>> ################################ >>>> >>>> BATCH_NAME= Apach >>>> >>>> CLIENTS_NUM_MAX=400 >>>> >>>> CLIENTS_NUM_START=100 >>>> >>>> CLIENTS_RAMPUP_INC=10 >>>> >>>> INTERFACE =eth2 >>>> >>>> NETMASK=16 >>>> >>>> IP_ADDR_MIN= 172.16.76.150 >>>> >>>> IP_ADDR_MAX= 172.16.246.250 #Actually - this is for self-control >>>> >>>> CYCLES_NUM= -1 >>>> >>>> URLS_NUM= 1 >>>> >>>> >>>> >>>> ########### URL SECTION #################################### >>>> >>>> >>>> >>>> URL=https://172.16.76.142/was/100KB.txt # the size of 100KB.txt is 100KB >>>> >>>> #URL=http://localhost/ACE-INSTALL.html >>>> >>>> URL_SHORT_NAME="local-index" >>>> >>>> REQUEST_TYPE=GET >>>> >>>> TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is >> enforced >>>> by cancelling url fetch on timeout >>>> >>>> TIMER_AFTER_URL_SLEEP =1000 >>>> >>>> ~ >>>> >>>> >>>> >>>> PC2. Works as Webserver,CPU Intel E7600,Mem 4G, 1000M NIC >>>> >>>> Server version: Apache/2.2.21 (Unix) >>>> >>>> Server built: Sep 21 2011 16:19:43 >>>> >>>> openssl-devel-1.0.0-4.el6_0.2.x86_64 >>>> >>>> openssl-1.0.0-4.el6_0.2.x86_64 >>>> >>>> openssl-perl-1.0.0-4.el6_0.2.x86_64 >>>> >>>> >>>> >>>> >>>> >>>> Interesting. >>>> >>>> >>>> >>>> What happens if you try HTTP? Does it impact throughput? >>>> >>>> >>>> >>>> Which tools you are using to measure throughput? >>>> >>>> >>>> >>>> What happens, if you try just to ftp some large file between the >> machines? >>>> >>>> >>>> >>>> What about CPU usage at both client and server? >>>> >>>> Which HTTP server is in use? >>>> >>>> >>>> >>>> Have you looked into logs of curl-loader and your web-server? >>>> >>>> >>>> >>>> -- >>>> Regards, >>>> Robert Iakobashvili, Ph.D. >>>> >>>> >>>> >>>> Home: http://www.ghotit.com >>>> >>>> Blog: http://dyslexia-blog.ghotit.com >>>> >>>> Twitter: http://twitter.com/ghotit >>>> >>>> Facebook: http://facebook.com/ghotit >>>> >>>> ...................................................................... >>>> >>>> Ghotit Dyslexia >>>> >>>> Assistive technology that understands you >>>> >>>> ...................................................................... >>>> >>>> >>>> >>>> ________________________________ >>>> >>>> *** Please note that this message and any attachments may contain >>>> confidential >>>> and proprietary material and information and are intended only for the >> use >>>> of >>>> the intended recipient(s). If you are not the intended recipient, you > are >>>> hereby >>>> notified that any review, use, disclosure, dissemination, distribution > or >>>> copying >>>> of this message and any attachments is strictly prohibited. If you have >>>> received >>>> this email in error, please immediately notify the sender and destroy >> this >>>> e-mail >>>> and any attachments and all copies, whether electronic or printed. >>>> Please also note that any views, opinions, conclusions or commitments >>>> expressed >>>> in this message are those of the individual sender and do not > necessarily >>>> reflect >>>> the views of Fortinet, Inc., its affiliates, and emails are not binding >> on >>>> Fortinet and only a writing manually signed by Fortinet's General > Counsel >>>> can be >>>> a binding commitment of Fortinet to Fortinet's customers or partners. >>> Thank >>>> you. *** >>>> >>>> ________________________________ >>>> >>>> >>> >> > ---------------------------------------------------------------------------- >>> -- >>>> All the data continuously generated in your IT infrastructure contains a >>>> definitive record of customers, application performance, security >>>> threats, fraudulent activity and more. Splunk takes this data and makes >>>> sense of it. Business sense. IT sense. Common sense. >>>> http://p.sf.net/sfu/splunk-d2d-oct >>>> _______________________________________________ >>>> curl-loader-devel mailing list >>>> cur...@li... >>>> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >>>> >>>> >>> >>> >>> >>> -- >>> Regards, >>> Robert Iakobashvili, Ph.D. >>> >>> Home: http://www.ghotit.com >>> Blog: http://dyslexia-blog.ghotit.com >>> Twitter: http://twitter.com/ghotit >>> Facebook: http://facebook.com/ghotit >>> ...................................................................... >>> Ghotit Dyslexia >>> Assistive technology that understands you >>> ...................................................................... >>> >>> >> > ---------------------------------------------------------------------------- >>> -- >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2d-oct >>> _______________________________________________ >>> curl-loader-devel mailing list >>> cur...@li... >>> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >>> >>> >>> *** Please note that this message and any attachments may contain >> confidential >>> and proprietary material and information and are intended only for the > use >> of >>> the intended recipient(s). If you are not the intended recipient, you are >> hereby >>> notified that any review, use, disclosure, dissemination, distribution or >> copying >>> of this message and any attachments is strictly prohibited. If you have >> received >>> this email in error, please immediately notify the sender and destroy > this >> e-mail >>> and any attachments and all copies, whether electronic or printed. >>> Please also note that any views, opinions, conclusions or commitments >> expressed >>> in this message are those of the individual sender and do not necessarily >> reflect >>> the views of Fortinet, Inc., its affiliates, and emails are not binding > on >>> Fortinet and only a writing manually signed by Fortinet's General Counsel >> can be >>> a binding commitment of Fortinet to Fortinet's customers or partners. >> Thank you. *** >>> >>> >> > ---------------------------------------------------------------------------- >> -- >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2d-oct >>> _______________________________________________ >>> curl-loader-devel mailing list >>> cur...@li... >>> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >>> >>> >> >> >> >> -- >> Regards, >> Robert Iakobashvili, Ph.D. >> >> Home: http://www.ghotit.com >> Blog: http://dyslexia-blog.ghotit.com >> Twitter: http://twitter.com/ghotit >> Facebook: http://facebook.com/ghotit >> ...................................................................... >> Ghotit Dyslexia >> Assistive technology that understands you >> ...................................................................... >> >> > ---------------------------------------------------------------------------- >> -- >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2d-oct >> _______________________________________________ >> curl-loader-devel mailing list >> cur...@li... >> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >> >> >> *** Please note that this message and any attachments may contain > confidential >> and proprietary material and information and are intended only for the use > of >> the intended recipient(s). If you are not the intended recipient, you are > hereby >> notified that any review, use, disclosure, dissemination, distribution or > copying >> of this message and any attachments is strictly prohibited. If you have > received >> this email in error, please immediately notify the sender and destroy this > e-mail >> and any attachments and all copies, whether electronic or printed. >> Please also note that any views, opinions, conclusions or commitments > expressed >> in this message are those of the individual sender and do not necessarily > reflect >> the views of Fortinet, Inc., its affiliates, and emails are not binding on >> Fortinet and only a writing manually signed by Fortinet's General Counsel > can be >> a binding commitment of Fortinet to Fortinet's customers or partners. > Thank you. *** >> >> > ---------------------------------------------------------------------------- > -- >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2d-oct >> _______________________________________________ >> curl-loader-devel mailing list >> cur...@li... >> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >> >> > > > > -- > Regards, > Robert Iakobashvili, Ph.D. > > Home: http://www.ghotit.com > Blog: http://dyslexia-blog.ghotit.com > Twitter: http://twitter.com/ghotit > Facebook: http://facebook.com/ghotit > ...................................................................... > Ghotit Dyslexia > Assistive technology that understands you > ...................................................................... > > ---------------------------------------------------------------------------- > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > > *** Please note that this message and any attachments may contain confidential > and proprietary material and information and are intended only for the use of > the intended recipient(s). If you are not the intended recipient, you are hereby > notified that any review, use, disclosure, dissemination, distribution or copying > of this message and any attachments is strictly prohibited. If you have received > this email in error, please immediately notify the sender and destroy this e-mail > and any attachments and all copies, whether electronic or printed. > Please also note that any views, opinions, conclusions or commitments expressed > in this message are those of the individual sender and do not necessarily reflect > the views of Fortinet, Inc., its affiliates, and emails are not binding on > Fortinet and only a writing manually signed by Fortinet's General Counsel can be > a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. *** > > ---------------------------------------------------------------------------- -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... ---------------------------------------------------------------------------- -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ curl-loader-devel mailing list cur...@li... https://lists.sourceforge.net/lists/listinfo/curl-loader-devel *** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. *** |
|
From: Robert I. <cor...@gm...> - 2011-10-12 08:52:03
|
Hi CK Zhang, Now it clear what happens. curl-loader: - establishes TCP connections; - makes expensive TLS/SSL handshake - fetches the file. After fetching file, curl-loader closes the TCP-connection. Next cycle it establishes the TCP-connection and makes the expensive TLS/SSL handshake again, and fetches the file. To achieve high throughput libcurl needs to be configured to re-use the established TCP connection and TLS/SSL for the next file transfer and not to re-establish it every cycle. I suggest you to look in curl (libcurl) options and I will also be doing that. Thanks for your reporting. On Wed, Oct 12, 2011 at 2:59 AM, CK Zhang <ck...@fo...> wrote: > > Attached logs, and output from console > > ============ loading batch is: Apach > ====================================== > ---------------------------------------------------------------------------- > ---- > Interval stats (latest:3 sec, clients:100, CAPS-curr:60): > H/F > Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To > :0B/s > H/F/S > Req:200,1xx:0,2xx:201,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:553ms,D-2xx:553ms,Ti > :6854220B/s,To:18800B/s > ---------------------------------------------------------------------------- > ---- > Summary stats (runs:48 secs, CAPS-average:60): > H/F > Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To > :0B/s > H/F/S > Req:2878,1xx:0,2xx:2873,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:614ms,D-2xx:614ms, > Ti:6087722B/s,To:17182B/s > ============================================================================ > ===== > Manual: clients:max[100],curr[100]. Inc num: [+|*]. > ============================================================================ > ===== > > Best Regards, > CK > #8042 > > > -----Original Message----- > From: Robert Iakobashvili [mailto:cor...@gm...] > Sent: Tuesday, October 11, 2011 5:49 PM > To: curl-loader-devel > Subject: Re: HTTPS throughput too low > > Please, try > > CLIENTS_NUM_MAX=100 > CLIENTS_NUM_START=100 > > and comment out > #CLIENTS_RAMPUP_INC=10 > > Say, what happens with traffic and send me the log. > > On Tue, Oct 11, 2011 at 11:36 AM, CK Zhang <ck...@fo...> wrote: >> Attached :) thanks! >> >> Best Regards, >> CK >> #8042 >> >> >> -----Original Message----- >> From: Robert Iakobashvili [mailto:cor...@gm...] >> Sent: Tuesday, October 11, 2011 5:33 PM >> To: curl-loader-devel >> Subject: Re: HTTPS throughput too low >> >> Could you send me it zipped not rarred? >> Thanks! >> >> On Tue, Oct 11, 2011 at 11:30 AM, CK Zhang <ck...@fo...> wrote: >>> Dear Robert >>> >>> Attached test log by command "./curl-loader -f https.conf -v" >>> >>> Best Regards, >>> CK >>> #8042 >>> >>> -----Original Message----- >>> From: Robert Iakobashvili [mailto:cor...@gm...] >>> Sent: Tuesday, October 11, 2011 5:19 PM >>> To: curl-loader-devel >>> Subject: Re: HTTPS throughput too low >>> >>> Dear CK Zhang, >>> >>> Can you run HTTPS sessions with -v detailed logging and say if >>> you seen in logs something interesting. >>> Thanks, >>> Robert >>> >>> >>> >>> On Tue, Oct 11, 2011 at 11:14 AM, CK Zhang <ck...@fo...> wrote: >>>> Dear Robert >>>> >>>> >>>> >>>> Thanks a lot for your replay, >>>> >>>> >>>> >>>> Here are some answer about your questions >>>> >>>> >>>> >>>> >>>> >>>> What happens if you try HTTP? Does it impact throughput? >>>> >>>> It is normal and perfect if I test with HTTP, The throughput can reach >> to >>>> 950Mbps. >>>> >>>> >>>> >>>> Which tools you are using to measure throughput? >>>> >>>> There are 2 ways I used, >>>> >>>> 1 check the log summary form cur-loader like this” >>>> Ti:5261372B/s,To:18375B/s” >>>> >>>> 2 check real time traffic speed on switch with connected test PC and > HTTP >>>> server >>>> >>>> >>>> >>>> What happens, if you try just to ftp some large file between the >> machines? >>>> >>>> NO test >>>> >>>> What about CPU usage at both client and server? >>>> >>>> Both they are busy, about 80% >>>> >>>> Which HTTP server is in use? >>>> >>>> Apache/2.2.21 >>>> >>>> Have you looked into logs of curl-loader and your web-server? >>>> >>>> Checked log, not find abnormal issue. >>>> >>>> >>>> >>>> >>>> >>>> Today, I used Loadrunner11 to simulate https traffic with same >>> environments >>>> (same apache server) , it can reach to 110Mpbs. But still only get >>> 800kbps >>>> with cur-loader. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Best Regards, >>>> >>>> CK >>>> >>>> #8042 >>>> >>>> >>>> >>>> From: Robert Iakobashvili [mailto:cor...@gm...] >>>> Sent: Tuesday, September 27, 2011 1:19 PM >>>> To: curl-loader-devel >>>> Subject: Re: HTTPS throughput too low >>>> >>>> >>>> >>>> Dear CK Zhang, >>>> >>>> On Mon, Sep 26, 2011 at 5:01 AM, CK Zhang <ck...@fo...> wrote: >>>> >>>> >>>> >>>> I want to get high https stream with curl loader, but the Https >> throughput >>>> is about 800kbps between two PC, Http throughput can reach 950Mbps in >> that >>> 2 >>>> pcs, I do know if some have experience like this, and get a high https >>>> throughput with curl-loader, Thanks for any supports and help!! >>>> >>>> >>>> >>>> >>>> >>>> Here is my configuration: >>>> >>>> >>>> >>>> PC1:CPU Inter E2200, Mem 2G, 1000M NIC >>>> >>>> OpenSSL: >>>> >>>> openssl-devel-1.0.0-4.el6_0.2.x86_64 >>>> >>>> openssl-1.0.0-4.el6_0.2.x86_64 >>>> >>>> openssl-perl-1.0.0-4.el6_0.2.x86_64 >>>> >>>> >>>> >>>> curl-loader-0.53 >>>> >>>> ########### GENERAL SECTION >>>> ################################ >>>> >>>> BATCH_NAME= Apach >>>> >>>> CLIENTS_NUM_MAX=400 >>>> >>>> CLIENTS_NUM_START=100 >>>> >>>> CLIENTS_RAMPUP_INC=10 >>>> >>>> INTERFACE =eth2 >>>> >>>> NETMASK=16 >>>> >>>> IP_ADDR_MIN= 172.16.76.150 >>>> >>>> IP_ADDR_MAX= 172.16.246.250 #Actually - this is for self-control >>>> >>>> CYCLES_NUM= -1 >>>> >>>> URLS_NUM= 1 >>>> >>>> >>>> >>>> ########### URL SECTION #################################### >>>> >>>> >>>> >>>> URL=https://172.16.76.142/was/100KB.txt # the size of 100KB.txt is 100KB >>>> >>>> #URL=http://localhost/ACE-INSTALL.html >>>> >>>> URL_SHORT_NAME="local-index" >>>> >>>> REQUEST_TYPE=GET >>>> >>>> TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is >> enforced >>>> by cancelling url fetch on timeout >>>> >>>> TIMER_AFTER_URL_SLEEP =1000 >>>> >>>> ~ >>>> >>>> >>>> >>>> PC2. Works as Webserver,CPU Intel E7600,Mem 4G, 1000M NIC >>>> >>>> Server version: Apache/2.2.21 (Unix) >>>> >>>> Server built: Sep 21 2011 16:19:43 >>>> >>>> openssl-devel-1.0.0-4.el6_0.2.x86_64 >>>> >>>> openssl-1.0.0-4.el6_0.2.x86_64 >>>> >>>> openssl-perl-1.0.0-4.el6_0.2.x86_64 >>>> >>>> >>>> >>>> >>>> >>>> Interesting. >>>> >>>> >>>> >>>> What happens if you try HTTP? Does it impact throughput? >>>> >>>> >>>> >>>> Which tools you are using to measure throughput? >>>> >>>> >>>> >>>> What happens, if you try just to ftp some large file between the >> machines? >>>> >>>> >>>> >>>> What about CPU usage at both client and server? >>>> >>>> Which HTTP server is in use? >>>> >>>> >>>> >>>> Have you looked into logs of curl-loader and your web-server? >>>> >>>> >>>> >>>> -- >>>> Regards, >>>> Robert Iakobashvili, Ph.D. >>>> >>>> >>>> >>>> Home: http://www.ghotit.com >>>> >>>> Blog: http://dyslexia-blog.ghotit.com >>>> >>>> Twitter: http://twitter.com/ghotit >>>> >>>> Facebook: http://facebook.com/ghotit >>>> >>>> ...................................................................... >>>> >>>> Ghotit Dyslexia >>>> >>>> Assistive technology that understands you >>>> >>>> ...................................................................... >>>> >>>> >>>> >>>> ________________________________ >>>> >>>> *** Please note that this message and any attachments may contain >>>> confidential >>>> and proprietary material and information and are intended only for the >> use >>>> of >>>> the intended recipient(s). If you are not the intended recipient, you > are >>>> hereby >>>> notified that any review, use, disclosure, dissemination, distribution > or >>>> copying >>>> of this message and any attachments is strictly prohibited. If you have >>>> received >>>> this email in error, please immediately notify the sender and destroy >> this >>>> e-mail >>>> and any attachments and all copies, whether electronic or printed. >>>> Please also note that any views, opinions, conclusions or commitments >>>> expressed >>>> in this message are those of the individual sender and do not > necessarily >>>> reflect >>>> the views of Fortinet, Inc., its affiliates, and emails are not binding >> on >>>> Fortinet and only a writing manually signed by Fortinet's General > Counsel >>>> can be >>>> a binding commitment of Fortinet to Fortinet's customers or partners. >>> Thank >>>> you. *** >>>> >>>> ________________________________ >>>> >>>> >>> >> > ---------------------------------------------------------------------------- >>> -- >>>> All the data continuously generated in your IT infrastructure contains a >>>> definitive record of customers, application performance, security >>>> threats, fraudulent activity and more. Splunk takes this data and makes >>>> sense of it. Business sense. IT sense. Common sense. >>>> http://p.sf.net/sfu/splunk-d2d-oct >>>> _______________________________________________ >>>> curl-loader-devel mailing list >>>> cur...@li... >>>> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >>>> >>>> >>> >>> >>> >>> -- >>> Regards, >>> Robert Iakobashvili, Ph.D. >>> >>> Home: http://www.ghotit.com >>> Blog: http://dyslexia-blog.ghotit.com >>> Twitter: http://twitter.com/ghotit >>> Facebook: http://facebook.com/ghotit >>> ...................................................................... >>> Ghotit Dyslexia >>> Assistive technology that understands you >>> ...................................................................... >>> >>> >> > ---------------------------------------------------------------------------- >>> -- >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2d-oct >>> _______________________________________________ >>> curl-loader-devel mailing list >>> cur...@li... >>> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >>> >>> >>> *** Please note that this message and any attachments may contain >> confidential >>> and proprietary material and information and are intended only for the > use >> of >>> the intended recipient(s). If you are not the intended recipient, you are >> hereby >>> notified that any review, use, disclosure, dissemination, distribution or >> copying >>> of this message and any attachments is strictly prohibited. If you have >> received >>> this email in error, please immediately notify the sender and destroy > this >> e-mail >>> and any attachments and all copies, whether electronic or printed. >>> Please also note that any views, opinions, conclusions or commitments >> expressed >>> in this message are those of the individual sender and do not necessarily >> reflect >>> the views of Fortinet, Inc., its affiliates, and emails are not binding > on >>> Fortinet and only a writing manually signed by Fortinet's General Counsel >> can be >>> a binding commitment of Fortinet to Fortinet's customers or partners. >> Thank you. *** >>> >>> >> > ---------------------------------------------------------------------------- >> -- >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2d-oct >>> _______________________________________________ >>> curl-loader-devel mailing list >>> cur...@li... >>> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >>> >>> >> >> >> >> -- >> Regards, >> Robert Iakobashvili, Ph.D. >> >> Home: http://www.ghotit.com >> Blog: http://dyslexia-blog.ghotit.com >> Twitter: http://twitter.com/ghotit >> Facebook: http://facebook.com/ghotit >> ...................................................................... >> Ghotit Dyslexia >> Assistive technology that understands you >> ...................................................................... >> >> > ---------------------------------------------------------------------------- >> -- >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2d-oct >> _______________________________________________ >> curl-loader-devel mailing list >> cur...@li... >> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >> >> >> *** Please note that this message and any attachments may contain > confidential >> and proprietary material and information and are intended only for the use > of >> the intended recipient(s). If you are not the intended recipient, you are > hereby >> notified that any review, use, disclosure, dissemination, distribution or > copying >> of this message and any attachments is strictly prohibited. If you have > received >> this email in error, please immediately notify the sender and destroy this > e-mail >> and any attachments and all copies, whether electronic or printed. >> Please also note that any views, opinions, conclusions or commitments > expressed >> in this message are those of the individual sender and do not necessarily > reflect >> the views of Fortinet, Inc., its affiliates, and emails are not binding on >> Fortinet and only a writing manually signed by Fortinet's General Counsel > can be >> a binding commitment of Fortinet to Fortinet's customers or partners. > Thank you. *** >> >> > ---------------------------------------------------------------------------- > -- >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2d-oct >> _______________________________________________ >> curl-loader-devel mailing list >> cur...@li... >> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >> >> > > > > -- > Regards, > Robert Iakobashvili, Ph.D. > > Home: http://www.ghotit.com > Blog: http://dyslexia-blog.ghotit.com > Twitter: http://twitter.com/ghotit > Facebook: http://facebook.com/ghotit > ...................................................................... > Ghotit Dyslexia > Assistive technology that understands you > ...................................................................... > > ---------------------------------------------------------------------------- > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > > *** Please note that this message and any attachments may contain confidential > and proprietary material and information and are intended only for the use of > the intended recipient(s). If you are not the intended recipient, you are hereby > notified that any review, use, disclosure, dissemination, distribution or copying > of this message and any attachments is strictly prohibited. If you have received > this email in error, please immediately notify the sender and destroy this e-mail > and any attachments and all copies, whether electronic or printed. > Please also note that any views, opinions, conclusions or commitments expressed > in this message are those of the individual sender and do not necessarily reflect > the views of Fortinet, Inc., its affiliates, and emails are not binding on > Fortinet and only a writing manually signed by Fortinet's General Counsel can be > a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. *** > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... |
|
From: CK Z. <ck...@fo...> - 2011-10-12 00:59:16
|
Attached logs, and output from console ============ loading batch is: Apach ====================================== ---------------------------------------------------------------------------- ---- Interval stats (latest:3 sec, clients:100, CAPS-curr:60): H/F Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To :0B/s H/F/S Req:200,1xx:0,2xx:201,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:553ms,D-2xx:553ms,Ti :6854220B/s,To:18800B/s ---------------------------------------------------------------------------- ---- Summary stats (runs:48 secs, CAPS-average:60): H/F Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To :0B/s H/F/S Req:2878,1xx:0,2xx:2873,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:614ms,D-2xx:614ms, Ti:6087722B/s,To:17182B/s ============================================================================ ===== Manual: clients:max[100],curr[100]. Inc num: [+|*]. ============================================================================ ===== Best Regards, CK #8042 -----Original Message----- From: Robert Iakobashvili [mailto:cor...@gm...] Sent: Tuesday, October 11, 2011 5:49 PM To: curl-loader-devel Subject: Re: HTTPS throughput too low Please, try CLIENTS_NUM_MAX=100 CLIENTS_NUM_START=100 and comment out #CLIENTS_RAMPUP_INC=10 Say, what happens with traffic and send me the log. On Tue, Oct 11, 2011 at 11:36 AM, CK Zhang <ck...@fo...> wrote: > Attached :) thanks! > > Best Regards, > CK > #8042 > > > -----Original Message----- > From: Robert Iakobashvili [mailto:cor...@gm...] > Sent: Tuesday, October 11, 2011 5:33 PM > To: curl-loader-devel > Subject: Re: HTTPS throughput too low > > Could you send me it zipped not rarred? > Thanks! > > On Tue, Oct 11, 2011 at 11:30 AM, CK Zhang <ck...@fo...> wrote: >> Dear Robert >> >> Attached test log by command "./curl-loader -f https.conf -v" >> >> Best Regards, >> CK >> #8042 >> >> -----Original Message----- >> From: Robert Iakobashvili [mailto:cor...@gm...] >> Sent: Tuesday, October 11, 2011 5:19 PM >> To: curl-loader-devel >> Subject: Re: HTTPS throughput too low >> >> Dear CK Zhang, >> >> Can you run HTTPS sessions with -v detailed logging and say if >> you seen in logs something interesting. >> Thanks, >> Robert >> >> >> >> On Tue, Oct 11, 2011 at 11:14 AM, CK Zhang <ck...@fo...> wrote: >>> Dear Robert >>> >>> >>> >>> Thanks a lot for your replay, >>> >>> >>> >>> Here are some answer about your questions >>> >>> >>> >>> >>> >>> What happens if you try HTTP? Does it impact throughput? >>> >>> It is normal and perfect if I test with HTTP, The throughput can reach > to >>> 950Mbps. >>> >>> >>> >>> Which tools you are using to measure throughput? >>> >>> There are 2 ways I used, >>> >>> 1 check the log summary form cur-loader like this >>> Ti:5261372B/s,To:18375B/s >>> >>> 2 check real time traffic speed on switch with connected test PC and HTTP >>> server >>> >>> >>> >>> What happens, if you try just to ftp some large file between the > machines? >>> >>> NO test >>> >>> What about CPU usage at both client and server? >>> >>> Both they are busy, about 80% >>> >>> Which HTTP server is in use? >>> >>> Apache/2.2.21 >>> >>> Have you looked into logs of curl-loader and your web-server? >>> >>> Checked log, not find abnormal issue. >>> >>> >>> >>> >>> >>> Today, I used Loadrunner11 to simulate https traffic with same >> environments >>> (same apache server) , it can reach to 110Mpbs. But still only get >> 800kbps >>> with cur-loader. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Best Regards, >>> >>> CK >>> >>> #8042 >>> >>> >>> >>> From: Robert Iakobashvili [mailto:cor...@gm...] >>> Sent: Tuesday, September 27, 2011 1:19 PM >>> To: curl-loader-devel >>> Subject: Re: HTTPS throughput too low >>> >>> >>> >>> Dear CK Zhang, >>> >>> On Mon, Sep 26, 2011 at 5:01 AM, CK Zhang <ck...@fo...> wrote: >>> >>> >>> >>> I want to get high https stream with curl loader, but the Https > throughput >>> is about 800kbps between two PC, Http throughput can reach 950Mbps in > that >> 2 >>> pcs, I do know if some have experience like this, and get a high https >>> throughput with curl-loader, Thanks for any supports and help!! >>> >>> >>> >>> >>> >>> Here is my configuration: >>> >>> >>> >>> PC1:CPU Inter E2200, Mem 2G, 1000M NIC >>> >>> OpenSSL: >>> >>> openssl-devel-1.0.0-4.el6_0.2.x86_64 >>> >>> openssl-1.0.0-4.el6_0.2.x86_64 >>> >>> openssl-perl-1.0.0-4.el6_0.2.x86_64 >>> >>> >>> >>> curl-loader-0.53 >>> >>> ########### GENERAL SECTION >>> ################################ >>> >>> BATCH_NAME= Apach >>> >>> CLIENTS_NUM_MAX=400 >>> >>> CLIENTS_NUM_START=100 >>> >>> CLIENTS_RAMPUP_INC=10 >>> >>> INTERFACE =eth2 >>> >>> NETMASK=16 >>> >>> IP_ADDR_MIN= 172.16.76.150 >>> >>> IP_ADDR_MAX= 172.16.246.250 #Actually - this is for self-control >>> >>> CYCLES_NUM= -1 >>> >>> URLS_NUM= 1 >>> >>> >>> >>> ########### URL SECTION #################################### >>> >>> >>> >>> URL=https://172.16.76.142/was/100KB.txt # the size of 100KB.txt is 100KB >>> >>> #URL=http://localhost/ACE-INSTALL.html >>> >>> URL_SHORT_NAME="local-index" >>> >>> REQUEST_TYPE=GET >>> >>> TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is > enforced >>> by cancelling url fetch on timeout >>> >>> TIMER_AFTER_URL_SLEEP =1000 >>> >>> ~ >>> >>> >>> >>> PC2. Works as Webserver,CPU Intel E7600,Mem 4G, 1000M NIC >>> >>> Server version: Apache/2.2.21 (Unix) >>> >>> Server built: Sep 21 2011 16:19:43 >>> >>> openssl-devel-1.0.0-4.el6_0.2.x86_64 >>> >>> openssl-1.0.0-4.el6_0.2.x86_64 >>> >>> openssl-perl-1.0.0-4.el6_0.2.x86_64 >>> >>> >>> >>> >>> >>> Interesting. >>> >>> >>> >>> What happens if you try HTTP? Does it impact throughput? >>> >>> >>> >>> Which tools you are using to measure throughput? >>> >>> >>> >>> What happens, if you try just to ftp some large file between the > machines? >>> >>> >>> >>> What about CPU usage at both client and server? >>> >>> Which HTTP server is in use? >>> >>> >>> >>> Have you looked into logs of curl-loader and your web-server? >>> >>> >>> >>> -- >>> Regards, >>> Robert Iakobashvili, Ph.D. >>> >>> >>> >>> Home: http://www.ghotit.com >>> >>> Blog: http://dyslexia-blog.ghotit.com >>> >>> Twitter: http://twitter.com/ghotit >>> >>> Facebook: http://facebook.com/ghotit >>> >>> ...................................................................... >>> >>> Ghotit Dyslexia >>> >>> Assistive technology that understands you >>> >>> ...................................................................... >>> >>> >>> >>> ________________________________ >>> >>> *** Please note that this message and any attachments may contain >>> confidential >>> and proprietary material and information and are intended only for the > use >>> of >>> the intended recipient(s). If you are not the intended recipient, you are >>> hereby >>> notified that any review, use, disclosure, dissemination, distribution or >>> copying >>> of this message and any attachments is strictly prohibited. If you have >>> received >>> this email in error, please immediately notify the sender and destroy > this >>> e-mail >>> and any attachments and all copies, whether electronic or printed. >>> Please also note that any views, opinions, conclusions or commitments >>> expressed >>> in this message are those of the individual sender and do not necessarily >>> reflect >>> the views of Fortinet, Inc., its affiliates, and emails are not binding > on >>> Fortinet and only a writing manually signed by Fortinet's General Counsel >>> can be >>> a binding commitment of Fortinet to Fortinet's customers or partners. >> Thank >>> you. *** >>> >>> ________________________________ >>> >>> >> > ---------------------------------------------------------------------------- >> -- >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2d-oct >>> _______________________________________________ >>> curl-loader-devel mailing list >>> cur...@li... >>> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >>> >>> >> >> >> >> -- >> Regards, >> Robert Iakobashvili, Ph.D. >> >> Home: http://www.ghotit.com >> Blog: http://dyslexia-blog.ghotit.com >> Twitter: http://twitter.com/ghotit >> Facebook: http://facebook.com/ghotit >> ...................................................................... >> Ghotit Dyslexia >> Assistive technology that understands you >> ...................................................................... >> >> > ---------------------------------------------------------------------------- >> -- >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2d-oct >> _______________________________________________ >> curl-loader-devel mailing list >> cur...@li... >> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >> >> >> *** Please note that this message and any attachments may contain > confidential >> and proprietary material and information and are intended only for the use > of >> the intended recipient(s). If you are not the intended recipient, you are > hereby >> notified that any review, use, disclosure, dissemination, distribution or > copying >> of this message and any attachments is strictly prohibited. If you have > received >> this email in error, please immediately notify the sender and destroy this > e-mail >> and any attachments and all copies, whether electronic or printed. >> Please also note that any views, opinions, conclusions or commitments > expressed >> in this message are those of the individual sender and do not necessarily > reflect >> the views of Fortinet, Inc., its affiliates, and emails are not binding on >> Fortinet and only a writing manually signed by Fortinet's General Counsel > can be >> a binding commitment of Fortinet to Fortinet's customers or partners. > Thank you. *** >> >> > ---------------------------------------------------------------------------- > -- >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2d-oct >> _______________________________________________ >> curl-loader-devel mailing list >> cur...@li... >> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel >> >> > > > > -- > Regards, > Robert Iakobashvili, Ph.D. > > Home: http://www.ghotit.com > Blog: http://dyslexia-blog.ghotit.com > Twitter: http://twitter.com/ghotit > Facebook: http://facebook.com/ghotit > ...................................................................... > Ghotit Dyslexia > Assistive technology that understands you > ...................................................................... > > ---------------------------------------------------------------------------- > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > > *** Please note that this message and any attachments may contain confidential > and proprietary material and information and are intended only for the use of > the intended recipient(s). If you are not the intended recipient, you are hereby > notified that any review, use, disclosure, dissemination, distribution or copying > of this message and any attachments is strictly prohibited. If you have received > this email in error, please immediately notify the sender and destroy this e-mail > and any attachments and all copies, whether electronic or printed. > Please also note that any views, opinions, conclusions or commitments expressed > in this message are those of the individual sender and do not necessarily reflect > the views of Fortinet, Inc., its affiliates, and emails are not binding on > Fortinet and only a writing manually signed by Fortinet's General Counsel can be > a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. *** > > ---------------------------------------------------------------------------- -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... ---------------------------------------------------------------------------- -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ curl-loader-devel mailing list cur...@li... https://lists.sourceforge.net/lists/listinfo/curl-loader-devel *** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. *** |
|
From: Robert I. <cor...@gm...> - 2011-10-11 10:19:08
|
Hi Oren, It does not exist. I mem there were people writing scripts for that; try to search. On Tue, Oct 11, 2011 at 12:07 PM, Oren Solomianik <or...@gm...> wrote: > Hi all, > > I wanted to know if it's possible to automatically instruct curl-loader > to fetch embedded URLs (images, js, css) from a given test URL. This > will help simulate actual browser load, and not just a single page > fetching time. > > I couldn't find this option in the confs or docs, did I miss it or does > it not exist? > > Thanks! > Oren > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > curl-loader-devel mailing list > cur...@li... > https://lists.sourceforge.net/lists/listinfo/curl-loader-devel > > -- Regards, Robert Iakobashvili, Ph.D. Home: http://www.ghotit.com Blog: http://dyslexia-blog.ghotit.com Twitter: http://twitter.com/ghotit Facebook: http://facebook.com/ghotit ...................................................................... Ghotit Dyslexia Assistive technology that understands you ...................................................................... |
25 messages has been excluded from this view by a project administrator.
