What do you do right after a server crashed.

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat What do you do right after a server crashed.
# 1  
Old 02-23-2011
What do you do right after a server crashed.

What do you check????

Thanks!

JC
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 server crashed two times

Hi, I have two Solaris 10 servers. First server crashed last week (Monday) and second one crashed over the weekend. I have checked the logs such as /var/adm/messages, syslog and dmesg. So for I found none. My management wants to know why the server crashed. I need to come with some kind of... (4 Replies)
Discussion started by: samnyc
4 Replies

2. IP Networking

DNS server crashed

If Freebsd DNS server that served 100 people is crashed. How to move this 100 people to a new FreeBSD DNS server as quickly as possible? (1 Reply)
Discussion started by: AIX_30
1 Replies

3. Solaris

System got crashed.

Hi Admins, In my local Vmware system i have installed solaris but while getting my root disk mirrored in svm I changed the vfstab entries and rebooted the server , the server got crashed, and now the root file systems and other filesystems are crashed. Please help me in recovering this. (2 Replies)
Discussion started by: Laxxi
2 Replies

4. Linux

Find out process that crashed the server

Hi everybody, I want to find out all the processes that ran before a server crashed. Is that possible? I've looked in /var/log/messages and found out that the system was out of memory. A user probably wrote a script (in Perl or Python) that used up all available memory and crashed the... (11 Replies)
Discussion started by: z1dane
11 Replies

5. Solaris

Disk crashed

My system is SUN Solaris 5.6 and one of the disks on the server got crashed. Here are the details d23: Mirror Submirror 0: d24 State: Okay Submirror 1: d25 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) ... (1 Reply)
Discussion started by: asalman.qazi
1 Replies

6. Linux

system getting crashed

Hello, Iam a running a apache webserver in CentOS and i get a heavy traffic about 2.5 lac pageviews daily and my db size is about 2GB. Now the problem is after serving some lacs of requests by apache....Both apache and mysql hangouts and the system gets hanged up...using all resources in the... (2 Replies)
Discussion started by: dheeraj4uuu
2 Replies

7. SuSE

suse 9 crashed

Hi, Running SLES 9 (update 4) on dell's poweredge 1950 server. Kernel: 2.6.5-7.315-smp #1 SMP Wed Nov 26 13:03:18 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux Yesterday night my monitoring service emailed me system(ssh/smtp) unreachable...I tried connection through ssh, it did not let me through... (0 Replies)
Discussion started by: upengan78
0 Replies

8. AIX

AIX Crashed..

My AIX 5.3 Machine Carshed Can any one tell some way to find out what went wrong.. I mean debug why it got creahed... (3 Replies)
Discussion started by: pbsrinivas
3 Replies

9. UNIX for Dummies Questions & Answers

old server crashed

Hello We had an old system designed in fortran that ran on a IBM RS6000 AIX 3.2 system. The person who designed is long gone. It was replaced with a completely different (non unix) system 6 years ago. We still used it for historical lookups of older information. Well yesterday it died. The... (5 Replies)
Discussion started by: billfaith
5 Replies

10. Post Here to Contact Site Administrators and Moderators

Gollum got crashed

Gollum got crashed, needs Administrator's attention. Check this: https://www.unix.com/showthread.php?p=302093676 (0 Replies)
Discussion started by: tayyabq8
0 Replies
Login or Register to Ask a Question
rpc_register(3ncs)														rpc_register(3ncs)

Name
       rpc_register - register an interface (server only)

Syntax
       #include <idl/c/rpc.h>

       void rpc_$register(ifspec, epv, status)
       rpc_$if_spec_t *ifspec;
       rpc_$epv_t epv;
       status_$t *status;

Arguments
       ifspec		   The interface being registered.

       epv		   The entry point vector (EPV) for the operations in the interface.  The EPV is always defined in the server stub that is
			   generated by the NIDL compiler from an interface definition.

       status		   The completion status.  If the completion status returned in is equal to status_$ok , then the routine that supplied it
			   was successful.

Description
       The  routine  registers	an  interface  with  the RPC runtime library.  After an interface is registered, the RPC runtime library will pass
       requests for that interface to the server.

       You can call several times with the same interface (for example, from various subroutines of the same server), but each call  must  specify
       the  same  EPV.	Each registration increments a reference count for the registered interface; an equal number of routines are then required
       to unregister the interface.

Examples
       The following statement registers the bank interface with the bank server host's RPC runtime library:
       rpc_$register (&bank_$if_spec, bank_$server_epv, &status);

Diagnostics
       This section lists status codes for errors returned by this routine in

       rpc_$op_rng_error   The requested operation does not correspond to a valid operation in the requested interface.

       rpc_$too_many_ifs   The maximum number of interfaces is already registered with the RPC runtime library; the server  must  unregister  some
			   interface before it registers an additional interface.

       rpc_$not_in_call    An internal error.

       rpc_$you_crashed    This error can occur if a server has crashed and restarted.	A client RPC runtime library sends the error to the server
			   if the client makes a remote procedure call before the server crashes,  then  receives  a  response	after  the  server
			   restarts.

       rpc_$proto_error    An internal protocol error.

       rpc_$illegal_register
			   You are trying to register an interface that is already registered and you are using an EPV different from the one used
			   when the interface was first registered.  An interface can be multiply registered, but you must use	the  same  EPV	in
			   each routine.

       rpc_$bad_pkt	   The server or client has received an ill-formed packet.

Files
See Also
       intro(3ncs), rpc_register_mgr(3ncs), rpc_register_object(3ncs), rpc_unregister(3ncs)

																rpc_register(3ncs)