Support #12508
closed
- Assignee changed from _InfraScience Systems Engineer to Fabio Sinibaldi
- Status changed from New to Feedback
Sorry i should have remembered the link of gcube logs.. i had a look to the logs and i got an internal error from geonetwork.. Fabio can you look into this? maybe the db is corrupted, some bad csw bad transaction created this issue. The issue prevents to load the csw get capabilities.. maybe can you inspect the geonetwork db? Thanks in advance
It's really difficult to find out the reasons, but some bug reports led me to check language references in the database.
Here a possible hint :
Requests with unknown language (found "cze" and "fra" - correct value seems "fre").
select * from requests where lang not in (select id from languages)
I'm not expert in this part of GeoNetwork, so I'm not sure if this is the actual cause. Please, let us know what you think.
- Status changed from Feedback to In Progress
- Assignee changed from Fabio Sinibaldi to Emmanuel Blondel
- Priority changed from Immediate to Normal
I will investigate a bit more. Some null entry is causing this issue somewhere.. Do you have possibility to make a dump of the geonetwork backend db?
In order to better assess what's wrong I would need to access the remote DB. Can this be authorized through online PgAdmin on the e-infra? Thanks
Hello @sinibaldi sorry to come back so late on that, but this was very low priority on my agenda. Would it be possible to check on the geonetwork db the table languages
and see if some default language is properly set by doing smthg like:
SELECT * FROM languages WHERE isdefault = 'y';
If there is no result, to set 'eng' as default language like this:
UPDATE languages SET isdefault = 'n';
UPDATE languages SET isdefault = 'y' WHERE id = 'eng';`
And restart Geonetwork.
Thanks in advance
Emmanuel
Hi Emmanuel,
the Select statement returned the following row (column names in first line), so I guess this part of the configuration is already ok :
"id";"isdefault";"isinspire";"name"
"eng";"y";"y";"English"
Ok, at some point, I think that we need to clean the DB, and start with an empty catalogue, because at some point some publication test during the previous workshop corrupted the DB. @julien.barde@ird.fr I guess you can then regenerate easily your test metadata sheets, let me know if you see any objection For the test Tuna atlas metadata sheets, no needs to regenerate now IMHO.
- Status changed from In Progress to Closed
Solved with cleaning the DB
Also available in: Atom
PDF