- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- system down
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
Forums
Discussions
Discussions
Discussions
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
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
05-18-2006 01:42 AM
05-18-2006 01:42 AM
system down
May 18 08:36:11 wschp sendmail[18658]: NOQUEUE: SYSERR(UID0): fill_fd: disconnew
and it keeps repeating every 5 minutes
thanks for your help in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 02:06 AM
05-18-2006 02:06 AM
Re: system down
Perhaps you can log onto the console and run some diagnostics.
tail -f syslog.log
bdf
ping anotherhost
I suggest you restart the system, if possible, cleanly at the console. If not possible, power switch it.
Watch the startup, check rc.log and run bdf, looking for full filesystems.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 02:08 AM
05-18-2006 02:08 AM
Re: system down
2. Verify that your netadmin haven't changed your switch port configuration
3. Make sure inetd is running
4. Make sure there is no duplicate IP configured in your network
5. Review the last changes you made
6. Check /etc/rc.config.d/netconf to make sure it's properly configured
Any of those could help... good luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 02:09 AM
05-18-2006 02:09 AM
Re: system down
from what you are writing the server is not actually down, but trying to re-start?
If so, bring the system to single-user mode and comment out any sendmail parts of the rc?.d scripts.
Secondly:
You can also force skip any rc script that may be stuck with CNTRl+\ on the console, but handle with care.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 02:11 AM
05-18-2006 02:11 AM
Re: system down
(Issue TC at the GSP prompt)
if the problem persists, this will allow You or HP do gather more information about it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 02:13 AM
05-18-2006 02:13 AM
Re: system down
Do this please check all your files for resolution on the system, like the hosts file, and if you have DNS, please check those configuration files too.
Try a nslookup with ip address
nslookup with hostname.
If they do not resolve just right it might be a misconfiguration on a resolution file.
Can you ping the ip of the server or telnet that equipment?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 02:16 AM
05-18-2006 02:16 AM
Re: system down
Check this doc.
Title: HP-UX Sendmail messages related to HDD performance issue
Document ID: 4000075001
US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079989949
Europe
http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079989949
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 03:29 AM
05-18-2006 03:29 AM
Re: system down
As of now I have reset/rebooted the server and things seems fine. i am sending .out files to hpux support.
i got the following iPlanet error from last night. Would someone enlighten me about it and I too will search google for it.
[17/May/2006:18:03:36] failure (15732): Error accepting connection -5970, oserr=23 (PR_SYS_DESC_TABLE_FULL_ERROR)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 04:55 AM
05-18-2006 04:55 AM
Re: system down
When you run out of nfiles, it is a server-wide problem: each process in the server will receive an error whenever it tries to open a file or use a network socket. Many programs don't handle this type of error well. This may cause things like sshd/inetd/syslogd to die, which makes the recovery more complicated.
Web server processes usually start up a large number of processes and/or threads to cope with loads of simultaneous requests. You should check the iPlanet's configuration to see when it will start limiting the number of requests. The maximum number of processes/threads multiplied by the number of files each thread needs to access must always be a number that is less than the nfiles value. If not, you must either increase the nfiles value or decrease the web server's load limits.
A public Web server is an easy target for Denial-of-Service attacks, many of which are based on creating a huge number of requests. You should always set the various limits so that the web server will hit the application-specific limits first, so there will be some reserve against overrunning the system-wide limit. When the web server hits its own internal limit, it should start replying to requests with HTTP error 503 (Out of resources) and recover gracefully when the load gets lighter again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 12:21 PM
05-18-2006 12:21 PM
Re: system down
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2006 01:46 AM
05-19-2006 01:46 AM
Re: system down
the formula is:
(16*(NPROC+16+MAXUSERS)/10+32+2*(NPTY+NSTRPTY+NSTRTEL))
Are there any repercussions to increasing any of these parameters, especially
NPTY (number of pseudo ttys)
NSTRPTY (max number of stream based pty)
NSTRTEL (number of telnet session device files)
Regards,
Abhimanyu.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2006 02:07 AM
05-19-2006 02:07 AM
Re: system down
there are no backinfluences from these formulas.
and these are only relevant to interactive users.
NPTY (number of pseudo ttys)
NSTRPTY (max number of stream based pty)
NSTRTEL (number of telnet session device files)
make nfile about three times the maximum amount of web sessions You want to support.
(each socket connection uses up a file handle or so)
You could also decrease some tcp parameters using ndd, mostly the *WAIT* ones, but this is unsupported by HP for some reason.