Problems with setting of system paths to a NAS-server in new installation of xnat 1.7.2

222 views
Skip to first unread message

Laura K.

unread,
Mar 16, 2017, 10:48:08 AM3/16/17
to xnat_discussion
Dear all,

I have installed xnat 1.7.2 by using Java_JDK_8u121, PostgreSQL_9_5_6_1, ApacheTomcat_7_0_75 on a Windows7 64-bit OS and renamed "xnat.war" to "root.war".
For test purposes, I created all xnat subfolders locally (on C:) and everything worked fine.

Our production server should be a NAS-server where the xnat-user has full access. This worked fine earlier with xnat 1.6.2.

With xnat1.7.2, when deploying "root.war" again and entering the new system paths, I obtain the following error:




The same error is documented in the obtained log-file: xnat_home\logs\tasks.

I tried also a new deployment after moving all the folders to the NAS-server (H:):
xnat_home and all the other folders: archive, prearchive, build, ftp, cache, pipeline,
and using a new created database xnat,

but I have the problem of accesing H:

org.nrg.framework.exceptions.NrgServiceRuntimeException: Error [Unknown]: Error [Unknown]: An error occurred trying to create the temp folder xnat_100480357057319 in the containing folder H:/test_XNAT/XNAT/home
    at org.nrg.xnat.initialization.XnatWebAppInitializer.getMultipartConfigElement(XnatWebAppInitializer.java:116)

Here is the log file catalina.log:

INFORMATION: Deploying web application archive C:\XNAT_Programms\ApTomcat_7_0_75\webapps\ROOT.war
Mär 14, 2017 2:48:11 PM org.apache.catalina.startup.TldConfig execute
INFORMATION: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Mär 14, 2017 2:48:12 PM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:162)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
    at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1092)
    at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1984)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Caused by: org.nrg.framework.exceptions.NrgServiceRuntimeException: Error [Unknown]: Error [Unknown]: An error occurred trying to create the temp folder xnat_100480357057319 in the containing folder H:/test_XNAT/XNAT/home
    at org.nrg.xnat.initialization.XnatWebAppInitializer.getMultipartConfigElement(XnatWebAppInitializer.java:116)
    at org.nrg.xnat.initialization.XnatWebAppInitializer.customizeRegistration(XnatWebAppInitializer.java:95)
    at org.springframework.web.servlet.support.AbstractDispatcherServletInitializer.registerDispatcherServlet(AbstractDispatcherServletInitializer.java:113)
    at org.springframework.web.servlet.support.AbstractDispatcherServletInitializer.onStartup(AbstractDispatcherServletInitializer.java:71)
    at org.nrg.xnat.initialization.XnatWebAppInitializer.onStartup(XnatWebAppInitializer.java:52)
    at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:169)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5623)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
    ... 10 more


Do you have an idea how to make the NAS-server accesible to XNAT? The xnat-user has full access to the NAS-server, is the owner of the tomcat-folders and of all xnat-folders.

Thank you for your help!

Laura K.






Auto Generated Inline Image 1

McKay, Mike

unread,
Mar 16, 2017, 2:26:10 PM3/16/17
to xnat_di...@googlegroups.com

Laura,

 

First of all, starting in XNAT 1.7, we are recommending that people run XNAT on Linux rather than Windows. We perform our testing on a Linux system, and it’s possible that there are XNAT bugs (likely related to paths) that will happen on Windows, but not on Linux. We also recommend using Java 7 rather than Java 8, though at this point we may have resolved all the compatibility issues between XNAT and Java 8, and I think this is unlikely to be the source of your problem.

 

That being said, I have a Windows workstation with XNAT 1.7 installed on it that I often use for testing and development. I haven’t encountered major issues, though I did encounter some weirdness with paths on the prearchive page a while ago.

 

For me, XNAT on Windows has no problem writing to and accessing directories on NAS. The only immediate difference I see between my setup and yours is that when I specified the paths to those directories, I used backslashes (e.g. H:\XNAT\prearchive). If you haven’t already tried this, could you try setting up XNAT with a fresh database and entering the paths to your NAS folders with backslashes during site setup?

 

-Mike

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at https://groups.google.com/group/xnat_discussion.
For more options, visit https://groups.google.com/d/optout.

 


