Brukerveiledning Avbryt

Manage and monitor Adobe Connect server logs

  1. Adobe Connect User Guide
  2. Introduction
    1. What's New in Adobe Connect
    2. Adobe Connect meeting room basics
    3. Adobe Connect Capabilities in HTML Client
    4. Adobe Connect application for desktop
    5. Adobe Connect technical specifications and system requirements
    6. Keyboard shortcuts in Adobe Connect
  3. Adobe Connect Meeting
    1. Start, attend, and manage Adobe Connect meetings and sessions
    2. Host and Presenter Area in Adobe Connect
    3. Adobe Connect application for desktop
    4. Adobe Connect pre-meeting diagnostic test
    5. Adobe Connect Central home page
    6. Share content during a session
      1. Screen sharing in sessions
      2. Share pod
      3. Screen sharing on browser
      4. Share system audio
      5. Share a document
      6. Share a presentation
      7. Share a whiteboard
      8. Share files
      9. Share web URLs
    7. Update and manage Adobe Connect meetings
    8. View meeting reports and analytics data
    9. Work with Pods
      1. Pods in sessions
      2. Notes pod
      3. Chat pod
      4. Q & A pod
      5. Poll pod
      6. Quiz pod    
    10. Reactions in Adobe Connect room
    11. Accessibility features in Adobe Connect
    12. Create virtual meeting rooms and arrange layouts
    13. Breakout rooms in Adobe Connect meetings
    14. Manage meeting attendees in Adobe Connect
  4. Adobe Connect administration and maintenance
    1. Enabling Adobe Connect HTML client
    2. Enabling single sign-on in Adobe Connect
    3. Change the timeout period
    4. Configure audio providers for Universal Voice
    5. Create and import users and groups in Adobe Connect
    6. Enhance Adobe Connect account security
    7. Generate usage reports in Adobe Connect Central
    8. Administer and manage Adobe Connect accounts
    9. Manage users and groups
    10. Set permissions for library files and folders
    11. Back up user data, database, and settings of Adobe Connect server
    12. Build custom reports from the Adobe Connect database
    13. Maintain disk space and clean cache on an Adobe Connect server
    14. Manage and monitor Adobe Connect server logs
    15. Start and stop Adobe Connect services
  5. Adobe Connect Events
    1. About Adobe Connect Events
    2. Manage Adobe Connect Events
    3. Attend Adobe Connect Events
    4. Create and edit Adobe Connect Events
    5. Event analytics for webinars
  6. Adobe Connect Training and Seminars
    1. About Adobe Connect courses and curriculum for training
    2. Conduct trainings with Adobe Connect
    3. Create and manage seminars
    4. Create training courses in Adobe Connect
    5. Create and manage training curriculum in Adobe Connect
    6. About Virtual Classrooms in Adobe Connect
    7. Adobe Connect reports to monitor training features
    8. Participate in Adobe Connect training sessions and meetings
    9. Session dashboard
    10. Closed captioning in Adobe Connect
  7. Audio and video conferencing in Adobe Connect
    1. Audio in Adobe Connect meetings
    2. Record and play back Adobe Connect meetings
    3. Video in Adobe Connect meetings
      1. Pop out video from video pod
  8. Manage user content in Adobe Connect
    1. View reports and usage information about uploaded content
    2. Work with content in the Content library
    3. Work with Adobe Connect library files and folders

 

Read to configure logging on, know the log files of, and understand the log file format of an Adobe Connect server.

About log files

Use Adobe Connect log files to view information about events that occur during operation. You can use the information in the log files to create monitoring mechanisms and reports, and to troubleshoot problems. Log files provide information about user activities and server performance. For example, log files can indicate the reason a user was denied access when attempting to log in, or the reason that a telephony connection failed.

Adobe Connect log files are in the RootInstallationFolder\logs folder.

The Apache Tomcat log files are in the RootInstallation\logs\tomcat folder.

Configuring log files

Adobe Connect uses the Apache log4j tool. Use the file RootInstallationFolder\appserv\conf\log4j.xml to configure logging. For more information, see Log4j XML Configuration Primer.

To configure log appender, use the details provided at the DailyRollingFileAppender page.

Sample log file entry

The following sample entry from the access.log file includes a heading, a list of the fields used in the log entry, and the specific data for this log entry:

#Version: 1.0 
#Start-Date: 2010-10-30 17:09:24 PDT 
#Software: Adobe Connect Server 
#Date: 2010-04-30 
#Fields: date time x-comment x-module x-status x-severity x-category x-user x-access-request time-taken db-logical-io db-transaction-update-count                     
2006-10-30 18:12:50 Not logged in. PRINCIPAL NO_ACCESS_NO_LOGIN W A PUBLIC {cookie=breezxnb5pqusyshfgttt, ip=138.1.21.100} GET http://joeuser.adobe.com&mode=xml 0 20/5 0

