Dedalo / jer_dd update

andreslopez

Context:
While attempting to update the ontology via Dedalo, using the GUI appears to process correctly, but the ontology version does not increment.

These warnings appear repeatedly in the PHP/Apache logs, indicating Dedalo keeps attempting to load a non-existent terminoID.
[DEBUG] ontology::parse_section_record_to_jer_dd_record jer_dd_record exec_time_unit: 3.85 ms
[DEBUG] ontology::insert_jer_dd_record Total time insert_jer_dd_record: 5.597 ms
[WARNING] RecordDataBoundObject::Load 'WARNING: No result found on Load arRow
last_error:
strQuery: SELECT ... FROM "jer_dd" WHERE "terminoID"='localontology0'
This query returns 0
The jer_dd table contains a record with terminoID='ontology0', but no record with terminoID='localontology0' exists.

Alex

That is not an error.

The warning indicates that your main localontology0 is not present as an active node in jer_dd. It appears to be a configuration that is not being utilized.

If you don't use local ontologies with localontology0, you can remove all records that are referenced with localontology0 set as section_tipo in the matrix_ontology table. For example:

1.- Check if you have records:

SELECT * FROM "matrix_ontology" WHERE "section_tipo"='localontology0';

2.-Then, proceed to delete.

DELETE FROM "matrix_ontology" WHERE "section_tipo"='localontology0';

andreslopez using the GUI appears to process correctly, but the ontology version does not increment.

Can you indicate the Dédalo version and the ontology version?

Best.

PaCo

Hy @andreslopez

It could be useful to known the Dédalo version and the ontology version as Alex say.

Anyway, it appears a pgpass issue.
Doble check your .pgpass file configuration and permissions pgpass.

You can try to run manually the 'terminal DB command' shown in the log using the same PHP user that is running Dédalo.

Good luck with this.

Best.

andreslopez

the log is too large and i get this errors:

AH01071: Got error '[seq]: component_common:get_time_machine_data_to_save >
component_common:get_dataframe_ddo >
common:get_ar_request_config >
RecordObj_dd:check_tipo_is_valid >
RecordObj_dd:get_modelo_name_by_tipo >
RecordObj_dd:get_modelo_name >
RecordDataBoundObject:Load'

AH01071: Got error 'DEBUG_LOG [WARNING] common::get_ar_request_config
WARNING. Ignored non valid section_tipo.
Maybe the TLD is not installed.
current_section_tipo: cg0

AH01071: Got error '[seq]: area_maintenance:update_ontology >
ontology:add_main_section >
ontology:create_jer_dd_ontology_section_node >
ontology:create_parent_grouper >
component_relation_common:Save >
section:save_component_dato'

AH01071: Got error 'DEBUG_LOG [WARNING] RecordDataBoundObject::Load
WARNING: No result found on Load arRow
strQuery: SELECT "terminoID","parent","modelo","model","esmodelo","esdescriptor",
"visible","norden","tld","traducible","relaciones","propiedades","properties","term"
FROM "jer_dd" WHERE "terminoID"='fj0'

AH01071: Got error 'DEBUG_LOG [WARNING] common::get_ar_request_config
WARNING. Ignored non valid section_tipo.
Maybe the TLD is not installed.
current_section_tipo: md0

AH01071: Got error 'DEBUG_LOG [WARNING] common::get_ar_request_config
WARNING. Ignored non valid section_tipo.
Maybe the TLD is not installed.
current_section_tipo: so0

AH01071: Got error 'DEBUG_LOG [WARNING] common::get_ar_request_config
WARNING. Ignored non valid section_tipo.
Maybe the TLD is not installed.
current_section_tipo: tr0

AH01071: Got error 'DEBUG_LOG [WARNING] backup::import_from_copy_file
Executing terminal DB command
/usr/lib/postgresql/18/bin/psql
-d DB_REDACTED
-h X.X.X.X
-p 5432
-U USER_REDACTED
--echo-errors
-c DELETE FROM "matrix_ontology" WHERE section_tipo IS NULL'

AH01071: Got error 'DEBUG_LOG [DEBUG]
ontology::parse_section_record_to_jer_dd_record
Record without order_data'

andreslopez

Thank you for your feedback.

Please note that the pgpass configuration seems to be working correctly because I can execute all other database operations from the maintenance menu without any issues.

As requested, I am attaching the command executed manually using the same PHP-FPM user:

Our current Dédalo version is 6.7.4, and the ontology version is also 6.7.4.

PaCo

Dédalo regular database queries do not use pgpass file, it's only used for backup and maintenance operations (dump and restore actions).

Can you try to execute a direct backup command like this using the PHP user ?

/mypath/bin/pg_dump -h /tmp -U myphpuser -F c -b -v dedalo6_myentity > "/mypath/backups/db/2025-12-16_093310.dedalo6_myentity.postgresql_-1_forced_dbv6-8-3.custom.backup"

Change your paths, names and host ('-h localhost' probably)
Execute the command as PHP specific user like
sudo -u username command

You should see something like 'pg_dump: executing ...'

Let me know if works.

Best

andreslopez

Hello PaCo,

Using this command:

sudo -u phpuser pg_dump -h 192.168.XX.XX -U postgres -F c -b -v dedalo_v6 \

/tmp/2025-12-16_backup.custom

I can perform the dump successfully.
The .pgpass file for phpuser contains the credentials for the PostgreSQL user.

andreslopez

I am currently experiencing issues updating.. Could you please advise on the next steps or provide any troubleshooting guidance?

Regards

Alex

andreslopez provide any troubleshooting guidance

This is a great idea!!!! You can create a markdown document to be included in the documentation, maybe here and provide the issues and solutions that you found. It will help the community.

Thanks for helping Dédalo to improve!!!

And, for your question; the log that you were sent doesn't show any problem, the only thing that is shown is a possible .pgpass issue, but as you try and it works... the next steps could be a screenshot of the error and the php_log/apache_log/posgreSQL_log and maybe will be useful if you can provide:

OS
Server info, Processors / Memory / HD
PHP version and configuration (memory assigned, etc)
Apache version
PostgreSQL version and configuration (memory assigned, etc)
Dédalo version
Dédalo ontology version
How you have configured the Vhost and the PHP pool
A screenshot about the error in Dédalo
A browser console error

Any other relevant information about your configuration, such as if the server is behind a proxy, VPN, firewall, or WAF... that can affect the connection with ontology master server.

Best

PaCo

OK, the available information is mainly in the documentation and in this forum.
In any case,
Is the problem general? Is it with a specific TLD? Does selecting only one TLD fail? Have you tried it on a different installation?

Best