Elluminate Live! Log Files

Transcription

1 Elluminate Live! Lg Files Fr Elluminate Live! Server Administratrs, the Elluminate Live! Lg files can help yu determine what transpired in a given sessin. This dcument prvides an verview f sme f the keys lg entries t lk fr. The elive.lg file will be lcated n yur Elluminate Live! server. By default, it will be hused n the /ElluminateLive/server6_0/lgs/ directry thugh it can be mved. Launch Lg The first example (See Example 1.1) shws the launch f the Elluminate Live! service n start up. Example :05:18 main.wrappersimpleappmain: DebugFlag.setEnabled: lg.lad=on :05:18 main.wrappersimpleappmain: DebugFlag.setEnabled: lg.launch=on :05:18 main.wrappersimpleappmain: DebugFlag.setEnabled: lg.access=on :05:18 Elluminate Live! Academic Editin (Elluminate Live! Dem License, 2 users) :05:18 Elluminate Live! Scheduler 6.0 applicatinsharing attendance audi breakutrms calculatr chair directmessaging framewrk hand multimedia participantinf plling quiz recrder starttime vide webtur whitebard Crimsn JDOM b8 Cpyright (c) by Elluminate Inc., All rights reserved.

2 Date/Time Stamp Prvides the date and time f entry Versin Infrmatin Prvides the versin infrmatin and license amunt Scheduler Shws what JAR files that are laded and their versin. These will vary depending n which editin and versin f Elluminate Live! yu are using. Nte: The first three lines are debugging infrmatin that has been placed in the cde. Yu may disregard this infrmatin. The furth line prvides the versin and the license file. The fifth line thrugh the secnd last prvides the scheduler versin, the JAR file names and JAR file versins. The last line is the cpyright infrmatin. Template Files The secnd example (See Example 1.2) shws a template file lading. Yu will need t mve the tmpl file t the examples (r temprary) flder t make the changes. DO NOT make changes t the tmpl file in a live directry as it may disrupt the sessin assciated with the file. Once yu have made changes t the file, mve it back t the live directry and yu may either wait fr the service t re-lad the template r yu may re-start the service which will frce the relad f the templates. Example :05:18 Lading template 'C:\Prgram Files\ElluminateLive\server6_0\sessins\ELMDefault.tmpl' :05:19 Lading template 'C:\Prgram Files\ElluminateLive\server6_0\sessins\Default.tmpl' Template Lad: Date/time f lad Template lcatin and name Whenever yu make changes t these template files, yu shuld check the lg t ensure that n errrs were thrwn. If there was an errr with the lading f a specific template file, yu will see the line number f the template file that is causing the prblem. When launching int a rm yu may see a 406 errr unexpected respnse frm server applet this may be due t the tmpl file either nt being present, changes that have nt been picked up, etc. Yu may need t either re-lad the template file r re-start the service.

3 Launching a Sessin Tw steps ccur when a sessin is launched: 1. The sessin will launch (if nt already running See Example 1.3) and the user will be lgged int the sessin. 2. The user will be lgged int the newly launched sessin. Example :05:45 Sessin Scheduler: Launching unscheduled sessin 'Meeting meeting1' (Meeting meeting1) :05:45 Meeting meeting1: Access GRANTED - participant// Launching a sessin: Date/time f sessin launch Sessin name Access Granted fr each participants and their user name, IP address. Shutting Dwn a Sessin When the last persn lgs ut f a sessin the server will Hld the rm in state fr 5 minutes (r ther, if re-defined in the grace perid in the tmpl file). After that, the scheduler will shut dwn the sessin (See Example 1.4). Example :45:29 Shutting dwn unscheduled sessin 'Meeting meeting1' (Meeting meeting1) Shutting dwn a sessin: Date/time f sessin shutdwn Sessin name

4 Adding Infrmatin t the Lg File In the elive.cm file (fund at /ElluminateLive/server6_0/ - See Example 1.5) there are parameters set fr the lg file utput. These parameters that can be added t get a better picture f what is happening in a sessin. Example 1.5 <lg file="c:\prgram Files\ElluminateLive\server6_0\lg\elive.lg" size="250000"> lg.lad lg.launch lg.access </lg> There are quite a number f messages that can be added if yu need mre infrmatin. These can be added t the lg sectin f the elive.cnf file. Here are the mst cmmn: lg.memry jinx.hangup Causes the server t issue JVM heap memry cnsumptin reprts apprximately nce per hur Causes the server t issue messages when clients are intentinally discnnected frm the server either by leaving the rm, being frced ut by a mderatr, pushed ut via the admin cnsle tl, server shutdwn, etc. jinx.discnnectin Causes the server t issue messages when clients discnnect frm the because f I/O prblems (timed ut n read, netwrk link drpped, etc.) Any changes dne t the cnf file requires a restart f the Elluminate Live! Server service If yu need additinal infrmatin infrmatin included in the file, please cntact Elluminate s Technical Services Team at supprt@elluminate.cm t determine if there is are additinal parameters that can be set.

5 Interpreting Discnnect Lgs There are a few reasns fr a participant exiting a sessin. Als, there are a few different types f discnnects frm a sessin. The mst cmmn is a remte discnnect (See Example 1.6) which means the user discnnected themselves frm the sessin. Example :40:29 Meeting meeting1.netrecv('participant',6): NetwrkTransceiver.run: User participant(/ ) has been discnnected remtely. Discnnect infrmatin: User date/time f discnnect Sessin name Cde Call (NetwrkTransceiver.run:) User name User IP address Reasn fr discnnect Discnnect reasns: User has been discnnected remtely: User discnnected manually frm the sessin r lst their Internet cnnectin. Input exceptin - java.net.scketexceptin: Cnnectin reset This is the result f a TCP cnnectin RESET request. It mst likely came frm the client system, prxy, firewall r ruter in the path frm the client system t the server. This culd be as the result f a netwrk errr seen by the client system causing its TCP/IP stack t believe the cnnectin is n lnger capable f peratin and thus resetting the cnnectin. Input exceptin - java.i.eofexcept The netwrk cnnectin has likely been drpped and pending input (read) peratin fr that client then takes this exceptin. This nt an errr in the sftware, just hw the discnnectin is seen thrugh the Java netwrk and I/O services. Input exceptin - java.net.sckettimeutexceptin: Read timed ut N watch-dg I/O was received frm the client system prir t the watch-dg timer expiring. The cnnectin was drpped by the server as it is believed the client is n lnger respnding. This culd be caused by netwrk discnnects r the client system hanging, lping, crashing, be rebted. If the client dismisses the applicatin n the desktp system, that wuld nrmally be seen by the server and wuld be listed as a "has been discnnected remtely" lg entry. User has been discnnected lcally (cmmand) Either the sessin shutdwn and the client was remved as part f shutdwn, r the participant was ejected frm the rm.