The following table explains the sample entry:

Field

Data

Description

date

2010-10-30

The date on which the logged event occurred.

time

18:12:50

The time when the logged event occurred.

x-comment

Not logged in.

Indicates that a user was unable to log in to the application server.

x-module

PRINCIPAL

The event occurred in the Principal module in the application server.

x-status

NO_ACCESS_NO_LOGIN

Indicates that the user was unable to log in.

x-severity

W

Identifies the event severity as a warning (W).

x-category

A

Indicates that the event is an access (A) issue (appearing in the access.log file).

x-user

PUBLIC

The current user; in this case, an unidentified guest, or public user.

x-access-request

http://joeuser.adobe.com&mode=xml

Source of the request.

time-taken

0

No time was required to process this request.

db-logical-io

20/5

20 database reads were required and 5 rows of data were returned.

db-transaction-update-count

0

No database rows were updated in processing this request.

Log file format

The Adobe Connect log files use the W3C Extended Log File Format and you can use any text editor to read them. For information about AEM log files, see Configure AEM logging.

Log fields in the access.log and error.log files

Each log entry contains 11 log fields, which provide information about what type of event occurred, where it occurred, its severity, and other relevant data:

Field

Format

Description

date

YYYY/MM/DD

Date on which transaction completed.

time

HH:MM:SS

Local computer time at which transaction completed.

x-comment

String

Contains human-readable information about the log entry. This field is always output as the leftmost field.

x-module

String

Indicates where the error occurred.

x-status

String

Indicates what event occurred.

x-severity

Text (one character)

Indicates whether the logged event is critical (C), error (E), warning (W), or information (I).

x-category

Text (one character)

Indicates whether the log entry represents an access (A) or system (S) event.

x-user

String

Text that represents current user. Applicable only if x-category is access (A); otherwise field is set to a single hyphen (-) to denote an unused field.

x-access-request

String

Text that represents the access request. This text can be a URL or an API name with passed parameters. Applicable only if x-category is access (A); otherwise this field is set to a single hyphen (-) to denote an unused field.

time-taken

Number

Time required to process the request (in seconds). Applicable only if x-category is access (A); otherwise this field is set to a single hyphen (-) to denote an unused field.

db-logical-io

String

Number of database reads required to process the request and the number of rows returned in <reads>/<rows> format.

db-transaction-update-count

String

Number of rows updated in transactions while processing the requests. If the request uses more than one transaction, this value is the sum of all updates.

Module field entries

A module is a component of the server that manages some related set of operations. Each module belongs to either the application server or the meeting server. The x-module field indicates where the log event occurred:

Log Entry for x-module Field

Description

Server

ACCESS_KEY

Manages access keys.

Application server

ACCOUNT

Manages account operations.

Application server

ACL

Manages ACL-related operations.

Application server

AICC

Manages all AICC communication between server and content.

Application server

BUILDER

Performs SCO builds.

Application server

Client

Client methods.

Meeting server

CLUSTER

Manages all cluster-related operations.

Application server

CONSOLE

Manages all console-related operations.

Application server

Content

Share pod.

Meeting server

DB

Represents the database.

Application server

EVENT

Manages all event-related operations.

Application server

HOSTED_MANAGER

Manages system accounts (create, update, delete, settings, and so on).

Application server

MEETING

Manages all meeting-related operations.

Application server

Misc

Miscellaneous module.

Meeting server

NOTIFICATION

Manages all email operations.

Application server

PERMISSION

Manages all permission-related operations.

Application server

Poll

Poll pod.

Meeting server

PLATFORM_FRAMEWORK

Represents the platform framework.

Application server

PRINCIPAL

Manages all principal-related operations.

Application server

REPORT

Represents reports.

Application server

Room

Manages meeting room startup and shutdown.

Meeting server

RTMP

Represents RTMPHandler.

Application server

SCO

Manages all SCO-related operations.

Application server

SEARCH

Manages all search-related operations.

Application server

START_UP

Represents the startup component.

Application server

TELEPHONY

Manages all telephony-related operations.

Application server

TRACKING

Manages all transcript-related operations.

Application server

TRAINING

Manages all training-related operations.

Application server

Comment and status field entries

The x-comment field and the x-status field indicate what type of event occurred. The x-status field provides a code for each logged event. The x-comment field provides a human-readable description of each logged event.

The following table lists the status codes, the comment associated with each status code, and an explanation of each logged event:

Log Entry for x-status Field

Log Entry for x-comment Field

Description

ACCESS_DENIED

Client trying to access protected method. Access is denied. {1}

Logged when client attempts to access protected method.

BECAME_MASTER

Server {1} has been designated the master.

Logged when the scheduler quits and this server becomes the scheduler.

CLUSTER_CON_BROKEN

Server {1} unable to reach {2} on port {3} to perform cluster operations.

Logged when Adobe Connect is unable to reach another server in the cluster.

CLUSTER_FILE_TRANSFER_ERROR

Unable to transfer {1} from server {2}.

Logged when an error is thrown while transferring a file.

CONNECT

New client connecting: {1}

Logged when new client connects.

CONNECT_WHILE_GC

Connecting while the application is shutting down - forcing shutdown.

Logged when client attempts to connect while application is shutting down.

DB_CONNECTION_ERROR

Unable to connect to database {1}.

Logged when Adobe Connect cannot reach the database.

DB_CONNECTION_TIME_OUT

Timed out waiting for database connection.

Logged when database connection takes too long.

DB_VERSION_ERROR

Database {1} is incompatible with the current version of Adobe Connect.

Logged when the database is out-of-date.

DISCONNECT

A client is leaving. Details: {1}

Logged when client disconnects.

EXT_ERROR

External error thrown by a third party.

Logged when external code threw an error.

FMS_CON_BROKEN

Health check failed due to broken AMS service connection.

Logged when service connection is severed.

FMS_NOT_FOUND

Unable to connect to AMS at startup.

Logged when Adobe Connect is unable to establish the service connection at startup.

INTERNAL_ERROR

Internal error occurred.

Logged when internal error is thrown.

INVALID

-

Logged when invalid operation is attempted.

INVALID_DUPLICATE

Value {1} is a duplicate in the system.

Logged when value entered duplicates a value in the system.

INVALID_FORMAT

Field {1} of type {2} is invalid.

Value specified is invalid for this field.

INVALID_ILLEGAL_OPERATION

Illegal operation performed.

Requested operation is not legal.

INVALID_ILLEGAL_PARENT

-

Logged when an ACL has an invalid parent. For example, if folder A is inside folder B, folder B cannot be in folder A.

INVALID_MISSING

Field {1} of type {2} is missing.

Missing required value for this field.

INVALID_NO_SUCH_ITEM

Value {1} is an unknown in the system.

Requested item does not exist.

INVALID_RANGE

The specified value must be between {1} and {2}.

Logged when value entered is out of range.

INVALID_TELEPHONY_FIELD

Service provider did not validate the telephony authentication values.

Service provider unable to validate telephony account.

INVALID_VALUE_GTE

The specified value must be greater than or equal to {1}.

Logged when value entered is out of range.

INVALID_VALUE_LTE

The specified value must be less than or equal to {1}.

Logged when value entered is out of range.

KILLING_LONG_CONNECTION

Client has been in the room for 12 hours, disconnecting.

Logged when client connection is terminated after time limit is reached.

LICENSE_EXPIRED

Your license has expired and your account will be disabled on {1}. Please upload a new license file through the console manager to continue using Adobe Connect.

Logged when customer is using Adobe Connect during grace period and access is about to be cut off.

LICENSE_EXPIRY_WARNING

Your license will expire on {1}. Please upload a new license file through the console manager to continue using Adobe Connect.

Logged when license is 15 days or fewer from expiring.

MASTER_THREAD_TIMED_OUT

Master thread has not reported progress in {1} milliseconds.

Scheduler thread not running.

MEETING_BACKUP_END

Server {1} is no longer the backup for room {2}.

Meeting backup has ended.

MEETING_BACKUP_START

Server {1} is now the backup for room {2}.

Meeting backup has started.

MEETING_FAILOVER

Meeting {1} failed over to {2}.

Logged when a meeting fails over to this server.

MEETING_TMP_READ

Meeting template {1} read for room {2}.

Template read from meeting.

MEETING_TMP_WRITTEN

Meeting template {1} written to room {2}.

Template written to meeting.

NO_ACCESS_ACCOUNT_EXPIRED

Your account has expired.

Accessed account has expired.

NO_ACCESS_DENIED

Permission check failed.

Permission check error.

NO_ACCESS_LEARNER

No permission to take courses.

Must be a member of the learner group to take a course.

NO_ACCESS_LEARNING_PATH_BLOCKED

You have not fulfilled a prerequisite or preassessment.

Prerequisite or preassessment error.

NO_ACCESS_NO_EXTERNAL_USER_MODIFICATION

External users cannot be modified.

User is not allowed to modify LDAP users.

NO_ACCESS_NO_LICENSE_FILE

Your license file has not been uploaded.

License file not found.

NO_ACCESS_NO_LOGIN

Not logged in.

Error thrown when user not logged in.

NO_ACCESS_NO_QUOTA

