- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- inetd failed after system reboot
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО09-15-2009 10:13 PM
тАО09-15-2009 10:13 PM
inetd failed after system reboot
Anyone could advise me at what circumstances whereby inetd failed to be running after system reboot. At any time, manual intervention like "/usr/sbin/inetd start" got to be performed.
And because of such, my system is won't be able to join part of cluster members.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2009 10:18 PM
тАО09-15-2009 10:18 PM
Re: inetd failed after system reboot
Did you check /etc/rc.config.d/netdaemons? INETD value should be 1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2009 10:22 PM
тАО09-15-2009 10:22 PM
Re: inetd failed after system reboot
2. Check what inetd settings are present in /etc/rc.config.d with the following command:
grep -i inetd /etc/rc.config.d/*
3. Consider starting inted with logging enabled to see if you can spot the issue by setting
INETD_ARGS="-l"
in the file /etc/rc.config.d/netdaemons
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2009 10:46 PM
тАО09-15-2009 10:46 PM
Re: inetd failed after system reboot
psa1a:/root# grep -i inetd /etc/rc.config.d/*
/etc/rc.config.d/netdaemons:# inetd configuration. See inetd(1m) #
/etc/rc.config.d/netdaemons:# NOTE: inetd is always started as part of the boot up process.
/etc/rc.config.d/netdaemons:# INETD_ARGS: The command line arguments to be used when
/etc/rc.config.d/netdaemons:# starting inetd. ("-l" is the only option
/etc/rc.config.d/netdaemons:export INETD_ARGS=-1
/etc/rc.config.d/nfsconf:# 0 if /etc/inetd.conf has an entry for mountd.
/etc/rc.config.d/nfsconf:# however, it can be started from either nfs.server or inetd, and
There was no error indication shows on syslog. I don't quite sure why. And since "INETD_ARGS=-1" should able to tell why, unfortunately it wasn't. Maybe i'm wrong.
At last, found out /usr/sbin/inetd wasn't running during the last occurrence.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2009 10:58 PM
тАО09-15-2009 10:58 PM
Re: inetd failed after system reboot
export INETD=1
export INETD_ARGS="-l"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2009 11:06 PM
тАО09-15-2009 11:06 PM
Re: inetd failed after system reboot
INETD_ARGS=-1
i.e. "hyphen one"
when it should be
INETD_ARGS=-l
i.e. "hyphen lower case L"
and as tugay says, you also need to have:
INETD=1
(in this case this is a 1 rather than a lower case LK)
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2009 11:13 PM
тАО09-15-2009 11:13 PM
Re: inetd failed after system reboot
export INETD_ARGS=1
export INETD_ARGS=-1
export INETD_ARGS=
I noticed the default comment pertaining to such right there is..
# NOTE: inetd is always started as part of the boot up process.
#
# INETD_ARGS: The command line arguments to be used when
# starting inetd. ("-l" is the only option
# available at startup.)
#
Is it always should be equal to 1 or left blank ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2009 11:22 PM
тАО09-15-2009 11:22 PM
Re: inetd failed after system reboot
>
>export INETD_ARGS=1
>export INETD_ARGS=-1
>export INETD_ARGS=
The first 2 are INCORRECT - as I said they are specifying "one" and "hyphen one" and neither of these are valid for INETD_ARGS - this is a mis-reading or typo by someone - you should either have INETD_ARGS set to "" or to "-l" (that's "hyphen lower case L").
And as we already said, you also need the parameter INETD set to 1 (in this case that *is* a one) in the netdaemons file.
HTH
Duncan
I am an HPE Employee