Changes between Version 12 and Version 13 of Troubleshooting

Timestamp:

04/21/08 22:53:58 (5 years ago)

Author:

chris

Comment:

--

Troubleshooting

@@ -111 +111 @@
 If this really doesn't help, then using the DEBUG builds of the system will give you much more information - a more descriptive exception message and the file and line number where the error occurred.
 
-'''DO NOT DO THIS''' for the store server, `bbstored`, as the debug version uses a different store file layout and it will NOT be compatible with your existing store.
+'''DO NOT DO THIS''' for `bbstored` or `bbstoreaccounts`, as the debug versions use a different store file layout and they will NOT be compatible with your existing store, and may well corrupt it.
 
-For example, if you are having problems with bbstoreaccounts, build the debug version with the following commands:
+For example, if you are having problems with bbackupquery, build the debug version with the following commands:
 
 {{{
 cd boxbackup-0.xx
-cd bin/bbstoreaccounts
+cd bin/bbackupquery
 make
 }}}
@@ -123 +123 @@
 (within the module directories, make defaults to building the debug version. At the top level, it defaults to release.)
 
-This will build an executable in debug/bin/bbstoreaccounts which you can then use instead of the release version. It will give far more useful error messages.
+This will build an executable in debug/bin/bbackupquery which you can then use instead of the release version. It will give far more useful error messages.
 
 When you get an error message, use the file and line number to locate where the error occurs in the code. There will be comments around that line to explain why the exception happened.
 
-If you are using a debug version of a daemon, these extended messages are found in the log files.
+If you are using a debug version of a daemon, these extended messages are found in the log files. You can also try running the daemon with the -DV options for debugging.
 
 == If All Else Fails ==