Missing register in landing page of registry

[arantzaetxebarria]

From: MartinTuchyna original issue

Dear Re3gistry Team,

any idea, why we are not able to see this testing Register https://er.hany.sk/extensions also on the landing page of the Re3gistry? https://er.hany.sk/registry

Thanks in advance,

best regards, Martin

[arantzaetxebarria]

From: MichalMed

To specify issue in more detail:

• register is seen in every language but the one in which it was created (English) and to which was translated label (Slovak).

[arantzaetxebarria]

From: emanuelaepure10

Hi @MartinTuchyna & @MichalMed ,

Can I ask you how you have create the register? From the management interface?

Do you see it in the management interface as a part of the registry?

if so, probably you need to remove the cache folder from you file system and try to reload the page.

Soon we have released a new version of the software which is updating the cache once 'something' has been change on the management interface.

Please let us know if removing the cache or after a update the problem has need solved

Thank you in advanced

[oscar9]

Dear,

It looks like the links provided are working properly. If you don’t receive any more information, we will close the issue and it will be marked as fixed. Thanks

Óscar

[MartinTuchyna]

Dear Oscar,

seems we are facing the same issue also on Docker instance of the registry, where for instance, we have tried to create following two registers:

Everything looked ok, but there is nothing available via landing page on the frontend

Thanks, Martin

[MartinTuchyna]

PS: What is also interesting, that in public frontend landig page I can not change current default language version from Slovak to English:

https://registry.stage.geocloud.sk/

When trying incognito / unlogeed access, situation is oposit. I can not change English to Slovak:

[oscar9]

Hi @MartinTuchyna ,

At first glance, the language selector looks like a non-Docker related bug, would you mind opening a new issue with it? Also, have you tried the new version 2.4.0-rc1? There were changes in the language section and in the cookies that may affect these errors that you are commenting on.

We will analyze this issue again in case it is not fixed as you commented.

Thanks in advance.

[MartinTuchyna]

Hi @oscar9 ,

yes, we have updated the version to the 2.4.0-rc1 (@PetoP), although on the landing page still indicates 2.3.0

and have to admit that this version comes with even more bugs, like for example, when trying to create first register initial page is splitted to two windows, whilst second does not allows any further actrion - see snap.

SK page for creating first register is missing completely:

So instead the progress, we are back on beginning.

[oscar9]

Hi @MartinTuchyna I'm going to label this ticket as bug. We will double-check with the development team and see what is happening. We will inform you of any discovery. Thanks

[jescriu]

Dear @MartinTuchyna, Really sorry to hear about these issues. JRC will push for the prioritisation of their resolution by the contractor, who recently delivered both, Re3gistry 2.4.0-rc1 and 2.4.0. By the way, I assume you are still using the ISO 19135 workflow for managing your registry, and not the recent simplified approach which was added in the last Re3gistry version - Could you please confirm?

[oscar9]

Hi @MartinTuchyna ,

1. The frontend works as a stand-alone application and the version of the registry that appears is manually modified. We are going to update that version in the repository because it was not modified during the last release, thanks for reporting that. This modification only involves modifying the value by hand in the different htmls of the webapp application . I take this opportunity to explain that by this I mean that this version is not obtained by calling the API with the re3gistry that it is using, the same frontend could run on different versions of the Registry at different times. https://github.com/ec-jrc/re3gistry/tree/master/sources/Re3gistry2ServiceWebapp/public_html

2. It looks like there is a problem in the Apache httpd configuration. I've accessed the address in your image (https://registry.stage.geocloud.sk/) and looked at the calls it makes. I don't see it making any API calls or similar.

For example, this is from a working example:

