Admins,
I have an answer from Derk:
I'd check what process is using port 2524 with lsof and check further.
It should still work ok, though. I suspect that the process using port
2524 has registered itself with the portmapper with an id number that is
to big for portmap. It could also be a bug in rpcinfo, reporting the
wrong number because it doesn't expect such a big number.
I verified the port number 2524 to a process, actually it is this process that
started the search. A user was complaining that he could not start an agent on
the server, where the server process is the process listed above. It claimed
rpc not registered.... He nows claims that on another machine he can run the
agent just fine. He is now happy but I am not...I think he should be able to
run the agent on the server machine as well... I'll check it out...
Lee Brewer
Received on Tue Aug 21 2001 - 14:31:51 NZST