Re: [Networktest-sctp] [SCTP] Problem in execution of SCTP first test case, please help.
Brought to you by:
fnst-netdev
Menu
▾
▴
Re: [Networktest-sctp] [SCTP] Problem in execution of SCTP first test case, please help.
|
From: Mohd. A. <moh...@gm...> - 2011-02-01 15:07:29
|
Hi Wei,
The test suite worked fine when i used fedora machines for NUT and TN.
But I am again stuck in problem when i used TN (fedora machine) and
NUT (WindRiver machine)
WindRiver is a linux based OS having kernel 2.6.27
1. serial port connection is fine.
2. cu -l ttyS0 has been tested,its fine. It is asking for login
authentication at first time and then it is not asking for login
authentication, as desired.
3. I'm using mingetty at NUT
4. The configurations (tn.def, nut.def, config.in) are also correct.
5. For your information, NUT has username: root, password: root,
hostname: L3Switch
6. In "make config", the problem is that TN is again trying to login
after the login (sending "root" and "root" at the terminal)
7. Is there any problem with the login prompt "root@L3Switch:/root>"
Please give your kind suggestions and help me.
But following problem is occurring in "make config":
=========================================
* Configure Node Under Test (NUT)
- Configure IP Address of eth0
rLogin: Retry error (> 8)
Before: ``Wed Feb 9 09:20:36 on ttyS0
Wind River Linux glibc_std (standard) 3.0
root@L3Switch:/root>
root@L3Switch:/root> root
-bash: root: command not found
root@L3Switch:/root>
root@L3Switch:/root> root
-bash: root: command not found
root@L3Switch:/root>
root@L3Switch:/root>
root@L3Switch:/root>
root@L3Switch:/root>
root@L3Switch:/root> ''
Match: ``login: ''
After: ``Wed Feb 9 09:20:36 on ttyS0
Wind River Linux glibc_std (standard) 3.0
=========================================
I'm attaching the complete log in the mail.
Please help...
Best Regards,
Arif
On Wed, Dec 29, 2010 at 1:09 PM, Mohd. Arif <moh...@gm...> wrote:
> Hi Wei,
> :) Thanks Champ!!! Thanks a lot for your help and sincere efforts!!!!
>
> Everything is fine now.
> The following statement of yours does wonder for me:
> ===========================
> I notice that you need to login to NUT everytime when you using cu,
> so I think this is the key problem. after run command on NUT, NUT
> force(?) you logout, and we know, if we logout, all our process will
> be kill. So you should config your NUT to not logout you cu.
>
> config by cu -l ttyS0, the first cu need to login, and the second does
> not need.
>
> # cu -l ttyS0
> Fedoar12NUT login:
> ...
> # cu -l ttyS0
> Connected.
> ==========================
>
> For some reason, mingetty was not working properly on my NUT machine
> so i used agetty.
> But agetty was forcing to log out the connection. I again tried to use
> mingetty and now its working.
>
> Everything is working fine now. You gave a lot of time to me which is
> highly appreciable.
>
> Thanks,
> Arif
>
> On Wed, Dec 29, 2010 at 6:50 AM, Wei Yongjun <yj...@cn...> wrote:
>> Hi
>>
>>> Hi Wei,
>>>
>>> Thanks for the response!
>>>
>>> Can you please tell me what does rcommandasync or rcommandsync command
>>> exactly does?
>>
>> rcommandsync wait util command return, but rcommandasync do not wait.
>>
>>
>>> Does it use any service which may not be available on NUT or TN?
>>
>> It does not use any service.
>>
>>> Please find below the output of the commands:
>>> a)rcommandasync.rmt ==> /tmp/tstcmd.log doesn't created at NUT
>>> b)rcommandasync.rmt but without using sleep ==> /tmp/tstcmd.log
>>> doesn't created at NUT
>>> c)rcommand.rmt ==> /tmp/tstcmd.log created at NUT
>>> d)cat rcommandasync.rmt
>>
>> It seems the rcommandasync.rmt did not run correctly on
>> your system. Your using default shell bash on NUT?
>>
>> Can your try the following patch for sctp test tool, and check
>> whether ./NormalInitClient.seq works after patch?
>>
>> --- a/common/SCTP.pm 2010-07-21 05:37:21.000000000 -0400
>> +++ b/common/SCTP.pm 2010-12-28 20:06:56.000000000 -0500
>> @@ -1562,7 +1564,8 @@ sub sctpRemoteCommandAsync($) {
>> }
>> }
>>
>> - vRemote("rcommandasync.rmt", "cmd=\"$cmd\"") && return 1;
>> + #vRemote("rcommandasync.rmt", "cmd=\"$cmd\"") && return 1;
>> + vRemote("rcommand.rmt", "cmd=\"$cmd\"") && return 1;
>>
>> return 0;
>> }
>> @@ -1582,7 +1585,8 @@ sub sctpRemoteCommandAsyncDelay($;$) {
>> $cmd .= " > /tmp/tstcmd.log 2>&1";
>> }
>>
>> - vRemote("rcommandasync.rmt", "cmd=\"sleep $dalay && $cmd\"") && return 1;
>> + #vRemote("rcommandasync.rmt", "cmd=\"sleep $dalay && $cmd\"") && return 1;
>> + vRemote("rcommand.rmt", "cmd=\"sleep $dalay && $cmd\"") && return 1;
>>
>> return 0;
>> }
>>
>>> =====================================================================================================================
>>> ro...@lo...$/usr/local/v6eval//bin/linux-v6//rcommandasync.rmt
>>> -t linux-v6 -u root -p password -d ttyS0 -o 1 cmd="sleep 5 &&
>>> sctp_test -H 192.168.0.21 -P 3009 -h 192.168.0.100 -p 2009 -T -s -c
>>> -1352 -X 1 -x 1 -o 1 >/tmp/tstcmd.log 2>&1 &"
>>> Connected.
>>>
>>> Fedora release 10 (Cambridge)
>>> Kernel 2.6.27.5-117.fc10.i686 on an i686 (ttyS0)
>>>
>>> L3Switch login: root
>>> Password:
>>> Last login: Tue Dec 28 13:03:08 on ttyS0
>>> [root@L3Switch ~]#
>>> [root@L3Switch ~]# ~.
>>> Disconnected.
>>> ro...@lo...$
>>> ro...@lo...$
>>> ro...@lo...$/usr/local/v6eval//bin/linux-v6//rcommandasync.rmt
>>> -t linux-v6 -u root -p password -d ttyS0 -o 1 cmd="sctp_test -H
>>> 192.168.0.21 -P 3009 -h 192.168.0.100 -p 2009 -T -s -c -1352 -X 1 -x 1
>>> -o 1 >/tmp/tstcmd.log 2>&1 &"
>>> Connected.
>>>
>>> Fedora release 10 (Cambridge)
>>> Kernel 2.6.27.5-117.fc10.i686 on an i686 (ttyS0)
>>>
>>> L3Switch login: root
>>> Password:
>>> Last login: Tue Dec 28 13:06:41 on ttyS0
>>> [root@L3Switch ~]#
>>> [root@L3Switch ~]# ~.
>>> Disconnected.
>>> ro...@lo...$
>>> ro...@lo...$
>>> ro...@lo...$/usr/local/v6eval//bin/linux-v6//rcommand.rmt
>>> -t linux-v6 -u root -p password -d ttyS0 -o 1 cmd="sctp_test -H
>>> 192.168.0.21 -P 3009 -h 192.168.0.100 -p 2009 -T -s -c -1352 -X 1 -x 1
>>> -o 1 >/tmp/tstcmd.log 2>&1 &"
>>> Connected.
>>>
>>> Fedora release 10 (Cambridge)
>>> Kernel 2.6.27.5-117.fc10.i686 on an i686 (ttyS0)
>>>
>>> L3Switch login: root
>>> Password:
>>> Last login: Tue Dec 28 13:06:56 on ttyS0
>>> [root@L3Switch ~]#
>>> -s -c -1352 -X 1 -x 1 -o 1 >/tmp/tstcmd.log 2>&1 & -h 192.168.0.100 -p 2009 -T
>>> [1] 12818
>>> [root@L3Switch ~]# sendMessagesSync: never got sctp_test -H
>>> 192.168.0.21 -P 3009 -h 192.168.0.100 -p 2009 -T -s -c -1352 -X 1 -x 1
>>> -o 1 >/tmp/tstcmd.log 2>&1 &
>>> echo $?
>>> 0
>>> [roo~.
>>> Disconnected.
>>> ro...@lo...$
>>> ro...@lo...$
>>> =====================================================================================================================
>>>
>>> FILE: rcommandasync.rmt
>>> ~~~~~~~~~~
>>> use V6evalRemote;
>>>
>>> $rOpt_timeout = 5 if ! defined $rOpt_timeout;
>>>
>>> rOpen() || goto error;
>>> rLogin($rOpt_timeout) || goto error;
>>>
>>> rCommandAsync("$rOpt_cmd ", 15) || goto error;
>>>
>>> rLogout($rOpt_timeout) || goto error;
>>>
>>> rClose();
>>> exit($V6evalRemote::exitPass);
>>>
>>> error:
>>> rClose();
>>> exit($V6evalRemote::exitFail);
>>> ~~~~~~~~~~~~~
>>>
>>> Kindly give your suggestions.
>>>
>>> Thanks,
>>> Arif
>>>
>>
>
|