Also, a possible test for this is, you could create a register or item and try to access that specific item (example similar to. https://registry.stage.geocloud.sk/myregister/item01 ) and also check if is working or if is just the main page that is failing.

3.We have created from scratch a new instance with master language EN, and languages EN,SK and vice-versa, master SK, languages EN,SK, but in any case we can replicate that error. Could you send us the tomcat logs when this error is ocurring?

We are testing all this over the final version 2.4.0, there were not major changes between this version and the rc1.

Let us know any feedback from this

Best regards, Óscar

[MartinTuchyna]

Dear @jescriu

By the way, I assume you are still using the ISO 19135 workflow for managing your registry, and not the recent simplified approach which was added in the last Re3gistry version - Could you please confirm?

Not sure, what is the difference between 2 approaches. Normaly, first step is to create the register under the Content tab. Example of the new register for INSPIRE Mappings:

After filling the content and summary and pressing "Add register" next page is offered:

but there is none option to continue, as you can see on the snap.

If I remember, above elements used to be on the first page, therefore this behaviour is quite strange.

@oscar9

As you can see, I am not able to create any item now. Anyway I will try to find out, if I can get the tomcat log.

Best regards, Martin

[PetoP]

Hi all,

I have updated all system components based on current state in this repo. I have also modified our docker-compose file to reflect all changes made in repository (our only change now are changed ports as we already have few of them occupied).

2. There was problem with permissions on the server. After fixing it more resources are loaded (now only logos pngs and one css files are missing). Overall state seem unchanged however.

3. @oscar9, following is tomcat log as you requested. No user actions are captured in it, if you are missing some, please let me know what should I test to do in order to get it into log file.

Listening for transport dt_socket at address: 8000
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version name:   Apache Tomcat/7.0.109
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built:          Apr 22 2021 18:43:38 UTC
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version number: 7.0.109.0
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name:               Linux
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version:            3.10.0-1127.19.1.el7.x86_64
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture:          amd64
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home:             /opt/java/openjdk/jre
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version:           1.8.0_292-b10
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor:            AdoptOpenJDK
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE:         /usr/local/tomcat
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME:         /usr/local/tomcat
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.util.logging.config.file=/usr/local/tomcat/conf/logging.properties
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dignore.endorsed.dirs=
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.base=/usr/local/tomcat
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=/usr/local/tomcat
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.io.tmpdir=/usr/local/tomcat/temp
Nov 11, 2022 5:50:40 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: Loaded Apache Tomcat Native library [1.2.28] using APR version [1.6.5].
Nov 11, 2022 5:50:40 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Nov 11, 2022 5:50:40 PM org.apache.catalina.core.AprLifecycleListener initializeSSL
INFO: OpenSSL successfully initialized [OpenSSL 1.1.1f  31 Mar 2020]
Nov 11, 2022 5:50:40 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-apr-8080"]
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 816 ms
Nov 11, 2022 5:50:40 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Catalina]
Nov 11, 2022 5:50:40 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.109
Nov 11, 2022 5:50:40 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory [/usr/local/tomcat/webapps/re3gistry2]
Nov 11, 2022 5:50:43 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
[localhost-startStop-1] INFO org.apache.shiro.web.env.EnvironmentLoader - Starting Shiro environment initialization.
[localhost-startStop-1] INFO org.apache.shiro.config.IniSecurityManagerFactory - Realms have been explicitly set on the SecurityManager instance - auto-setting of realms will not occur.
[localhost-startStop-1] INFO org.apache.shiro.web.env.EnvironmentLoader - Shiro environment initialized in 322 ms.
### Initializing the system ...
File name properties path: configurations_files/configuration.properties
78 properties loaded from configurations_files/configuration.properties
### Setting up the logger
### The system is now initialized. Path for the helper files: /usr/local/tomcat/webapps/re3gistry2/WEB-INF
Nov 11, 2022 5:50:44 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory [/usr/local/tomcat/webapps/re3gistry2] has finished in [3,731] ms
Nov 11, 2022 5:50:44 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory [/usr/local/tomcat/webapps/re3gistry2restapi]
Nov 11, 2022 5:50:45 PM org.apache.catalina.startup.TldConfig execute
INFO: 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.
### Initializing the system ...
File name properties path: configurations_files/configuration.properties
6 properties loaded from configurations_files/configuration.properties
### The system is now initialized. Path for the helper files: /usr/local/tomcat/webapps/re3gistry2restapi/WEB-INF/classes/configurations_files
[EL Info]: 2022-11-11 17:50:47.49--ServerSession(2005687168)--EclipseLink, version: Eclipse Persistence Services - 2.7.5.v20191016-ea124dd158
[EL Info]: connection: 2022-11-11 17:50:48.059--ServerSession(2005687168)--/file:/usr/local/tomcat/webapps/re3gistry2restapi/WEB-INF/classes/_Re3gistry2 login successful
Nov 11, 2022 5:50:48 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory [/usr/local/tomcat/webapps/re3gistry2restapi] has finished in [3,833] ms
Nov 11, 2022 5:50:48 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-apr-8080"]
Nov 11, 2022 5:50:48 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 7699 ms

Best regards,

Peter

[oruscalleda]

Hi all,

A solution to this issue has been included in the pre release version published today. Please update your instance of the software an let us know if the error still happens.

Best regards,

Oriol

[MartinTuchyna]

Dear Oriol,

we have updated to the 2.4.1 version (although in HTML source code is still written 2.3.0).

After login to the backend, when trying to create the first register - these are the only options available:

So we are not able to even start to create Register.

On the default frontend, we are not able to see even Example codelist preprepared in backend: https://registry.stage.geocloud.sk/examplecodelist

[oruscalleda]

Hi @MartinTuchyna,

Sorry to hear that, I'll get into it and let you know when I discover something.

I can see from your print screen you seem to have something wrong on your configuration, as you can see the address for your registry has "http://host.docker.internal/registry" as its URI, but it should be something like "https://registry.stage.geocloud.sk/registry"

A few questions to try and replicate your problem:

• How have you deployed your instance, Docker or Tomcat?
• Have you done a new installation or just deployed the new version?

Thanks in advance

[MartinTuchyna]

Hi @oruscalleda

regarding your questions:

How have you deployed your instance, Docker or Tomcat? - Docker Have you done a new installation or just deployed the new version? - New instalation

After some modifications, we were able to make initial registers available on the landing page:

https://registry.stage.geocloud.sk/registry

Meamwhile we have encountered another issue #259, but lets close this topic.