The RealServer Access Log (pnaccess.log) displays the number of clients that are connected to your server, the names of the client machines, the clips they listened to, the times of day they connected, and errors that were generated by RealServer. This information can give you an idea of who your audience is and which clips are popular.
Two configuration parameters, LoggingStyle and StatsMask, control what is captured in the Access Log.
If StatsMask is configured to gather statistics type 3, note that the Access Log file size will grow rapidly. If you configure StatsMask to collect this information, be sure to review the log file frequently, as described in "Log File Maintenance."
For more information on these settings, see Configuring and Maintaining RealServer.
View the Access Log File by opening the pnaccess.log or pnaccess file in a word processor or text editor.
The format for an Access Log record is:
<IP_address> <- -> <timestamp> "<GET
filename> <protocol>" <return_code> <bytes_sent>
[<client_ID_string>] [<client_unique_id>] <stat1> <stat2>
<stat3> <file_size> <file_time> <sent_time> <resends>
<failed_resends>
where:
<IP_address> |
IP address of Client. For example:
|
<- -> |
Two hyphens for compatibility with Web server log formats. |
<timestamp> |
Time that Client accessed the file in the format
where TZ is the time zone expressed as the number of hours relative to the Coordinated Universal Time (Greenwich, England). For example:
|
<GET filename> |
File requested by Client. Filename is the relative path to the Server's BasePath value. For example:
|
<protocol> |
Protocol and version used by Client in the format: PNA<type>/<number> where:<type> is T for TCP connections, H
for PNAviaHTTP, M for Multicast, and blank for UDP connections. Type appears only if the LoggingStyle configuration parameter is set to 1. <number> is the PN protocol number.
For example:PNA/8 PNAT/8 |
<return_code> |
Return code using HTTP standard error codes. |
<bytes_sent> |
Number of bytes transferred to Client during play. This field may be lower than the total size of the media file, indicating partial playback of the file. If this field is consistently low for some or all media files, it may mean that RealPlayers are able to connect to your server, but are unable to play files. Check your system Error Logs for messages relating to network system errors. |
[<client_ID_string>] |
Client ID string. This field is not part of the common Web server Access
Log format; it is text sent by the Client that describes the version and
type of Player being used. RealAudio Player versions 2 and 3 use the following
format: where:
RealAudio Player version 1 uses an ID string in the following format:
The field descriptions are the same as the newer format. For example:
If the client is a splitter, the Client ID field contains the following string:
|
<client-unique_id> |
Unique ID generated during RealPlayer installation that enables you to track details for individual players, allowing you to enhance the quality of the captured statistics. This entry is displayed only when LoggingStyle is set to 2. This will also display the new entries for LoggingStyle 1. |
<stat1> |
Connection statistics sent by the Client when it completes playing a
clip. These optional fields are sent only when the StatsMask configuration
parameter is set to 1 or 3. The Player user can also set a preference value
to block sending connection statistics. When the Client blocks connection
statistics, when the Client is a splitter, or when StatsMask is set to 0,
the The connection statistics field starts with the string "Stat1" and has the following format:
where:
For example: |
<stat2> |
Extended connection statistics sent by the Player when it completes playing a clip. These statistics are supported by all Players. These optional fields are sent only when the StatsMask configuration
parameter is set to 2 or 3. The Player user can also set a preference value
to block sending connection statistics. When the Client blocks connection
statistics, when the Client is a splitter, or when StatsMask is set to 0,
the The extended connection statistics field starts with the string "Stat2" and has the following format:
where:
For example:
|
<stat3> |
Statistics sent by the client which capture behavior observed by a data renderer. These statistics are only sent to the RealServer when the RealPlayer preferences are set to send statistics. Moreover, these fields are only requested by the RealServer when the StatsMask configuration setting is set to 4, 5, 6, or 7. Pipe '|' characters are used as field separators in the Stat3 record. Multiple Stat3 records are delimited by a semi-colon character (;).
where: For example: Note: a Stat3 record is not generated at either the initial play or natural end of .rm file stream. This information is directly derived from the main section of the Access Log. Data Definitions Within the
where: For example:
where: For example:
where:
For example:
|
The following example shows three Access Log entries:
172.16.2.139 - - [04/Nov/1996:14:45:57 -0700] "GET newclips/realcool.ra
PNA/8" 200 590976 [Win95_4.0_3.0.0.19_play32_PN01_EN_586] [Stat1: 2592
0 0 0 0 28.8][Stat2: 15234 15552 0 0 0 0 0 0 0 0 220 28.8] 590976 310 310
0 0 172.16.2.139 - - [04/Nov/1996:14:53:49 -0700] "GET classic/xyz144.ra
PNAT/8" 200 4 [Win95_4.0_3.0.0.19_play32_PN01_EN_586] [UNKNOWN] 5580
5 0 0 0 172.16.2.139 - - [04/Nov/1996:16:01:10 -0700] "GET speeches/carter.ra
PNA/5" 200 55680 [Win1.0.0] [Stat1: 229 0 0 0 0] 630020 630 55 0 0