Changes between Version 2 and Version 3 of ReportingABug


Ignore:
Timestamp:
Oct 21, 2013 1:35:50 PM (6 years ago)
Author:
killyourtv
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReportingABug

    v2 v3  
    1010
    1111
    12 * If you're experiencing very high RAM or CPU usage
     12* If you're experiencing very high RAM or CPU usage:
    1313
    1414  1. Make sure you're using a recommended version of Java. Oracle Java Version 7, OpenJDK 7, or IcedTea7 are recommended for most systems. On the Raspberry Pi, use Oracle 8 Early Access. PowerPC users should try IBM SDK 7.
    1515
    16   2. If you're running [http://plugins.i2p plugins] such as Seedless or I2P-Bote, try disabling them to see if the problem goes away.
     16  2. If you're running [http://plugins.i2p plugins] such as Seedless or I2P-Bote, try disabling them to see if the problem goes away. In some cases you may need to restart I2P after disabling the plugin.
     17
     18  3. If I2P is crashing/restarting, [http://127.0.0.1:7657 check the logs] to see if you're having OOM (Out of Memory) issues. By default, I2P is limited to using 128 MB of RAM. If you have a high bandwidth router or are running multiple plugins you may need to allocate more RAM to I2P. See [[ChangingRAMLimits]].
    1719   
    18 * If your bug is other than problems in third-party plugins (new features, improvements, etc.), follow the steps below.
     20* If your bug is for something other than a problem in third-party plugins (new features, improvements, etc.), follow the steps below.
    1921
    2022= Steps for Bug Report Submission =
    2123
    2224
    23 1. [/search?q=&noquickjump=1&ticket=on Search for existing bug reports], in order not to submit a duplicated one.
     251. [/search?q=&noquickjump=1&ticket=on Search for existing bug reports], in order not to submit a ticket for a problem that we already know about.
    2426
    25272.
     
    4850
    49511. If you can access the router console (usually at http://127.0.0.1:7657), go to the [http://127.0.0.1:7657/configservice service tab]. In the '''Debugging''' section will be a ''Dump Threads'' button. Click it.
     52
    50532. The thread dump will be visible in the [http://127.0.0.1:7657/logs.jsp#servicelogs wrapper.log file]. The location of `wrapper.log` will also be listed on the [http://127.0.0.1:7657/logs router console's logs page].
     54
    51553. Copy & paste the thread dump to http://pastethis.i2p, noting the URL in the ticket, or attach a file with the thread dump to the ticket.
    5256