Service Management Facility

1. SMF 특징(SMF Features)

가. (Legacy 스크립트) SMF 서비스(새로운 서비스 관리 방식)와 Legacy Run Control스크립트 (이전 서비스 관리 방식, SMF 서비스에 의해 관리 되지 않는다.)를 둘 다 사용할 수 있다.

나. (서비스 restart) 서비스의 의존성 순서를 점검하고, 자동으로 실패한 서비스를 restart 한다.

# svcs -a | grep sendmail/* sendmail 서비스 online 상태 */

# pgrep -lf sendmail /* 정상적으로 데몬이 떠 있는 상태 */

# pkill -9 sendmail /* sendmail 데몬을 강제 종료 */

# pgrep -lf sendmail /* 데몬 restart */

다. (SMF 서비스 관리에 대해) svcadm 명령어를 통해 disable/enable 할 수 있으며, 이런 경우 영구적으로 설정 된다. -t 옵션으로 현재만 서비스의 상태를 disable/enable 할 수 있다

라. (부팅시의 메시지) 부팅할 때 콘솔 출력 메시지를 자세하게 보여주지 않는다.

마. (서비스 설정 저장소) service configuration repository는 서비스마다 snapshot 설정을 유지하며, 최근에 성공했던 snapshot 설정으로 돌리는 것이 가능하다.

바. (서비스 설정 snapshot) 서비스 설정에 대한 자동 snapshot 기능에 의해 서비스 설정에 대한 쉬운 백업, 복구, 이전 상태로 변경할 수 있다.

사. (서비스 의존성 관계) 서비스간의 의존성 관계의 정의 때문에, 서비스간의 이상 관계를 쉽게 발견할 수 있도록 해 주거나, 서비스를 병렬적으로 수행할 수 있도록 해 준다. 그래서 부팅이 빨라졌다.

2. SMF 아키텍처(SMF Architecture)

- SMF 구성 요소(Main components of SMF)

● 서비스 추상화(Service abstraction)

● 서비스 저장소(Repository of service information, (예) /etc/svc/repository.db)

● 저장소 관리 데몬(Daemon to access the repository, svc.configd)

● 저장소 접근 API(APIs for access to the repository)

● 메인 재시작 데몬(Master restarter daemon, svc.startd)

● 위임된 재시작 데몬(Delegated restarters, (예) inetd)

● 명령행 툴(Command line tools, (예) svcs, svcadm, svccfg)

3. SMF 서비스(SMF Services)

가. 서비스의 종류(Categories of Service)

● milestone (런레벨)

● system (시스템)

● network (네트워크)

● application (응용프로그램)

● legacy (이전 방식)

● device (디바이스)

● site (사이트)

● platform (플랫폼)

나. 서비스 URI문법

- 다음의 FMRI 형식은 모두 같은 의미이다.

● svc:/system/console-login:default

● svc://localhost/system/console-login:default

● system/console-login:default

● console-login:default

● console-login

- vold 데몬 관리 예

# svcadm disable svc:/system/filesystem/volfs:default

= svcadm disable system/filesystem/volfs:default

= svcadm disable filesystem/volfs:default

= svcadm disable volfs:default

= svcadm disable volfs

다. 서비스 상태

- Disabled -> (Offline -> Maintenance) -> Online

라. 서비스 구성요소

1) svc.startd Daemon

- 시스템의 서비스를 책임지는 Daemon. Master Daemon 이라고도 한다.

2) /etc/svc/repository.db

- 서비스의 정보를 담고 있는 파일. 부팅 할 때 이 파일의 내용을 가지고 서비스를 실행한다.

- /lib/svc/seed/global.db 파일은 비어있는 파일이다.

- Solaris를 설치할 때 global.db 파일을 repository.db 파일로 복사한다. 

3) SMF Profile & SMF Manifest

가) SMF Profile

(1) 시스템이 부팅될 때 활성화 되는 서비스 인스턴스들의 목록

(2) 부팅될 때 사용 되는 파일은 아니다. 부팅될 때는/etc/svc/repository.db 파일을 사용

(3) 초기 repository.db 파일의 서비스 목록과 부팅시 활성화할 목록을 만들때 사용

(4) repository.db에 로딩하기 위해서는 다음과 같이 사용할 수 있다.

(예) # svccfg apply /var/svc/profile/generic.xml

(5) SMF Profile은 /var/svc/profile/generic.xml파일이다.

- 이 파일은 generic_open.xml or generic_limited_net.xml 파일에 심볼릭 링크 걸려 있다.

- generic_open.xml 파일을 사용하면 일반적인 원격 서비스는 모두 enable

- generic_limited_net.xml 파일을 사용하면 ssh 서비스를 제외한 원격서비스는 disable

나) SMF Manifests

(1) XML 형식의 파일로 구성된 서비스 또는 서비스 인스턴스의 관계 설정 파일로 Property의 집합으로 구성된다.

(2) 서비스에 대한 서비스명, 서비스 start/stop Method, 또는 여러 가지 목록이다.

