Task #2492 (closed)
Opened 9 years ago
Closed 9 years ago
BUG: SQL errors after new config?
| Reported by: | cxallan | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.2 |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | 2010-05-27 (10) |
Description
On Blitz startup after the configuration commits I now have SQL errors.
Change History (4)
comment:1 Changed 9 years ago by cxallan
comment:2 Changed 9 years ago by jmoore
From devteam log (below) it looks like the prefs upgrade took place, but to the wrong file (OMERO-TRUNK/etc/grid/config.xml rather than OMERO-TRUNK/dist/etc/grid/config.xml).
$ dist/bin/omero admin start
Creating directory /Users/callan/code/OMERO-TRUNK/dist/var
Importing pre-4.2 preferences
Creating /Users/callan/code/OMERO-TRUNK/dist/var/master
Initializing /Users/callan/code/OMERO-TRUNK/dist/var/log
Creating /Users/callan/code/OMERO-TRUNK/dist/var/registry
No descriptor given. Using etc/grid/default.xml
Waiting on startup. Use CTRL-C to exit
.............................Failed to startup after 5 minutes
$ dist/bin/omero config get
etc/grid/config.xml not found; using /Users/callan/omero/config.xml
$ ls -al ~/omero/config.xml
-rw-r--r-- 1 callan staff 524 9 Jun 09:06 /Users/callan/omero/config.xml
$ cat ~/omero/config.xml
<?xml version="1.0" ?>
<icegrid>
<!--
This file was generated at Wed Jun 9 09:06:52 2010 by the OmeroConfig system.
Do not edit directly but see bin/omero config for details.
This file may be included into your IceGrid application.
-->
<properties id="__ACTIVE__">
<property name="omero.config.profile" value="default"/>
<property name="omero.config.version" value="4.2.0"/>
</properties>
<properties id="default">
<property name="omero.config.version" value="4.2.0"/>
</properties>
</icegrid>
comment:3 Changed 9 years ago by jmoore
comment:4 Changed 9 years ago by cxallan
- Resolution set to invalid
- Status changed from new to closed
Possible issue with OMERO_CONFIG and/or database oddities. drop/create resolved the problem.