Use rpcinfo to look at the rpc program/port registration.  The output should
look something like this:

agrams@phx-remarsiso-01 agrams$ rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  rpcbind
    100000    3   tcp    111  rpcbind
    100000    2   tcp    111  rpcbind
    100000    4   udp    111  rpcbind
    100000    3   udp    111  rpcbind
    100000    2   udp    111  rpcbind
...
    390600    8   tcp   2020  arserverd
    390600    9   tcp   2020  arserverd
    390600   10   tcp   2020  arserverd
    390600   11   tcp   2020  arserverd
    390600   12   tcp   2020  arserverd
    390600   13   tcp   2020  arserverd
    390600   14   tcp   2020  arserverd
    390601    8   tcp   2020  arserverd
    390601    9   tcp   2020  arserverd
    390601   10   tcp   2020  arserverd
    390601   11   tcp   2020  arserverd
    390601   12   tcp   2020  arserverd
    390601   13   tcp   2020  arserverd
    390601   14   tcp   2020  arserverd
...

Make sure the port matches what you have your arserver configured for.  If
it doesn't then there is an issue with the RPC program registration.  Look
back at the rpc debug logs for the RPCB_SET entries and see what those log
entries show.  Do they show the right port?

If that doesn't reveal anything, get a packet dump (tcpdump) during your
attempt to login and use Wireshark to look for the rpcbind packets (tcp/111
and udp/111) and see what the communications contain.  Wireshark will decode
the packets so that you can see the request and response in human readable
format.

Axton Grams

The opinions, statements, and/or suggested courses of action expressed in
this E-mail do not necessarily reflect those of BMC Software, Inc.  My
voluntary participation in this forum is not intended to convey a role as a
spokesperson, liaison or public relations representative for BMC Software,
Inc.

2011/3/9 michep <[email protected]>

> OMG! Its getting more and more interesting with every step!
>
> Ok, thanx to Conny ("-i" parameter to rpcbind service) now im able to
> start ARS server with Register-With-Portmapper:T option without
> errors. BUT!!!
> Now trying to connect to ARS server with RUT without specified TCP
> port I receive error:
>
> ARERR [90] Cannot establish a network connection to the AR System
> server : msk-m1-rem001 : RPC: Miscellaneous tli error - System error
> (Connection refused)
>
> Ok, thanx to Axton, I stop rpcbind service and started it in debug
> mode: rpcbind -id, and able to see whats happen inside.
>
> Restart ARS server, and see that a lot of registration commands
> (RPCB_SET) was processed and succeeded.
>
> Now, connecting with RUT without specified TCP and see rpc command in
> rpcbind log:
>
> PMAP_GETPORT req for (390620, 18, tcp) from
> 192.168.170.10.250.247 :port = 47240
>
> So, comment was proessed and port number was returned - 47240.
>
> WTH!? I didn't remove port options in ar.conf, now its looks like:
>
> Register-With-Portmapper: T
> TCD-Specific-Port: 35000
> Plugin-Port: 36000
>
> and netstat shows that ports 35000 and 36000 are in LISTEN state, so
> why rpcbind returned wrong port number?
>
> Next, comment out port options:
>
> Register-With-Portmapper: T
> #TCD-Specific-Port: 35000
> #Plugin-Port: 36000
>
> and restart ARS server, truing to connect with RUT without specified
> TCP port - error again, rpcbind returns:
>
> PMAP_GETPORT req for (390620, 18, tcp) from
> 192.168.170.10.223.199 :port = 18773
>
> BUT! ARS server is listening on different port:
>
> # lsof +M -p 13564|grep IPv4
> ...
> arserverd 13564 root    9u  IPv4 1994493      0t0     TCP *:21833
> (LISTEN)
> ...
>
> Whats goning on?!
>
> And even one more finding - in this configuration arplugin reports
> segfault every one and a half minutes:
>
> Mar  9 16:02:10 msk-m1-rem001 kernel: [2598443.587831]
> arplugin[13909]: segfault at 1c ip 00000000f6a33cc1 sp
> 00000000f42fae28 error 4 in libc-2.11.1.so[f69c2000+15b000]
>
> I call support ...
>
> On 6 мар, 12:48, Conny Martin <[email protected]> wrote:
> > so go to /etc/sysconfig/rpcbind and add this line
> >
> > RPCBIND_OPTIONS="-i"
> >
> > then restart rpcbind (/etc/init.d/rpcbind restart)
> > you should now see the -i option in ps output
> > If you start your arserver it should now be able to register with
> portmapper
>
>
> On 6 мар, 02:33, Axton <[email protected]> wrote:
> > Try starting rpcbind in debug mode to see what it reports.  Look in
> > /var/log/messages to see if rpcbind is reporting anything there already.
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to