inetd[12186]: Cannot register service: RPC: Timed out

From: Mark Schubert <Mark.Schubert_at_cogita.com.au>
Date: Tue, 05 Mar 2002 17:26:01 +1100

Hi all,

We had the magic disappearing inetd process problem for V4.0F occur today
(there is a patch for it which we will apply)!

However, when we restarted inetd we had the following errors in daemon.log:
Mar 5 11:09:53 pha401 inetd[18011]: Cannot register service: RPC: Timed out
Mar 5 11:14:53 pha401 inetd[18011]: Cannot register service: RPC: Timed out
Mar 5 11:16:08 pha401 inetd[18011]: Cannot register service: RPC: Timed out
Mar 5 11:19:53 pha401 last message repeated 2 times
Mar 5 11:19:53 pha401 telnetd[5169]: ttloop: peer died: No such file or
directory
Mar 5 11:19:53 pha401 named[3063]: "1.64.10.in-addr.arpa IN NS" points to a
CNAME (ditto.goldenglow.com.au)
Mar 5 11:19:53 pha401 telnetd[255]: ttloop: peer died: No such file or
directory
Mar 5 11:19:53 pha401 telnetd[13147]: ttloop: peer died: No such file or
directory
Mar 5 11:19:53 pha401 telnetd[9676]: ttloop: peer died: Not owner
Mar 5 11:19:53 pha401 telnetd[5885]: ttloop: peer died: Not owner
Mar 5 11:19:53 pha401 telnetd[18373]: ttloop: peer died: Not owner

The main issue was the "Cannot register service" message and the fact that
no-one could telnet in for about 10 minutes (from 11:09 until at 19:53).

Does anyone know what the above messages are telling me?
Is there somewhere else I should have looked in order to speed up the 10
minute RPC initialisation?

TIA,

Mark.
Received on Tue Mar 05 2002 - 06:27:28 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:43 NZDT