Inetd dies

[Mr. R. Astles]

Can anyone point me in the direction of anything that could cause the inetd to die with a signal 11 recorded in the syslog.log

inetd[1127]: Going down on signal 11

This has never happened before and co-incidently it has happened twice this week on different servers.

[Peter Kloetgen]

Hi,

more information about signals:

kill -l (lists all killing signals with numbers and names)

man -k signals (shows you where to find information of the meanings of signals)

Allways stay on the bright side of life!

Peter

[Steven Sim Kok Leong]

Hi,

Signal 11, or officially known as "segmentation fault", means that the program accessed a memory location that was not assigned. It usually meant a bug in the program.

Have you installed the latest patches for your server, in particular PHNE_XXXXX patches?

Try updating your inetd with the patches and see if that helps.

Hope this helps. Regards.

Steven Sim Kok Leong

[Steven Sim Kok Leong]

Hi,

If there is a core dump, probably it will say SIGSEGV inetd but in any case, the following will hopefully tell you more about the segmentation fault (if it is one):

# file core
# strings core

Hope this helps. Regards.

Steven Sim Kok Leong

[Steve Steel · Accepted solution]

Hi

If 11. then

Fix in the patches :

11.00 - PHNE_26365
11.11 - PHNE_26366


Steve Steel

[Brian Watkins]

You haven't made any application changes on these systems, have you? If you haven't, has anyone else made changes? ($#%@!%# developers....) :)

It's been my experience that the sudden occurrance of problems out of the blue are caused by some kind of change, either to the system's configuration or an application running on the system.

If no changes were made, then I'd check patch levels on the system.

[Stefan Marquardt_1]

One suggestions:

portscans mit nmap !
On other OS i see that inetd dies after doing that.