System freezes after "could not getpeername"

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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

Hi Andreas,

Inetd "invokes all internet services as needed.=A0 connection-oriented
services are invoked each time a connection is made, by creating a
process.=A0 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.=A0 Is that cor=
rect?

What's the date on inetd.conf?=A0 Any changes there?

What flavour + version of linux are you running?

Kind regards,

Herta

On 27 August 2010 19:59, Andreas Moroder =
wrote:
>
> Hello,
>
> we have a old =A02.4.19-64GB-SMP server. Today it freezed twice and m=
e 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@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html



--
"Life on Earth may be expensive,
=A0but 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

unsubscribe linux-admin

On 8/27/2010 5:21 PM, Herta Van den Eynde wrote:
> 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 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@vger.kernel.org
>> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

Check this page, perhaps you need to verify inetd security.

http://alas.matf.bg.ac.rs/manuals/lspe/snode=3D142.html

Cheers,
Gerardo

On Fri, Aug 27, 2010 at 12:59 PM, Andreas Moroder
wrote:
> Hello,
>
> we have a old =A02.4.19-64GB-SMP server. Today it freezed twice and m=
e 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@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

Herta Van den Eynde schrieb:
> 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
Hello Herta,

it's a SLES 9 2.4.19-64GB-SMP.
This messages appear in /var/log/messages as last entries before we hat
to shutdown ( switch off ) the server.

Bye
Andreas

--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

Gerardo Juarez-Mondragon schrieb:
> Check this page, perhaps you need to verify inetd security.
>
> http://alas.matf.bg.ac.rs/manuals/lspe/snode=142.html
>
> Cheers,
> Gerardo
>
Hello Gerardo,

the strange thing is that it worked for years.
Now I started vsftpd from a init script so inetd is no more involved.

Thanks
Andreas

--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

.... ciao:

: on "8-28-2010" "Andreas Moroder" writ:
: the strange thing is that it worked for years.
: Now I started vsftpd from a init script so inetd is no more involved.

from the man page:

"SYNOPSIS
vsftpd [configuration file]

DESCRIPTION
vsftpd is the Very Secure File Transfer Protocol Daemon. The
server should be invoked from a ``super-server'' such as inetd(8)
or xinetd(8)."


i'd start there ...


--
.... it's not what you see ,
but in stead , notice ...
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

>
> DESCRIPTION
> vsftpd is the Very Secure File Transfer Protocol Daemon. The
> server should be invoked from a ``super-server'' such as inetd(8)
> or xinetd(8)."
>
>
> i'd start there ...
>
Hello Terry,

I know,

but there seems to be a correlation between the getpeername call in
inted and the freeze of the machine, so I prefer to avoid inetd in this
case .

Bye
Andreas

--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

.... ciao:

: on "8-30-2010" "Andreas Moroder" writ:

: but there seems to be a correlation between the getpeername call in inted and
: the freeze of the machine, so I prefer to avoid inetd in this case .

i tend to think that solution cosmetic at best, and at worst, a
misdirected effort. my reading of the 'inetd' manpage does not suggest
it calls 'getpeername', but insteat hands off connections to implied
servers. seems to me, 'getpeername' is more likely local to the
answering server, that's just a quess though.

"having" to bypass inetd, is expedient, but not an elegant solution.

for my part, i'd start looking at bind ...


--
.... it's not what you see ,
but in stead , notice ...
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

Am 30.08.2010 11:01, schrieb terry white:
> ... ciao:
>
> : on "8-30-2010" "Andreas Moroder" writ:
>
> : but there seems to be a correlation between the getpeername call in inted and
> : the freeze of the machine, so I prefer to avoid inetd in this case .
>
> i tend to think that solution cosmetic at best, and at worst, a
> misdirected effort. my reading of the 'inetd' manpage does not suggest
> it calls 'getpeername', but insteat hands off connections to implied
> servers. seems to me, 'getpeername' is more likely local to the
> answering server, that's just a quess though.
>
> "having" to bypass inetd, is expedient, but not an elegant solution.
>
> for my part, i'd start looking at bind ...
>
>
Hello Terry,

I am sure you are right that this is not the solution but I hope that
this way we have more time to find the true source of problems.

out of our logilfe:
inetd[1397]: could not getpeername

according to this on other OSes getpeername is used
http://fxr.googlebit.com/source/usr.sbin/inetd/inetd.c?v=OPE NBSD-CURRENT
so I suppose that this is true for linux too that inetd uses getpeername.

Could you please explain me why you would start to look at bind ?

One strange thing we also see on the machine ist that
/proc/sys/fs/file-nr is constantly growing. May it be that getpeername
did stop to work because it needed a filehandle and did not get it ?


Thanks
Andreas






--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

.... ciao:

: on "8-30-2010" "Andreas Moroder" writ:

: inetd[1397]: could not getpeername
: according to this on other OSes getpeername is used
: http://fxr.googlebit.com/source/usr.sbin/inetd/inetd.c?v=OPE NBSD-CURRENT

and from that:

"44 * Inetd - Internet super-server
45 *
46 * This program invokes all internet services as needed.
----------------------^
47 * connection-oriented services are invoked each time a
48 * connection is made, by creating a process. This process
---------------------------------^---------^
49 * is passed the connection as file descriptor 0 and is
50 * expected to do a getpeername to find out the source host
----------^----------------^
51 * and port."

from my reading of that, 'inetd' is reporting an error of a child
process, not one of its own making. 'getpeername' suggests a name
resolution issue as reported by inetd.


: Could you please explain me why you would start to look at bind ?

i've had sendmail hang my system on dns failure. in fact, i test for
a working dns before calling sendmail.


: One strange thing we also see on the machine ist that
: /proc/sys/fs/file-nr is constantly growing. May it be that getpeername did
: stop to work because it needed a filehandle and did not get it ?

i don't know enough about that, to even guess ...


--
.... it's not what you see ,
but in stead , notice ...
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: System freezes after "could not getpeername"

terry white wrote:

> : but there seems to be a correlation between the getpeername call in inted and
> : the freeze of the machine, so I prefer to avoid inetd in this case .
>
> i tend to think that solution cosmetic at best, and at worst, a
> misdirected effort. my reading of the 'inetd' manpage does not suggest
> it calls 'getpeername',

It calls getpeername() to determine whether the connection originates
from port 20 (ftp-data), and refuses it if it does (to prevent FTP
"bounce" attacks):

http://ftp.fr.openbsd.org/pub/OpenBSD/src/usr.sbin/inetd/ine td.c

Personally, I think that the inetd messages are unlikely to be related
to the system freezing. They just happen to be the only thing in the
"messages" log file.

The sort of things which will cause a hard lock up (i.e. requiring the
use of Alt-SysRq to reboot) won't log anything in "messages". If
they're logged anywhere (which isn't guaranteed), it's more likely to
be "kernel".

--
Glynn Clements
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html