<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [ome-users] 4.1.0 fails to start</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hey Josh-<BR>
<BR>
>> =====================================================<BR>
>> Data access exception: Did you create your database?<BR>
>> =====================================================<BR>
><BR>
>Could I get the whole log? There may be a clue buried in there somewhere.<BR>
><BR>
><BR>
>This certainly looks good. What's the value from:<BR>
><BR>
>psql -h localhost -U omero -c "select * from dbpatch"<BR>
<BR>
Well there's the clue. This returns an error. A quick look at the database show the source of the problem - Blitz works much better when you don't have an empty database. I managed to trash it somehow; re-running the db config script has got OMERO running again. Oops.<BR>
<BR>
>> Perhaps it's python - DropBox complains:<BR>
<BR>
>In general, Blitz doesn't depend on any of the other services, only<BR>
>the other way around. The DropBox error is just saying your missing a<BR>
>required library, so DropBox won't work for you.<BR>
<BR>
>> 2009-10-29 12:41:41,141 ERROR [ fsclient.DropBox] (MainThread) System<BR>
>> requirements not met:<BR>
>> Traceback (most recent call last):<BR>
>> File "lib/python/fsDropBox.py", line 66, in run<BR>
>> fsUtil.monitorPackage()<BR>
>> File "/home/mrmike/Documents/omero-Beta4.1.0/lib/python/fsUtil.py", line 117, in monitorPac<BR>
>> kage<BR>
>> raise Exception("Libraries required by OMERO.fs monitor unavailable: " + errorString)<BR>
>> Exception: Libraries required by OMERO.fs monitor unavailable: pynotify version 0.8.6 is not<BR>
>> compatible with Python 2.4. Install 0.8.5 or lower to use DropBox<BR>
<BR>
I'm still getting this error; is DropBox not compatible with Python 2.6/pynotify 0.8.6?<BR>
Perhaps this is related to the problem reported in diagnostics?<BR>
<BR>
>Thanks for catching this. "diagnostics" was looking for a version of<BR>
>the form "2.5.4" and "2.6" sadly confused it.<BR>
<BR>
I'm still seeing the following errors related to file lock and a socket exception; I'm more concerned about the socket exception - have I botched Ice somehow?<BR>
<BR>
Oct 30, 2009 10:00:41 AM java.util.prefs.FileSystemPreferences checkLockFile0Err<BR>
orCode<BR>
WARNING: Could not lock System prefs. Unix error code 0.<BR>
Oct 30, 2009 10:00:41 AM java.util.prefs.FileSystemPreferences syncWorld<BR>
WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException: Cou<BR>
ldn't get file lock.<BR>
10/30/09 10:00:41.511 OMERO.Glacier2: error: service caught unhandled exception:<BR>
Network.cpp:1083: Ice::SocketException:<BR>
socket exception: Address already in use<BR>
Oct 30, 2009 10:00:41 AM java.util.prefs.FileSystemPreferences checkLockFile0Err<BR>
orCode<BR>
WARNING: Could not lock System prefs. Unix error code 0.<BR>
Oct 30, 2009 10:00:41 AM java.util.prefs.FileSystemPreferences syncWorld<BR>
WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException: Cou<BR>
ldn't get file lock.<BR>
10/30/09 10:00:42.023 OMERO.Glacier2: error: service caught unhandled exception:<BR>
Network.cpp:1083: Ice::SocketException:<BR>
socket exception: Address already in use<BR>
<BR>
<BR>
Thanks again!<BR>
Mike<BR>
</FONT>
</P>
</BODY>
</HTML>