| Version 1 (modified by , 10 years ago) (diff) |
|---|
12 Troubleshooting (Contents?) (Main page)
In this section it explains how to formally submit a bug and provide debug logs so that this imformation is provided to the developers to action, it will explain how to use the trac ticket system to check and submit bugs for futher analisis.
- Only a registered Users can create Tickets. If you are not yet registered, you can register here Register
- The User must be logged in, You can Login here
- To achieve a faster and easier trouble shooting, we now offer the Ticketsytem. That way you can directly pinpoint your error to the competent Developer. In the next steps we will explain the new Ticketsystem.
- First, check the existing Tickets if the error has already been reported. This is done as follows.
- Click the button View Tickets or go directly to Active Tickets.
- Click on Search and tick the Tickets and begin the search.
- Here you can see the current active Tickets, if the same error is listed, you can attach your error message to the Ticket.
- Click the button View Tickets or go directly to Active Tickets.
12.1 Report a new Error (Contents?) (Main page)
- You have discovered a new bug and it has not been reported so you want to create a new ticket
- Click the button New Ticket
- The following fields need to be filled in.
- Summary:
- This is the displayed name of the reported error
- This is the displayed name of the reported error
- Description:
- Copy the link from the AAF Board (Community) where the posting was made.
- If no posting excists in the Community you can describe the error here.
- Component:
- Set the critaria suiting the error so the appropriate Developer is informed.
- Set the critaria suiting the error so the appropriate Developer is informed.
- Responsible:
- Here the ticket can explicitly be assigned to a specific Developer.
- Summary:
- The following fields can be filled in.
- Priority:
- Blocker - very urgent the ticket requires urgent attention.
- Critical - urgent other tickets or processes depend upon this error.
- Major - standard urgency (default).
- Minor - minor has a lot of time and is not so important.
- trivial - of no importance has even more time and is least important.
- Milestone:
- Default is standard if a more appropriate urgency is required it can be used.
- Tags
- This information is used by the Search - is usually not specified/required.
- Version:
- Is only applicable from version 2.0
- Observer:
- Only a Developer need to fill in this field if he wants to assign this ticket to a User, the user then sees it in My Tickets
- Priority:
- The following fields need to be filled in.
- To complete the ticket you click on the field create Ticket
12.2 Bug Update (Contents?) (Main page)
- You have discovered a bug and it has been reported but you have aditional information that may be helpfull to the developers to repair the problem or have aditional comments on the problem
- Click the Show Tickets > Active Tickets or Search Button and open the existing.
- The following fields must be filled in.
- Add comment:
- Here you can add more details to the error description.
- Here you can add more details to the error description.
- Add comment:
- To complete the ticket you click on Submit changes
- The following fields must be filled in.
12.3 Bug Resolve (Report error as completed) (Contents?) (Main page)
- You have discovered a previously reported bug is now fixed and want to close the ticket to inform the dev the bug is now fixed.
- Click on View Tickets > Active Tickets and open the respective ticket
- Scroll down to Action and set the field resolve as to fixed
- Click on the field _Submit changes
12.4 DebugLevel (Contents?) (Main page)
- In the Configuration file /mnt/config/titan.cfg you can set following debug levels
- Minimal: 10
- TopfieldVFD: 40
- Media Center: 50
- MenuList: 60
- Network Browser: 70
- Hard Disk: 80
- Screensaver: 90
- Tithek: 99
- Global: 100
- Ipkg: 130
- Imdb/imdbapi/TMDB: 133
- Eplayer: 150
- Tuning: 200
- Stream/Record/Softcam: 250
- Radio text: 270
- Subtitle: 300
- EPG: 400
- MediaDB: 777
- Mutexes: 900
- Function (in/out): 1000
- The default debug level = 10
12.5 Debug Logging (Contents?) (Main page)
Logging is a means of getting debug messages from the reciever for development and bug tracking purposes, this can be used to attach to a bug report or track ticked to assist the developer to find where a problem or bug may be traced from.
- You have several options for logging
- via Telnet:
- A Network connection is assential
- Client (Putty) configure the PC for Telnet session
- Open the Telnet session to the receiver
- Killall -9 rcS titan
- Set: (DebugLevel=)
- Titan /mnt/config/titan.cfg > /tmp/titan.error.log 2> & 1
- To terminate logging press (ctrl+z)
- Copy the log file (/tmp/titan.error.log) to your PC via ftp and send it as a ticket to the respective Developer
- Via RS232 (serial connection)
- A Serial connection must consist
- Configure (Putty) on the PC for Serial
- Open serial session to the receiver
- Then send it as a ticket to the respective Developer
- via Telnet:
- Using debug Images you can also query the kernel messages via a telnet session
- Network connection must exist
- Configure (Putty) on the PC for Serial
- Open serial session to the receiver
- cat/proc/kmsg > /tmp/titan.kernel.log 2>&1
- To terminate logging press (ctrl+z)
- Copy the log file (/tmp/titan.kernel.log) to your PC via ftp and send it as a ticket to the respective Developer
