- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Opcom message "%NTP-E-INVRPCTYP, Invalid RPC t...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО08-22-2008 06:22 AM
тАО08-22-2008 06:22 AM
Opcom message "%NTP-E-INVRPCTYP, Invalid RPC type" every second.
I just set NTP service on my cluster. It's running well. Time is synchronizing. But on the console i start receiving this messages.
HPA1:SYSTEM>
%%%%%%%%%%% OPCOM 22-AUG-2008 16:17:50.75 %%%%%%%%%%%
Message from user SYSTEM on SMHPA1
%NTP-E-INVRPCTYP, Invalid RPC type 1107296384 from source 00000000, message disgarded.
HPA1:SYSTEM>
%%%%%%%%%%% OPCOM 22-AUG-2008 16:17:50.75 %%%%%%%%%%%
Message from user SYSTEM on SMHPA1
%NTP-E-INVRPCTYP, Invalid RPC type 1107296384 from source 00000000, message disgarded.
HPA1:SYSTEM>
%%%%%%%%%%% OPCOM 22-AUG-2008 16:17:50.75 %%%%%%%%%%% (from node SMHPA2 at 22-AUG-2008 16:17:50.76)
Message from user SYSTEM on SMHPA2
%NTP-E-INVRPCTYP, Invalid RPC type 1107296384 from source 00000000, message disgarded.
HPA1:SYSTEM>
%%%%%%%%%%% OPCOM 22-AUG-2008 16:17:50.75 %%%%%%%%%%% (from node SMHPA2 at 22-AUG-2008 16:17:50.76)
Message from user SYSTEM on SMHPA2
%NTP-E-INVRPCTYP, Invalid RPC type 1107296384 from source 00000000, message disgarded.
I'm not able to find any information about this message. Thanks for help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-22-2008 07:30 AM
тАО08-22-2008 07:30 AM
Re: Opcom message "%NTP-E-INVRPCTYP, Invalid RPC type" every second.
$ diff sys$sysroot:[tcpip$ntp]tcpip$ntp.conf SYS$SYSROOT:[TCPIP$NTP]TCPIP$NTP.TEMPLATE
You may still have an "example" server ip address left in there, when they should have been replaced by your own server list.
Are you also using DTSS?
# The following commands allow interoperation of NTP with another time service
# such as DTSS. If enabled (by removing #), NTP will not set the system clock.
# server 127.127.1.0 prefer
# fudge 127.127.1.0 stratum 0
# The following commands allow this node to act as a backup NTP server (or as
# the sole NTP server on an isolated network), using its own system clock as
# the reference source. If enabled (by removing #), this NTP server will
# become active only when all other normal synchronization sources are
# unavailable.
# server 127.127.1.0
# fudge 127.127.1.0 stratum 8
Duncan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2008 10:24 PM
тАО08-24-2008 10:24 PM
Re: Opcom message "%NTP-E-INVRPCTYP, Invalid RPC type" every second.
DTSS is not running and in TCPIP$NTP.CONF is only this:
# Copyright 2000 Compaq Computer Corporation
# NTP Configuration File
# This file is modified by P.vd.Aa & W.Schooten
# please do not make any changes to this file
driftfile SYS$SPECIFIC:[TCPIP$NTP]TCPIP$NTP.DRIFT
server 10.224.178.151 prefer
server 10.224.178.152 prefer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2008 12:52 AM
тАО08-27-2008 12:52 AM
Re: Opcom message "%NTP-E-INVRPCTYP, Invalid RPC type" every second.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2008 03:14 AM
тАО08-27-2008 03:14 AM
Re: Opcom message "%NTP-E-INVRPCTYP, Invalid RPC type" every second.
Which version of tcp ?
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2008 03:37 AM
тАО08-27-2008 03:37 AM
Re: Opcom message "%NTP-E-INVRPCTYP, Invalid RPC type" every second.
on a COMPAQ AlphaServer DS20E 666 MHz running OpenVMS V7.3-2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2008 05:49 AM
тАО08-27-2008 05:49 AM
Re: Opcom message "%NTP-E-INVRPCTYP, Invalid RPC type" every second.
http://h71000.www7.hp.com/doc/732final/6526/6526pro_contents_003.html#toc_chapter_13
for setting debug levels for NTP. You can then look in SYS$SPECIFIC:[TCPIP$NTP]TCPIP$NTP_RUN.LOG for the output.
Try using ntpq to check your setting and connections with the time servers.
If all else fails, you will probably want to trace the incoming UDP packets on port 123. Maybe you have some other application trying to use the same port?
Duncan