I cloned and built images and ran the containers.
Here is the output from $docker ps —
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
24cece1ae576 openmrs/openmrs-reference-application-3-gateway:qa “/docker-entrypoint.…” 53 seconds ago Up 40 seconds 0.0.0.0:80->80/tcp openmrs-distro-referenceapplication_gateway_1
4911e6dfd119 openmrs/openmrs-reference-application-3-frontend:qa “/docker-entrypoint.…” About a minute ago Up 53 seconds (healthy) 80/tcp openmrs-distro-referenceapplication_frontend_1
05b765c305c5 openmrs/openmrs-reference-application-3-backend:qa “/usr/bin/tini – /o…” About a minute ago Up 59 seconds (health: starting) 8080/tcp openmrs-distro-referenceapplication_backend_1
2a7609670ad1 mariadb:10.8.2 “docker-entrypoint.s…” About a minute ago Up About a minute (healthy) 3306/tcp openmrs-distro-referenceapplication_db_1
All the containers are running.
When I try using these links below -
New OpenMRS UI is accessible at http://localhost/openmrs/spa
OpenMRS Legacy UI is accessible at http://localhost/openmrs
I get 404 errors.
We do not need :80 as it is the default http port.
I went ahead and tried that too - still same 404 error displayed in the browser.
I did rebuild and restarted - and still the same 404 error displayed in the browser.
In the terminal after running $docker-compose up - I see the attempt from the ‘frontend’
frontend_1 | 127.0.0.1 - - [11/Oct/2023:17:45:27 +0000] “GET / HTTP/1.1” 301 169 “-” “curl/8.3.0”
frontend_1 | 127.0.0.1 - - [11/Oct/2023:17:45:57 +0000] “GET / HTTP/1.1” 301 169 “-” “curl/8.3.0”
And in the ‘backend’ I see this exception thrown - this is a periodic print -
backend_1 | Caused by: java.sql.SQLSyntaxErrorException: Unknown column ‘queueentry5_.queue_coming_from’ in ‘field list’
backend_1 | at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
backend_1 | at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
backend_1 | at com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:916)
backend_1 | at com.mysql.cj.jdbc.ClientPreparedStatement.executeQuery(ClientPreparedStatement.java:972)
backend_1 | at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:1471)
backend_1 | at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:57)
backend_1 | … 62 more
Not sure what is going on. There is no exception in the terminal - when I use this URL in a Chrome browser tab.
http://localhost/openmrs/spa or http://localhost:80/openmrs/spa
Appreciate the response.
What happens when you add a
/ at the end of
spa. Something like this?
Same output - 404 page not found.
@ravimadhu have you tried clearing browser cache?
Thanks for the suggestion, cleared browser cache.
Still getting the same error.
Can you paste the full server side log at pastebin.com?
Here is the pastebin link - OpenMRS docker compose logs - Pastebin.com
Thanks for reviewing.
The error that you are getting on the server
Unknown column 'queueentry5_.queue_coming_from' in 'field list' should have been fixed with these changes: O3-2382 Add column to denote patient previous queue (rename column) by CynthiaKamau · Pull Request #39 · openmrs/openmrs-module-queue · GitHub
Can you try pulling the images again?
Pulled the images again and ran it.
Still same error.
Here are the logs - OpenMRS docker compose logs 2 - Pastebin.com
I have just cloned, run
docker compose build and then
docker compose up. Though i also get the same server side errors of
queueentry5_.queue_coming_from' in 'field list, I am still able to go the browser and type
http://localhost/openmrs/spa which takes me to the O3 log in screen where i successfully log in, choose a location, and go to the home page. Can you try to access
http://localhost/openmrs/spa while using a different browser?
I tried Chrome, Brave and Firefox - same 404 error. With this URL - http://localhost/openmrs/spa.
Uploaded a screenshot from Chrome.
WIth those other browsers, can you share a screenshot with a
/ and the end of
To be precise:
We ran the same on another server on the cloud and we had no issues. Must have been something with the ubuntu laptop we were using.
It took around 15 mins before the UI came up. Must have been a backend loading of initial data…
We are able to access the URLS …/spa and / - general Administration and Concepts etc.
Thanks for the support. I will get back when we figure out the issue with our ubuntu laptops …