![Teledyne Dock Server User Manual Download Page 179](http://html.mh-extra.com/html/teledyne/dock-server/dock-server_user-manual_1080796179.webp)
Revision 7.10
2/28/2012
When contacting glider support concerning possible erroneous Dock Server behavior,
always include the portion of console.log that covers the questionable behavior. The
following sections detail portions of the console.log file.
A.1.1 Dock Server Startups
This section describes the master log entries made during Dock Server startup. The
initial entries detail the Dock Server application’s version running on your server
machine. Please, always include the version information that begins with “glider” when
contacting Webb Glider Support concerning Dock Server issues. For example, this log
portion came from Dock Server version “glider 6.24 ALPHA_20060901_191924
20060901 19:19:24”. The entry following the version describes the last major bug fix
or enhancement made to this Dock Server version.
20060901T194640 ========================
20060901T194640 ++++++++++++++++++++++++ DOCK SERVER VERSION 4.7 RELEASE 4.7
IS STARTING UP...
20060901T194640 ++++++++++++++++++++++++ glider 6.24 ALPHA_20060901_191924 20060901
19:19:24
20060901T194640 ++++++++++++++++++++++++
20060901T194640 ++++++++++++++++++++++++ Last Fix/Enhancement: New glider detection method
glider name no longer in persistent store.
20060901T194640 ========================
When Dock Server starts up, it restores the state of all Dock Server scripts associated
with managed gliders. Each time a script’s status changes, Dock Server saves the
change in a file, gliderState.xml, associated with the script’s glider. During a restart, this
file allows Dock Server to resume each script at the point left off due to the last Dock
Server shutdown.
For example upon start up, the following log entries show the scripts on gliders ru12 and
sim015 now UNLOADED – i.e., no script is currently associated with these gliders.
And, the script, /opt/gmc/factoryscripts/glmpc.xml, is RUNNING on glider sim012 and
has resumed at the state, “waitForDisconnect” (refer to Appendix C for a description of
scripts and their states).
Note that the glider, “unknown”, has no script associated with it (i.e., UNLOADED).
Since upon initial contact, Dock Server treats all gliders as the glider “unknown” until
Page 179 of 228