most logins fail on xnat-docker-compose

94 views
Skip to first unread message

a.m....@gmail.com

unread,
Jan 13, 2022, 10:59:06 AM1/13/22
to xnat_discussion
I'm managing an XNAT that was made with the xnat-docker-compose scripts, and I have a number of logins, including my own username and 'admin'.

When I login with my own username that works straight away, but when I user other names, most of which I haven't used for a while, then I get the following error in my browser:
Firefox can’t establish a connection to the server at localhost.
and in the location bar, the site part of the URL has changed to localhost (my laptop) instead of the name of the true hostname. Only when I use my username, the address of the host stays in the URL.

I need to be able to log in as admin, so I tried to change the site and then re-load the URL after the error message, but then I was re-directed to a page to change the admin password. I may need to hard-reset this, although I did give the correct password to start.

Does anyone know that this is related to a specific setting / link missing on the server?

Not sure if this is related but when I do login as myself, everything loads up except the "Recent Data Activity" pane. It shows the hourglass for a while and then produces this error dialog:
Experiment List Error
ERROR 504: Failed to load experiment list.

Could this be an external problem, like a DNS being out?

Many thanks for your help!

a.m....@gmail.com

unread,
Jan 28, 2022, 4:54:31 AM1/28/22
to xnat_discussion
I tried to solve this by re-downloading the xnat-docker compose scripts from version 1.7, to go back to the original XNAT as I downloaded it,  and then adding the settings that I've changed.

When I downloaded the version 1.7 final files (1.7.6.zip from the NrgXNAT repository) and brought up the dockers (after bringing down the current version), I got this error message:

...
Creating xnatdockercompose176_xnat-web_1 ...
Creating xnatdockercompose176_xnat-web_1 ... error

ERROR: for xnatdockercompose176_xnat-web_1  Cannot start service xnat-web: driver failed programming external connectivity on endpoint xnatdockercompose176_xnat-web_1 (36ca0bf359d238e7ccf81201dd71cf48ddcde4da2091b57e440d2661c73e37d5): Error starting userland proxy: listen tcp4 0.0.0.0:22: bind: address already in use

ERROR: for xnat-web  Cannot start service xnat-web: driver failed programming external connectivity on endpoint xnatdockercompose176_xnat-web_1 (36ca0bf359d238e7ccf81201dd71cf48ddcde4da2091b57e440d2661c73e37d5): Error starting userland proxy: listen tcp4 0.0.0.0:22: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Could this be the same problem that causes my current XNAT login problems as well?
Is there a logical fix for this? I got this error straight after uncompressing the ZIP file.

Thanks for your help!

a.m....@gmail.com

unread,
Jan 28, 2022, 5:33:21 AM1/28/22
to xnat_discussion
The only program now listening on :22 is sshd, but I can hardly stop that ... and did not need to before!

a.m....@gmail.com

unread,
Jan 28, 2022, 11:21:46 AM1/28/22
to xnat_discussion
Upon restarting the nginx docker seems to start without problems, the xnat-web (tomcat) docker waits for the database but then finalises. But the xnat_db-1 docker gives these errors during startup:

xnat-db_1     | ERROR:  relation "activemq_msgs" already exists
xnat-db_1     | STATEMENT:  CREATE TABLE ACTIVEMQ_MSGS(ID BIGINT NOT NULL, CONTAINER VARCHAR(250), MSGID_PROD VARCHAR(250), MSGID_SEQ BIGINT, EXPIRATION BIGINT, MSG BYTEA, PRIMARY KEY ( ID ) )
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  CREATE INDEX ACTIVEMQ_MSGS_MIDX ON ACTIVEMQ_MSGS (MSGID_PROD,MSGID_SEQ)
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  CREATE INDEX ACTIVEMQ_MSGS_CIDX ON ACTIVEMQ_MSGS (CONTAINER)
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  CREATE INDEX ACTIVEMQ_MSGS_EIDX ON ACTIVEMQ_MSGS (EXPIRATION)
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL, SUB_DEST VARCHAR(250), CLIENT_ID VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR VARCHAR(250), LAST_ACKED_ID BIGINT, PRIMARY KEY ( CONTAINER, CLIENT_ID, SUB_NAME))
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  CREATE TABLE ACTIVEMQ_LOCK( ID BIGINT NOT NULL, TIME BIGINT, BROKER_NAME VARCHAR(250), PRIMARY KEY (ID) )
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  INSERT INTO ACTIVEMQ_LOCK(ID) VALUES (1)
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  ALTER TABLE ACTIVEMQ_MSGS ADD PRIORITY BIGINT
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  CREATE INDEX ACTIVEMQ_MSGS_PIDX ON ACTIVEMQ_MSGS (PRIORITY)
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  ALTER TABLE ACTIVEMQ_MSGS ADD XID BYTEA
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  ALTER TABLE ACTIVEMQ_ACKS ADD PRIORITY BIGINT DEFAULT 5 NOT NULL
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  ALTER TABLE ACTIVEMQ_ACKS ADD XID BYTEA
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  ALTER TABLE ACTIVEMQ_ACKS DROP CONSTRAINT "activemq_acks_pkey"
xnat-db_1     | ERROR:  current transaction is aborted, commands ignored until end of transaction block
xnat-db_1     | STATEMENT:  ALTER TABLE ACTIVEMQ_ACKS ADD PRIMARY KEY (CONTAINER, CLIENT_ID, SUB_NAME, PRIORITY)

Does anyone know what this means/how serious this is, and whether this can be solved?
Many thanks!

Herrick, Rick

unread,
Jan 28, 2022, 1:27:41 PM1/28/22
to xnat_di...@googlegroups.com

You said you downloaded the docker-compose scripts from 1.7. What version of XNAT are you actually running?

 

This looks very much like a configuration issue, but it’s really hard to say. Check out this issue on xnat-docker-compose github and see if anything in there looks like what you’re seeing. One thing to look at is the tomcat logging output, most likely the localhost.date.log file. When something goes wrong early it happens in the application server context, not the application context, so gets logged to Tomcat and not XNAT logs (often XNAT’s logging isn’t even functional at that point).

 

-- 

Rick Herrick

XNAT Architect/Developer

Computational Imaging Laboratory

Washington University School of Medicine

 

 

From: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of a.m....@gmail.com <a.m....@gmail.com>
Date: Friday, January 28, 2022 at 10:21 AM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Re: most logins fail on xnat-docker-compose

* External Email - Caution *

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/xnat_discussion/dfe284f0-5bc7-492a-abbf-c84aaa9e0094n%40googlegroups.com.

 


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.

a.m....@gmail.com

unread,
Jan 31, 2022, 5:57:45 AM1/31/22
to xnat_discussion
Thanks for your answer, Rick. I looked at the github issue, and from your last message I understood that the SQL message is not an error. It did not look like the OP's problem was fixed?
Also, their problem is different than mine I think. I do get the startup page on port 80, but my problem is after the login. If it helps I can also make a github issue.

About your comments on versions and logs:

I set up the xnat-docker-compose ages ago, when the current WAR file was version 1.7.5.3, and I had already changed that to 1.7.5.6 in the yml file without problems.

Last December I did do a git pull which messed up the system(!), because the postgres version had changed  but after putting back the original directories it just came back up again. People have successfully downloaded thousands of files around Christmas.

I think the most likely cause is some security setting around the local 'cloud' that the XNAT host is in.

The log files that have been written last Friday show that one user was actually downloading, which makes me think that if you have an existing login / cookie / set of credentials -> sweet, you can keep using the system, the problem is with getting access with a new login at the start? Since I have restarted the XNAT, I cannot login any more either.

On Friday, there was no restlet.log file, on other days that file does exist and says something like
...
2022-01-17 20:58:31,881 [http-apr-8080-exec-6] ERROR org.nrg.xnat.restlet.resources.QueryOrganizerResource - Unknown alias "URI" processing query for root element: subjectAssessorData
2022-01-17 20:58:32,104 [http-apr-8080-exec-1] ERROR org.nrg.xnat.restlet.resources.QueryOrganizerResource - Unknown alias "URI" processing query for root element: imageScanData
...
It's always exec-<number from 1 to 10> followed by those 2 warnings. This may have to do with the failure to retrieve "recent data activity"?

