Hi Andreas, Inetd "invokes all internet services as needed. connection-oriented services are invoked each time a connection is made, by creating a process. This process is passed the connection as file descriptor 0 and is expected to do a getpeername to find out the source host and port." (from inetd.c) So it looks like these messages are written at boottime. Is that correct? What's the date on inetd.conf? Any changes there? What flavour + version of linux are you running? Kind regards, Herta On 27 August 2010 19:59, Andreas Moroder <andreas.moroder@xxxxxxxxxxxx> wrote: > > Hello, > > we have a old 2.4.19-64GB-SMP server. Today it freezed twice and me had to reboot via sysreq. > > In messages I found > > Aug 27 17:22:08 galileo2 -- MARK -- > Aug 27 17:38:01 galileo2 inetd[1397]: could not getpeername > Aug 27 17:38:08 galileo2 inetd[1397]: could not getpeername > Aug 27 17:39:34 galileo2 last message repeated 2 times > Aug 27 17:46:52 galileo2 inetd[1397]: could not getpeername > Aug 27 18:20:41 galileo2 -- MARK -- > Aug 27 18:07:52 galileo2 inetd[1397]: could not getpeername > Aug 27 18:07:59 galileo2 last message repeated 6 times > > Can anyone please tell me what could be the reason for this error ? > Is this a DNS problem or a file-nr problem ? > > Thanks > Andreas > > -- > To unsubscribe from this list: send the line "unsubscribe linux-admin" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- "Life on Earth may be expensive, but it comes with a free ride around the Sun." -- To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
