This action might not be possible to undo. Are you sure you want to continue?
svcs -- Report Service Status svcs : lists all "enabled" services and their current status ( online, offline, disabled, maintenance, etc ) svcs -a : list all services available regardless of being enabled or not and the ir current status. svcs -x : lists "enabled" services that are not running ( faulted/maintenance ) or that are preventing other services from starting ( dependency ) svcs -l <service> : List detailed information on a defined service. svcs -? : List all available switches to the command. See manpage for additional information. svcadm -- Manipulate Service Instances svcadm enable <service name> : Enables a disabled service ... brings it online/s tarts it. Persistent across reboots unless -t ( Temporary ) switch is included. svcadm disable <service name> : Disables an enabled service ... brings it offlin e/stops it. Persistent across reboots unless -t ( Temporary ) switch is included . svcadm restart <service name> : Restarts an enabled service. ( stop / start ) svcadm refresh <service name> : Refreshes a service ( HUP -- if service is writt en to facilitate/handle a refresh ) svcadm clear <service name> : Clears a service in maintenance state after proble m has been addressed. svcadm milestone <milestone name> : Moves a system to the specified milestone. ( single-user, multi-user, multi-user-server, custom milesone ) svccfg -- Import/Export/Modify Service Configurations svccfg : Standalone with no arguments. Puts you into an interactive Service Conf iguration Shell. Useful for the creation of a service from scratch. svccfg import <file> : imports a service manifest xml file. Used to install a ne w predefined service to svc. svccfg export <service name> > file : Exports a currently running service in xml format. svccfg delete <service name> : Permanently deletes a defined service ( use cauti on with this command ) See manpage for additional usage. inetadm -- observe / configure inetd-based services. Allows management for inetd specific SMF services. Replaces /etc/inet/inetd.conf inetadm : Standalone with no arguments. Lists all defined services whether enabl ed or disabled, and their current status. inetadm -e <inet service> : Eneables the inetd service. inetadm -d <inet service> : Disables the inetd service. inetadm -l <inet service> : Lists properties associated with the specified servi ce. inetadm -m <inet service> name=value : Manipulate the "named" property of a defi ned service. inetadm -M name=valie : Globally manipulate the "named" property of all services . inetadm -p : Lists all default "named" properties and current defaults. inetconv : Converts new /etc/inet/inetd.conf entries to a service. This is usefu l when an application writes required service information into the inetd framewo rk under the old inetd.conf method. Once this command is executed, the service i s imported & written to SMF where it can then be managed via the inetadm or svc commands. Use the svc disable/svccfg delete commands to remove the service once defined.
If the root/usr filesystem services fault. VER: 1.error] SUNW-MSG-ID: SUN4U-8000-2S . Fault Management: fmadm faulty : Displays a list of faulty resources. Used to display the contents of any of the log files associated with the Fault Manager. boot -m milestone=single-user ( same as "boot -s" which is still supported ) boot -m milestone=multi-user : Boot with all networking services enabled. fmstat : Used to report fault management module statistics.VER Y VERBOSE. fmadm config : Display current Fault Management Configuration and Modules Loaded and their status. CSN: -.Sun-Fire-880. This is extremely helpfu l in troubleshooting problems under SMF that have occurred recently or during th e boot process. resort to fsck to clean and svcadm clear to retry the mount. Booting and Milestones: boot -m milestone=none : Used to boot a system that has a serious configuration issue. Similar to runlevel 2. but absolutely NO services are started. and cannot even boot to single-user mode without faulting.fmadm. boot -m debug : Start all SMF services in serial. fmdump : Fault Management log viewer. boot -m quiet : Default boot mode. Very little console output. and will contain only service log infor mation from last boot to current time for each service. Review the following document for steps to deal with faulty hardware: Solaris 10 includes a Fault Manager Daemon . This is a pseudo filesystem mounted on swap. and attempts to work around faults as they occur. boot -m verbose : Displays all SMF Service Start Messages on the console during boot up.SMF Log File Locations: Each service defined under SMF has an individual log file located in /var/svc/lo g. Helpful in determining what may be failing on a boot if the boot cannot complete. Display all SMF actions -. These are continuously appended log files. For example. All SMF Service S tart Messages are redirected to their corresponding log files. a faulty DIMM will cause memory pages to be relocated to functioning DIMMs. and will contain complete history for that service /etc/svc/volatile will also contain individual logs files for each service. SEVERITY: Minor Jan 10 14:23:14 csxtil5 EVENT-TIME: Tue Jan 10 14:23:14 CST 2006 Jan 10 14:23:14 csxtil5 PLATFOR M: SUNW. not even the root filesystem service. HOSTNAME: csxtil5 . to enable the root filesystem run the following : svcadm enable svc:/system/filesystem/root:default svcadm enable svc:/system/filesystem/usr:default This will allow you to now continue troubleshooting any issues with the root fil esystems available. The log file will reflect the name of the service as seen from svcs -a. Once logged in. This daemon keeps track of h ardware faults. TYPE: Fault. This will boot a kernel. Does n ot start "server" services. The Fault Manager will cause messages like the following to appear on the consol e and messages log: Jan 10 14:23:14 csxtil5 fmd: [ID 441519 daemon. These log files are cleaned during each boot.
Using fmdump -v -u. Jan 10 14:23:14 csxtil5 AUTO-RESPONSE: Pages of memory associated with this memo ry module are being removed from service as errors are reported.2382 e31c43f5-701a-64fa-a465-8754591e0e6f SUN4U-8000-2S 95% fault.memory.---------------------------------------------------------------------- . but may not. Jan 10 14:23:14 csxtil5 REC-ACTION: Schedule a repair procedure to replace the affected memory module. Refer to http://sun. generates output similar to the following: root@csxtil5: fmdump -v -u e31c43f5-701a-64fa-a465-8754591e0e6f TIME UUID SUNW-MSG-ID Jan 10 14:23:14. Use fmdump -v -u <EVENT_ID> to identify the module.com/msg/SUN4U-8000-2S for more information. It should output a description of the failed c omponent. the error message will reappear with each succeeding reboot. Issue the "fmadm faulty" command. as normal. root@servername: fmadm faulty STATE RESOURCE / UUID -------.When the server boots. as described in the line above. REV: 1. Jan 10 14:23:14 csxtil5 IMPACT: Total system memory capacity will be reduced as pages are retired.Jan 10 14:23:14 csxtil5 SOURCE: cpumem-diagnosis.dimm FRU: mem:///component=Slot.7799 e31c43f5-701a-64fa-a465-8754591e0e6f SUN4U-8000-2S 95% fault.dimm FRU: mem:///component=Slot.A:J8100 rsrc: mem:///component=Slot.A:J8100 rsrc: mem:///component=Slot.memory. the error message s hould not reappear. But unless steps are taken.A:J8100 Have the hardware replaced.3 Jan 10 14:23:14 csxti l5 EVENT-ID: e31c43f5-701a-64fa-a465-8754591e0e6f Jan 10 14:23:14 csxtil5 DESC: The number of errors associated with this memory m odule has exceeded acceptable levels.A:J8100 Jan 10 16:06:06.
The argumen t should be that of the event. issue the "fmadm repair" command.root@csxtil5: To reset the fault manager daemon.A:J8100: specified resou rce is not cached by fault manager .A:J8100 fmadm: failed to record repair to mem:///component=Slot. not the address of the resource: root@servername: fmadm repair e31c43f5-701a-64fa-a465-8754591e0e6f fmadm: recorded repair to e31c43f5-701a-64fa-a465-8754591e0e6f root@servername: fmadm repair mem:///component=Slot.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.