The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

Laura K.

unread,
Mar 17, 2017, 8:01:55 AM3/17/17
to xnat_discussion
Hello Mike,

thank you for your kind response!
To switch to Linux OS isn't so easy at the moment, because we have no computer available for testing...

I tried a new setup of XNAT with a fresh database, like you suggested, and used backslashes in the paths entering during site setup, but I obtained the same error as before:



Please note that by using local XNAT folder paths the system is working fine (C:\XNAT_Programms\data\xnat\archive, etc.)

For further debugging, I attach here the errors edited in the log-files:

- axis.log:

151053 [localhost-startStop-1] ERROR org.apache.axis.configuration.EngineConfigurationFactoryServlet  - Unable to find config file.  Creating new servlet engine config file: /WEB-INF/server-config.wsdd
151221 [localhost-startStop-1] ERROR org.apache.axis.configuration.EngineConfigurationFactoryServlet  - Unable to find config file.  Creating new servlet engine config file: /WEB-INF/server-config.wsdd

- configuration.log:

2017-03-17 10:02:49,846 [localhost-startStop-1] WARN  org.nrg.xnat.initialization.PropertiesConfig - No node configuration found.
2017-03-17 10:02:50,140 [localhost-startStop-1] WARN  org.nrg.xnat.initialization.DatabaseConfig - No value set for the XNAT datasource class, using the default value of org.apache.commons.dbcp2.BasicDataSource
2017-03-17 10:02:50,140 [localhost-startStop-1] WARN  org.nrg.xnat.initialization.DatabaseConfig - No value set for the XNAT datasource initial connection pool size, using the default value of 20
2017-03-17 10:02:50,140 [localhost-startStop-1] WARN  org.nrg.xnat.initialization.DatabaseConfig - No value set for the XNAT datasource maximum connection pool size, using the default value of 40
2017-03-17 10:02:50,141 [localhost-startStop-1] WARN  org.nrg.xnat.initialization.DatabaseConfig - No value set for the XNAT datasource connection pool idle size, using the default value of 10

tasks.log:

2017-03-17 10:03:11,679 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:03:11,692 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.AbstractInitializingTask - The table 'xdat_search.xs_item_access' does not yet exist. Deferring execution.
2017-03-17 10:03:11,696 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.AbstractInitializingTask - The system is not yet fully initialized. Delaying execution of the intializing task "Encrypt XNAT passwords" until initialization is completed.
2017-03-17 10:03:11,814 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.GetSiteWideAnonScript - Creating Script Table.
2017-03-17 10:03:12,205 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.GetSiteWidePETTracerList - Creating PET Tracer List.
2017-03-17 10:03:12,340 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.AbstractInitializingTask - The system is not yet fully initialized. Delaying execution of the intializing task "System Path Verification" until initialization is completed.
2017-03-17 10:03:12,342 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.UpdateConfigurationService - No suspect configuration entries found.
2017-03-17 10:03:12,359 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.AbstractInitializingTask - The system is not yet fully initialized. Delaying execution of the intializing task "Update new secure definitions" until initialization is completed.
2017-03-17 10:03:12,385 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.AbstractInitializingTask - The system is not yet fully initialized. Delaying execution of the intializing task "Update the user authentication table" until initialization is completed.
2017-03-17 10:03:27,407 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:03:42,498 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:03:57,528 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:04:12,550 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:04:27,573 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:04:42,600 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:04:57,628 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:05:12,649 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:05:27,679 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - This service is the primary XNAT node, checking whether database updates are required.
2017-03-17 10:05:27,683 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - XDATServlet indicates that views do not need to be updated, terminating task.
2017-03-17 10:05:27,684 [taskScheduler-1] INFO  org.nrg.xnat.initialization.tasks.CreateOrUpdateDatabaseViews - Initializing database views...
2017-03-17 10:13:30,698 [taskScheduler-1] ERROR org.nrg.xnat.initialization.tasks.SystemPathVerification - XNAT_FAU System Path Verification Failure: The following system path errors have been discovered:
    1. Archive path "H:\test_XNAT\XNAT\archive" does not exist.
    2. Cache path "H:\test_XNAT\XNAT\cache" does not exist.
    3. Pipeline path "H:\test_XNAT\XNAT\pipeline" does not exist.
    4. Build path "H:\test_XNAT\XNAT\build" does not exist.
    5. Prearchive path "H:\test_XNAT\XNAT\prearchive" does not exist.

