Updating to v6.4.0 and beyond (Current Ontology version: null)

Felipe

Good morning,

After updating Dédalo from the v6.3.1 it happens to me that when updating ontology I do not get confirmation or error message. I also observed that I am no longer detected by current ontology version

Any idea, please?

Thank you

Alex

Hi!

The update has changed in version >6.4.0, now you need to choose the server that provide the ontology and press the «Update Dédalo to the latest version» button.

If you don't see any error or confirmation message, maybe you have some error in the server log.

See the PHP error log and tell me.

Best

Felipe

Almost 4000 lines of php error log mostly warnings.

I saw this ERROR fragment inside de log (there is many WARNINGS too long to post here):

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
[20-Mar-2025 12:01:33 Europe/Madrid] ERROR [dd_error::captureError]: Array
(
[type] => 2
[message] => pg_query(): Query failed: ERROR: fila de índice requiere 10200 bytes, tamaño máximo es 8191
file => /home/www/vhosts/wondercoins.uca.es/httpdocs/dedalo/core/db/class.RecordDataBoundObject.php
line => 442
)

[20-Mar-2025 12:01:33 Europe/Madrid] DEBUG_LOG [ERROR]
RecordDataBoundObject::Save Error: DDBB query error. INSERT record. Data is not saved
ERROR: fila de índice requiere 10200 bytes, tamaño máximo es 8191
INSERT INTO "jer_dd" ("terminoID", "modelo", "model", "esmodelo", "esdescriptor", "visible", "tld", "traducible", "relaciones", "properties", "term") VALUES ............ (...much more here Alex.....)
[seq]: dd_manager:manage_request > dd_area_maintenance_api:class_request > area_maintenance:update_ontology > ontology:set_records_in_jer_dd > ontology:insert_jer_dd_record > RecordObj_dd:insert > RecordDataBoundObject:Save

[20-Mar-2025 12:01:33 Europe/Madrid] DEBUG_LOG [ERROR]
dd_area_maintenance_api::class_request Exception caught [class_request] : Error Processing Save Insert Request (1). error: ERROR: fila de índice requiere 10200 bytes, tamaño máximo es 8191
[seq]: dd_manager:manage_request > dd_area_maintenance_api:class_request

[20-Mar-2025 12:01:33 Europe/Madrid] ERROR [dd_error::captureError]: Array
(
[type] => 1024
[message] => Error Processing Save Insert Request (1). error: ERROR: fila de índice requiere 10200 bytes, tamaño máximo es 8191
file => /home/www/vhosts/wondercoins.uca.es/httpdocs/dedalo/core/api/v1/common/class.dd_area_maintenance_api.php
line => 97
)
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

8MB maxi size, I'dont know what index row referes

I'll send you the complet log file by email

Thank you very much

PaCo

Hello Felipe

it seems that you have a problem with the indexes or columns of the jer_dd table.
Check that the jer_dd columns are like this (you can export the table structure to verify it).

CREATE SEQUENCE jer_dd_id_seq INCREMENT 1 MINVALUE 0 MAXVALUE 9223372036854775807 CACHE 1;

CREATE TABLE "public"."jer_dd" (
    "id" integer DEFAULT nextval('jer_dd_id_seq') NOT NULL,
    "terminoID" character varying(32),
    "parent" character varying(32),
    "modelo" character varying(8),
    "esmodelo" sino,
    "esdescriptor" sino,
    "visible" sino,
    "norden" numeric(4,0),
    "tld" character varying(32),
    "traducible" sino,
    "relaciones" text,
    "propiedades" text,
    "properties" jsonb,
    "term" jsonb,
    "model" text,
    CONSTRAINT "jer_dd_id" PRIMARY KEY ("id")
) WITH (oids = false);

COMMENT ON TABLE "public"."jer_dd" IS 'Model, a typology of the tipo';

CREATE UNIQUE INDEX "terminoID_unique" ON public.jer_dd USING btree ("terminoID");

CREATE INDEX jer_dd_esdescriptor ON public.jer_dd USING btree (esdescriptor);

CREATE INDEX jer_dd_esmodelo ON public.jer_dd USING btree (esmodelo);

CREATE INDEX jer_dd_modelo ON public.jer_dd USING btree (modelo);

CREATE INDEX jer_dd_norden ON public.jer_dd USING btree (norden);

CREATE INDEX jer_dd_parent ON public.jer_dd USING btree (parent);

CREATE INDEX jer_dd_parent_esdescriptor_norden ON public.jer_dd USING btree (parent, esdescriptor, norden);

CREATE INDEX jer_dd_relaciones ON public.jer_dd USING btree (relaciones);

CREATE INDEX jer_dd_traducible ON public.jer_dd USING btree (traducible);

CREATE INDEX jer_dd_usableindex ON public.jer_dd USING btree (tld);

CREATE INDEX jer_dd_visible ON public.jer_dd USING btree (visible);

I hope it helps you to find out where the problem is.

Best
PaCo

Felipe

Hello Paco,

I get some differences:
Two DROPS at the beginning
The way and place that terminoID_unique is restricted
We have more index created than you posted

This is the export of our jer_dd table:

