GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: RPC program registering
Operating System - HP-UX
1847397
Members
2699
Online
110264
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2006 12:08 AM
10-20-2006 12:08 AM
RPC program registering
Hi,
I have installed the TIBCO staffware application. When it starts up it needs to register a port with rpc, but it fails with the following errors:
T004: RESTART: WQS RPC number = 1073741824
T004: RESTART: LI RPC number = 1073741824
T004: Using RPC version 11
R004: rpcport_alloc (mode= 0, ptype = 2, pid = 119)
T004: sw_register_rpcport_server non-TI_RPC (rpc=391875, port=0, tcp, ver=11)
T001: check_rpc_prog (tcp) : Failed to register program 391875 version 11
T001: check_rpc_prog (tcp) : clnt_create() failed for program 391875 version 11
T001: check_rpc_prog (tcp) : 'sw_register_rpcpport_server: RPC: Program not registered
T004: check_rpc_prog () : pmap_unset () for program 391875 version 11 failed
T001: register_rpcport (pid=119, prog=391875) - unable to register tcp
T001: Registering RPC Listener Server Failed (RPCnum/port= 391875/0)
How could I test that RPC is running OK on the server (without restarting it! - It's a shared production server)
rpcbind daemon is running.
Thanks in advance,
Helena
I have installed the TIBCO staffware application. When it starts up it needs to register a port with rpc, but it fails with the following errors:
T004: RESTART: WQS RPC number = 1073741824
T004: RESTART: LI RPC number = 1073741824
T004: Using RPC version 11
R004: rpcport_alloc (mode= 0, ptype = 2, pid = 119)
T004: sw_register_rpcport_server non-TI_RPC (rpc=391875, port=0, tcp, ver=11)
T001: check_rpc_prog (tcp) : Failed to register program 391875 version 11
T001: check_rpc_prog (tcp) : clnt_create() failed for program 391875 version 11
T001: check_rpc_prog (tcp) : 'sw_register_rpcpport_server: RPC: Program not registered
T004: check_rpc_prog () : pmap_unset () for program 391875 version 11 failed
T001: register_rpcport (pid=119, prog=391875) - unable to register tcp
T001: Registering RPC Listener Server Failed (RPCnum/port= 391875/0)
How could I test that RPC is running OK on the server (without restarting it! - It's a shared production server)
rpcbind daemon is running.
Thanks in advance,
Helena
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2006 12:36 AM
10-20-2006 12:36 AM
Re: RPC program registering
There are several kinds of RPC in existence. Furthermore, RPC is not a process but a way for the processes to "talk" to each other, so it's a bit of a misnomer to say that "RPC is running". You can certainly check that the central component of the RPC server is running, but that doesn't tell you everything you need.
There is "Sun RPC" which is used in NFS, NIS and some other services. A key part of it is the rpcbind process (also known as "portmapper" on some unix flavours). To test this one, you could run "rpcinfo -p" - it should list all the active SunRPC services on the current host.
Then there is "DCE RPC" which is entirely different thing. On HP-UX, there is a process called "rpcd" (/opt/dce/sbin/rpcd) to handle this one. One way to test this one is to run this command:
rpccp show mapping ncacn_ip_tcp:127.0.0.1
If all's well, it should display several groups of four lines (object, interface id, string binding and annotation).
To start the rpcd component of DCE RPC on HP-UX, the command is (note the capital R):
sh /sbin/init.d/Rpcd start
The messages from your application look like it's probably trying to use SunRPC, but I'm not completely certain.
Check /var/adm/inetd.sec to see if there are any access restrictions defined: they apply to (some) SunRPC services too.
There is "Sun RPC" which is used in NFS, NIS and some other services. A key part of it is the rpcbind process (also known as "portmapper" on some unix flavours). To test this one, you could run "rpcinfo -p" - it should list all the active SunRPC services on the current host.
Then there is "DCE RPC" which is entirely different thing. On HP-UX, there is a process called "rpcd" (/opt/dce/sbin/rpcd) to handle this one. One way to test this one is to run this command:
rpccp show mapping ncacn_ip_tcp:127.0.0.1
If all's well, it should display several groups of four lines (object, interface id, string binding and annotation).
To start the rpcd component of DCE RPC on HP-UX, the command is (note the capital R):
sh /sbin/init.d/Rpcd start
The messages from your application look like it's probably trying to use SunRPC, but I'm not completely certain.
Check /var/adm/inetd.sec to see if there are any access restrictions defined: they apply to (some) SunRPC services too.
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP