Para uses PostgreSQL and data corrupted

[maor-paz-hs]

Hi,
I'm using managed RDS under AWS of a kind PostgreSQL.

Creating a database for Scoold so para can use it,
after restarting the pod of Para, this Error pops out:

2023-10-11 10:31:17 [INFO ] --- Para.initialize() [production] ---
2023-10-11 10:31:17 [INFO ] Loaded new DAO, Search and Cache implementations - SqlDAO, LuceneSearch and CaffeineCache.
2023-10-11 10:31:17 [INFO ] HikariPool-1 - Starting...
2023-10-11 10:31:18 [INFO ] HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@56ace400
2023-10-11 10:31:18 [INFO ] HikariPool-1 - Start completed.
2023-10-11 10:31:19 [WARN ] Server is unhealthy - the search index may be corrupted and may have to be rebuilt.

Then the configuration file of para-application.conf is not being created and scoold is unable to connect his backend.

Please advise.

[albogdano]

If you are using Docker or K8s you need to have a volume mounted for Para to store its data ./data. The search index is saved there and I guess that volume doesn't exist or is not writable so Para fails to create its search index files. The data in PostgreSQL should not be affected but Para won't function normally without a search index. You can try to fix the volume issue or use an external search service like OpenSearch, for example.