@@ -7,6 +7,9 @@ aliases = ["docs/using/ship-troubleshooting/"]
77
88Urbit is still in the development stage, so there's a chance that your ship won't start properly, or will stop working properly when you're running it. That's ok! This document is intended to help you in such an event.
99
10+This page contains resolutions to many of the most commonly encountered issues.
11+If your issue is not covered here, please check out our [Troubleshooting Knowledgebase](https://github.com/urbit/support/wiki).
12+
1013## Table of Contents
1114
1215- [Best practices](#best-practices)
@@ -97,6 +100,15 @@ Since version `0.8.0`, changes no longer automatically sync between the Unix sid
97100
98101You may have booted a ship with your keyfile twice in the same era. To fix this, you must perform a [personal breach](#personal-breach).
99102
103+### I don't have the latest OTA
104+
105+You can check what build your ship is on by entering `+trouble` into dojo and
106+reading the `%base` hash. If this does not match the latest hash published in
107+the `urbit-dev` mailing list, you are behind.
108+
109+Your sponsor may just be lagging behind, so sometimes this will resolve on its
110+own with patience. Otherwise, try the procedure outlined [here](https://github.com/urbit/support/wiki/Missing-OTA).
111+
100112### I keep getting an `ames` error stack-trace
101113
102114You may see a message like this one: `/~zod/home/~2019.7.22..18.55.46..83a3/sys/vane/ames:<[line column].[line column]>`. This is a clay path to a Hoon file, pointing to the line and column where an expression crashed. This kind of error might be accompanied by a `crud` message.
@@ -131,10 +143,6 @@ This is the result of deleting your pier and starting your ship again. To fix th
131143
132144## Booting Issues {#booting-issues}
133145
134−### My ship won't boot and gets a `terminals database is inaccessible` message
135−
136−This happens when you try to run the Urbit binary through your `$PATH`. When running the command, you need to be explicit and specify the actual path to it in the filesystem. This is a side-effect of the way we build the release binaries, which will be fixed.
137−
138146### My ship booted for the first time, but it turned into a comet instead of my planet or star
139147
140148You may have used the wrong arguments when booting your ship for the first time. Delete this comet and try again.
@@ -174,9 +182,15 @@ Copy this stack trace and include it in your GitHub issue.
174182
175183### My ship crashed with a `bail: meme` error.
176184
177−1. Make sure you are running version to `0.8.2` if you are not already on it.
185+This means that your ship ran out of memory.
186+
187+1. Make sure you are running the latest binary if you are not already on it.
188+
189+2. Restart your ship. If you don't crash again, everything may be fine.
190+
191+3. Try the procedure outlined [here](https://github.com/urbit/support/wiki/ship-exits-with-a-bail:-meme-error).
178192
179−2. Restart your ship. If you don't crash again, everything may be fine. If you **do** crash again, then you should perform a [personal breach](#personal-breach).
193+4. If you **do** crash again, then you should perform a [personal breach](#personal-breach).
180194
181195### My ship crashed with a `bail: oops` error
182196