`-- Adminer 4.8.1 PostgreSQL 17.0 (Ubuntu 17.0-1.pgdg22.04+1) dump

DROP TABLE IF EXISTS "jer_dd";
DROP SEQUENCE IF EXISTS jer_dd_id_seq;
CREATE SEQUENCE jer_dd_id_seq INCREMENT 1 MINVALUE 0 MAXVALUE 9223372036854775807 CACHE 1;

CREATE TABLE "public"."jer_dd" (
"id" integer DEFAULT nextval('jer_dd_id_seq') NOT NULL,
"terminoID" character varying(32),
"parent" character varying(32),
"modelo" character varying(8),
"esmodelo" sino,
"esdescriptor" sino,
"visible" sino,
"norden" numeric(4,0),
"tld" character varying(32),
"traducible" sino,
"relaciones" text,
"propiedades" text,
"properties" jsonb,
"term" jsonb,
"model" text,
CONSTRAINT "jer_dd_id" PRIMARY KEY ("id"),
CONSTRAINT "terminoID_unique" UNIQUE ("terminoID")
) WITH (oids = false);

CREATE INDEX "jer_dd_esdescriptor" ON "public"."jer_dd" USING btree ("esdescriptor");

CREATE INDEX "jer_dd_esmodelo" ON "public"."jer_dd" USING btree ("esmodelo");

CREATE INDEX "jer_dd_modelo" ON "public"."jer_dd" USING btree ("modelo");

CREATE INDEX "jer_dd_norden" ON "public"."jer_dd" USING btree ("norden");

CREATE INDEX "jer_dd_parent" ON "public"."jer_dd" USING btree ("parent");

CREATE INDEX "jer_dd_parent_esdescriptor" ON "public"."jer_dd" USING btree ("parent", "esdescriptor");

CREATE INDEX "jer_dd_parent_esdescriptor_esmodelo" ON "public"."jer_dd" USING btree ("parent", "esdescriptor", "esmodelo");

CREATE INDEX "jer_dd_parent_esdescriptor_norden" ON "public"."jer_dd" USING btree ("parent", "esdescriptor", "norden");

CREATE INDEX "jer_dd_properties" ON "public"."jer_dd" USING btree ("properties");

CREATE INDEX "jer_dd_propiedades" ON "public"."jer_dd" USING btree ("propiedades");

CREATE INDEX "jer_dd_relaciones" ON "public"."jer_dd" USING btree ("relaciones");

CREATE INDEX "jer_dd_term" ON "public"."jer_dd" USING btree ("term");

CREATE INDEX "jer_dd_terminoID_norden" ON "public"."jer_dd" USING btree ("terminoID", "norden");

CREATE INDEX "jer_dd_terminoid" ON "public"."jer_dd" USING btree ("terminoID");

CREATE INDEX "jer_dd_tld" ON "public"."jer_dd" USING btree ("tld");

CREATE INDEX "jer_dd_traducible" ON "public"."jer_dd" USING btree ("traducible");

CREATE INDEX "jer_dd_usableindex" ON "public"."jer_dd" USING btree ("tld");

CREATE INDEX "jer_dd_visible" ON "public"."jer_dd" USING btree ("visible");

COMMENT ON TABLE "public"."jer_dd" IS 'Model, a typology of the tipo';

INSERT INTO "jer_dd" ("id", "terminoID", "parent", "modelo", "esmodelo", "esdescriptor", "visible", "norden", "tld", "traducible", "relaciones", "propiedades", "properties", "term", "model") VALUES
......
......
......
`

Thank you

PaCo

Hello @Felipe

try to remove index jer_dd_properties

DROP INDEX jer_dd_properties;

Could be corrupt.

Good luck

Felipe

Hi @PaCo

Thanks for your indications.
I have made advances in the update of our Dédalo installation but now I have a new issue

This is our login info:

I made a clean update of code to v6.4.5 and now the ontology update is ok (but version only says "Dédalo")

Now I'm trying to update data from v6.42 --->v.6.4.3 but I have a new error when it run_scripts,

The php log only shows debug lines (I put the last two here):

[22-Mar-2025 07:08:22 Europe/Madrid] process loop: is_running: true - pid: 330161 - pfile: process-1_2025-03-22_07-07-01_1717709314570812
[22-Mar-2025 07:08:22 Europe/Madrid] DEBUG_LOG [DEBUG] dd_utils_api::get_process_status {"pid":330161,"pfile":"process-1_2025-03-22_07-07-01_1717709314570812","is_running":true,"data":{"memory":"86 MB","counter":253,"msg":"Updating run_scripts 1 of 1","data":{"info":"Update data of time_machine of component_dataframe, add section_tipo_key to its data","script_class":"transform_data","script_method":"update_dataframe_tm_to_v6_4_3","script_vars":"[]"},"table":"matrix","section_tipo":"numisdata5","section_n_rows":253,"n_sections":517,"section_counter":0,"n_components":2},"time":"2025-03-22 07:08:22","total_time":"1.34 min","update_rate":1000,"errors":[]}

[22-Mar-2025 07:08:23 Europe/Madrid] process loop: is_running: false - pid: 330161 - pfile: process-1_2025-03-22_07-07-01_1717709314570812
[22-Mar-2025 07:08:23 Europe/Madrid] DEBUG_LOG [DEBUG] dd_utils_api::get_process_status {"pid":330161,"pfile":"process-1_2025-03-22_07-07-01_1717709314570812","is_running":false,"data":{"msg":"transform_data::get_section_tipo_key_from_main_component(): Return value must be of type string, null returned","errors":["captureException"]},"time":"2025-03-22 07:08:23","total_time":"1.357 min","update_rate":1000,"errors":[]}

I have also been looking at the "pfile: Process_-1_2025-03-22_07-07-01_1717709314570812" in the sessions folder
and its last line before stopping is this:

{"memory":"14 MB","counter":86,"msg":"Procesando: components_update | component_dataframe | section: Entidad (rsc106) | section_id: 91","data":"component_dataframe","table":"matrix","section_tipo":"rsc106","section_n_rows":120,"n_sections":517,"section_counter":0,"n_components":1}

The last thing I want is to bother you on your trip so if you want we leave it for when you return.
Thank you!