Sponsored Content
Full Discussion: Server Shutdown Problem
Operating Systems Solaris Server Shutdown Problem Post 302332594 by frank_rizzo on Thursday 9th of July 2009 02:33:29 PM
Old 07-09-2009
sounds like your root file system is corrupt or the disk is bad. is this mirrored? do you have a backup? are you able to check /var/adm/messages ? can you boot off a cd or the network and check the file systems and or hardware?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Server shutdown Troubleshooting

SCO Unixware 7.1.1 Hi friends, At 11:30pm last night mymain Unix Server hung or rebooted (Unaware which one), and was bot available for 10 minutes. Is there a log file somewhere which will tell me what happened ? I have looked ad /var/adm/syslog, but cannot make head nor tail of it. ... (1 Reply)
Discussion started by: sureshy
1 Replies

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. Solaris

Server shutdown based on temperature

Working with a T5240/Solaris 10 and trying to figure out if there is a setting that will automatically shutdown the server if it hits a certain temperature. I'm just trying to identify if there is a setting in place and what that temperature is... Any help is much appreciated! (5 Replies)
Discussion started by: ojgraham
5 Replies

10. Red Hat

Shutdown server when network inactive

I was referring script to shutdown server from local interface ubuntuforums.org/archive/index.php/t-2017336.html. This is scheduled in CRON. It will run every 20 minutes and check for inactivity. It compares the RX and TX packets from 20 minutes ago to detect if they significantly increased. If... (0 Replies)
Discussion started by: sanjaymp
0 Replies
dmu(8)							      System Manager's Manual							    dmu(8)

NAME
dmu - Dataless management utility SYNOPSIS
/usr/sbin/dmu DESCRIPTION
The dataless management utility (dmu) manages Dataless Management Services (DMS) environments and clients, letting you install, configure, and list DMS environments, and add, list, modify, or remove DMS clients. DMS maintains root (/), /usr, and /var file systems on a DMS server for DMS clients. All swapping and dumping is done on the DMS client's local disk. The dmu utility creates a root file system based on the software subsets installed in the DMS environment area on the server. This root file system is accessed by DMS clients over a Local Area Network (LAN). DMS lets system administrators customize the root file systems before it is accessed by DMS clients. Caution DMS is not supported in a clusters environment. A cluster member cannot be a DMS server or a dataless client. Dataless Management Services The DMS server maintains a separate copy of the root file system for each DMS client in a client root directory (usually /clients) in the DMS area. Each DMS root area is customized for the DMS client to allow for different environmental requirements. The DMS server also reserves a DMS area where copies of the /usr file system reside. The /usr file system is shared by DMS clients with read-only access. The server's DMS root and /usr areas are available to DMS clients through a network file system (NFS), with each client accessing the DMS disk area on the DMS server over a LAN. Each DMS client is booted over the network from its private root area on the DMS server. Once booted, the DMS client continues to use its root files and /usr files from the server's DMS area. DMS Environments One or more DMS environments can reside in a DMS area. Each DMS environment contains one or more root areas; a root area exists for each general type of DMS client supported. DMS client root areas reside in the /var/adm/dms directory, and are named /var/adm/dms/dmsN.arch, where N is a sequentially-assigned integer starting with 0 and arch is a name identifying the client's machine architecture, such as alpha. The first DMS area for Alpha clients would be named /var/adm/dms/dms0.alpha. DMS Client Areas DMS maintains a DMS client area in the /clients directory. Each root area for an individual DMS client is tailored from the appropriate generic root file system, and contains a customized kernel to support that DMS client's actual system configuration. Each DMS client views its private root area and the shared /usr area as local although these areas actually reside on the DMS server and are accessed through NFS. As with the /var/adm/dms area, multiple client areas can be established in different partitions. DMS Software Installation Use the dmu utility's Install Software option to install software into each /var/adm/dms/dmsN.arch file system. All software must be installed and configured in the DMS server area before DMS clients can be added to the DMS environment. DMS Client Registration Before you use the dmu utility to serve a DMS client, you must register the DMS client for a DMS area or make an entry for the DMS client in the /etc/hosts file on the DMS server. You must have the following information to register a DMS client: The client's host name. The /var/adm/dms/dmsN.arch DMS environment where the DMS client will be registered. The location of the DMS client's root directory. The path must not exceed 25 characters and be located under the /clients directory. The DMS client's network interface, subnet mask, and default route for this network interface. The DMS client's hardware network address. The gateway address between the DMS client and server. The swap device and partition and swap device type. The type of kernel build support to be provided for the DMS client. RESTRICTIONS
You must log in as root or have superuser privileges to invoke the dmu utility. Tru64 UNIX DMS servers do not support dataless environments on DMS clients that do not support the BOOTP Internet Boot Protocol. DMS is not supported in a clusters environment. A cluster member cannot be a DMS server or a dataless client. EXAMPLES
The following command invokes the dmu utility from the root system prompt on the DMS server: # /usr/sbin/dmu You see the DMU Main Menu, and you can select dmu functions. *** DMU Main Menu *** Choices without key letters are not available. a) ADD a client c) CONFIGURE software environments d) DELETE software environments i) INSTALL software environments l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software environments x) EXIT Enter your choice: Available menu options depend upon previous actions. For example, you cannot list, modify, or remove clients until you have added at least one DMS client. In that case, the m, l, and r key letters are not shown in front of their respective options: a) ADD a client c) CONFIGURE software environments d) DELETE software environments i) INSTALL software environments ) LIST registered clients ) MODIFY a client ) REMOVE a client s) SHOW software environments x) EXIT FILES
Base directory for Dataless Management Services Default location of client's root directory DMS client database file SEE ALSO
Commands: bindsetup(8), doconfig(8), nissetup(8), pmerge(8), setld(8) Files: bootptab(4) Sharing Software on a Local Area Network Installation Guide Installation Guide -- Advanced Topics dmu(8)
All times are GMT -4. The time now is 12:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy