Oracle Video Server Administrator's Guide: UNIX
Release 2.1.7.3
A42271_4

Library

Product

Contents

Index

Chapter 6
Monitoring the Oracle Video Server

This chapter tells you how to monitor the Oracle Video Server (OVS) using log files and monitoring utilities. Topics covered in this chapter are:

Oracle Video Server Log Files

The OMN logger process (mnlogsrv) writes system and trace messages generated by the OVS components to the log file mzlog. mzlog is located in $ORACLE_HOME/vs21/log, and should be used to troubleshoot OVS and OMN components. For information on the messages written by mnlogsrv, refer to the Oracle Video Server Logger Messages guide.

Note

mnlogsrv is started by the script ovsstart. Should you need to change the
start-up option used by mnlogsrv, edit the ovsstart script. For information on ovsstart, refer to The Start-up Script in the "Operating the Oracle Video Server" chapter.

Example 1

This example starts mnlogsrv for all OVS components using the message file mzlm.dat in the directory $ORACLE_HOME/vs21/mesg and the log file mzlog in the directory $ORACLE_HOME/vs21/log:

% mnlogsrv -m $ORACLE_HOME/vs21/mesg/mzlm.dat \

-f $ORACLE_HOME/vs21/log/mzlog -l 7 &

Example 2

This example uses the -s command line option to route messages to the server console:

% mnlogsrv -m $ORACLE_HOME/vs21/mesg/mzlm.dat -s -l 7 &

For further information about mnlogsrv and the system logging functions that it provides, refer to mnlogsrv section of the "Oracle Video Server Components Reference" chapter later in this guide.

Monitoring Communication with mnping

mnping allows you to determine whether or not the OMN address server (mnaddrsrv) can be reached.

The syntax for mnping is:

mnping -g media_net_address

where:

-g

is the physical address of the OMN address server. The Media Net address is defined as the IP address and UDP port number assigned to the OVS at installation.

Example

This example uses OMN_ADDR as the argument to -g:

% mnping -g $OMN_ADDR

echo from 0xffffffff.1, ms=2

Obtaining a List of Registered Services

Once you have determined that you can contact mnaddrsrv, you can use the mnls utility to obtain a list of all services currently registered with it.

mnls takes no command line options or arguments.

The OMN_ADDR environment variable must contain the physical address that mnaddrsrv uses to communicate with the OVS processes established at installation.

Example

This example output shows nine services registered with the address server:

% mnls

Name                                    Address                                  Program ID

/mds                                    1.0.5.3                                  6d64730000000001  7.0

/ocs                                    1.0.4.1                                  0200000000000000  1.0

/mfsi                                  1.0.2.5                                  7e0b4a4d81f4b5b2  1.0

/mnsc                                  1.0.2.1                                  75d86072657bc692  1.0

/mznm                                  65535.65535.0.2                  0000000000000002  1.0

/mzsi                                  1.0.2.3                                  8bb95b5176c39dfc  2.0

/sctrl                                1.0.4.4                                  dc9f35727f768c74  1.0

/logserv                            1.0.3.1                                  0806070209040900  1.0

/vspump                              1.0.27.4                                8bb95b51b710cfb3  1.0

(9 entries)

Monitoring Oracle Media Net Process Server Queues

The OMN process server (mnprocsrv) receives service requests from clients that are intended for the stream service or other application services and routes these requests to a process which services the request. If several requests are made at once, a process server queue of requests may form as mnprocsrv attempts to direct requests to various processes.

For example, in large deployments of the OVS, several clients sometimes request a file at once. If your server has only one instance of the stream service (vsstrmsrv), the requests will form a process server queue as the one instance of vsstrmsrv can only respond to one request at a time.

In deployments where multiple instances of vsstrmsrv are running, mnprocsrv will balance the load and divide incoming requests among the available vsstrmsrv instances. Note that if several clients make requests simultaneously, even with multiple instances of vsstrmsrv, process server queues can form behind each instance; the queues will just be shorter and thus executed more rapidly.

You can monitor the status of the OMN process server queues with the mnps utility. This utility queries the OMN process server and displays information about its queues.

Syntax

mnps [-s] [-c] [-a] [-l] [queue_address...]

where:

-a

equivalent to specifying both -c and -s.

-c

shows additional information about pending calls in the specified queues.

-l

shows additional information about the specified queues and attached server instances.

-s

shows additional information about each server instance attached to the specified queues.

queue_address

shows information about the specified queues. If you omit the queue addresses, mnps shows information on all queues.

Example

This example shows sample output when using mnps:

% mnps -al 
QUEUE ADDR             SF ISTAT        CSTAT        QSTAT          NAME

1.0.2.5                   R  1/1/1/1      0/1/1/4      0/0/1/2ms      mzsi 
      INSTANCE ADDR        ST GETTM FWDTM CCNT DELAY  CALL ADDR

      1.0.6.1              W     2h    2h    4    1s  1.0.35.5 
QUEUE ADDR             SF ISTAT        CSTAT        QSTAT          NAME

1.0.2.5                   R  1/1/1/1      0/1/1/4      0/0/1/6ms      mfsi 
      INSTANCE ADDR        ST GETTM FWDTM CCNT DELAY  CALL ADDR

      1.0.28.1             W     2h    2h    4 832ms  1.0.35.2

Output

The mnps utility output contains information about:

queues
service instances
calls

Queue Information

This section lists the fields mnps may show for a queue:

Table 6-1: mnps fields displayed for a queue

QUEUE ADDR	the address of the queue as registered with the name server.
SF	the status of the queue. The first letter may be one of the following: R The queue is active P The queue is paused S The queue is stopped
NAME	the name of the queue as registered in the name server.
ICNT	the number of instances currently registered.
CCNT	the number of calls currently dispatched.
QCNT	the number of calls pending in the queue.

The mnps utility also shows these fields if you use the -l command-line option:

Table 6-2: mnps fields displayed when using -l.

ISTAT	the current, average, maximum concurrent, and total number of server instances registered.
CSTAT	the current, average, maximum concurrent, and the total number of calls dispatched.
QSTAT	the current, average, and maximum length of the queue, followed by the average time a call spends in the queue.

Instance Information

The section lists the fields mnps may show for an instance:

Table 6-3: mnps fields displayed for an instance.

INSTANCE ADDR	is the address of the server instance.
ST	is the state of the instance. This may be one of the following: P the instance is paused I the instance is initializing W the instance is waiting R the instance is running
RP	the instance is running and will be paused when it attempts to get the next request.
RS	the instance is running and will be stopped when it attempts to get the next request.
LAST	the last time there was activity from the instance. This is the lesser of GETTM and FWDTM.
CCNT	the number of calls dispatched to the instance.
DELAY	the average interval between the time when the call is forwarded to the instance and the next time it attempts to get a request. This statistic measures how fast the instance processes a call.
GETTM	the elapsed time since the instance called the process server to get the next request.
FWDTM	the elapsed time since the process server forwarded a request to the instance.
CALL ADDR	the address of the client who made the last call that was dispatched to the instance.