Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (herse.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=PY0l+fov2rzEg27WIKhMcowKR0mcslNU3jh8lpAYtDvxCsgDCPMv3/ot7ZQBPJHpuPil1xrH3EWhwNFI/yUHiaXeL7C7pzoPBxfZM11BKpFg3c9aYVSLEpDyKJGF/eQMSV2WZpTu+v+z74ByBpJ8wgWMAyahYH5Oj8MBCKGZrLY=;
Date: Tue, 8 May 2007 19:28:15 -0700 (PDT)
From: Jerome Benezech <jbenezech@yahoo.com>
Reply-To: jbenezech@bigfoot.com
Subject: embedded eXist won't startup on Linux prod
To: users@cocoon.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <597576.67226.qm@web32214.mail.mud.yahoo.com>

Hi all,

My application uses cocoon 2.2 and an embedded eXist
database. The eXist part runs well on my developpement
environement (XP, jetty) but I run into problems
deploying it on my production server (Linux, tomcat
5.5.9).
After (re)starting the webapp, I connect to my base
URL and get the "Local Database Server is not running"
message. At that point, eXists seem to have started
correctly (exist.log) and no error besides the
"Database not running" can be found in cocoon.log or
tomcat log.

I manage to start it eventually doing the following:
- delete the lock file dbx_dir.lck on the database
- delete the lock file  WEB-INF/data/journal.lck
- access directly the exist servlet in the URL:
http://domain.com/mywebapp/servlet/db/../resource.xml

After doing that, I can access my cocoon URL with no
problem. But this is off course not a viable solution
for a production environement.

My prod environement is running on a shared Linux
account so I do not have control over the tomcat part.

Any idea where this problem could come from ? 
One big difference between dev and prod is of course
Linux permissions. I installed my app using my user
account but the web server is running as
tomcat:nobody. So I guess tomcat:nobody needs
permissions to some directories. I for now (to get
started until I find a better solution) gave full
permission (777) to the database and logs directories.

Any help appreciated.
Jerome


Jerome Benezech
jbenezech@yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org