|
| 1 | +<!DOCTYPE html> |
| 2 | +<html lang="en"> |
| 3 | +<head> |
| 4 | + <meta charset="utf-8"> |
| 5 | + <meta http-equiv="X-UA-Compatible" content="IE=edge"> |
| 6 | + <meta name="viewport" content="width=device-width, initial-scale=1"> |
| 7 | + <script src="../js/documentation.js" type="application/javascript"></script> |
| 8 | + <link href="../css/light.css" rel="stylesheet"> |
| 9 | + <link href="../bower_components/bootstrap/dist/css/bootstrap.min.css" rel="stylesheet"> |
| 10 | + <script src="../bower_components/jquery/dist/jquery.min.js"></script> |
| 11 | + <script src="../bower_components/bootstrap/dist/js/bootstrap.min.js"></script> |
| 12 | + <style> |
| 13 | + #pageTitle::before { |
| 14 | + content: "Troubleshooting Tools"; |
| 15 | + } |
| 16 | + </style> |
| 17 | + <link href="../css/documentation.css" rel="stylesheet"> |
| 18 | + <link href="../documentation-favicon.ico" rel="shortcut icon" type="image/png"> |
| 19 | + <title>Troubleshooting Tools</title> |
| 20 | +</head> |
| 21 | +<body> |
| 22 | +<div w3-include-html="/documentation/pageHeader.html" id="pageHeader"></div> |
| 23 | +<div class="Layout"> |
| 24 | +<div class="Layout-sidebar" w3-include-html="/documentation/sidebar.html" id="sidebar"></div> |
| 25 | +<div class="Layout-main markdown-body" id="mainContents"> |
| 26 | + |
| 27 | +<p> |
| 28 | +This pages lists some tools and techniques to aid in troubleshooting Allsky. |
| 29 | +If you have any other tools, please submit a GitHub Discussion and let the |
| 30 | +Allsky developers know. |
| 31 | +</p> |
| 32 | + |
| 33 | + |
| 34 | +<h2><code>allsky-config</code> command</h2> |
| 35 | +<p> |
| 36 | +The <code>allsky-config</code> command performs various actions. |
| 37 | +Some let you easily configure a feature |
| 38 | +(like the ability to share files between your Pi and a PC or Mac), |
| 39 | +while other actions let you view various types of information |
| 40 | +which is often used to troubleshoot. |
| 41 | +<br> |
| 42 | +The list of actions grows often so is not shown here but you can |
| 43 | +enter <code>allsky-config --help</code> to see the list. |
| 44 | + |
| 45 | +<blockquote> |
| 46 | +The Allsky developers may ask you to run <code>allsky-config</code> |
| 47 | +to provide additional information. |
| 48 | +In most cases you can simply copy and paste the command you are asked to run into |
| 49 | +a terminal window on the Pi. |
| 50 | +</blockquote> |
| 51 | +</p> |
| 52 | +<p> |
| 53 | +<code>allsky-config</code> can be used two different ways: |
| 54 | +<ol> |
| 55 | + <li><strong>Menu-driven</strong> |
| 56 | + <br> |
| 57 | + In this mode you simply type <code>allsky-config</code> and |
| 58 | + are presented with a menu of actions you can perform. |
| 59 | + Use the up and down arrow keys to navigate the list |
| 60 | + and the left right arrow keys to go to the choices at the end of the list. |
| 61 | + After selecting an action, |
| 62 | + if additional information is needed you are prompted for it. |
| 63 | + The action you selected is then executed and its output displayed. |
| 64 | + <br> |
| 65 | + You can then enter <code>q</code> to quit <code>allsky-config</code> or |
| 66 | + press return to be shown the menu of actions again. |
| 67 | + |
| 68 | + <p> |
| 69 | + When viewing the menu, the name of the action that will be taken |
| 70 | + is listed at the end of every entry. |
| 71 | + That action name is used in the next mode of <code>allsky-config</code> |
| 72 | + - see below. |
| 73 | + </p> |
| 74 | + <li><strong>Action-specific</strong> |
| 75 | + <br> |
| 76 | + In this mode, you type <code>allsky-config ACTION</code> |
| 77 | + where "ACTION" is the name of an actions to execute, optionally followed by arguments. |
| 78 | + <br> |
| 79 | + For example: <code>allsky-config show_supported_cameras --zwo</code>. |
| 80 | + <p> |
| 81 | + Most actions only output information but a few first prompt for something |
| 82 | + then perform the action. |
| 83 | + </p> |
| 84 | +</ol> |
| 85 | +</p> |
| 86 | +<p> |
| 87 | +To see what an action does and what, if any arguments it takes, |
| 88 | +enter <code>allsky-config ACTION --help</code>, |
| 89 | +replacing "ACTION" with an action name shown in the command above. |
| 90 | +</p> |
| 91 | + |
| 92 | + |
| 93 | +<h2><code>htop</code></h2> |
| 94 | +<p> |
| 95 | +If your Pi seems very slow you can run the Linux <code>htop</code> command which |
| 96 | +displays the usage of all the CPUs and the amount of memory and swap in use, |
| 97 | +as well as the processes using the most CPU. |
| 98 | +The display is updated roughly every second. |
| 99 | +</p> |
| 100 | +<p> |
| 101 | +You will probably first need to install <code>htop</code> by executing |
| 102 | +<code>sudo apt install htop</code>. |
| 103 | +</p> |
| 104 | + |
| 105 | +<h2>Other troubleshooting tools</h2> |
| 106 | +<p> |
| 107 | +More to come... |
| 108 | +</p> |
| 109 | + |
| 110 | + |
| 111 | +</div><!-- Layout-main --> |
| 112 | +</div><!-- Layout --> |
| 113 | +</body> |
| 114 | +</html> |
| 115 | +<script> includeHTML(); </script> |
0 commit comments