dCache / oncrpc4j

Pure Java implementation of ONCRPC/SUNRPC
Other
30 stars 30 forks source link

Can't register program on IBM AIX 5.1 #6

Open derekhsu opened 10 years ago

derekhsu commented 10 years ago

Hello,

I am trying write a ONCRPC program on IBM AIX 5.1. First, I tested it on my windows 7 desktop and worked, but when I run it on IBM AIX 5.1, the program can't be registered to portmap service. The log listed below:


09:43:33.828 [WrapperSimpleAppMain] INFO com.csc.dl.rpc.server.Runner - Starting program... 09:43:33.860 [WrapperSimpleAppMain] INFO com.csc.dl.rpc.server.Runner - Start RPC Server @ Program: 9999 09:44:51.460 [WrapperSimpleAppMain] INFO com.csc.dl.rpc.server.Runner - Starting program... 09:44:51.498 [WrapperSimpleAppMain] INFO com.csc.dl.rpc.server.Runner - Start RPC Server @ Program: 9999 09:44:52.077 [WrapperSimpleAppMain] DEBUG c.c.d.rpc.helpers.EnvironmentHelper - Get env property by IP: test 09:44:54.542 [WrapperSimpleAppMain] INFO com.csc.dl.rpc.server.Limiter - Load threshold data 09:45:00.221 [WrapperSimpleAppMain] INFO org.dcache.xdr.OncRpcSvc - Registering new program [9999:1] : com.csc.dl.rpc.server.Applic ation@a8bf6e6e 09:45:00.553 [WrapperSimpleAppMain] DEBUG o.d.xdr.portmap.RpcbindV4Client - portmap pina 0mpmppcbindV4Cli59 [WrapperSimpleAppMain] DEBUG org.dcache.xdr.ReplyQueue - Registering key 1 09:45:00.582 [WrapperSimpleAppMain] DEBUG org.dcache.xdr.ReplyQueue - query key 1 with timeout 09:45:00.593 [Grizzly-kernel(1) SelectorRunner] DEBUG org.dcache.xdr.ReplyQueue - updating key 1 09:45:00.596 [WrapperSimpleAppMain] DEBUG o.d.xdr.portmap.RpcbindV4Client - portmap unset port: prog: 9999 vers: 1, owner: root 09:45:00.601 [WrapperSimpleAppMain] DEBUG org.dcache.xdr.ReplyQueue - Registering key 2 09:45:00.603 [WrapperSimpleAppMain] DEBUG org.dcache.xdr.ReplyQueue - query key 2 with timeout 09:45:00.605 [Grizzly-kernel(1) SelectorRunner] DEBUG org.dcache.xdr.ReplyQueue - updating key 2 09:45:00.628 [WrapperSimpleAppMain] DEBUG o.d.xdr.portmap.RpcbindV4Client - portmap ping 09:45:00.629 [WrapperSimpleAppMain] DEBUG org.dcache.xdr.ReplyQueue - Registering key 3 09:45:00.631 [WrapperSimpleAppMain] DEBUG org.dcache.xdr.ReplyQueue - query key 3 with timeout 09:45:00.633 [Grizzly-kernel(1) SelectorRunner] DEBUG org.dcache.xdr.ReplyQueue - updating key 3 09:45:00.636 [WrapperSimpleAppMain] DEBUG o.d.xdr.portmap.RpcbindV4Client - portmap set port: prog: 9999 vers: 1, netid: udp addr: 0 :0:0:0:0:0:0:0.117.48, owner: root 09:45:00.638 [WrapperSimpleAppMain] DEBUG org.dcache.xdr.ReplyQueue - Registering key 4 09:45:00.639 [WrapperSimpleAppMain] DEBUG org.dcache.xdr.ReplyQueue - query key 4 with timeout 09:45:00.641 [Grizzly-kernel(1) SelectorRunner] DEBUG org.dcache.xdr.ReplyQueue - updating key 4 09:45:00.642 [WrapperSimpleAppMain] INFO com.csc.dl.rpc.server.Application - RPC Server started.


Can you provide any suggestion? Thank you.

kofemann commented 10 years ago

Hi,

could you check that rpcbind/portmap on AIX allowes updates from non privilaged ports. On linux this is enabled with '-i' option to rpcbind.

kofemann

vladanvulovic commented 5 years ago

It seems we have similar problem on AIX: service is binded to a port (logs says successfully) but rpcinfo doesn't list it... [DEBUG][RpcbindV4Client : ping] portmap ping [2019-05-31 12:48:14 CEST][main] [DEBUG][RpcbindV4Client : ping] portmap ping [2019-05-31 12:48:14 CEST][main] [DEBUG][RpcbindV4Client : unsetPort] portmap unset port: prog: 805306432 vers: 1, owner: vladan [2019-05-31 12:48:14 CEST][main] [DEBUG][RpcbindV4Client : ping] portmap ping [2019-05-31 12:48:14 CEST][main] [DEBUG][RpcbindV4Client : setPort] portmap set port: prog: 805306432 vers: 1, netid: tcp addr: 0:0:0:0:0:0:0:0.31.162, owner: vladan [2019-05-31 12:48:14 CEST][main] [DEBUG][RpcbindV4Client : setPort] portmap set port: prog: 805306432 vers: 1, netid: tcp6 addr: 0:0:0:0:0:0:0:0.31.162, owner: vladan [2019-05-31 12:48:14 CEST][main] Do we have any update on this issue? Is it an OS related issue?