- sql.log:

2017-03-17 10:05:14,275 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction - Preparing to convert table xhbm_script_launch_request_event to use sequence for default value.
2017-03-17 10:05:14,276 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction - Queries prepared for conversion:
2017-03-17 10:05:14,276 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction -  *** CREATE SEQUENCE xhbm_script_launch_request_event_id_seq
2017-03-17 10:05:14,276 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction -  *** ALTER TABLE xhbm_script_launch_request_event ALTER COLUMN id SET DEFAULT nextval('xhbm_script_launch_request_event_id_seq')
2017-03-17 10:05:14,276 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction -  *** ALTER TABLE xhbm_script_launch_request_event ALTER COLUMN id SET NOT NULL
2017-03-17 10:05:14,277 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction -  *** ALTER SEQUENCE xhbm_script_launch_request_event_id_seq OWNED BY xhbm_script_launch_request_event.id
2017-03-17 10:05:14,288 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction - Ran the query SELECT (MAX(id) + 1) AS value FROM xhbm_script_launch_request_event and got the value 1
2017-03-17 10:05:14,288 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction - Now preparing to run the query: SELECT setval('xhbm_script_launch_request_event_id_seq', 1) AS value
2017-03-17 10:05:14,289 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction - Preparing to convert table xhbm_script_aud to use sequence for default value.
2017-03-17 10:05:14,289 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction - Queries prepared for conversion:
2017-03-17 10:05:14,289 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction -  *** CREATE SEQUENCE xhbm_script_aud_id_seq
2017-03-17 10:05:14,289 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction -  *** ALTER TABLE xhbm_script_aud ALTER COLUMN id SET DEFAULT nextval('xhbm_script_aud_id_seq')
2017-03-17 10:05:14,289 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction -  *** ALTER TABLE xhbm_script_aud ALTER COLUMN id SET NOT NULL
2017-03-17 10:05:14,289 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction -  *** ALTER SEQUENCE xhbm_script_aud_id_seq OWNED BY xhbm_script_aud.id
2017-03-17 10:05:14,293 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction - Ran the query SELECT (MAX(id) + 1) AS value FROM xhbm_script_aud and got the value 1
2017-03-17 10:05:14,293 [localhost-startStop-1] ERROR org.nrg.xft.db.DBAction - Now preparing to run the query: SELECT setval('xhbm_script_aud_id_seq', 1) AS value

Regarding the Tomcat properties, I attach here the settings:

Log On as xnat01, the owner of Tomcat, not as local system -- could this be a problem?




- Tomcat localhost.log:

Mär 17, 2017 10:02:46 AM org.apache.catalina.core.ApplicationContext log
INFORMATION: 1 Spring WebApplicationInitializers detected on classpath
Mär 17, 2017 10:02:47 AM org.apache.catalina.core.ApplicationContext log
INFORMATION: Initializing Spring root WebApplicationContext
Mär 17, 2017 10:05:19 AM org.apache.catalina.core.ApplicationContext log
INFORMATION: Initializing Spring FrameworkServlet 'dispatcher'
Mär 17, 2017 10:13:29 AM org.apache.catalina.core.StandardWrapperValve invoke
SCHWERWIEGEND: Servlet.service() for servlet [turbine] in context with path [] threw exception
java.lang.RuntimeException: Failed to create working file H:\test_XNAT\XNAT\cache\archive_specification.xml, please check permissions and file system.
    at org.nrg.xnat.turbine.utils.ArcSpecManager.GetInstance(ArcSpecManager.java:70)
    at org.nrg.xnat.turbine.utils.ArcSpecManager.GetInstance(ArcSpecManager.java:55)
    at org.nrg.xnat.security.XnatExpiredPasswordFilter.doFilter(XnatExpiredPasswordFilter.java:70)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
    at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:91)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
    at org.springframework.security.web.access.channel.ChannelProcessingFilter.doFilter(ChannelProcessingFilter.java:152)
    at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
    at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:213)
    at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:176)
    at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
    at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:452)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1087)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
    at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2536)
    at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2525)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Unknown Source)

- postgresql.log:

2017-03-17 10:02:59 CET FEHLER:  Relation »arc_archivespecification« existiert nicht bei Zeichen 22
2017-03-17 10:02:59 CET ANWEISUNG:  select count(*) from arc_archivespecification
2017-03-17 10:03:12 CET FEHLER:  Relation »xdat_user« existiert nicht bei Zeichen 28
2017-03-17 10:03:12 CET ANWEISUNG:  SELECT login, enabled FROM xdat_user WHERE login NOT IN (SELECT xdat_username FROM xhbm_xdat_user_auth)
2017-03-17 10:03:25 CET FEHLER:  Relation »xdat_user« existiert nicht bei Zeichen 22
2017-03-17 10:03:25 CET ANWEISUNG:  SELECT COUNT(*) FROM xdat_user
2017-03-17 10:03:25 CET FEHLER:  Relation »xdat_user« existiert nicht bei Zeichen 22
2017-03-17 10:03:25 CET ANWEISUNG:  SELECT COUNT(*) FROM xdat_user
2017-03-17 10:03:27 CET FEHLER:  Relation »xdat_element_security« existiert nicht bei Zeichen 74
2017-03-17 10:03:27 CET ANWEISUNG:  SELECT xdat_element_security.element_name AS xdat_element_security0 FROM xdat_element_security xdat_element_security
2017-03-17 10:03:27 CET FEHLER:  Relation »xdat_user« existiert nicht bei Zeichen 28
2017-03-17 10:03:27 CET ANWEISUNG:  SELECT login, enabled FROM xdat_user WHERE login NOT IN (SELECT xdat_username FROM xhbm_xdat_user_auth)
2017-03-17 10:03:42 CET FEHLER:  Relation »xdat_element_security« existiert nicht bei Zeichen 74
2017-03-17 10:03:42 CET ANWEISUNG:  SELECT xdat_element_security.element_name AS xdat_element_security0 FROM xdat_element_security xdat_element_security
2017-03-17 10:03:42 CET FEHLER:  Relation »xdat_user« existiert nicht bei Zeichen 28
2017-03-17 10:03:42 CET ANWEISUNG:  SELECT login, enabled FROM xdat_user WHERE login NOT IN (SELECT xdat_username FROM xhbm_xdat_user_auth)
2017-03-17 10:03:57 CET FEHLER:  Relation »xdat_element_security« existiert nicht bei Zeichen 74
2017-03-17 10:03:57 CET ANWEISUNG:  SELECT xdat_element_security.element_name AS xdat_element_security0 FROM xdat_element_security xdat_element_security
2017-03-17 10:03:57 CET FEHLER:  Relation »xdat_user« existiert nicht bei Zeichen 28
2017-03-17 10:03:57 CET ANWEISUNG:  SELECT login, enabled FROM xdat_user WHERE login NOT IN (SELECT xdat_username FROM xhbm_xdat_user_auth)
2017-03-17 10:04:12 CET FEHLER:  Relation »xdat_element_security« existiert nicht bei Zeichen 74
2017-03-17 10:04:12 CET ANWEISUNG:  SELECT xdat_element_security.element_name AS xdat_element_security0 FROM xdat_element_security xdat_element_security
2017-03-17 10:04:12 CET FEHLER:  Relation »xdat_user« existiert nicht bei Zeichen 28
2017-03-17 10:04:12 CET ANWEISUNG:  SELECT login, enabled FROM xdat_user WHERE login NOT IN (SELECT xdat_username FROM xhbm_xdat_user_auth)
2017-03-17 10:04:17 CET WARNUNG:  Hash-Indexe werden nicht im WAL geloggt und von ihrer Verwendung wird abgeraten.

