--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To post to this group, send email to xnat_di...@googlegroups.com.
To unsubscribe from this group, send email to xnat_discussi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xnat_discussion?hl=en.
jordan
To post to this group, send email to xnat_discussion@googlegroups.com.
To unsubscribe from this group, send email to xnat_discussion+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/xnat_discussion/-/2jeK5UcI6qwJ.
To post to this group, send email to xnat_di...@googlegroups.com.
To unsubscribe from this group, send email to xnat_discussi...@googlegroups.com.
PrearcTableBuilder PSQLException
2012-03-29 14:41:18,764 [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-2] ERROR org.nrg.xnat.helpers.prearchive.PrearcTableBuilder - org.postgresql.util.PSQLException: ERROR: relation "xdat_search.prearchive" does not exist Position: 15 [truncated]
DBAction PSQLException
2012-03-29 14:42:07,225 [http-8080-6] ERROR org.nrg.xft.db.DBAction - org.postgresql.util.PSQLException: ERROR: relation "xdat_meta_element_meta_data" does not exist Where: PL/pgSQL function "update_ls_xdat_meta_element" line 6 at FOR over SELECT rows
The message that may appear in sql.log relates to the meta-data table initialization. It doesn't appear as an error, but may be repeated enough to cause concern and looks similar to this:
2012-03-29 14:42:19,886 - SELECT update_ls_xdat_meta_element(573,NULL)
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
The xdat log is unrelated because when you install a new XNAT from the 1.6 release and start Tomcat, before logging in and initializing the system, you may see a number of errors in the xdat.log and sql.log files. These are caused by delayed initialization of some of the dependent tables and will stop occurring once you've logged in and initialized the system settings. This includes the one you copied, plus, potentially:
PrearcTableBuilder PSQLException
2012-03-29 14:41:18,764 [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-2] ERROR org.nrg.xnat.helpers.prearchive.PrearcTableBuilder -
org.postgresql.util.PSQLException: ERROR: relation "xdat_search.prearchive" does not exist
Position: 15
[truncated]
DBAction PSQLException
2012-03-29 14:42:07,225 [http-8080-6] ERROR org.nrg.xft.db.DBAction - org.postgresql.util.PSQLException: ERROR: relation "xdat_meta_element_meta_data" does not exist
Where: PL/pgSQL function "update_ls_xdat_meta_element" line 6 at FOR over SELECT rows
The message that may appear in sql.log relates to the meta-data table initialization. It doesn't appear as an error, but may be repeated enough to cause concern and looks similar to this:
2012-03-29 14:42:19,886 - SELECT update_ls_xdat_meta_element(573,NULL)
Do you see anything else in your logs besides those?
Can you open firebug (or equivalent) and see if the network traffic or console gives you any idea which calls are failing?
Thank you,
Jordan
On Tue, Jul 31, 2012 at 4:31 PM, David Just <Just....@mayo.edu> wrote:
Yes, text boxes are completely disabled.
On 7/31/12 4:26 PM, "Jordan Woerndle" <jord...@gmail.com <http://jord...@gmail.com> > wrote:
This might be similar to a problem we're seeing on one instance here.. Similar stack trace, but we get a 404 instead of a 500.
are your text boxes empty and disabled so that you can't enter data even if you wanted?
Jordan
--
David, most of those messages indicate anything in particular and really are just a herring shop:
· The Axis message is a rather annoying message that we can’t seem to stomp out. It just means that we don’t have a wsdd configuration for Axis and that makes it rather grumpy. We don’t use Axis in the way that would require a wsdd configuration, so it pouts all the time.
· Most of that hideous ERRORing going on in xdat.log consists of unclean teardown in the logging and scheduler frameworks. This is basically pointless: it won’t create a memory leak because it will soon be deceased and/or pining for the fjords. Again, something that shows up that we can’t get rid of in a non-trivial manner.
· Things get interesting with the message: “INFO: The APR based Apache Tomcat Native…” This is where the restart happens. Everything after that is pretty normal initialization and bootstrapping of stuff in the database.
I’m not sure why you say: “It appears that xnat is not picking up the settings from my build.properties file.”
One thing to check is whether or not you have a build.properties file in your home folder (i.e. ~/build.properties). I just learned a valuable lesson around this particular item. Maven 1, in its wisdom, will look in your home folder and, if there is a build.properties file there, will use that in preference to the build.properties located right in the xnat_builder_1_6dev folder. Failure to know this simple fact results in plenty of frustration and cursing. At least, if you’re someone who reacts to such things with frustration and cursing and I assure you that I am. So if you’re seeing weird property settings, check on that possibility.
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To post to this group, send email to
xnat_di...@googlegroups.com.
To unsubscribe from this group, send email to
xnat_discussi...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/xnat_discussion?hl=en.
Ah, then what you’re seeing there is a failure of the settings restlet that drives the new configuration page. The values are most likely there, they’re just not making it from the server to your browser!
As of yesterday afternoon, I was getting through that portion of the build and installation process, so I think we’ve knocked that issue out. It was related to a code change over the weekend that started invoking the workflow engine before it was ready.
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To post to this group, send email to
xnat_di...@googlegroups.com.
To unsubscribe from this group, send email to
xnat_discussi...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/xnat_discussion?hl=en.