Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Server shutdown Troubleshooting Post 23646 by RTM on Wednesday 26th of June 2002 01:55:52 PM
Old 06-26-2002
You can try the dmesg command (it may have some info), check where your system sends info by looking at /etc/syslog.conf. If it sends to /var/adm/syslog, then try looking at syslog again. There will be normal messages such as DNS may put stats into it, messages from Sendmail, that type of thing. Look for things that are not normally there (look at old syslog files to figure out what is normally there versus not).

Anything you think is suspicious but you don't know what it means, try posting it here or check out these two links - you can search for errors in their databases.

pcunix.com/scofaq
Caldera KnowledgeBase

pcunix.com/SCOFAQ has a troubleshooting guide that may help:
link

Part of it...
System logs may be very useful. However, before you look at them, get the "ls -l", "ls -c" and "ls -u" from the logs- this tells you when the log was last used, etc.- if there's no current information and there should be, those dates are important clues..

You need to know what to look for in the logs. SCO makes it easier by using words like "CONFIG" "NOTICE" and "WARNING" that you can grep for, but on other OS'es you may have to just look manually until you can figure out what sort of key words they would use.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

shutdown a unix server

Hi, how to shutdown a unix machine ? We are on SunOS server15.8 Generic_108528-24 sun4u sparc SUNW,Ultra-Enterprise Many thanks. (2 Replies)
Discussion started by: big123456
2 Replies

2. UNIX for Advanced & Expert Users

Mysterious Server Shutdown

Virtually no UNIX admin experience. Any admin duties are shared by several folks with no special training. Today we had our Sun v880 server, running Solaris 5.8, shutdown for no apparent reason. When we checked on server we found it completely powered down, yet still connected to a fully... (6 Replies)
Discussion started by: buechler66
6 Replies

3. AIX

server is getting shutdown

Hi Guys, Please help in this...when we start HACMP services ..server is getting shutdon. Error mesg from cluster.log. Apr 14 08:43:27 bascop17 snmpd: NOTICE: SMUX trap: (0 0) (127.0.0.1+46302+1) Apr 14 08:43:33 bascop17 topsvcs: (Recorded using libct_ffdc.a cv 2):::Error ID:... (1 Reply)
Discussion started by: b_manu78
1 Replies

4. UNIX for Advanced & Expert Users

RHEL 4 U5 - Server immediate shutdown

Dear all, My server has shutdown frequently. It is AMD64, OS is RHEL 4 U5. I've seen the system log, before the shutdown occured: Jul 29 04:28:56 localhost kernel: EDAC k8 MC0: general bus error: participating processor(local node response), time-out(no timeout) memory transaction... (2 Replies)
Discussion started by: mr_bold
2 Replies

5. Solaris

Server Shutdown Problem

I have a sparc T1 server (I know its old) running Solaris 8, which we use for testing. It has been very slow in response- prompt takes couple of minutes to come up, so I decided to reboot the server but I can reboot it, it is giving following errors when I try to shutdown it down. root@deva:/#... (3 Replies)
Discussion started by: Tirmazi
3 Replies

6. AIX

Troubleshooting NIM Server

hello folks, Can someone help me troubleshoot the NIM Server NIM MASTER: >> # hostname oldbcoedv # cat /etc/hostname 192.52.100.29 bcoeqa bcoeqa.bin.com.sa 192.52.100.66 oldbcoedv # cat /etc/bootptab ..... # T180 -- (xstation only) -- enable virtual screen #NO CLIENTS... (6 Replies)
Discussion started by: filosophizer
6 Replies

7. Solaris

Startup and shutdown a server

Are rc scripts executed serially or all at the same time. Is there a way to see this happen? A log file or the syslogd? This is Solaris 10. (2 Replies)
Discussion started by: djehresmann
2 Replies

8. UNIX for Advanced & Expert Users

Shutdown the Linux server if no one is using the server

Hi All, I want to shutdown the server if no one is actualy using it. Its a linux server. I thought of sending a msg on users terminal for those who all are logged in and expecting a input from them. If they will reply system should not get shutdown else it should not. Can any one... (2 Replies)
Discussion started by: Sadhana
2 Replies

9. AIX

Server Shutdown

Hi, is it possible to find out ip address of user who has shutdown or rebooted the server , I have used the command errpt -a , in that it is showing server rebooted but it is not showing ip address who has shutdown the serve, even I have used command last reboot. Please suggest. Regards, ... (3 Replies)
Discussion started by: manoj.solaris
3 Replies

10. Ubuntu

Apache Server troubleshooting

