HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- inetd died on signal 13
Operating System - HP-UX
1834644
Members
2377
Online
110069
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
01-05-2004 03:37 AM
01-05-2004 03:37 AM
I have a strange intermittent problem that is bothering me. I havent found much info on it anywhere.
Every once in a while, I get a "inetd died Signal 13" error... This occurs on a N-4000-55, running 11.i
It seems non-fatal, but I would just like to know what may be causing it. I have checked after each time and inetd is still running and has a start time BEFORE the error occured... as if it never died.
The current proc has been running since Dec 20th.
# grep "Died on signal 13" syslog.log
Dec 24 22:01:18 chdcfas1 inetd[1286]: ident/tcp: Died on signal 13
Dec 25 10:18:40 chdcfas1 inetd[1286]: ident/tcp: Died on signal 13
Dec 31 22:01:15 chdcfas1 inetd[1286]: ident/tcp: Died on signal 13
root:/var/adm/syslog
# grep "Died on signal 13" OLDsyslog.log
Dec 17 22:01:17 chdcfas1 inetd[1510]: ident/tcp: Died on signal 13
Every once in a while, I get a "inetd died Signal 13" error... This occurs on a N-4000-55, running 11.i
It seems non-fatal, but I would just like to know what may be causing it. I have checked after each time and inetd is still running and has a start time BEFORE the error occured... as if it never died.
The current proc has been running since Dec 20th.
# grep "Died on signal 13" syslog.log
Dec 24 22:01:18 chdcfas1 inetd[1286]: ident/tcp: Died on signal 13
Dec 25 10:18:40 chdcfas1 inetd[1286]: ident/tcp: Died on signal 13
Dec 31 22:01:15 chdcfas1 inetd[1286]: ident/tcp: Died on signal 13
root:/var/adm/syslog
# grep "Died on signal 13" OLDsyslog.log
Dec 17 22:01:17 chdcfas1 inetd[1510]: ident/tcp: Died on signal 13
Unix, the other white meat.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2004 03:52 AM
01-05-2004 03:52 AM
Solution
From KB..
Sendmail uses identd but does not depend on
identd to be working to process mail. So, if there is no other reason you
need identd (strictly an advisory mechanism) you can disable it with the
following steps:
Comment out the service the file:
/etc/inetd.conf
Restart inetd with the command:
/sbin/init.d/inetd stop
/sbin/init.d/inetd start
or re-read the inetd.conf file with the command:
inetd -c
There is also a patch available to fix this
PHNE_26304 will for 11.00
PHNE_26305 will for 11.11
Select latest and appropriate one for your env.
Goodluck..
-USA..
Sendmail uses identd but does not depend on
identd to be working to process mail. So, if there is no other reason you
need identd (strictly an advisory mechanism) you can disable it with the
following steps:
Comment out the service the file:
/etc/inetd.conf
Restart inetd with the command:
/sbin/init.d/inetd stop
/sbin/init.d/inetd start
or re-read the inetd.conf file with the command:
inetd -c
There is also a patch available to fix this
PHNE_26304 will for 11.00
PHNE_26305 will for 11.11
Select latest and appropriate one for your env.
Goodluck..
-USA..
Good Luck..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2004 04:00 AM
01-05-2004 04:00 AM
Re: inetd died on signal 13
Signal 13 is _SIGPIPE.
The comment in the definition file is "write on a pipe with no one to read it".
This is a known problem on 11.00 and 11.11 and their are patches for the problem.
The fix was originally put into the 11.00 patch, PHNE_26304 and the 11.11 patch, PHNE_26305.
Best regards,
Kent M. Ostby
The comment in the definition file is "write on a pipe with no one to read it".
This is a known problem on 11.00 and 11.11 and their are patches for the problem.
The fix was originally put into the 11.00 patch, PHNE_26304 and the 11.11 patch, PHNE_26305.
Best regards,
Kent M. Ostby
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2004 07:58 AM
01-23-2004 07:58 AM
Re: inetd died on signal 13
Okay got a good answer from HP support on this...
You can edit 1 of 2 files... and comment out ident with no advers effects...
/etc/inetd.conf and reread inet with inetd -c
OR
You can edit sendmail.cf and then re-read it with newaliases
Ident merely performs a reverse lookup for the senders hostname/ip address... It MAY seem like a security hole to do this, but it was Berline who I got as a support person and she is surely a security guru...
She said it was a bad way to try to break into a box! so I believed her of course! but seriously, she said there are far better ways to compromise a unix box...
You can edit 1 of 2 files... and comment out ident with no advers effects...
/etc/inetd.conf and reread inet with inetd -c
OR
You can edit sendmail.cf and then re-read it with newaliases
Ident merely performs a reverse lookup for the senders hostname/ip address... It MAY seem like a security hole to do this, but it was Berline who I got as a support person and she is surely a security guru...
She said it was a bad way to try to break into a box! so I believed her of course! but seriously, she said there are far better ways to compromise a unix box...
Unix, the other white meat.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP