From: grubert <grubert@57a73879-2fb5-44c3-a270-3262357dd7e2>
Date: Thu, 14 Feb 2002 11:11:36 +0000 (+0000)
Subject:  . more detail on failing open.
X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=10aca513a28ea50e4fdfac6e274850e600aaf477;p=roundup.git

 . more detail on failing open.


git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@623 57a73879-2fb5-44c3-a270-3262357dd7e2
---

diff --git a/doc/FAQ.txt b/doc/FAQ.txt
index 253d60e..3b5dbec 100644
--- a/doc/FAQ.txt
+++ b/doc/FAQ.txt
@@ -1,6 +1,6 @@
 Roundup FAQ
 
-  '$Date: 2002-02-14 08:50:14 $'
+  '$Date: 2002-02-14 11:11:36 $'
 
   NOTE: This is just a grabbag, most of this should go into documentation.
 
@@ -71,25 +71,38 @@ Installation
     * roundup-mailgw called via .forward from MTA, or running a cron job
       fetching via pop.
 
+    see Troubleshooting.
 
 Troubleshooting
 
-  mailgw bouncing
+  
+  AttributeError: '_roundup_instance_1' module has no attribute 'open'
+
+    Sorry: in html it is not formatted correct.
 
-    messages are bouncing with the following error message.::
+    For example submitting issues via roundup-mailgw breaks similar to this.::
 
       Command died with status 1:
       "/usr/local/bin/python /usr/local/bin/roundup-mailgw /home/roundup".
       Command output: Traceback (most recent call last):  
-        File "/usr/local/bin/roundup-mailgw", line 178, in ? sys.exit(main(sys.argv))
-        File "/usr/local/bin/roundup-mailgw", line 153, in main db =
-          instance.open('admin') AttributeError: '_roundup_instance_1' module 
-          has no attribute 'open'
-
-      
-    Happens when roundup-mailgw is called by a user that doesn't have
-    read/execute permissions to the instance_home directory and sub
-    directories.
+        File "/usr/local/bin/roundup-mailgw", line 178, in ? 
+           sys.exit(main(sys.argv))
+        File "/usr/local/bin/roundup-mailgw", line 153, in main 
+          db = instance.open('admin')
+           AttributeError: '_roundup_instance_1' module has no attribute 'open'
+
+    Happens if the user which accesses the instance has no read right
+    on 'INSTANCE/dbinit.py' or 'pyc'. 
+
+    If the user has no rights on the 'INSTANCE/db' the mailgw finishes,
+    but is, of course, unable to add the message. A notification to
+    the roundup-admin is sent, with a longer trace ending in::
+
+      File "/opt/python/lib/python2.2/dbhash.py", line 16, in open
+        return bsddb.hashopen(file, flag, mode)
+      error: (13, 'Keine Berechtigung')
+
+    Replace 'Keine Berechtigung' by 'Not permitted' or ...
 
     An easy way to test whether it's a permissions problem, or some other mail
     server configuration problem is to cat an email-formatted text file