Switching on Logging

General discussion about the media server. Feature requests. Hints, tips and tricks.
User avatar
Posts: 1222
Joined: Fri Jul 08, 2005 1:19 pm
AV Hardware: TwonkyMedia AV UPnP Mediaserver (Marvell Kirkwood ARM Sheevaplug with Debian Squeeze).
2x Noxon V2 audio client
1x PS3 Slim 500GB Audio/Video UPnP client.
1x Sony VGF-CP1 Wireless Photoframe.
Location: UK

Switching on Logging

Post by mgillespie » Wed Dec 26, 2007 12:15 pm

If you are having problems and need support, for a speedy resolution, debugging information can be very helpful. The debug log file is saved, by default in the following locations:

V4: in the application directory, and called TwonkyMediaServer-log.txt
V5: in the system temp directory (/tmp on Linux/NAS and %temp% on Windows) called TwonkyMediaServer-log.txt

The debug information is disabled by default, but can be enabled in one of 2 ways.

1. Using the web interface.

In V4:
Open the web interface, select Troubleshooting from the list on the L/H side of the web interface.
Click the system areas you wish to debug. If you are unsure, tick everything.
Click Save Changes.

In V5:
Open the web interface, select Maintenance from the list on the L/H side of the web interface.
Check the box next to Logging
Click Save Changes.

2. Using the configuration file, or command line

If your problems are so severe, that the server fails to start, or you cannot access the web interface to use method 1. then you can switch on logging using the "-v" method. You need to determine the value that equates to the type of debugging you require, use the list at the end of this post. Once you know the value, this can be set in either the twonkyvision-mediaserver.ini file, under the #v v= option, or you can start the server from the commandline, using:

for Linux/Mac

Code: Select all

/twonkymediaserver -v #value#
for Windows

Code: Select all

C:\Program Files\TwonkyMedia\twonkymediaserver.exe -v #value#

Determining Debug level (Commandline and INI file methods only)

System messages 1
SSDP messages 2
Database related 4
HTTP related 8
client identification 16
UPnP eventing 32
XML parser 64
Plugin 128
Scan 256

If you want to get messages from several system components, just add their values.

-v 8 provides all http related messages
-v 7 provides all system messages, all ssdp messages and all database related messages
-v 511 provides all messages[/b]