Sponsored Content
Operating Systems HP-UX Sudden application crash in servers Post 303009710 by hicksd8 on Tuesday 19th of December 2017 03:51:19 AM
Old 12-19-2017
Possibly the system has run out of network buffer resources. Has the load/number of users been steadily increasing?

Network configurations determine the number of buffers available for network packets (of various different sizes) arriving and departing, and also the maximum number of connections.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sudden poweroff ??

Hi I am using unix for last few days. Here is my problem during boot the machine stop giving video signal and I don't know what's happening. When I ping (during boot) it from another machine it comes alive then goes out. The power on the CPU is on all the time. please help. (9 Replies)
Discussion started by: santosh1981
9 Replies

2. UNIX for Dummies Questions & Answers

Application servers, proper usage

Is it common in the Unix/Linux environment to install compute intensive applications on a Server system and have the client machines download the executables into memory at runtime to run locally? This model seems taxing to the network, and as I understand, has been largely abandoned in the... (1 Reply)
Discussion started by: jonwillog
1 Replies

3. UNIX for Advanced & Expert Users

Application Servers Installation and Users

Hi, When most of the server applications get installed, they create their own user. I believe this is to not use the "root" account. For example, Apache when installed creates a user called "apache". And the directories which it uses are all owned by this user. This seems to be the... (2 Replies)
Discussion started by: srikanths
2 Replies

4. Shell Programming and Scripting

Difference between development and Production unix servers for a application??

Hi all I am running a major script of my application in development for implementing code changes for process improvement in time. The script runs in production once in a month . It takes 8 hours 30 mins in Production server . what surprice me is , when I run the same script in development server... (9 Replies)
Discussion started by: sakthifire
9 Replies

5. Programming

socket system call can not succedd right after application crash.

hello all, I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error. But there is a problem regarding application crash.After an intentionally... (1 Reply)
Discussion started by: Sedighzadeh
1 Replies

6. Programming

Client/Server Socket Application - Preventing Client from quitting on server crash

Problem - Linux Client/Server Socket Application: Preventing Client from quitting on server crash Hi, I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64. I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies

7. Solaris

System date sudden change

Hi there, We have a Solaris 10 machine which has been up and running for more than 400 days. A strange behaviour happened. The system date defaulted to epoch timestamp. Oracle stopped and application failed causing management to parade. We managed to reset the date. All other servers and... (8 Replies)
Discussion started by: sundar63
8 Replies

8. Red Hat

XCB crash while Video Rendering in multithreded application

I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0 Following is the back trace of the multi-threaded program I am working on:... (0 Replies)
Discussion started by: anuachin
0 Replies
crash(8v)																 crash(8v)

Name
       crash - what happens when the system crashes

Description
       This section explains what happens when the system crashes and shows how to analyze crash dumps.

       When the system crashes voluntarily it prints a message on the console in the form:

	      panic: explanation

       The  system takes a dump on a mass storage peripheral device or the network, and then invokes an automatic reboot procedure as described in
       Unless there is some unexpected inconsistency in the state of the file systems due to hardware or software failure, the system then resumes
       multi-user operations.  If auto-reboot is disabled, the system halts at this point.

       The system has a large number of internal consistency checks; if one of these fails, it prints a short message indicating which one failed.

       The  most  common cause of system failures is hardware failure.	In all cases there is the possibility that hardware or software error pro-
       duced the message in some unexpected way.  These messages are the ones you are likely to encounter:

       IO err in push
       hard IO err in swap
	    The system encountered an error when trying to write to the paging device or an error in reading  critical	information  from  a  disk
	    drive.  Fix your disk if it is broken or unreliable.

       timeout table overflow
	    Due to the current data structure, running out of entries causes a crash.  If this happens, make the timeout table bigger.

       Exception Condition
	    An unexpected system error has occurred.  The exception types are as follows:

	    ---------------------------------------------------------------
	    Mnemonic   Description
	    ---------------------------------------------------------------
	    INT        External interrupt
	    MOD        TLB modification exception
	    TLBL       TLB miss exception (load or instruction fetch)
	    TLBS       TLB miss exception (store)
	    AdEL       Address error exception (load or instruction fetch)
	    AdES       Address error exception (store)
	    IBE        Bus error exception (for an instruction fetch)
	    DBE        Bus error exception (for a data load or store)
	    Sys        Sys call exception
	    Bp	       Breakpoint exception
	    CpU        Coprocessor unusable exception
	    Ovf        Arithmetic overflow exception
	    ---------------------------------------------------------------

       KSP not valid
	      This indicates either a problem in the system or failing hardware.

       init died
	      The  system initialization process has exited.  The only solution is the automatic reboot procedure described in Until this is done,
	      new users cannot log in.

       When the system crashes, it attempts to write an image of memory into the back end of the primary swap area.  After the system is rebooted,
       the  program  runs  and	preserves  a  copy  of	this core image and the current system in a specified directory for later access.  See for
       details.

       To analyze a dump, you should begin by running with the flag on the core dump.

See Also
       dbx(1), reboot(8), savecore(8)

								       RISC								 crash(8v)
All times are GMT -4. The time now is 11:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy