To turn the ACR debug logs on and off in ACR
Example:
http://10.x.x.x:8080/log?level=DEBUG (turns debug on)
http://10.x.x.x:8080/log?level=INFO (turns debug off)
Logs are located in:
D:\Program Files\Avaya\ContactRecorder\logs
To turn the ACR debug logs on and off in ACR
Example:
http://10.x.x.x:8080/log?level=DEBUG (turns debug on)
http://10.x.x.x:8080/log?level=INFO (turns debug off)
Logs are located in:
D:\Program Files\Avaya\ContactRecorder\logs
Generally you can view the fileserver Utility server webpage, and can download the log as a text file and use via Notepad etc.
However you can also SSH to the Utility server via the ‘admin’ login, and run the following commands;
tail –f /var/log/httpd/access_log (Shows last few lines of the handsets access the log and entries in realtime.)
cat /var/log/httpd/access_log | grep <VARIABLE> (will show you all entries in the log for the variable entered)
Variables:
IP address (of handset)
Extension
Handset type
GET or PUT (for handset backups)
Filename (for specific file downloads – eg 46xxsettings.txt etc)
HTTP command results (eg “200” = OK, “404” = file not found etc)
For example handset has an IP address of 10.10.10.10 you would use the following;
tail -f /var/log/httpd/access_log| grep -i 10.10.10.10
dadmin@S8300> dhelp logc logv [OPTIONS]... [LOGS...] [-t TIME] [[-a]FILTERS]... logc [OPTIONS]... [LOGS...] [-t TIME] [[-a]FILTERS]... logw [OPTIONS]... [LOG] [[-a]FILTERS]... Merges and displays the various log files in the system. Logv edits (vi) the results, while logc sends (cats) them to the standard output. Logw watches the single specified logfile for changes applying the specified filters. OPTIONS to modify command operation: HELP -? produce this message -v show the version of the command OUTPUT OPERATION -c cat the log instead (set if called with name logc) -ls list the names and sizes of log files -w watch the log instead (set if called with name logw) OUTPUT FORMAT -b remove blank lines -d augment timestamps with time delta between resulting entries --dsep[N] separator line will be output for times greater than N (1) seconds -r reverse order (latest entry is shown first) -s strip off the timestamp (and other header) on each line -st strip off other header (leaving timestamp) on each line -sd strip off other header (leaving timestamp) on each line, and format the timestamp yyyy/mm/dd HH:MM:SS VIEW OPERATIONS --views List the predefined log views. A view specifies a log type as well as other selection parameters. --view VIEWNAME Display the log using the parameters associated with VIEWNAME LOG FILE OPERATIONS -ld dir look for log files in directory dir (instead of default directory) -lf file assume file is a log file (multiple -lf's can be given) -clear clear the log files (only logmanager files) LOGS all all possible lm Logmanager debug trace lxboot Operating system boot messages lxsys Linux syslog lxsec Linux access security log lxwtmp Linux login/logout/reboot log lxxfer Linux file transfer log wd Watchdog logs cmds Platform command history log httperr HTTP/web server error log httpssl HTTP/web SSL request log httpaccess HTTP/web access log cmrestart Communication Manager Restart log filesync Communication Manager file synchronizations multiple logs can be given--logs are merged and sorted by time SELECTION FILTERS -l only the latest file in a log searched (default is all) -t TIME filter for a particular date/time yyyy[mm[dd:[HH[MM[SS[mmm]]]]]] time pattern yyyy[mm[dd:[HH[MM[SS[mmm]]]]]]-yyyy[mm[dd:[HH[MM[SS[mmm]]]]]] time range today yesterday multiple time patterns/ranges can be given--entries that match any time will be output app-pat filter events for particular application/process (e.g. capro). An arbitrary string which does not match any LOG name can be given. Unless -g is specified, app-pat must be found at beginning of a :-separated field or preceeded by a [ or space. Multiple app-pats can be given--log entries that match any app-pat will be output unless -a is also specified. -a app-pats following a -a are applied to the output of those preceding the -a. App-pats following -a are considered to be grep patterns. -g assume app-pat filters are grep patterns instead of appnames -i assume app-pat filters are grep patterns and ignore case of letters ogc - cat logfiles logc -? logc --views - List the predefined log views logc --view ipevt - IP events (interfaces up/down; telephone/endpoint registration / unregistration logc --view bashhist - Platform bash command history log logc --view mst - Communication Manager's raw Message Sequence Trace (MST) log logc --view mt - Communication Manager's processed Message Tracer (MDF) logc --view msa - Communication Manager's interpreted Message Tracer (MTA) logc --view hwerr - Communication Manager's hardware error and alarm events logc --view sat - Communication Manager's SAT events logc --view swerr - Communication Manager's software events logc -t today --view mta logc -t yesterday --view mta logc -t 20060216 --view mta logc -t 20060216 MST logc cmds -t 20061208-20061209 logc -t 20061114:220130853-20061115:065455306 > bulk_lofiles logc -t 20060112:2355 --view mst (yyyy[mm[dd:[HH[MM[SS[mmm]]]]]]) logc -t 20061114:220130853-20061115:065455306 | grep -i mst | logmst > /var/home/defty/MST_12_09_1.M;
For example to view the IPEVT system log via shell using a super user account
“logc –view ipevt” or “sudo logc –view ipevt”