From 0864fa8f1001896bf0822ab3eee69b65e46b7a25 Mon Sep 17 00:00:00 2001 From: mj Date: Tue, 29 Jan 2002 22:09:46 +0000 Subject: [PATCH] Added some tips for troubleshooting. --- doc/INSTALL.mir | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/doc/INSTALL.mir b/doc/INSTALL.mir index 3d04d799..06f1a0b4 100755 --- a/doc/INSTALL.mir +++ b/doc/INSTALL.mir @@ -72,13 +72,14 @@ as user postgres: cat dbscripts/help*.sql | psql -Upostgres dbname cat dbscripts/populate*.sql | psql -Upostgres dbname + 10. Add the dupe prevention trigger to the database: cd dbscripts/dupetrigger There, read INSTALL and follow the instructions. -11. Set permissions +11. Set permissions -- IMPORTANT! READ THIS! We provide a script that sets all files' and direcories' permissions to a quite reasonable state. The most important thing you have to do after the invokation of this script is to ensure that the log files -- @@ -137,8 +138,8 @@ You should make sure that no copy of config.properties (neither in mir nor in Mir/src nor in Mir/WEB-INF/classes) is world-readable. Else you wouldn't have to install a password, anyway. -If you can't access PostgreSQL after this for any reason, try to change -"password" in /etc/postgresql/pg_hba.conf into "trust". This should disable +If you can't access PostgreSQL after this for any reason, try and change +"password" in /etc/postgresql/pg_hba.conf to "trust". This should disable any authentication method and make the database accessible again. that's it :) @@ -152,3 +153,14 @@ and the openposting-servlet via http://host/OpenMir standard login is redaktion/indymedia + + + +TROUBLESHOOTING + +You can give these a try if anything goes wrong: + ++ Restart Tomcat. Especially after compiling the sources Tomcat has to be + restarted. + ++ Check file permissions and ownership. Try and run perms.sh. \ No newline at end of file -- 2.11.0