  | | | DCE - RPC Communication Breaks on Redhat 9.0 | DCE - RPC Communication Breaks on Redhat 9.0 2005-06-29 - By Vaibhav Khanduja
Back Hi All, I have done some more investigation on this and have reached to a conclusion that rpcd daemon running on port 135 is being contacted through UDP communication but somehow it is not able to receive it. netstat -a returs Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 localhost.localdo:32769 *:* LISTEN tcp 0 0 *:shell *:* LISTEN tcp 0 0 *:135 *:* LISTEN tcp 0 0 *:sunrpc *:* LISTEN tcp 0 0 *:x11 *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 *:ssh *:* LISTEN tcp 0 0 localhost.localdoma:ipp *:* LISTEN tcp 0 0 *:telnet *:* LISTEN tcp 0 0 localhost.localdom:smtp *:* LISTEN tcp 72 0 vmlctlx4.india.hp.c:135 nt12254.india.hp.c:1497 ESTABLISHED tcp 0 0 vmlctlx4.india.h:telnet nt1751.india.hp.co:3436 ESTABLISHED tcp 0 2 vmlctlx4.india.h:telnet nt1751.india.hp.co:3337 ESTABLISHED udp 65344 0 *:135 *:* udp 0 0 *:sunrpc *:* udp 0 0 *:631 *:* Active UNIX domain sockets (servers and established) Proto RefCnt Flags Type State I-Node Path unix 2 [ ACC ] STREAM LISTENING 1717 /dev/gpmctl unix 2 [ ACC ] STREAM LISTENING 1838 /tmp/.font-unix/fs7100 unix 2 [ ACC ] STREAM LISTENING 1962 /tmp/.X11-unix/X0 unix 9 [ ] DGRAM 1113 /dev/log unix 2 [ ACC ] STREAM LISTENING 1952 /tmp/.gdm_socket unix 3 [ ] STREAM CONNECTED 1992 /tmp/.X11-unix/X0 unix 3 [ ] STREAM CONNECTED 1991 unix 3 [ ] STREAM CONNECTED 1988 /tmp/.X11-unix/X0 unix 3 [ ] STREAM CONNECTED 1987 unix 3 [ ] STREAM CONNECTED 1972 /tmp/.font-unix/fs7100 unix 3 [ ] STREAM CONNECTED 1971 unix 3 [ ] STREAM CONNECTED 1974 /tmp/.X11-unix/X0 unix 3 [ ] STREAM CONNECTED 1965 unix 2 [ ] DGRAM 1860 unix 2 [ ] DGRAM 1728 unix 2 [ ] DGRAM 1693 unix 2 [ ] DGRAM 1679 unix 2 [ ] DGRAM 1563 unix 2 [ ] DGRAM 1323 unix 2 [ ] DGRAM 1122
cat /proc/net/udp returns sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode 7: 00000000:0087 00000000:0000 07 00000000:0000FF40 00:00000000 00000000 0 0 26555 2 c1391080 111: 00000000:006F 00000000:0000 07 00000000:00000000 00:00000000 00000000 0 0 1151 2 c1935060 119: 00000000:0277 00000000:0000 07 00000000:00000000 00:00000000 00000000 0 0 1809 2 cdcbc0c0
As you can see some bytes present in the UDP queue. I am not sure why rpcd listening is not able to get this. Any help would be appreciated. Thanks, Vaibhav Khanduja
"Steven J. Yellin" <yellin@(protected)> wrote: You are using the original RH9 kernel. I don't know how to deal with the problem you've partly described, but the first thing to try is getting all the updates, including the latest kernel, version 2.4.20-43.9.
Steven Yellin
On Sun, 26 Jun 2005, Vaibhav Khanduja wrote:
> Hi All, > > I am problems dce/rpc communication on Redhat Linux 9.0 > > uname -a > > 2.4.20-8smp #1 SMP Thu Mar 13 17:45:54 EST 2003 i686 i686 i386 GNU/Linux > > cat /etc/redhat-release > > Red Hat Linux release 9 (Shrike) > DCE rpc communication comes with a daemon rpcd, which is used to > register rpc server interfaces running the machine. The rpcd daemon runs > on port 135 and any external client who wants to take service of the rpc > server contacts rpcd, gets the interfaces and port number of rpc server > and then sends a request. The problem which I see here is the rpc > servers are not getting registered with rpcd i.e. because the rpc > communication breaks. This problem immediately does not come on Redhat > 9.0 but is observed after some and is persistent. > Any help in this regard is realy appreciated. I have also seen a bug > in bugzilla related to nfs rpc communication, it might be similar to > that. > > The bugzilla link is > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118839 > > Thanks,
-- Shrike-list mailing list Shrike-list@(protected) https://www.redhat.com/mailman/listinfo/shrike-list
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com <DIV>Hi All, </DIV> <DIV> </DIV> <DIV>I have done some more investigation on this and have reached to a conclusion that rpcd daemon running on port 135 is being contacted through UDP communication but somehow it is not able to receive it. </DIV> <DIV> </DIV> <DIV>netstat -a returs </DIV> <DIV> </DIV> <DIV>Active Internet connections (servers and established)<BR>Proto Recv-Q Send -Q Local Address Foreign Address State<BR>tcp 0 0 localhost.localdo:32769 *:* LISTEN <BR>tcp 0   ; 0 *:shell *:* LISTEN<BR>tcp 0 0 *:135 *:* LISTEN<BR>tcp 0 0 *:sunrpc * :* LISTEN<BR>tcp 0 0 *:x11 *:* LISTEN<BR>tcp 0 0 *:ftp *:* LISTEN<BR>tcp 0 0 *:ssh *:* LISTEN<BR>tcp 0 0 localhost.localdoma:ipp *:* LISTEN <BR>tcp 0   ; 0 *:telnet *:* LISTEN<BR>tcp 0 0 localhost.localdom :smtp *:*   ; LISTEN<BR>tcp   ; 72 0 vmlctlx4.india.hp.c:135 nt12254.india.hp.c:1497 ESTABLISHED<BR>tcp 0 0 vmlctlx4.india.h:telnet nt1751.india.hp .co:3436 ESTABLISHED<BR>tcp 0 2 vmlctlx4.india.h:telnet nt1751.india.hp.co:3337 ESTABLISHED<BR>udp 65344 0 * :135 *:*<BR>udp 0 0 *:sunrpc *:*<BR>udp 0 0 *:631 * :*<BR>Active UNIX domain sockets (servers and established)<BR>Proto RefCnt Flags Type State I-Node Path<BR>unix 2 [ ACC ] STREAM LISTENING 1717 /dev /gpmctl<BR>unix 2 [ ACC ] STREAM LISTENING 1838 /tmp/.font-unix/fs7100<BR>unix 2 [ ACC ] STREAM LISTENING 1962 /tmp/.X11 -unix/X0<BR>unix 9 [ ] DGRAM 1113 /dev/log<BR>unix 2 [ ACC ]  ; STREAM LISTENING 1952 /tmp/.gdm_socket<BR>unix 3 [ ] STREAM CONNECTED 1992 /tmp/.X11-unix /X0<BR>unix 3 [ ] STREAM CONNECTED 1991<BR>unix 3 &nbs! p; [ ] STREAM CONNECTED 1988 /tmp/.X11-unix/X0<BR >unix 3 [ ] STREAM CONNECTED 1987<BR>unix 3 [ ] STREAM CONNECTED 1972 /tmp/.font-unix/fs7100<BR>unix 3 [ ] STREAM CONNECTED 1971<BR>unix 3 [ ] STREAM CONNECTED 1974 /tmp/.X11-unix/X0<BR>unix 3   ; [ ] STREAM CONNECTED 1965<BR>unix 2 [ ] DGRAM 1860<BR>unix 2  ; [ ] DGRAM 1728<BR>unix 2   ; [ ] DGRAM 1693<BR>unix 2   ; [ ] DGRAM 1679<BR>unix 2 [ ] DGRAM 1563<BR>unix 2   ; [ ] DGRAM 1323<BR>unix 2   ; [ ] DGRAM 1122<BR></DIV> <DIV> </DIV> <DIV>cat /proc/net/udp returns</DIV> <DIV> </DIV> <DIV> sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode<BR> 7: 00000000:0087 00000000:0000 07 00000000:0000FF40 00:00000000 00000000 0 0 26555 2 c1391080<BR> 111: 00000000:006F 00000000:0000 07 00000000:00000000 00 :00000000 00000000 0 0 1151 2 c1935060<BR> 119: 00000000:0277 00000000:0000 07 00000000 :00000000 00:00000000 00000000 0 </DIV> <DIV>0 1809 2 cdcbc0c0<BR><BR>As you can see some bytes present in the UDP queue. I am not sure why rpcd listening is not able to get this. </DIV> <DIV> </DIV> <DIV>Any help would be appreciated.</DIV> <DIV> </DIV> <DIV>Thanks,</DIV> <DIV>Vaibhav Khanduja</DIV> <DIV> </DIV> <DIV><BR><B><I>"Steven J. Yellin" <yellin@(protected)></I></B> wrote:</DIV> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER -LEFT: #1010ff 2px solid">You are using the original RH9 kernel. I don't know how to deal with<BR>the problem you've partly described, but the first thing to try is getting<BR>all the updates, including the latest kernel, version 2.4.20 -43.9.<BR><BR>Steven Yellin<BR><BR>On Sun, 26 Jun 2005, Vaibhav Khanduja wrote: <BR><BR>> Hi All,<BR>><BR>> I am problems dce/rpc communication on Redhat Linux 9.0<BR>><BR>> uname -a<BR>><BR>> 2.4.20-8smp #1 SMP Thu Mar 13 17:45:54 EST 2003 i686 i686 i386 GNU/Linux<BR>><BR>> cat /etc /redhat-release<BR>><BR>> Red Hat Linux release 9 (Shrike)<BR>> DCE rpc communication comes with a daemon rpcd, which is used to<BR>> register rpc server interfaces running the machine. The rpcd daemon runs<BR>> on port 135 and any external client who wants to take service of the rpc<BR>> server contacts rpcd, gets the interfaces and port number of! rpc server<BR>> and then sends a request. The problem which I see here is the rpc<BR>> servers are not getting registered with rpcd i.e. because the rpc <BR>> communication breaks. This problem immediately does not come on Redhat <BR>> 9.0 but is observed after some and is persistent.<BR>> Any help in this regard is realy appreciated. I have also seen a bug<BR>> in bugzilla related to nfs rpc communication, it might be similar to<BR>> that.<BR>> <BR>> The bugzilla link is<BR>> https://bugzilla.redhat.com/bugzilla/show _bug.cgi?id=118839<BR>><BR>> Thanks,<BR><BR>-- <BR>Shrike-list mailing list<BR>Shrike-list@(protected)<BR>https://www.redhat.com/mailman/listinfo /shrike-list<BR></BLOCKQUOTE><p>__ ____ ____ ____ ____ ____ ____ ____ ____ _____ __<br>Do You Yahoo!?<br>Tired of spam? Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com -- Shrike-list mailing list Shrike-list@(protected) https://www.redhat.com/mailman/listinfo/shrike-list
|
|
 |