(3) 모든 Manifest는 /var/svc/manifest directory에 위치하고, 이 directory의 로컬 그룹 서비스의 서브디렉토리들을 포함할 수 있다.

4) /var/svc/log Directory

가) /var/svc/log -> SMF log file 존재(누적 로그 기록)

나) 부팅시에 Service Instance 실행시 에러가 있는지 확인

# egrep -l '(ERROR|WARNING)' /var/svc/log/*

출처 : http://www.bigcom.co.kr/tech/admin/hddiag.htm

출처 : http://cafe.naver.com/hunistyle.cafe?iframe_url=/ArticleRead.nhn%3Farticleid=30

http://dlc.sun.com/pdf/816-5166/816-5166.pdf

Name

svcs– report service status

Synopsis

svcs [-aHpv?] [-o col[,col]]... [-R FMRI-instance]... 
     [-sS col]... [FMRI | pattern]...

svcs {-d | -D} [-Hpv?] [-o col[,col]]... [-sS col]... 
     [FMRI | pattern] ...

svcs -l [FMRI | pattern]...

svcs -x [-v] [FMRI]...

Description

The svcs command displays information about service instances as recorded in the service configuration repository.

The first form of this command prints one-line status listings for service instances specified by the arguments. Each instance is listed only once. With no arguments, all enabled service instances, even if temporarily disabled, are listed with the columns indicated below.

The second form prints one-line status listings for the dependencies or dependents of the service instances specified by the arguments.

The third form prints detailed information about specific services and instances.

The fourth form explains the states of service instances. For each argument, a block of human-readable text is displayed which explains what state the service is in, and why it is in that state. With no arguments, problematic services are described.

Error messages are printed to the standard error stream.

The output of this command can be used appropriately as input to the svcadm(1M) command.

Options

The following options are supported:

-?

Displays an extended usage message, including column specifiers.

-a

Show all services, even disabled ones. This option has no effect if services are selected.

-d

Lists the services or service instances upon which the given service instances depend.

-D

Lists the service instances that depend on the given services or service instances.

-H

Omits the column headers.

-l

(The letter ell.) Displays all available information about the selected services and service instances, with one service attribute displayed for each line. Information for different instances are separated by blank lines.

The following specific attributes require further explanation:

dependency

Information about a dependency. The grouping and restart_on properties are displayed first and are separated by a forward slash (/). Next, each entity and its state is listed. See smf(5) for information about states. In addition to the standard states, each service dependency can have the following state descriptions:

absent

No such service is defined on the system.

invalid

The fault management resource identifier (FMRI) is invalid (see smf(5)).

multiple

The entity is a service with multiple instances.

File dependencies can only have one of the following state descriptions:

absent

No such file on the system.

online

The file exists.

If the file did not exist the last time that svc.startd evaluated the service's dependencies, it can consider the dependency to be unsatisfied. svcadm refresh forces dependency re-evaluation.

unknown

stat(2) failed for a reason other than ENOENT.

See smf(5) for additional details about dependencies, grouping, and restart_on values.

enabled

Whether the service is enabled or not, and whether it is enabled or disabled temporarily (until the next system reboot). The former is specified as either true or false, and the latter is designated by the presence of (temporary).

A service might be temporarily disabled because an administrator has run svcadm disable -t, used svcadm milestone, or booted the system to a specific milestone. See svcadm(1M) for details.

-o col[,col]...

Prints the specified columns. Each col should be a column name. See COLUMNS below for available columns.

-p

Lists processes associated with each service instance. A service instance can have no associated processes. The process ID, start time, and command name (PID, STIME, and CMD fields from ps(1)) are displayed for each process.

-R FMRI-instance

Selects service instances that have the given service instance as their restarter.

-s col

Sorts output by column. col should be a column name. See COLUMNS below for available columns. Multiple -s options behave additively.

-S col

Sorts by col in the opposite order as option -s.

-v

Without -x, displays verbose columns: STATE, NSTATE, STIME, CTID, and FMRI.

With -x, displays extra information for each explanation.

-x

Displays explanations for service states.

Without arguments, the -x option explains the states of services which:

• are enabled, but are not running.

• are preventing another enabled service from running.

Operands

The following operands are supported:

FMRI

A fault management resource identifier (FMRI) that specifies one or more instances (see smf(5)). FMRIs can be abbreviated by specifying the instance name, or the trailing portion of the service name. For example, given the FMRI:

svc:/network/smtp:sendmail

The following are valid abbreviations:

sendmail :sendmail smtp smtp:sendmail network/smtp

The following are invalid abbreviations:

mail network network/smt

If the FMRI specifies a service, then the command applies to all instances of that service, except when used with the -D option.

Abbreviated forms of FMRIs are unstable, and should not be used in scripts or other permanent tools.

pattern

A pattern that is matched against the FMRIs of service instances according to the “globbing” rules described by fnmatch(5). If the pattern does not begin with svc:, then svc:/ is prepended. The following is a typical example of a glob pattern:

qexample% svcs \*keyserv\* STATE STIME FMRI disabled Aug_02 svc:/network/rpc/keyserv:default

FMRI-instance