A {1} quota error occurred for account {2} with limit {3}.

Out of quota.

NO_ACCESS_NO_RETRY

You have reached the max limit and cannot take the course again.

User has exceeded course retry limit.

NO_ACCESS_NO_SERVER

Server not available

Requested server is not available.

NO_ACCESS_NOT_AVAILABLE

The requested resource is unavailable.

Logged when the requested resource is not available.

NO_ACCESS_NOT_SECURE

SSL request made on a non-SSL server.

Secure request made on non-secure server.

NO_ACCESS_PASSWORD_EXPIRED

Your password has expired.

Logged when a user password has expired.

NO_ACCESS_PENDING_ACTIVATION

Your account has not been activated yet.

Account is not activated yet.

NO_ACCESS_PENDING_LICENSE

Your account activation is pending a license agreement.

Account not usable until license agreement is read.

NO_ACCESS_SCO_EXPIRED

The course you tried to access is no longer available.

Course end date is passed.

NO_ACCESS_SCO_NOT_STARTED

Course is not open yet.

Course start date is not reached.

NO_ACCESS_WRONG_ZONE

Content accessed from wrong zone.

Thrown when content or user accesses a server in the wrong zone.

NO_DATA

Permission check failed.

Query did not return any data.

NO_DISKSPACE

Health check failed due to lack of disk space.

Logged when the account runs out of disk space.

NOT_AVAILABLE

Requested resource is not available.

Error thrown when resource is not available.

OK

-

Request successfully processed.

OPERATION_SIZE_ERROR

Operation too large to complete.

Logged when operation can’t be completed because of size.

REQUEST_RETRY

Unable to process request. Please try again.

The request failed.

RESPONSE_ABORTED

Client that made request is not available to receive response.

Logged when user closes browser before server can send response back.

RTMP_SVC_BLOCKED

Adobe Connect service request blocked from {1} because the server has not fully started up yet.

Service connection requested from SCO but the server is still starting.

RTMP_SVC_CLOSED

Adobe Connect service connection closed for {1}.

Service connection closed for SCO.

RTMP_SVC_REQUEST

Adobe Connect service request received from {1}.

Service connection requested from SCO.

RTMP_SVC_START

Adobe Connect service connection established with {1}.

Service connection established with SCO.

SCRIPT_ERROR

Run-Time Script Error. Details: {1}

Logged when script error is detected.

SERVER_EXPIRED

Health check failed due to server expiry (expiry date={1}, current time={2}).

Logged when server does not pass health check before timing out.

SOME_ERRORS_TERMINATED

Some actions terminated with an error.

Logged when an error causes some actions to terminate.

START_UP_ERROR

Start up error: {1}.

Logged when an exception is thrown during startup.

START_UP_ERROR_UNKNOWN

Unable to start up server. Adobe Connect might already be running.

Logged when an unknown error is thrown during startup. JRUN prints the error.

TEL_CONNECTION_BROKEN

Telephony connection {1} was unexpectedly broken.

Logged when the telephony connection breaks.

TEL_CONNECTION_RECOVERY

Telephony connection {1} was reattached to conference {2}.

Logged when Adobe Connect recovers a connection to the conference again.

TEL_DOWNLOAD_FAILED

Unable to download {1} for archive {2}.

Logged when time-out occurs while downloading telephony audio files.

TOO_MUCH_DATA

Multiple rows unexpectedly returned.

Logged when an operation returns more data than expected.

UNKNOWN_TYPE

{1}

Logged when variable type is unknown.

Merk:

In the preceding table, {1} and {2} are variables that are replaced with a value in the log entry.

Severity field entries

The x-severity field indicates how serious a condition is, which helps you determine the appropriate response level.

Log Entry for x-severity

Meaning

Suggested Action

Example

C

Critical

Configure third- party monitoring tools to alert pagers when a log entry with this severity level occurs.

Can’t reach the database.

Can't start or end a process.

A failure is affecting the system.

E

Error

Configure third- party monitoring tools to send an email when a log entry with this severity level occurs.

Can't reach Adobe® Premiere®.

Conversion failed.

A failure is affecting a user or account, but not the whole system.

W

Warning

Generate and review periodic reports to identify possible operational and product improvements.

Disk or memory use has exceeded the specified threshold.

I

Info

Review log entries for auditing or RCA purposes.

Server started, stopped, or restarted.

Category field entries

The x-category field indicates whether the event relates to access issues (A) or general system issues (S). All entries of category A appear in the access.log file, and all entries of category S appear in the error.log file.

Log Entry for x-category field

Meaning

Description

A

access

Status code is related to access issues. Logged in access.log file.

S

system

Status code is related to general system issues. Logged in error.log file.

 Adobe

Få hjelp raskere og enklere

Ny bruker?