<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Error while request from client RPC to Server RPC in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/error-while-request-from-client-rpc-to-server-rpc/m-p/2788637#M584545</link>
    <description>Hi&lt;BR /&gt;&lt;BR /&gt;As in your other entry . It must be something like that.&lt;BR /&gt;&lt;BR /&gt;Check you dmesg and syslog and if there are no messages then check the program coded limits&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It will run till a limit is reached.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;          steve Steel</description>
    <pubDate>Tue, 20 Aug 2002 09:40:29 GMT</pubDate>
    <dc:creator>Steve Steel</dc:creator>
    <dc:date>2002-08-20T09:40:29Z</dc:date>
    <item>
      <title>Error while request from client RPC to Server RPC</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-while-request-from-client-rpc-to-server-rpc/m-p/2788635#M584543</link>
      <description>Hi,&lt;BR /&gt;    Im using the RPC functions in HP UX 11.00. The problem is sometimes the client RPC terminated by Server RPC with the error "RPC : Miscellaneous tli error - bad flags" error. I'm not sure when and why this error is coming. i always use the port tcp. The problem resolved once the RPC daemon is restarted.&lt;BR /&gt;&lt;BR /&gt;Please let me know if you have come accross this problem and why this error is thrown out?? and what will be the resolution??.</description>
      <pubDate>Mon, 19 Aug 2002 07:13:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-while-request-from-client-rpc-to-server-rpc/m-p/2788635#M584543</guid>
      <dc:creator>M.R.Anand</dc:creator>
      <dc:date>2002-08-19T07:13:08Z</dc:date>
    </item>
    <item>
      <title>Re: Error while request from client RPC to Server RPC</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-while-request-from-client-rpc-to-server-rpc/m-p/2788636#M584544</link>
      <description>Anand ,&lt;BR /&gt;&lt;BR /&gt;    A TLI Error (Transport layer interface) is normally sent out if there is a problem  with client server communication .&lt;BR /&gt;  Since you say that you are using TCP , one of the  common problems faced with TCP is the&lt;BR /&gt;process running out of file handles. This happens when the server process has too many clients.&lt;BR /&gt;This can be managed by increasing the limit.&lt;BR /&gt;  Another area  where you might want to look into is your portmapper service -"rpcbind"&lt;BR /&gt;&lt;BR /&gt;Best of Luck ,&lt;BR /&gt; Subir</description>
      <pubDate>Tue, 20 Aug 2002 09:26:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-while-request-from-client-rpc-to-server-rpc/m-p/2788636#M584544</guid>
      <dc:creator>Subir Singh</dc:creator>
      <dc:date>2002-08-20T09:26:05Z</dc:date>
    </item>
    <item>
      <title>Re: Error while request from client RPC to Server RPC</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-while-request-from-client-rpc-to-server-rpc/m-p/2788637#M584545</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;As in your other entry . It must be something like that.&lt;BR /&gt;&lt;BR /&gt;Check you dmesg and syslog and if there are no messages then check the program coded limits&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It will run till a limit is reached.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;          steve Steel</description>
      <pubDate>Tue, 20 Aug 2002 09:40:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-while-request-from-client-rpc-to-server-rpc/m-p/2788637#M584545</guid>
      <dc:creator>Steve Steel</dc:creator>
      <dc:date>2002-08-20T09:40:29Z</dc:date>
    </item>
  </channel>
</rss>