An FMRI that specifies an instance.

COLUMNS

Column names are case insensitive. The default output format is equivalent to “-o state,stime,fmri”. The default sorting columns are STATE, STIME, FMRI.

CTID

The primary contract ID for the service instance. Not all instances have valid primary contract IDs.

DESC

A brief description of the service, from its template element. A service might not have a description available, in which case a hyphen (-) is used to denote an empty value.

FMRI

The FMRI of the service instance.

INST

The instance name of the service instance.

NSTA

The abbreviated next state of the service instance, as given in the STA column description. A hyphen denotes that the instance is not transitioning. Same as STA otherwise.

NSTATE

The next state of the service. A hyphen is used to denote that the instance is not transitioning. Same as STATE otherwise.

SCOPE

The scope name of the service instance.

SVC

The service name of the service instance.

STA

The abbreviated state of the service instance (see smf(5)):

DGD

degraded

DIS

disabled

LRC

legacy rc*.d script-initiated instance

MNT

maintenance

OFF

offline

ON

online

UN

uninitialized

Absent or unrecognized states are denoted by a question mark (?) character. An asterisk (*) is appended for instances in transition, unless the NSTA or NSTATE column is also being displayed.

See smf(5) for an explanation of service states.

STATE

The state of the service instance. An asterisk is appended for instances in transition, unless the NSTA or NSTATE column is also being displayed.

See smf(5) for an explanation of service states.

STIME

If the service instance entered the current state within the last 24 hours, this column indicates the time that it did so. Otherwise, this column indicates the date on which it did so, printed with underscores (_) in place of blanks.

Examples

---

Example 1 Displaying the Default Output




This example displays default output:

example% svcs STATE STIME FMRI ... legacy_run 13:25:04 lrc:/etc/rc3_d/S42myscript ... online 13:21:50 svc:/system/svc/restarter:default ... online 13:25:03 svc:/milestone/multi-user:default ... online 13:25:07 svc:/milestone/multi-user-server:default ...

---

---

Example 2 Listing All Local Instances




This example lists all local instances of the service1 service.

example% svcs -o state,nstate,fmri service1 STATE NSTATE FMRI online - svc:/service1:instance1 disabled - svc:/service1:instance2

---

---

Example 3 Listing Verbose Information




This example lists verbose information.

example% svcs -v network/rpc/rstat:udp STATE NSTATE STIME CTID FMRI online - Aug_09 - svc:/network/rpc/rstat:udp

---

---

Example 4 Listing Detailed Information




This example lists detailed information about all instances of system/service3. Additional fields can be displayed, as appropriate to the managing restarter.

example% svcs -l network/rpc/rstat:udp fmri svc:/network/rpc/rstat:udp enabled true state online next_state none restarter svc:/network/inetd:default contract_id dependency require_all/error svc:/network/rpc/bind (online)

---

---

Example 5 Listing Processes




example% svcs -p sendmail STATE STIME FMRI online 13:25:13 svc:/network/smtp:sendmail 13:25:15 100939 sendmail 13:25:15 100940 sendmail

---

---

Example 6 Explaining Service States Using svcs -x




(a) In this example, svcs -x has identified that the print/server service being disabled is the root cause of two services which are enabled but not online. svcs -xv shows that those services are print/rfc1179 and print/ipp-listener. This situation can be rectified by either enabling print/server or disabling rfc1179 and ipp-listener.

example% svcs -x svc:/application/print/server:default (LP print server) State: disabled since Mon Feb 13 17:56:21 2006 Reason: Disabled by an administrator. See: http://sun.com/msg/SMF-8000-05 See: lpsched(1M) Impact: 2 dependent services are not running. (Use -v for list.)

(b) In this example, NFS is not working:

example$ svcs nfs/client STATE STIME FMRI offline 16:03:23 svc:/network/nfs/client:default

(c) The following example shows that the problem is nfs/status. nfs/client is waiting because it depends on nfs/nlockmgr, which depends on nfs/status:

example$ svcs -xv nfs/client svc:/network/nfs/client:default (NFS client) State: offline since Mon Feb 27 16:03:23 2006 Reason: Service svc:/network/nfs/status:default is not running because a method failed repeatedly. See: http://sun.com/msg/SMF-8000-GE Path: svc:/network/nfs/client:default svc:/network/nfs/nlockmgr:default svc:/network/nfs/status:default See: man -M /usr/share/man -s 1M mount_nfs See: /var/svc/log/network-nfs-client:default.log Impact: This service is not running.

---

Exit Status

The following exit values are returned:

0

Successful command invocation.

1

Fatal error.

2

Invalid command line options were specified.

Attributes

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWcsu
Interface Stability	See below.

Screen output is Uncommitted. The invocation is Committed.

See Also

ps(1), svcprop(1), svcadm(1M), svccfg(1M), svc.startd(1M), stat(2), libscf(3LIB), attributes(5), fnmatch(5), smf(5) 

jsp-2_0-fr-spec.zip

출처 : Sun Microsystem

jstl-1_0-fr-spec.pdf

출처 : Sun Microsystems