The files from Friday are
axis.log.2022-01-24 (872B)
jms.log.2022-01-24 (3748B)
sql.log (8469B)
access.log.2022-01-24 (646KB)

axis.log has the line
2022-01-24 11:43:08,568 [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
4 times, in 2 pairs (two at one time point, two at another).

jms.log has the message:
2022-01-24 11:39:53,692 [ActiveMQ Connection Executor: vm://localhost#0] WARN  org.springframework.jms.connection.CachingConnectionFactory - Encountered a JMSException - resetting the underlying JMS Connection
javax.jms.JMSException: Broker has been stopped: org.apache.activemq.broker.BrokerService$5@6c626e5
        at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
        at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1949)
        at org.apache.activemq.ActiveMQConnection$3$1.run(ActiveMQConnection.java:1869)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.activemq.broker.BrokerStoppedException: Broker has been stopped: org.apache.activemq.broker.BrokerService$5@6c626e5
        at org.apache.activemq.broker.ErrorBroker.removeConsumer(ErrorBroker.java:155)
        at org.apache.activemq.broker.MutableBrokerFilter.removeConsumer(MutableBrokerFilter.java:123)
        at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
        at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:76)
        at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)
        at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:152)
        at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
        at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
        at org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:241)
        at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
        at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
        ... 3 more
twice -- exactly the same but different time points.

sql.log contains errors from the user who was successfully logged in at the time I caused the XNAT to go down.

access.log is massive, contains a lot of repetition, so here are only the unique types of message
first there is the user who can access (renamed to loggedinuser, site renamed to xnat_host.me)
...
2022-01-24 09:42:17,250 - loggedinuser 137.220.68.205 Authentication SUCCESS
2022-01-24 09:42:17,942 - loggedinuser 137.220.68.205 SCREEN: Index
2022-01-24 09:42:19,405 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&users=true&XNAT_XHR=x3hpp43lg-1643017339403
2022-01-24 09:42:19,406 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&XNAT_XHR=x7p150usx-1643017339401
2022-01-24 09:42:19,409 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects?format=json&favorite=true&XNAT_XHR=xyclf4wvs-1643017339404
2022-01-24 09:42:19,415 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/search/saved?format=json&XNAT_XHR=x9hb3px16-1643017339413
2022-01-24 09:42:19,440 - loggedinuser 137.220.68.205 GET http://xnat_host.me/xapi/siteConfig/buildInfo
2022-01-24 09:42:19,471 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects?accessible=true&XNAT_XHR=x2hwc5hqj-1643017339462&format=json
2022-01-24 09:42:19,477 - loggedinuser 137.220.68.205 SCREEN: DataTypeSearch
2022-01-24 09:42:19,601 - loggedinuser 137.220.68.205 GET http://xnat_host.me/xapi/siteConfig/buildInfo
2022-01-24 09:42:19,603 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/experiments?recent=true&XNAT_XHR=xlbqkkpzf-1643017339465&format=json
2022-01-24 09:42:21,493 - loggedinuser 137.220.68.205 SCREEN: XDATScreen_report_xnat_projectData xnat:projectData epadIMI_nii
2022-01-24 09:42:22,799 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&XNAT_XHR=xegwbvwj6-1643017342774
2022-01-24 09:42:22,801 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&users=true&XNAT_XHR=xqaaklisp-1643017342776
2022-01-24 09:42:22,829 - loggedinuser 137.220.68.205 GET http://xnat_host.me/xapi/siteConfig/buildInfo
2022-01-24 09:42:22,835 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/search/saved?format=json&XNAT_XHR=xoaub40in-1643017342782
2022-01-24 09:42:22,836 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects?format=json&favorite=true&XNAT_XHR=xyo5hoyf9-1643017342777
2022-01-24 09:42:23,112 - loggedinuser 137.220.68.205 GET http://xnat_host.me/xapi/siteConfig/buildInfo
2022-01-24 09:42:23,115 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects/epadIMI_nii/config/resource_config/script?contents=true&format=json&_=1643017342609
2022-01-24 09:42:23,127 - loggedinuser 172.19.0.4 GET http://xnat_host.me/REST/projects/epadIMI_nii/searches/@xnat:subjectData?XNAT_CSRF=7cf3c331-d74e-422c-9ad4-831fe8a1be4f&rnd=1643017343128
2022-01-24 09:42:23,254 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects/epadIMI_nii/automation/handlers?format=json&XNAT_CSRF=7cf3c331-d74e-422c-9ad4-831fe8a1be4f&_=1643017342610
2022-01-24 09:42:23,282 - loggedinuser 172.19.0.4 POST http://xnat_host.me/REST/search?XNAT_CSRF=7cf3c331-d74e-422c-9ad4-831fe8a1be4f&format=json&cache=true&refresh=true
2022-01-24 09:42:23,315 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/automation/handlers?format=json&XNAT_CSRF=7cf3c331-d74e-422c-9ad4-831fe8a1be4f&_=1643017342611
2022-01-24 09:42:24,302 - loggedinuser 172.19.0.4 GET http://xnat_host.me/REST/search/_epadIMI_nii_xnat_col_subjectData_loggedinuser_1643017343434?format=xList&offset=0&limit=200&XNAT_CSRF=7cf3c331-d74e-422c-9ad4-831fe8a1be4f&rnd=1643017344296
2022-01-24 09:42:24,303 - loggedinuser 137.220.68.205 GET http://xnat_host.me/xapi/schemas/datatypes/names/all
2022-01-24 09:42:33,408 - loggedinuser 172.19.0.4 GET http://xnat_host.me/REST/search/_epadIMI_nii_xnat_col_subjectData_loggedinuser_1643017343434?format=xList&offset=800&limit=200&XNAT_CSRF=7cf3c331-d74e-422c-9ad4-831fe8a1be4f&rnd=1643017353401
2022-01-24 09:42:34,269 - loggedinuser 172.19.0.4 GET http://xnat_host.me/REST/search/_epadIMI_nii_xnat_col_subjectData_loggedinuser_1643017343434?format=xList&offset=1000&limit=200&XNAT_CSRF=7cf3c331-d74e-422c-9ad4-831fe8a1be4f&rnd=1643017354264
2022-01-24 09:43:05,224 - loggedinuser 137.220.68.205 ACTION: QuickSearchAction
2022-01-24 09:43:05,359 - loggedinuser 137.220.68.205 SCREEN: QuickSearchMatch
2022-01-24 09:43:05,831 - loggedinuser 172.19.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&XNAT_XHR=xaytny3ww-1643017385811
...
Many repetitions of combinations of these types of line. 137.220.68.205 is the host from which the user logs in, 172.19.0.4 is the XNAT host.

Then admin, amsterdam and amwink (all me) log in:
...
2022-01-24 12:41:49,988 - admin 80.114.10.166 Authentication SUCCESS
2022-01-24 12:41:50,797 - admin 80.114.10.166 Authentication FAILED
2022-01-24 12:41:54,514 - amsterdam 80.114.10.166 Authentication SUCCESS
2022-01-24 12:42:05,514 - amwink 80.114.10.166 Authentication SUCCESS
2022-01-24 12:42:06,185 - amwink 80.114.10.166 SCREEN: Index
2022-01-24 12:42:08,350 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/browseable
2022-01-24 12:42:08,357 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/browseableCreateable
2022-01-24 12:42:08,365 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/searchableByPluralDesc
2022-01-24 12:42:08,368 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/searchable
2022-01-24 12:42:08,370 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/searchableByDesc
2022-01-24 12:42:08,371 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/createable
2022-01-24 12:42:08,827 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/siteConfig/buildInfo
2022-01-24 12:42:08,830 - amwink 172.21.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&users=true&XNAT_XHR=xit3l1hqs-1643028128355
2022-01-24 12:42:08,832 - amwink 172.21.0.4 GET http://xnat_host.me/data/projects?format=json&favorite=true&XNAT_XHR=xx2mlxj8m-1643028128356
2022-01-24 12:42:08,834 - amwink 172.21.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&XNAT_XHR=x8ni87350-1643028128354
2022-01-24 12:42:08,834 - amwink 172.21.0.4 GET http://xnat_host.me/data/projects?accessible=true&XNAT_XHR=x7ctden60-1643028128385&format=json
2022-01-24 12:42:08,860 - amwink 80.114.10.166 SCREEN: DataTypeSearch
2022-01-24 12:42:08,873 - amwink 172.21.0.4 GET http://xnat_host.me/data/experiments?recent=true&XNAT_XHR=xarrxax4d-1643028128394&format=json
2022-01-24 12:42:08,958 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/siteConfig/buildInfo
2022-01-24 12:42:08,969 - amwink 172.21.0.4 GET http://xnat_host.me/data/search/saved?format=json&XNAT_XHR=xaalk13r9-1643028128360
...
Of the other logins, one for amsterdam and one for admin as well as amwink, say SUCCESS (and I know the passwords were correct) but then I got to the 'localhost' error page from the top of the thread. Here 80.114.10.166 is the host from where I log in.It looks to me as if commands like 'buildinfo', which were sent to 172.19.0.4 in the successful login above, are now sent to my own computer -- the wrong localhost?