I'm having issues getting apache to respond to requests outside of my local LAN. If I goto my server URL (www .poillion. com) it says connecting... but never finishes and returns anything. I'm using Ubuntu Server 10.10. a) The DNS is working fine. It's pointed to my cable modem's IP and... (1 Reply)
Discussion started by: lorewap3
1 Replies
cimserver(8)						      System Manager's Manual						      cimserver(8)

NAME
cimserver - start or stop the CIM Server; display the version number or running status of the CIM Server SYNOPSIS
cimserver [configProperty=value] ... cimserver -s [ shutdownTimeout = value ] cimserver -v cimserver -h cimserver --help cimserver --version cimserver --status Remarks This command can only be executed by a privileged user. DESCRIPTION
The cimserver command provides a command line interface to stop and start the CIM Server, as well as to display the version number or run- ning status of the CIM Server. After installation, the CIM Server must be started using the cimserver command. If the system is rebooted, the CIM Server will automati- cally restart, with the exception of the case where the CIM Server was shutdown prior to the reboot. Generally, once the CIM Server is started, it is expected to be always running and ready to serve CIM requests. However, if the CIM Server must be stopped and restarted, the cimserver command can be used to shutdown the CIM Server gracefully and restart it at a later time. Starting the CIM Server Issuing the cimserver command without any options starts the CIM Server process. When starting the CIM Server using the cimserver command, the <configProperty=value> syntax can be used to set the configuration properties to be used by the CIM Server. It is important to know that the values specified in the cimserver command apply only to the current CIM Server process that gets started. The default values for the configuration properties do not change. For a list of the CIM Server config- uration properties, see the man page for the cimconfig command. Shutting down the CIM Server Issuing the cimserver command with the -s option stops the CIM Server. Optionally, a timeout value can be specified by setting the shut- downTimeout configuration property. Under normal operation, CIM Server should be able to be shutdown fairly quickly without problem. There are, however, situations that may prevent CIM Server from shutting down within a reasonable amount of time. For example, a provider that is not responding to requests, or a provider that is servicing a long-running CIM request. To handle such situations and to ensure that the CIM Server can be shutdown without having the user wait a long period of time (or indefinitely), a shutdown timeout value is used. The shutdown timeout value is the maximum amount of time (in seconds) the user is willing to wait for the CIM Server to complete all the outstanding CIM operation requests before shutting down the CIM Server. If the specified shutdown timeout period expires, the CIM Server will be shutdown even if there are CIM operations in progress. The shutdown timeout value is a CIM Server configuration property (shut- downTimeout ) that can be changed using the command. The default shutdown timeout value is 10 seconds. A timeout value (in seconds) can be specified in the cimserver command to shutdown the CIM Server using the =value> syntax. This overrides the default shutdown timeout value. The minimum timeout value is 2 seconds. While CIM Server is shutting down, a client connection request will result in a connection error (the same as if the CIM Server were not running). For clients who have already established a connection to the CIM Server, new CIM requests will be rejected with a CIM error indicating that the CIM Server is shutting down. When a client receives a response containing a CIM error indicating that the CIM Server is shutting down, it should close the connection and reconnect to CIM Server at a later time. Options The cimserver command recognizes the following options: -v, --version Display the version number or running status of the CIM Server. -h, --help Display the command usage. --status Display the running status of the CIM Server. -s Stop the CIM Server. Specify the timeout value for shutting down the CIM Server. This can only be used in conjunction with the -s option. The minimum timeout value is 2 seconds. If this is not specified, the default configurable timeout value will be used. configProperty=value Set the value for the specified configuration property to be used in starting the CIM Server. EXIT STATUS
The cimserver command returns one of the following values: 0 Success 1 Error The cimserver --status command returns one of the following values: 0 The CIM Server is running 1 Error 2 The CIM Server is not running When an error occurs, an error message is written to stderr and an error value of 1 is returned. DIAGNOSTICS
unable to connect to CIM Server. CIM Server may not be running. The cimserver command was issued to stop the CIM Server when CIM Server was not running. An exit status value of 1 is returned. Error: Bind failed: Failed to bind socket. The cimserver command was issued to start the CIM Server and the CIM Server was already running. An exit status value of 1 is returned. EXAMPLES
Stop the CIM Server with the default timeout value of 10 seconds. cimserver -s Stop the CIM Server with a timeout value of 5 seconds. cimserver -s shutdownTimeout=5 Start the CIM Server. cimserver Start the CIM Server with the configuration property enableNamespaceAuthorization set to true. cimserver enableNamespaceAuthorization=true Display the version number of the CIM Server. This version number is used to identify the release version of the CIM Server in the OpenPe- gasus release. cimserver -v Display the command usage. cimserver -h SEE ALSO
cimconfig(8). cimserver(8)
All times are GMT -4. The time now is 02:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy