Changes between Version 10 and Version 11 of pl/Troubleshooting


Ignore:
Timestamp:
Jan 22, 2019 2:44:09 AM (2 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • pl/Troubleshooting

    v10 v11  
     1[[TranslatedPages]] 
     2---- 
     3'''12  Troubleshooting ''' [=#point12] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page]) 
     4---- 
     5 
     6== Troubleshooting Contents == 
     7  
     8This section 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. 
     9 
     10* Only a __registered__ Users__ can create __Tickets__. If you are not yet registered, you can register here __[http://sbnc.dyndns.tv/trac/register Register]__ 
     11* The __User__ must be logged in, You can __[http://sbnc.dyndns.tv/trac/login Login]__ here 
     12* 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__.[[Br]] 
     13* First, check the existing __ Tickets__ if the error has already been reported. This is done as follows. [[Br]] 
     14  * Click the button __[http://sbnc.dyndns.tv/trac/report View Tickets]__ or go directly to __[http://sbnc.dyndns.tv/trac/report/1 Active Tickets]__.[[br]] 
     15  * Click on __[http://sbnc.dyndns.tv/trac/search Search]__ and tick the __Tickets__ and begin the search. 
     16  * Here you can see the current __active Tickets__, if the same error is listed, you can attach your error message to the __Ticket__.[[Br]] 
     17 
     18 
     19 please select an item below for more information. 
     20 
     21 * ([#point12.1 12.1 Bug Reporting]) 
     22 * ([#point12.2 12.2 Bug Update]) 
     23 * ([#point12.3 12.3 Bug Resolve]) 
     24 * ([#point12.4 12.4 Debuglevel]) 
     25 * ([#point12.5 12.5 Debug logging]) 
     26[[br]] 
     27 
     28---- 
     29'''12.1 Report a new Error''' [=#point12.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page]) 
     30---- 
     31 
     32* You have discovered a new bug and it has not been reported so you want to create a new ticket[[br]] 
     33* Click the button __[http://sbnc.dyndns.tv/trac/newticket New Ticket]__[[br]] 
     34  * The following fields __need__ to be filled in.[[Br]] 
     35    * __Summary:__ 
     36      - This is the __displayed name__ of the reported error[[br]] 
     37    * __Description:__ 
     38      - Copy the link from the __[http://www.aaf-digital.info/forum/forum.php AAF Board (Community)]__ where the posting was made. 
     39      - If no posting excists in the __Community__ you can describe the error here.[[br]] 
     40    * __Component:__ 
     41      - Set the critaria suiting the error so the appropriate __Developer__ is informed.[[br]] 
     42    * __Responsible:__ 
     43      - Here the ticket can explicitly be assigned to a specific __Developer__. 
     44  * The following fields can be __filled in__. [[Br]] 
     45    * __Priority:__ 
     46      - Blocker - __very urgent__ the __ticket__ requires urgent attention. 
     47      - Critical - __urgent__ other tickets or processes depend upon this error. 
     48      - Major - __standard__ urgency (__default__). 
     49      - Minor - __minor__ has a lot of time and __is not so important__. 
     50      - trivial - __of no importance__ has even more time and __is least__ important. 
     51    * __Milestone:__ 
     52      - Default is __standard__ if a more appropriate urgency is required it can be used. 
     53    * __Tags__ 
     54      - This information is used by the __[http://sbnc.dyndns.tv/trac/search Search]__ - is usually not specified/required. 
     55    * __Version:__ 
     56      - Is only applicable from version __2.0__ 
     57    * __Observer:__ 
     58      - 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 __[http://sbnc.dyndns.tv/trac/report/7 My Tickets] __ 
     59 
     60  * To complete the ticket you click on the field __create Ticket__ 
     61[[br]] 
     62[#point12 Top of Page] 
     63---- 
     64'''12.2 Bug Update''' [=#point12.2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page]) 
     65---- 
     66 
     67* 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[[br]] 
     68* Click the __[http://sbnc.dyndns.tv/trac/report Show Tickets]__ > __[http://sbnc.dyndns.tv/trac/report/1 Active Tickets]__ or __ [http://sbnc.dyndns.tv/trac/search Search]__ Button and __open__ the existing.[[br]] 
     69  * The following fields __must__ be filled in.[[Br]] 
     70    * __Add comment__: 
     71      - Here you can add more details to the error description.[[br]] 
     72  * To complete the ticket you click on __Submit changes__ 
     73[[br]] 
     74[#point12 Top of Page] 
     75---- 
     76'''12.3 Bug Resolve (Report error as completed)''' [=#point12.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page]) 
     77---- 
     78 
     79 
     80* 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.[[br]] 
     81* Click on __[http://sbnc.dyndns.tv/trac/report View Tickets]__ > __[http://sbnc.dyndns.tv/trac/report/1 Active Tickets]__ and open the respective ticket[[br]] 
     82  * Scroll down to Action and set the field __resolve as__ to __fixed__ 
     83  * Click on the field _Submit changes__ 
     84[[br]] 
     85[#point12 Top of Page] 
     86---- 
     87'''12.4 DebugLevel''' [=#point12.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page]) 
     88---- 
     89 
     90 
     91* In the Configuration file /mnt/config/titan.cfg you can set following debug levels 
     92  * Minimal: 10 
     93  * TopfieldVFD: 40 
     94  * Media Center: 50 
     95  * MenuList: 60 
     96  * Network Browser: 70 
     97  * Hard Disk: 80 
     98  * Screensaver: 90 
     99  * Tithek: 99 
     100  * Global: 100 
     101  * Ipkg: 130 
     102  * Imdb/imdbapi/TMDB: 133 
     103  * Eplayer: 150 
     104  * Tuning: 200 
     105  * Stream/Record/Softcam: 250 
     106  * Radio text: 270 
     107  * Subtitle: 300 
     108  * EPG: 400 
     109  * MediaDB: 777 
     110  * Mutexes: 900 
     111  * Function (in/out): 1000 
     112 
     113* The default debug level = 10 
     114[[br]] 
     115[#point12 Top of Page] 
     116---- 
     117'''12.5 Debug Logging''' [=#point12.5] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page]) 
     118---- 
     119 
     120Logging 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. 
     121 
     122 
     123* You have several options for logging 
     124 * via Telnet: 
     125  * A Network connection is assential 
     126  * Client ([http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty]) configure the PC for Telnet session 
     127  * Open the Telnet session to the receiver 
     128  * killall -9 rcS titan 
     129  * Set: ([#point112.4 DebugLevel=]) 
     130  * titan /mnt/config/titan.cfg > /tmp/titan.error.log 2>&1 
     131  * To terminate logging press (ctrl+z) 
     132  * Copy the log file (/tmp/titan.error.log) to your PC via ftp and send it as a ticket to the respective Developer 
     133 * Via RS232 (serial connection) 
     134  * A Serial connection must consist 
     135  * Configure ([http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty]) on the PC for Serial 
     136  * Open serial session to the receiver 
     137  * Then send it as a ticket to the respective Developer 
     138 
     139* Using debug Images you can also query the kernel messages via a telnet session 
     140  * Network connection must exist 
     141  * Configure ([http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty]) on the PC for Serial 
     142  * Open serial session to the receiver 
     143  * cat/proc/kmsg > /tmp/titan.kernel.log 2>&1 
     144  * To terminate logging press (ctrl+z) 
     145  * Copy the log file (/tmp/titan.kernel.log) to your PC via ftp and send it as a ticket to the respective Developer 
     146[[br]] 
     147[#point12 Top of Page]