After this set of failed logins, and possibly a reboot already of the XNAT host, there are more messages from loggedinuser, successfully doing searches and downloading files, and more messages from amwink, which are more repeats of these 17 lines:
...
2022-01-24 12:42:05,514 - amwink 80.114.10.166 Authentication SUCCESS
2022-01-24 12:42:06,185 - amwink 80.114.10.166 SCREEN: Index
2022-01-24 12:42:08,350 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/browseable
2022-01-24 12:42:08,357 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/browseableCreateable
2022-01-24 12:42:08,365 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/searchableByPluralDesc
2022-01-24 12:42:08,368 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/searchable
2022-01-24 12:42:08,370 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/searchableByDesc
2022-01-24 12:42:08,371 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/access/displays/createable
2022-01-24 12:42:08,827 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/siteConfig/buildInfo
2022-01-24 12:42:08,830 - amwink 172.21.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&users=true&XNAT_XHR=xit3l1hqs-1643028128355
2022-01-24 12:42:08,832 - amwink 172.21.0.4 GET http://xnat_host.me/data/projects?format=json&favorite=true&XNAT_XHR=xx2mlxj8m-1643028128356
2022-01-24 12:42:08,834 - amwink 172.21.0.4 GET http://xnat_host.me/data/projects?format=json&accessible=true&XNAT_XHR=x8ni87350-1643028128354
2022-01-24 12:42:08,834 - amwink 172.21.0.4 GET http://xnat_host.me/data/projects?accessible=true&XNAT_XHR=x7ctden60-1643028128385&format=json
2022-01-24 12:42:08,860 - amwink 80.114.10.166 SCREEN: DataTypeSearch
2022-01-24 12:42:08,873 - amwink 172.21.0.4 GET http://xnat_host.me/data/experiments?recent=true&XNAT_XHR=xarrxax4d-1643028128394&format=json
2022-01-24 12:42:08,958 - amwink 80.114.10.166 GET http://xnat_host.me/xapi/siteConfig/buildInfo
2022-01-24 12:42:08,969 - amwink 172.21.0.4 GET http://xnat_host.me/data/search/saved?format=json&XNAT_XHR=xaalk13r9-1643028128360
...

Does this make any sense in terms of logs?
Many thanks for looking into it!

a.m....@gmail.com

unread,
Feb 2, 2022, 3:33:37 AM2/2/22
to xnat_discussion
I was able to login with X on the host that runs the dockers and start a browser session on localhost.

All user passwords that I tried (the ones I know) needed to be updated. It looks like (very careful here) I can login again as the users whose passwords were reset. So there seems to be a connection error between nginx and tomcat when the password is expired?

So (if I may) three new questions now remain:
    - is this something (the disconnection) that can be fixed by changing settings, or is it more serious?
    - is there a way, as admin on localhost, to blanket reset user passwords? this will help them: they cannot get in themselves.
    - is this also related to the failure to load "recent data activity"? (because that remains for everyone who can login again)

Many thanks!
Reply all
Reply to author
Forward
0 new messages