Mlbviewer writes a number of log files to assist in debugging. If an error is encountered in media request, it is helpful to save one of these files for reporting the issue.
All log files will be found in ~/.mlb directory.
| Log File | Purpose |
|---|---|
| cookie | This is the cookie received from mlb.com authentication and workflow pages. It is generally not helpful for debugging but necessary for normal operation. |
| cookielog | Contains helpful information about cookie morsels read from file, received from network, and written to file. This is very useful for debugging Sign-On Restriction Errors. |
| fmscloud.xml | For SD mode requests (non-NexDef), the first media URL is to an FMS (Flash Media Server.) This log contains the response from the FMS request which contains a base URL and URL suffixes for the different media speeds. Errors generally don't occur in this step but this may be contain useful information if an error does occur here. |
| innwin.log | Log file for parsing innings listing with start times for each half innings. Currently, this file is not used and is expected to be empty. |
| log | Main log file. Used by many classes in MLBviewer library and thus contains information from various steps of mlbviewer work flow. |
| sessionkey | Session key is like a cookie morsel that connects a computer to a session. For as long as the session key is valid (a few hours), this session key is re-used to prevent Sign-On Restriction Errors. The life cycle of the sessionkey can be observed in the cookielog. |
| successful-1.xml | Media location occurs in two steps. The first step is a request for all media related to a specific game. The contents of this file is the most recent successful response to this generic media request. |
| successful-2.xml | The second step in media location is a request for a specific media by content-id from the list of all media in the first request. The contents of this file is the most recent successful response for this specific media request. |
| unsuccessful-1.xml | If the first generic (all media) request returns an error, the contents of the error response are written to this file. |
| unsuccessful-2.xml | If the second specific media request returns an error, the contents of the error response are written to this file. More often, errors such as blackouts or media not found errors occur in this second request. Use "ls -lrt" command to find the most recent unsuccessful-#.xml file when a media request error occurs. The file at the bottom of the "ls -lrt" command output is the most recent. |
XML response files (files ending in ".xml") can be formatted in a more user-friendly manner using the mediaxml.py script in the test subdirectory in the mlbviewer program directory. For example, if the mlbviewer program directory is mlbviewer2014, to parse the unsuccessful-1.xml file, use the command,
mlbviewer2014/test/mediaxml.py ~/.mlb/unsuccessful-1.xml