2017-03-17 10:05:05 CET FEHLER:  Relation »xdat_element_security« existiert nicht bei Zeichen 74
2017-03-17 10:05:05 CET ANWEISUNG:  SELECT xdat_element_security.element_name AS xdat_element_security0 FROM xdat_element_security xdat_element_security
2017-03-17 10:05:12 CET FEHLER:  Relation »xdat_element_security« existiert nicht bei Zeichen 74
2017-03-17 10:05:12 CET ANWEISUNG:  SELECT xdat_element_security.element_name AS xdat_element_security0 FROM xdat_element_security xdat_element_security
2017-03-17 10:05:12 CET FEHLER:  Relation »xdat_user« existiert nicht bei Zeichen 28
2017-03-17 10:05:12 CET ANWEISUNG:  SELECT login, enabled FROM xdat_user WHERE login NOT IN (SELECT xdat_username FROM xhbm_xdat_user_auth)
2017-03-17 10:05:18 CET FEHLER:  Spalte »xnat_projectData_resource_id« von Relation »xnat_projectdata_resource« existiert nicht
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT pg_get_serial_sequence('xnat_projectData_resource','xnat_projectData_resource_id') AS col_name
2017-03-17 10:05:18 CET FEHLER:  Spalte »xnat_projectData_investigator_id« von Relation »xnat_projectdata_investigator« existiert nicht
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT pg_get_serial_sequence('xnat_projectData_investigator','xnat_projectData_investigator_id') AS col_name
2017-03-17 10:05:18 CET FEHLER:  Relation »xnat_projectdata_investigator_xnat_projectdata_investigator_id_« existiert nicht bei Zeichen 15
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT * FROM xnat_projectData_investigator_xnat_projectData_investigator_id_seq
2017-03-17 10:05:18 CET FEHLER:  Relation »xnat_projectdata_investigator_xnat_projectdata_investigator__se« existiert nicht bei Zeichen 15
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT * FROM xnat_projectData_investigator_xnat_projectData_investigator__seq
2017-03-17 10:05:18 CET FEHLER:  Spalte »xnat_subjectData_resource_id« von Relation »xnat_subjectdata_resource« existiert nicht
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT pg_get_serial_sequence('xnat_subjectData_resource','xnat_subjectData_resource_id') AS col_name
2017-03-17 10:05:18 CET FEHLER:  Spalte »xnat_experimentData_resource_id« von Relation »xnat_experimentdata_resource« existiert nicht
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT pg_get_serial_sequence('xnat_experimentData_resource','xnat_experimentData_resource_id') AS col_name
2017-03-17 10:05:18 CET FEHLER:  Relation »xnat_experimentdata_resource_xnat_experimentdata_resource_id_se« existiert nicht bei Zeichen 15
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT * FROM xnat_experimentData_resource_xnat_experimentData_resource_id_seq
2017-03-17 10:05:18 CET FEHLER:  Spalte »xnat_datatypeProtocol_fieldGroups_id« von Relation »xnat_datatypeprotocol_fieldgroups« existiert nicht
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT pg_get_serial_sequence('xnat_datatypeProtocol_fieldGroups','xnat_datatypeProtocol_fieldGroups_id') AS col_name
2017-03-17 10:05:18 CET FEHLER:  Relation »xnat_datatypeprotocol_fieldgroups_xnat_datatypeprotocol_fieldgr« existiert nicht bei Zeichen 15
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT * FROM xnat_datatypeProtocol_fieldGroups_xnat_datatypeProtocol_fieldGroups_id_seq
2017-03-17 10:05:18 CET FEHLER:  Relation »xnat_datatypeprotocol_fieldgro_xnat_datatypeprotocol_fieldgro_s« existiert nicht bei Zeichen 15
2017-03-17 10:05:18 CET ANWEISUNG:  SELECT * FROM xnat_datatypeProtocol_fieldGro_xnat_datatypeProtocol_fieldGro_seq

Is there any other file I should check?

Thank you all for your support!

Best regards,
Laura
Auto Generated Inline Image 1
Auto Generated Inline Image 2

McKay, Mike

unread,
Mar 17, 2017, 11:50:45 AM3/17/17
to xnat_di...@googlegroups.com

This sounds like the user running Tomcat does not have access to these directories. For me, my Tomcat Log On properties has “Log on as:” set to “Local System account”. I am able to access my NAS through the Windows File Explorer and Tomcat is also able to access files on my NAS. You will want to make sure that the Tomcat user is a user that has access to your NAS.

 

-Mike  

 

From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Laura K.


Sent: Friday, March 17, 2017 7:02 AM
To: xnat_discussion <xnat_di...@googlegroups.com>

--

You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at https://groups.google.com/group/xnat_discussion.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages